That’s one way, and preferred, but a quicker way is to just downgrade the core using the CLI
ha core update --version 2024.10.4
This works just as well as long as there are no database schema updates (none in this update) and it is much quicker.
That’s one way, and preferred, but a quicker way is to just downgrade the core using the CLI
ha core update --version 2024.10.4
This works just as well as long as there are no database schema updates (none in this update) and it is much quicker.
Oh crap, you are right. Hadn’t thought of trying that. Force refresh of the browser fixed it. Duh.
So nice to see sections be made a full feature finally, just as I finish moving everything over to it in experimental haha
How do I tell if WebRTC is working on my cameras and which ones are using it?
Is nabucasa needed for the webrtc ?
Not directly, but if you are going to access your cameras remotely then some form of remote access is required
Anyone else got problems with recorder after updating to 2024.11?
Got a message that something was wrong and had to check the logs.
Reverted back to 2024.10.4 and everything is working.
Hmm , I already have the webrtc and go2rtc addon running, will there be no conflict now?
No, because the go2rtc implementation in HA uses different ports
Ok , so then there are actually 2 go2rtc components running? Do I still need them both? Can I move the config from the addon to the new HA component?
Same here, previously I’d used the Custom Component and was thinking I’d stick the same PAT in the official component as I use there, but it fails. When I click the link the page is blank. Could be the PAT would work if the service was up? Unclear.
Guess I’m sticking with the Custom Component for now!
Yeah, but I don’t use the webrtc card anymore, only frigate card, using the go2rtc addon… I removed just now the webrtc integration…
So just wondering if I can drop the go2rtc addon too…
The go2rtc new module in 2024.11, does it also provide a yaml file for the config like the addon? Sorry for Q, didn’t update yet
if you are just using the frigate card then yes there is no need, frigate card supports go2rtc streaming even before this HA update
@crzynik
Yeah , but I use the go2rtc addon to create a stream… There is no camera entity in HA, but I can use Frigate to show the stream that I defined in the go2rtc addon, with the yaml file… I was wondering if I can do the same with the new embedded go2rtc module, if there is also an yaml file , I can move over the config…
the recommendation would be to define the stream in Frigate’s go2rtc config
I was running the 2024.11 beta and just updated to 2024.11.0 without any issues so far.
One thing I will say is that migrating dashboards to the Sections style can be tricky if you have very long cards. I had to use a PC as it’s too hard on a phone due to the page not auto-scrolling up when trying to drag a card into the new dashboard. Even on a PC I had to reduce the browser zoom to about 35% to fit everything in while dragging cards up.
eg: to drag this bottom card up into position I have to reduce the browser zoom to 33% since otherwise I can’t see the Section to drag into and the page won’t auto-scroll up.
Ok , then i keep the go2rtc addon running too, if there is indeed no conflict…
There is no yaml file now for go2rtc that’s embedded with 2024.11?
Locally my cameras are now lightning fast, but when accessing my HA though its cloudflare tunnel, I find on the first load i consistently must reload to get it to remove the “unknown command” error. On mobile I can’t get them to display at all through the tunnel…