Battery powered eufy cameras always initially fail with "mse: streams: wrong user/pass, wrong response on DESCRIBE" until refreshed

[lone-cloud]

Describe the bug

Every time I run camera.turn_on the video is stream is started in an error'ed state with the error message: "mse: streams: wrong user/pass, wrong response on DESCRIBE". I believe this is happening because the stream is started instantly where as the battery powered eufy cams require some time to initialize. You can see this with start-up period with a loading spinner in the official app. When I click in the top right corner, the stream refreshes and everything starts to work as expected.

To reproduce

Steps to reproduce the behavior: I'm using the camera with the following card set UI set up:

        conditions:
          - entity: camera.porch
            state: idle
        card:
          show_state: false
          show_name: false
          type: picture-entity
          entity: image.porch_event_image
          tap_action:
            action: call-service
            service: camera.turn_on
            data: {}
            target:
              entity_id: camera.porch
      - type: conditional
        conditions:
          - entity: camera.porch
            state: streaming
        card:
          type: vertical-stack
          cards:
            - show_name: true
              show_icon: false
              type: button
              tap_action:
                action: call-service
                service: camera.turn_off
                data: {}
                target:
                  entity_id: camera.porch
              entity: camera.porch
              name: Stop
            - type: custom:webrtc-camera
              entity: camera.porch
              poster: image.porch_event_image
              ui: true
              mode: mse
              style: '.pictureinpicture {display: none}'

Expected behavior

The camera should know to wait for x seconds until the battery powered camera is turned on and then play the camera feed.

Additional information

• Home Assistant Installation Type (OS - Supvervised - Core): Home Assistant OS
• Home Assistant Core Version: core-2024.9.2
• Eufy Security Add-on Version: eufy-security-ws (1.9.0)
• Eufy Security Integration Version: 8.0.4

Hardware Information;

• Camera Model: eufyCam S220 (eufyCam 2C Pro)

• Live Streaming Protocol (RTSP/P2P): RTSP

• Debug Logs from Home Assistant:

  Source: components/stream/__init__.py:448
  integration: Stream ([documentation](https://www.home-assistant.io/integrations/stream), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+stream%22))
  First occurred: 9:35:39 PM (5 occurrences)
  Last logged: 8:12:23 AM
  
  Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found, rtsp://****:****@192.168.0.194/live1)
  Error from stream worker: Error opening stream (HTTP_UNAUTHORIZED, Server returned 401 Unauthorized (authorization failed), rtsp://****:****@192.168.0.194/live1)

• Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 364
  }
  2024-09-17 15:24:30.265 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA DATA - Processing sequence 364... {
  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 364
  }
  2024-09-17 15:24:30.317 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA DATA - Processing sequence 364... {
  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 364
  }
  2024-09-17 15:24:30.362 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA DATA - Processing sequence 364... {
  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 364
  }
  2024-09-17 15:24:30.405 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA DATA - Processing sequence 364... {
  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 364
  }
  2024-09-17 15:24:57.813 DEBUG   eufy-security-ws:eufy-security-client   [http] [Station.stopRTSPStream] Station stop rtsp stream - sending command {
  stationSN: 'T8010N1321402DAC',
  deviceSN: 'T8142N9321430E37'
  }
  2024-09-17 15:24:57.815 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol._sendCommand] Sending p2p command... {
  station: 'T8010N1321402DAC',
  sequence: 366,
  commandType: 1146,
  channel: 1,
  retries: 0,
  messageStatesSize: 1
  }
  2024-09-17 15:24:58.581 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleMsg] Received message - DATA DATA - Processing sequence 365... {
  stationSN: 'T8010N1321402DAC',
  remoteAddress: '192.168.0.194',
  remotePort: 16885,
  dataType: 'DATA',
  seqNo: 365
  }
  2024-09-17 15:24:58.585 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleData] Handle DATA DATA - Received data {
  stationSN: 'T8010N1321402DAC',
  seqNo: 365,
  commandIdName: 'CMD_NAS_TEST',
  commandId: 1146,
  resultCodeName: 'ERROR_PPCS_SUCCESSFUL',
  resultCode: 0,
  resultData: '00390000030f0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
  data: '0000000000390000030f0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
  seqNumber: 367,
  p2pDataSeqNumber: 366,
  offsetDataSeqNumber: 0
  }
  2024-09-17 15:24:58.587 DEBUG   eufy-security-ws:eufy-security-client   [p2p] [P2PClientProtocol.handleData] Handle DATA DATA - Result data for command received {
  stationSN: 'T8010N1321402DAC',
  message: {
  sequence: 366,
  commandType: 1146,
  nestedCommandType: undefined,
  channel: 1,
  acknowledged: true,
  retries: 0,
  returnCode: 0,
  data: <Buffer d1 00 01 6e 58 5a 59 48 7a 04 90 00 00 00 01 00 01 02 00 00 92 af 3b dd 1b 48 3e 56 eb d8 5c 75 48 b9 6b ff 53 16 1d 45 d5 1f 0f f3 a4 43 3e 9e 95 3c ... 114 more bytes>,
  customData: {
    property: {
      name: 'rtspStream',
      value: true
    }
  }
  },
  resultCodeName: 'ERROR_PPCS_SUCCESSFUL',
  resultCode: 0
  }
  2024-09-17 15:24:58.590 DEBUG   eufy-security-ws:eufy-security-client   [http] [Station.onCommandResponse] Station got p2p command response {
  station: 'T8010N1321402DAC',
  commandType: 1146,
  channel: 1,
  returnCodeName: 'ERROR_PPCS_SUCCESSFUL',
  returnCode: 0,
  customData: {
  property: {
    name: 'rtspStream',
    value: true
  }
  }
  }

[kmil4]

+1 having same issues with RTC enabled 360 Pan & Tilt models.

60% of the time I can recover by keeping the stream running and navigating away then navigating back, or refreshing

[HarryBouch96]

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.