Api command channel_up gives socket hangup error

Channels Android TV
#1

I've only just tried using channel_up and channel_down as api commands and there seems to be a bug.

The commands do work and the channel changes as expected but I get a ""RequestError: socket hang up" error from the http request node that I call it from in Node Red. Then ECCONRESET appears below the request node.

I'm using exactly the same command format in node red for many other api calls which work fine without the error it just seems to be channel_up and channel_down that cause the issue.

#2

Does curl work?

#3

Not sure about curl, don't know how I would try that to be honest.

This is the response in Node Red to a toggle_pause command that works fine

_msgid: "b310b43033b45fb3"

url: "http://192.168.1.220:57000/api/toggle_pause"

statusCode: 200

headers: object

responseUrl: "http://192.168.1.220:57000/api/toggle_pause"

payload: object

status: "playing"

now_playing: object

channel: object

redirectList: array[0]

retry: 0

And this is the response from the channel_up command with everything else the same.

09/07/2024, 21:43:58[node: POST](http://192.168.1.4:1880/#)msg : error

"RequestError: socket hang up"

09/07/2024, 21:43:58[node: debug 403](http://192.168.1.4:1880/#)msg : Object

object

_msgid: "ef573efc02be7a5d"

url: "http://192.168.1.220:57000/api/channel_up"

payload: "RequestError: socket hang up : http://192.168.1.220:57000/api/channel_up"

statusCode: "ECONNRESET"
#4

We don’t know anything about NodeRed. For all we know this is an issue with just NodeRed.

It would be helpful if you tried the request with a more standard http lib like curl, which is simpler and with less overhead baggage like a whole app.

#5

I've never used curl in terms of api calls so don't know how to test it or from where (browser, terminal window?) Tell me what to type where and I'll happily do it. I only have Linux machines though.

But, where I'm calling the api from seems a red herring to me.

I can use any of the other Channels api calls from node red, and do so regularly, day in day out. They all work fine, without any errors.

But now using "channel_up" (or down) for the first time, with everything else identical, it gives an error. It surely has to be an error in the api doesn't it?

It looks like the command executed correctly but it doesn't give the status response that all the other commands do.

#6

How to use curl is heavily documented on the internet. It should be easy to find how to submit a POST http request.

#7

curl -X POST http://192.168.1.3:57000/api/channel_up
curl: (52) Empty reply from server

curl -X POST http://192.168.1.3:57000/api/toggle_pause
{"status":"paused","now_playing":{"title":"Live: Wimbledon 2024","summary":"Live coverage of the third Grand Slam of the season continues, from at the All England Club.","image_url":"http://192.168.1.8:8089/tmsimg/assets/p27306879_b_h9_ad.jpg?w=720&h=540","episode_title":"Day 10"},"channel":{"number":"2","name":"BBC Two HD","image_url":"http://192.168.1.4:1880/Logo/BBC2"}

#8

Thanks, we'll look into it.