That looks like it’s outside HA, so you don’t change anything.
It does not work because i have removed hacs webrtc (& go2rtc) in favour of HA’s native go2rtc.
Without the following, i cant access http:[HA_IP]:1984 or 11984:
go2rtc:
debug_ui: true
the rest command is defined like this:
pipup_url_on_tv_wz:
# Use with Webrtc camera as described here:
# https://github.com/AlexxIT/WebRTC/wiki/Cast-or-share-camera-stream#html-page
url: http://192.168.0.4:7979/notify
content_type: 'application/json'
verify_ssl: false
method: 'post'
timeout: 20
payload: >
{
"duration": {{ duration | default(20) }},
"position": {{ position | default(0) }},
"title": "{{ title | default('') }}",
"titleColor": "{{ titleColor | default('#50BFF2') }}",
"titleSize": {{ titleSize | default(10) }},
"message": "{{ message }}",
"messageColor": "{{ messageColor | default('#fbf5f5') }}",
"messageSize": {{ messageSize | default(14) }},
"backgroundColor": "{{ backgroundColor | default('#0f0e0e') }}",
"media": {
"web": {
"uri": "{{ url }}",
"width": {{ width | default(640) }},
"height": {{ height | default(480) }}
}
}
}
And was called like this:
- data:
title: Ding Dong!
message: Es steht jemand vor der Tür!
width: 960
height: 720
duration: 60
url: http://192.168.0.8:1984/stream.html?src=doorbell_main&mode=webrtc
enabled: true
action: rest_command.pipup_url_on_tv_wz
Also tried url http://192.168.0.8:11984/stream.html?src=doorbell_main&mode=webrtc
in browser, the stream also doesnt work when debug_ui is false.
I want to use HA’s native integration of go2rtc, so i dont have to mess around with the hacs webrtc camera & go2rtc.
How can i get an go2rtc link from HA’s native go2rtc with debug_ui disabled?
P.S.: when enabling debug_ui, and with the help of my magic mirror, which always starts an dashboard (with an stream), i can use the url http://192.168.0.8:11984/stream.html?src=camera.tuer_sub&mode=webrtc and it works. But if my MagicMirror (which shows an dashboard) is offline, that would’nt.
Please help, how i can get an link from HA for my automation.
thx
I’ve seen a feature request for this. Perhaps do a search and vote for it. The alternative (replacing the default config with what you need) is so simple that I personally don’t think the FR will ever be implemented.
The FR has been denied multiple times. The core team doesn’t want to support it largely because it may or may not actually exclude the integration. Integrations in HA will use other integrations if it’s a dependency. When this happens, the integration will load regardless if you have it via default_config for not. So excluding integrations isn’t really a thing.
2 Likes
Sorry, I don’t know enough bout that external lib to help.
Thats not an external lib.
I want to use the integrated go2rtc to generate an http webrtc link (as before with hacs addons). Just sending this link to an android TV app (pipUp) which displays the camera stream.
Now, that go2rtc is highly integrated into HA, which action/service do i have to call to get an http stream link, which i can use in my automations?
Ps.: For now i have installed go2rtc addon again and will use it alongside HA’s native, but running/maintaining the same process two times is not what i prefer.
But it works.
Just an idea: Is the go2rtc HTTP stream perhaps available as a device or entity?
I don’t use go2rtc but have integrated the RTSP streams from my cameras directly.
In my case, the stream from a camera is played on my Nest Hubs when someone presses the doorbell button, but I could of course also play the stream on my Android TV.
Valid. I forgot about the outcome. I just vaguely remembered it. Doesn’t bother me personally though.
Yeah it is, but just as an camera… entity. So you can just use it with actions/services which takes an camera enitity (like play_stream you used).
But i try just to get an http stream from the internal go2rtc to feed it an android tv app, which does not support rtsp (it just supports http).
Yes, that’s what I meant. It could have been that the http stream from go2rtc was also available as a camera stream. As a device or entity. 
Since I neither use go2rtc nor want to use it, 
nor need an http stream from it, I unfortunately cannot help you.
- Logging home assistant core gives garbage.
- Conversion of dashboard to sections, is minimal. Only badges were converted. The rest is manual.
where is the button to convert to the new sections layout?
It appears when you change the dashboard’s view type to sections
Where is a type option?
Thank you - this was the exact info I was looking for!
I finally found it. Its a view type which is a tab of the dashboard.
Is there a limitation of using WebRTC with cameras in MacOS? The WebRTC Streams work on MacOS via browser: Safari or Chrome, but fail always when using the Companion App. iPadOS and iOS work fine. I’ve opened a bug request about this… had me scratching my head for a couple of hours. If this is a limitation, there should be a way to default back to RTSP on MacOS Companion app. Now I’m just updated with static pictures every 10 seconds in the Companion app running on MacOS.
I’m on HA core (on a Pi4) about to move to HAOS on a NUC. This update really screwed me up.
I was on 2024.09.3… I went straight to 2024.11
I was cleaning out my integrations (the LG ThinQ, WebRTC) to switch to the new stock ones. But since this update I can’t actually install any integrations. But I successfully installed updates to existing ones.
Adguard Home(service is hosted elsewhere), LG ThingQ, WebRTC… some I’ve tried.
“Error
Config flow could not be loaded: {“message”:“Invalid handler specified”}”
What caused that?
If I install HAOS 2024.11 on my NUC now & manually transfer my data in… will I copy this problem over? (I need my year of solar usage data, can’t start over)
Also my Sonos & Spotify got broken in this update. But I deleted those to try & reinstall, can’t put back anyway now. Changelog didn’t even mention those.
After upgrading from 2024.10.x to 2024.11.1, all of my cameras (which come through the Frigate integration) only show a static image.
Mine don’t. But if they did I would give details and logs.