Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quit working with Web-RTC card #1195

Open
timothybuchanan opened this issue May 13, 2024 · 8 comments
Open

Quit working with Web-RTC card #1195

timothybuchanan opened this issue May 13, 2024 · 8 comments

Comments

@timothybuchanan
Copy link

Bridge is working fine, but the WebRTC card no longer displays the camera. I'm using url: rtsp://127.0.0.1:8554/ski-hut-deck. The card displays mse;streams: wrong response on DESCRIBE.

@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

Authentication for the webUI and streams is on by default now, so you need to update the username and password for the stream with something like this:

rtsp://wb:MyUniqueWbApiKey@127.0.0.1:8554/ski-hut-deck

The username for the stream is wb and the password should be unique API Key displayed at the bottom of your WebUI like this:

random key

You can change the API key by setting the WB_API ENV variable.

If you're running the bridge 100% local, then you can probably set WB_AUTH=False to disable authentication and run it like it was before.

Please see the release log for more info:
https://github.com/mrlt8/docker-wyze-bridge/releases/tag/v2.9.0

@timothybuchanan
Copy link
Author

I first tried setting WB_AUTH=False and the card to rtsp://127.0.0.1:8554/ski-hut-deck. Same error of wrong response on DESCRIBE. I then set WB_AUTH=True, and noticed that the API Key on the WebUI is different from the one that Wyze assigned. I tried each on the card, like so: url: rtsp://wb:ApiKey@127.0.0.1:8554/ski-hut-deck. Each key gives the same error. What now to try? Thanks.

@mrlt8
Copy link
Owner

mrlt8 commented May 16, 2024

I know it's a little confusing but the "API Key" in the web UI is a random string unrelated the wyze api key.

You can actually customize the "API key" for the web UI and streams by setting the WB_API environment variable.

@timothybuchanan
Copy link
Author

I tried this too. Here is the add-on configuration:

ENABLE_AUDIO: false
ON_DEMAND: true
WB_AUTH: true
MOTION_API: false
MQTT_DTOPIC: homeassistant
CAM_OPTIONS: []
WB_ENV: MyKey
WYZE_EMAIL: My Email
WYZE_PASSWORD: My Wyze Password
API_ID: The ID Wyze sent me
API_KEY: The Key Wyze sent me
NET_MODE: ANY
SNAPSHOT: Disable
SUBSTREAM: false

Here is the lovelace card configuration:

type: custom:webrtc-camera
url: rtsp://wb:MyKey@127.0.0.1:8554/ski-hut-deck
ui: true
style: >-
.shortcuts {left: 40px; top: 10px; right: unset; display: flex;
flex-direction: line} .mode {display: none}

With these two files, as in all other configurations I've tried, the WebUI for the Bridge functions. The WebRTC card returns the error on screen of "mse;streams: wrong response on DESCRIBE."

These are the only two files I can change. Can you think of any changes to these files that might cause the lovelace card to display the camera? Thank you.

@mrlt8
Copy link
Owner

mrlt8 commented May 16, 2024

Try setting on_demand to false ON_DEMAND: false?
Can you also try the rtsp stream in another media player like VLC?

If you your run your HA 100% local then you could also try disabling auth with WB_AUTH: false

@timothybuchanan
Copy link
Author

ON_DEMAND and WB_AUTH both set to false; same error. Is there a way to install an earlier version? It was working fine before the update.

@ggallegosm
Copy link

ggallegosm commented May 19, 2024

I have the same problem. The WebUI works fine, I can see the webrtc stream from the link the WebUI provides in any browser, but in the WebRTC card it fails with the message: "mse: streams: wrong response on DESCRIBE."
I turned off the WB_AUTH and removed the credentials in the URL, but still doesn't work.
I also have been working with ON_DEMAND set to false.
This is my first insall of the wyze bridge.
Any suggestion?

edit: turning "Enable Audio For All Cameras" off switch made it. Now I can see through the rtsp stream.

@mrlt8
Copy link
Owner

mrlt8 commented May 19, 2024

hmm, which camera is that @ggallegosm? audio shouldn't cause an issue with the streams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants