Mse: streams: wrong response on DESCRIBE / can't get url for camera.xx

Configuration
,
1

Hi there. I apologize if I am in the wrong spot, but didnt know exactly where to start.

I have the latest version of Home Assistant running, and I have installed Eufy Security, Go2RTC and the WebRTC integrations.

I have used the documentation from github for adding cards and they work for the most part…

If I use this setup below, then the rtsp stream runs no matter what and it times out after a few minutes and you can’t get it to start again without going into the Eufy App and toggling on/off the RTSP feature for that camera. The error that pops up is “mse: streams: wrong response on DESCRIBE”

type: custom:webrtc-camera
url: rtsp://[email protected]/live2
poster: image.backyard_event_image
ui: true
shortcuts:
  - name: Play
    icon: mdi:play
    service: camera.turn_on
    service_data:
      entity_id: camera.backyard
  - name: Stop
    icon: mdi:stop
    service: camera.turn_off
    service_data:
      entity_id: camera.backyard

AND if I use this alternate configuration below, I get an error that says “can’t get url for camera.xx” and I don’t know why, or where to find the url. I checked the entities of the camera as well and it does in fact show me the stream url and rtsp url. So I know they are there.

type: custom:webrtc-camera
entity: camera.backyard
poster: image.backyard_event_image
ui: true
shortcuts:
  - name: Play
    icon: mdi:play
    service: camera.turn_on
    service_data:
      entity_id: camera.backyard
  - name: Stop
    icon: mdi:stop
    service: camera.turn_off
    service_data:
      entity_id: camera.backyard

Can someone people tell what I may be missing, need to add or what might be wrong?

Ultimately I would like to be able to open the dashboard and play the rtsp streams at the push of a button and stop them accordingly OR maybe it makes sense for them to start auto playing when the dashboard is being viewed only?

Any help would be appreciated.

cams
cams507×577 117 KB

2

I’m having the same issue since the beginning. I also tried different configurations and it still the same. Sometimes, restarting the addon (eufy-security-ws) fixes and the cameras start working but just for a few minutes.
The firmware of my HomeBase 2 is up-to-date (v3.3.4.1h).

3

Absolutely the same issue. I removed all integrations/add-ons and re-did the installation process - same result.

Any bright minds with a solution here? :frowning:

4

I solved the issue by running the “Start streaming via RTSP” entity provided by the device.
After breaking my head, I found an excellent video explaining how to make it work here:

5

Thank you for sharing that! It is really useful video and it works like a charm when motion is detected, etc. - however I did not see being addressed a continuous streaming where there is no motion…

Yet, the video gave me a hint and I managed to fix this pesky error, by creating a simple automation of “time trigger”, where the RTSP stream is continuously turned on (i noticed the stream “expires” usually after 5 minutes and then the thumbnail breaks)

Screenshot 2024-09-22 002349
Screenshot 2024-09-22 0023491425×624 25.8 KB

Problem solved!!! :slight_smile:

3 Likes
6

I wish I found this post earlier! I’ve been banging my head against the desk for hours before finally arriving at the same conclusion. Although I trigger my automation every 5 minutes rather than 1 minute and that seems to be frequent enough. The only issue is now it has to be a continuous stream which I cant stop otherwise it juts starts again after 5 minutes.

7

Based on the information in this thread I figured out that two conditions have to be met in order for my Eufy cams to start streaming:

  1. The RTSP Stream switch needs to be enabled
  2. The camera.turn_on property needs to be set (I assume this starts the WebRTC)

This fixed the “wrong response on DESCRIBE” error for me, so I wrote an automation to turn on the stream:

sequence:
  - target:
      entity_id: "{{ camera_rtsp_switch_id }}"
    action: switch.turn_on
  - delay:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
    enabled: false
  - wait_template: "{{ is_state(camera_rtsp_switch_id, 'on') }}"
    timeout: "00:00:30"
    continue_on_timeout: false
    enabled: true
  - target:
      entity_id: "{{ camera_id }}"
    action: camera.turn_on
fields:
  camera_id:
    name: Camera ID
    description: Should be camera.<camera name>
    required: true
    selector:
      entity:
        domain: camera
  camera_rtsp_switch_id:
    name: Camera RTSP Switch
    description: Should be switch.<camera name>_rtsp_stream
    required: true
    selector:
      entity:
        domain: switch
alias: "Eufy: Start RTSP Stream"
description: ""
icon: mdi:cctv
mode: parallel

The script can be called instead of the turn_on one from the documentation:

shortcuts:
  - name: Play
    icon: mdi:play
    service: script.eufy_start_rtsp_stream
    service_data:
      camera_id: camera.<camera name>
      camera_rtsp_switch_id: switch.<camera name>_rtsp_stream

Still sometimes the screen stayed black. I figured that by clicking on the text in the upper right corner (usually “MJPEG” or “error”) the stream would change to MSE, which is the mode that works without lags. This mode can also be configured in the custom WebRTC component by adding:

mode: mse

to it. Hope this saves someone some time :slight_smile: