Occasionally, I have trouble recording a channel using the http interface and I want to find out why. I always get the 503 error. Is that error message the same whether the error is low signal strength, unavailable tuner or ???
Is there any way to differentiate?
Is there a way to check the signal strength via http?
drm
(503) Server Unavailable
Re: (503) Server Unavailable
If the request cannot be completed at this time (for example all tuners are in use) the tuner will return “503 Service Unavailable”.
If the program cannot be not found in the stream within 5 seconds or the program cannot be authorized within 5 seconds the tuner will return “503 Service Unavailable”.
If the program requires content-protection not requested by the client the tuner will return “503 Service Unavailable” after 5 seconds. This error code may change in the future to return a more relevant error code.
If the program cannot be not found in the stream within 5 seconds or the program cannot be authorized within 5 seconds the tuner will return “503 Service Unavailable”.
If the program requires content-protection not requested by the client the tuner will return “503 Service Unavailable” after 5 seconds. This error code may change in the future to return a more relevant error code.
Re: (503) Server Unavailable
Look for the "X-HDHomeRun-Error" http header in the 503 response - this will tell you more specifically what the problem is.
Nick
Nick
Re: (503) Server Unavailable
And as I recall, for after the fact information, the tuner system log has additional details (I don't know the exact texts, but presume it is substantially equivalent to the X-HDHomeRun-Error header), which you should be able to access via the tuner web interface.
-
- Posts: 16
- Joined: Wed Feb 24, 2010 1:01 pm
Re: (503) Server Unavailable
Thanks for the suggestions. I will look at the header and the log.
drm
drm
Re: (503) Server Unavailable
If I understand this part of your question, as I recall (I have a stash with some WIP that I never fully integrated into one of my codes, but I believe it was at least partially working at one point) after a successful tune, the http response header includes the X-HDHomeRun-Resource which provides the tuner reference, which can then be used to associate the response from the http://<device_ip>/status.json response to get values such as the signal strength, quality, and symbol quality (and some other useful information).