ffmpeg time out / bad request issue about ring-mqtt HOT 6 CLOSED

Did you restart ring-mqtt? Is that really all of the log messages? The most confusing thing is that, immediately after the message "Received set live stream state ON-DEMAND", there should be a message stating that it is "Starting a live stream session via Ring servers", yet that message doesn't exist in the logs you posted. This implies that there is a live session stuck in activating state, but restarting should clear it.

from ring-mqtt.

Hi,

no I didn't restart ring-mqtt by intention ;-) Couldn't sleep, so I restarted it just now in the middle of the night. Let's see tomorrow if the issue is gone. Feel free to close the ticket.

Btw: A nice feature would be to automatically save a still image every X seconds (not sure if this would be even possible)

best regards

from ring-mqtt.

I may need to add some additional debugging, but I've seen a few reports where, after a while, the live stream will stop activating for some reason. I think it's because a stream gets into activating state, but never actually activates, and then just hangs there, thus new request aren't able to be processed because they detect that a stream is already activating, however, I've never been able to actually reproduce this issue myself. Probably I need to add some timeouts and perhaps some additional debugging, to try to get to the bottom of those cases.

Btw: A nice feature would be to automatically save a still image every X seconds (not sure if this would be even possible)

That's not really something that fits within the realm of this project. To goal of this project is to be the bridge between Ring's proprietary API and standard based protocols of MQTT and RTSP, that's it. From that point any tool that can use these protocols can be leveraged to do whatever a user wants with the data. For example, ring-mqtt already supports taking snapshots on motion or at set intervals (down to as often as every 10 seconds, although that's battery drainer for non-line powered cameras), and it sends these images via MQTT topics. It's up to whatever tool you like to use to look for these images and save them or otherwise do whatever you want with them. A simple HA automation or Node Red flow can do what you ask.

from ring-mqtt.

Just to add, the restart fixed the issue until it came back the day after :-( Since I didn't have time to restart again, I will do it right now.

from ring-mqtt.

I can confirm now this happens from time to time and a restart solves it.

from ring-mqtt.

Without full logs of a session where it was working and then fails, there's not much that can be done here.

from ring-mqtt.