-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
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
Add option to set a stun server for RTSPtoWebRTC #72574
Conversation
Converting to draft as I need to add translations. |
Can be merged if frontend pR is ready |
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
a0e9cf3
to
aaeb186
Compare
I've sent a new version of a frontend PR that uses this in home-assistant/frontend#12084 |
I've made a few updates to the config flow. This can use another look, though frontend PR that depends on this has not yet been reviewed. |
The frontend PR has been approved: home-assistant/frontend#13942 and this is ready for another review after some updates/test improvements related to the options flow. |
Proposed change
Add a configuration option to set a stun server for RTSPtoWebRTC, and a websocket exposed so that the javascript frontend webrtc player can fetch it.
Frontend PR: home-assistant/frontend#13942
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: