On the evening of 2019-03-18, I implemented new bouncer behavior in response to a situation where the stream was down but the network was still up.
On the following day, 2019-03-19, I noticed that the stream got reset a couple of times during the day, possibly due to the new behavior.
Old behavior: Only look at network response. New behavior: Look at network response and also use YouTube-dl to decide whether the YouTube live stream was getting any kind of an error such as the stream not being up.
My guess: YouTube-dl is sometimes throwing an error even if the stream is not totally down.
To do:
Check synology logs to confirm if this is the issue.
If so, add some hysteresis to the YouTube-dl part of the bounce script.
On the evening of 2019-03-18, I implemented new bouncer behavior in response to a situation where the stream was down but the network was still up.
On the following day, 2019-03-19, I noticed that the stream got reset a couple of times during the day, possibly due to the new behavior.
Old behavior: Only look at network response. New behavior: Look at network response and also use YouTube-dl to decide whether the YouTube live stream was getting any kind of an error such as the stream not being up.
My guess: YouTube-dl is sometimes throwing an error even if the stream is not totally down.
To do: