Stream not working with Version 2.0 #49

weitheng · 2021-05-04T05:06:47Z

Getting error message on new version. Tried on Safari Desktop and HA iOS App

Se7enair · 2021-05-04T06:21:44Z

Same problem here.

card:

type: 'custom:webrtc-camera'
url: '!secret garten_kamera_hof_stream'

core: 2021.4.5
su: 2021.04.3
HomeAssistant OS: 5.12
Browser: Firefox 88.0

Same on iPhone 7 wit iOS 14.5

Changed nothing, except the update. Updated from 1.3 to 1.4 to 2.0 without restart between 1.4 and 2.0. Did a restart after 2.0

LEJOUI · 2021-05-04T07:11:43Z

In the logs I've this error

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:87
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 9:09:09 (2 occurrences)
Last logged: 9:09:09

[140175567879424] Received invalid command: webrtc/stream

inah72 · 2021-05-04T07:14:12Z

reload page many times then works with chrome or empty cache

LEJOUI · 2021-05-04T07:20:59Z

reload page many times then works with chrome or empty cache

Thanks. Cache deleted fixed it.

shammysha · 2021-05-04T07:46:53Z

New error after deleting cache:

{"error":"RTSP Client Unauthorized 401"}

Downgrading to1.4.0 - all ok

weitheng · 2021-05-04T09:00:01Z

Now seems to work fine, changed nothing on HA iOS App, but cleared cache and website data on Safari Web

AlexxIT · 2021-05-04T09:08:35Z

The cache problem is fixed in the latest master version.

@shammysha How do you set a password for your camera? In the lovelace card or in the camera entity?

Se7enair · 2021-05-04T09:17:55Z

BigBuckBunny Stream is playing after clearing the cache.
My camera now shows
ERROR: Support only RTSP-Stream

AlexxIT · 2021-05-04T09:20:37Z

RTSP check is very simple, url must starts with rtsp

shammysha · 2021-05-04T09:23:18Z

The cache problem is fixed in the latest master version.

@shammysha How do you set a password for your camera? In the lovelace card or in the camera entity?

I do not set passwd for camera anywhere

AlexxIT · 2021-05-04T09:26:41Z

@shammysha so you need to do it, because your camera doesn't work without it

Se7enair · 2021-05-04T09:28:14Z

RTSP check is very simple, url must starts with rtsp

The url is a rtsp-stream. But I use a secret there. If I change to the direct url it works.

So using a secret is not possible at the moment. It worked till 1.3

type: 'custom:webrtc-camera'
url: '!secret garten_kamera_hof_stream'

This is my url: rtsp://user:[email protected]:554/h264Preview_01_main

shammysha · 2021-05-04T09:35:31Z

@shammysha so you need to do it, because your camera doesn't work without it

In rtsp url to camera password exist.

  - type: 'custom:webrtc-camera'
    url: >-
      rtsp://192.168.1.10:554/user=admin&password=********&channel=1&stream=1.sdp?real_stream--rtp-caching=100

Config does not changes between versions

weitheng · 2021-05-04T09:55:26Z

The cache problem is fixed in the latest master version.

@shammysha How do you set a password for your camera? In the lovelace card or in the camera entity?

Updated to the master version. Stream seems to take more than 10-15 seconds to load (blank screen) on my HA iOS App running on iOS 14.6, iPhone 11; iPadOS 14.4.1, iPad mini 4. Previously stream loads instantly. Is this normal?

On Safari Desktop, there's almost no delay. I suspect it is due to the CPU usage as it defaults to MSE at the start or because iOS 14.6 doesn't play over MSE, as once WebRTC takes over (delay of few seconds), it plays smoothly and instantly?

AlexxIT · 2021-05-04T10:44:34Z

@Se7enair you can't use secret in lovelace card. Create ffmpeg or generic camera and use it entity in webrtc card config

AlexxIT · 2021-05-04T10:57:32Z

@shammysha fix in latest master version

majkers · 2021-05-04T11:04:54Z

@AlexxIT how about new official version? :)

AlexxIT · 2021-05-04T11:21:22Z

Need to collect more hotfixes

AlexxIT · 2021-05-04T11:27:33Z

@weitheng iOS doesn't support MSE, I have fixed readme.

WebRTC not always starts instantly. Sometimes it takes time to get a public IP address. In theory, the connection can be speeded up, but there is a lot of work need to be done.

Se7enair · 2021-05-04T12:06:01Z

@Se7enair you can't use secret in lovelace card. Create ffmpeg or generic camera and use it entity in webrtc card config

I tested only on a testcard directly in lovelace. There it wont work.

Normally I use the card as a popup on my dashboard, there it works with secret.

              action: fire-dom-event
              browser_mod:
                command: popup
                title: Hof
                style:
                  .: |
                    :host .content {
                      width: 1280px;
                    }
                card:
                  type: 'custom:webrtc-camera'
                  url: !secret garten_kamera_hof_stream

Gferretta · 2021-05-04T12:16:43Z

Do not function for me. 😪
Last version show this errors

Reinstaling v1.4.0 and works like a charm again

shammysha · 2021-05-04T13:03:50Z

@shammysha fix in latest master version

Reinstall via HACS, error {"error":"RTSP Client Unauthorized 401"} still exists

majkers · 2021-05-04T13:09:31Z

@shammysha fix in latest master version

Reinstall via HACS, error {"error":"RTSP Client Unauthorized 401"} still exists

master is not the same as HACS version...at least for now

weitheng · 2021-05-04T13:10:52Z

@weitheng iOS doesn't support MSE, I have fixed readme.

WebRTC not always starts instantly. Sometimes it takes time to get a public IP address. In theory, the connection can be speeded up, but there is a lot of work need to be done.

I see. But before updating to Version 2.0.0, it was way faster, no long delay before the stream was played. Because right now, it is consistently taking 10-15 seconds before the streams starts playing. I have tried multiple times and over different networks (WiFi, Mobile Data)

Is it normal to be getting this message every time before a stream starts? 2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF

shammysha · 2021-05-04T13:23:55Z

@shammysha fix in latest master version

Reinstall via HACS, error {"error":"RTSP Client Unauthorized 401"} still exists

master is not the same as HACS version...at least for now

Thank You. Will test when HACs version become the same as master :)

weitheng · 2021-05-04T13:49:07Z

@weitheng iOS doesn't support MSE, I have fixed readme.
WebRTC not always starts instantly. Sometimes it takes time to get a public IP address. In theory, the connection can be speeded up, but there is a lot of work need to be done.

I see. But before updating to Version 2.0.0, it was way faster, no long delay before the stream was played. Because right now, it is consistently taking 10-15 seconds before the streams starts playing. I have tried multiple times and over different networks (WiFi, Mobile Data)

Is it normal to be getting this message every time before a stream starts? 2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF

Getting this while playing on iOS HA App:

2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/05/04 - 21:45:28 | 200 | 11.75648582s | 127.0.0.1 | GET "/ws?url=rtsp://admin:[email protected]:554/cam/realmonitor?channel%3D1%26subtype%3D0%26unicast%3Dtrue%26proto%3DOnvif"
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/05/04 - 21:45:28 | 200 | 11.756810889s | 127.0.0.1 | GET "/ws?url=rtsp://admin:[email protected]:554/cam/realmonitor?channel%3D12%26subtype%3D0"

shammysha · 2021-05-04T14:06:45Z

Alphanumeric symbols only From: Alex X ***@***.***> Sent: Tuesday, May 4, 2021 1:49 PM To: AlexxIT/WebRTC ***@***.***> Cc: shammysha ***@***.***>; Mention ***@***.***> Subject: Re: [AlexxIT/WebRTC] Stream not working with Version 2.0 (#49) @shammysha <https://github.com/shammysha> what chars in your pass? Letters/numb or some spec? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#49 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/APWVNMIUY5YORJOGZDHCWXDTL7GIJANCNFSM44CAEUYQ> . <https://github.com/notifications/beacon/APWVNMLVXONCIVRMA7YSV7DTL7GIJA5CNFSM44CAEUY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGGKQLOA.gif>

weitheng · 2021-05-04T14:17:07Z

@weitheng iOS doesn't support MSE, I have fixed readme.
WebRTC not always starts instantly. Sometimes it takes time to get a public IP address. In theory, the connection can be speeded up, but there is a lot of work need to be done.

I see. But before updating to Version 2.0.0, it was way faster, no long delay before the stream was played. Because right now, it is consistently taking 10-15 seconds before the streams starts playing. I have tried multiple times and over different networks (WiFi, Mobile Data)
Is it normal to be getting this message every time before a stream starts? 2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF

Getting this while playing on iOS HA App:
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/05/04 - 21:45:28 | 200 | 11.75648582s | 127.0.0.1 | GET "/ws?url=rtsp://admin:[email protected]:554/cam/realmonitor?channel%3D1%26subtype%3D0%26unicast%3Dtrue%26proto%3DOnvif"
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 21:45:28 websocket.JSON.Receive EOF
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/05/04 - 21:45:28 | 200 | 11.756810889s | 127.0.0.1 | GET "/ws?url=rtsp://admin:[email protected]:554/cam/realmonitor?channel%3D12%26subtype%3D0"

Had a looked at the code in master branch and noticed the difference in using web sockets (ws) over stream in Version 2.0.0. Previously video stream takes milliseconds to load
2021-05-04 21:51:27 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/04/22 - 21:51:27 | 200 | 147.851143ms | 127.0.0.1 | POST "/stream" but in Version 2.0.0, using ws, video streams take seconds to load
2021-05-04 21:45:28 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2021/05/04 - 21:45:28 | 200 | 11.75648582s | 127.0.0.1 | GET "/ws?url=rtsp://admin:[email protected]:554/cam/realmonitor?channel%3D1%26subtype%3D0%26unicast%3Dtrue%26proto%3DOnvif"

shammysha · 2021-05-04T14:54:05Z

@shammysha fix in latest master version

Reinstall via HACS, error {"error":"RTSP Client Unauthorized 401"} still exists

Changed url to format rtsp://admin:password@address:port
Now all work correct

Gferretta · 2021-05-04T16:26:49Z

@shammysha fix in latest master version

Reinstall via HACS, error {"error":"RTSP Client Unauthorized 401"} still exists

Changed url to format rtsp://admin:password@address:port
Now all work correct

I has setting in this form and not working.

nau53 · 2021-05-04T16:42:12Z

Hi Alex, thanks for update.

My cameras set like this:
rtsp://admin:Password&[email protected]:554/ISAPI/Streaming/Channels/501"

With version 2 it stop working (error parsing). I think 2.0 parse it wrong because & symbol in password. With 1.4 it worked just fine.
2021-05-04 22:32:59 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 22:32:59 Stream Try Connect rtsp://admin:Password
2021-05-04 22:32:59 DEBUG (webrtc) [custom_components.webrtc.utils] 2021/05/04 22:32:59 parse "rtsp://admin:Password": invalid port ":Password" after host

majkers · 2021-05-04T16:56:42Z

ok testing v2.0.1 with two cameras. I have it working for the first but the second is not with error (EDIT it stared but errors still in javascript console):

webrtc-camera.js?v2.0.1:72 DOMException: Failed to execute 'appendBuffer' on 'SourceBuffer': This SourceBuffer is still processing an 'appendBuffer' or 'remove' operation. at WebSocket.ws.onmessage (http://ha:8123/webrtc/webrtc-camera.js?v2.0.1:70:34)

And one more. It looks like it breaks my external nabu casa access after some while. I asume it uses MSE access and although the stream is being displayed I still see loading circle (using android device with nabu casa access) and after a while working like this i suddenly can't access my nabu casa address. It takes some time and it works again...

The same as above on Chrome PC with this error in console:

https://XXXX.ui.nabu.casa/api/hls/2b3a36f0cfc41c0e3b81415d5dab9cb6637e1be0f44a8b849c4dbb6d0d6c98d8/segment/232.m4s 404 (Not Found)

Looks like trying to access nabu casa with MSE is problematic. When is switches to WebRTC I see no more errors in console and stream is working fine.

I think it should be configurable wheter to use MSE or WebRTC first when connecting.

AlexxIT · 2021-05-04T18:23:04Z

/api/hls/... - this is not from my component

Failed to execute 'appendBuffer' and loading circle is normal situation with some "slow" cameras or connection.

Maybe you just have a problem with the Internet?

majkers · 2021-05-04T18:51:36Z

But these errors heppen when stream is in connection phase. After connected they stop. No I have no problems with connection to the internet

weitheng · 2021-05-04T19:24:22Z

The cache problem is fixed in the latest master version.
@shammysha How do you set a password for your camera? In the lovelace card or in the camera entity?

Updated to the master version. Stream seems to take more than 10-15 seconds to load (blank screen) on my HA iOS App running on iOS 14.6, iPhone 11; iPadOS 14.4.1, iPad mini 4. Previously stream loads instantly. Is this normal?

On Safari Desktop, there's almost no delay. I suspect it is due to the CPU usage as it defaults to MSE at the start or because iOS 14.6 doesn't play over MSE, as once WebRTC takes over (delay of few seconds), it plays smoothly and instantly?

The long delay is fixed with the latest master version. Only a tiny 1-2s now, barely noticeable. Thanks @AlexxIT :)

AlexxIT · 2021-05-07T03:54:09Z

I think problems in this issue closed in latest version

AlexxIT added the bug Something isn't working label May 4, 2021

AlexxIT closed this as completed May 7, 2021

Stream not working with Version 2.0 #49

Stream not working with Version 2.0 #49

Comments

weitheng commented May 4, 2021

Se7enair commented May 4, 2021 • edited Loading

LEJOUI commented May 4, 2021

inah72 commented May 4, 2021 • edited Loading

LEJOUI commented May 4, 2021

shammysha commented May 4, 2021 • edited Loading

weitheng commented May 4, 2021

AlexxIT commented May 4, 2021

Se7enair commented May 4, 2021

AlexxIT commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021

AlexxIT commented May 4, 2021

Se7enair commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021 • edited Loading

weitheng commented May 4, 2021 • edited Loading

AlexxIT commented May 4, 2021

AlexxIT commented May 4, 2021

majkers commented May 4, 2021

AlexxIT commented May 4, 2021

AlexxIT commented May 4, 2021

Se7enair commented May 4, 2021

Gferretta commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021

majkers commented May 4, 2021

weitheng commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021

weitheng commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021 via email

weitheng commented May 4, 2021 • edited Loading

shammysha commented May 4, 2021

Gferretta commented May 4, 2021

nau53 commented May 4, 2021

majkers commented May 4, 2021 • edited Loading

AlexxIT commented May 4, 2021 • edited Loading

majkers commented May 4, 2021

weitheng commented May 4, 2021 • edited Loading

AlexxIT commented May 7, 2021

Se7enair commented May 4, 2021 •

edited

Loading

inah72 commented May 4, 2021 •

edited

Loading

shammysha commented May 4, 2021 •

edited

Loading

AlexxIT commented May 4, 2021 •

edited

Loading

Se7enair commented May 4, 2021 •

edited

Loading

shammysha commented May 4, 2021 •

edited

Loading

weitheng commented May 4, 2021 •

edited

Loading

Gferretta commented May 4, 2021 •

edited

Loading

weitheng commented May 4, 2021 •

edited

Loading

weitheng commented May 4, 2021 •

edited

Loading

weitheng commented May 4, 2021 •

edited

Loading

majkers commented May 4, 2021 •

edited

Loading

AlexxIT commented May 4, 2021 •

edited

Loading

weitheng commented May 4, 2021 •

edited

Loading