I have several Eufy cameras and 1 of them supports RTSP.
Now I have imported this into Home Assistant via RTSP with generic camera and with WebRTC and that works, but it does not work for very long.
After a while, which is quite short, there is no longer a connection and you get a message like “mse streams wrong response on describe” or “not available”
I searched the internet and this forum but couldn’t find an answer that solved it.
I now know that when I turn off RTSP on my camera in the Eufy app and then turn it back on, the connection works again via RTSP.
Given that you have to toggle RTSP on and offf on the camera sounds like a problem within the Eufy camera firmware itself. You might want to try their support and see if there is a firmware update or something that fixes that.
I have exactly the same problem! After a few minutes, the cameras stop working with the same error (mse streams wrong response on describe). What also helps (beside restarting the camera itself) for me is to restart the add-on (eufy-security-ws). Then it works again for a few minutes. Firmware is up to date.
It seems many people are experiencing this issue. I have found a work around and that is to create an automation which starts the RTSP stream every 5 minutes using the entity provided. This means that I can no longer stop the stream though or else it just starts again after 5 minutes but a continuous stream is fine for my needs.
ive only seen this recently on two cameras that I have live RTSP feds on via the NAS storage setting…nothing has been changed by me…but it only seems to be affected on playback on one device (EchoShow 15 ) on my other FireHD10 and HomeAssistant in a browser, it works without issue…
So in my mind, maybe something has updated on the cameras themselves. My two affected cameras are the E220 Outdoor wired cameras and have always had full RTSP functionality with no issues…I know some of my Pro 2 cameras can now also have RTSP functionality as well now but I don’t really use them with that as it means the batteries can take quite a hit
now I dont want to tempt fate, but in the process of thinking about ways around this…I noticed there was a go2rtc update in the queue…and having run this…all of my RTSP feed timeouts have fixed themselves. This was 1.9.6
And it does state
and part one might be what the issue had been…
So 2 hours in, I’ve not had any time outs at all on the camera feeds that had been problematic for the past few weeks so I have to assume a recent core update had affected this requiring the gortc integration needing an update
Hope this helps anyone that’s had the same issue
Update:
An hour or so later the issue seems to have come back again so now not sure if this had any effect at all and wasn’t just a timing thing
In the end I duplicated my dashboard and had an automation cycle between them every 4 minutes which means it always displays a live feed but the appearance never changes…so the problem is effectively resolved…but Id like it to go back to how it was…but as stated…this is ONLY an issue on my EchoShow 15 so I assumed it was a change on that front as on my FireHD10 and Browser dashboards the rtsp feeds never fault at all