I’m a bit confused by all the posts above and a bit hesitant to upgrade… If I want to continue using the 3rd party WebRTC integration, are there additional steps required in upgrading? I can’t see anything in the breaking changes section
I am also using Frigate which I assume is what’s providing go2rtc but it’s been years since I set it up… However I do see go2rtc-1.9.4 in the homeassistant directory
I’m running frigate separate (LXC in Proxmox) from HA using the WebRTC integration with custom:webrtc cards and have noticed no difference in stream speed or quality.
I do eventually want to use HA’s native WebRTC for remote viewing, just haven’t had the time to play with it yet. YMMV.
Please make energy/current available for LG ThinQ devices as this Custom integration.
I can monitor energy consumption for those devices that have support. New LG ThinQ integration don´t make energy consumption entities available.
Same here, I was using the RTSPtoWebRTC addon and my camera’s worked flawlessly.
Since version 2024.11 they don’t work or the streams are very laggy. I tried everything they advised me but no luck.
Please, delete this “build-in working straight out of the box” thing !!!
already there.
Yesterday I updated from Core 2024.10.4 to Core 2024.11.3.
The go2rtc errors and problems with audio and the H.265 codec seem to have been resolved with Core 2024.11.2, but this morning various error messages about go2rtc appeared. I hope these are just temporary “connection problems”. So just an FYI:
Logger: homeassistant.components.go2rtc.server
Quelle: components/go2rtc/server.py:186
Integration: go2rtc (Dokumentation, Probleme)
Erstmals aufgetreten: 08:49:50 (1 Vorkommnisse)
Zuletzt protokolliert: 08:49:50
Go2rtc unexpectedly stopped, server log:
Logger: homeassistant.components.go2rtc.server
Quelle: components/go2rtc/server.py:156
Integration: go2rtc (Dokumentation, Probleme)
Erstmals aufgetreten: 08:49:50 (22 Vorkommnisse)
Zuletzt protokolliert: 08:49:50
github.com/AlexxIT/go2rtc/pkg/core/listener.go:16
github.com/AlexxIT/go2rtc/pkg/webrtc.NewConn.func5(0x6)
github.com/AlexxIT/go2rtc/pkg/webrtc/conn.go:129 +0x68
created by github.com/pion/webrtc/v3.(*PeerConnection).onConnectionStateChange in goroutine 8202
github.com/pion/webrtc/[email protected]/peerconnection.go:496 +0x16f
Is anyone looking at the issues reporting here with webrtc that were on the 3rd party addon? There seem to be a number of people now stuck on 2024.10
I would say only errors in my Log since 2024.11 are related to that “go2rtc” thing.
Using default_config and no “camera” integrations (used to have 2 generic cameras for kodi media_player to acquire thumbnails, removed these cameras almost immediately for testing).
Including this “go2rtc” thing into default config was rather hasty & w/o a proper thinking.
Sadly it is still not fixed after 1.5 months.
Using HA in docker from a standard repo (sudo docker pull homeassistant/home-assistant:stable).
Basically, November and december releases are a disaster. Also media reader was not working in november, Broken cameras, documentation on how to use native webrtc not available, what else? Hope they spent sometime for bug fixing
Why are you responding to my post about logging colors? Please create a support thread to fix your issues.
Presumably to try and illicit some sort of a response. Everyone really appreciates all the hard work that goes into HA (like seriously, it’s super awesome), but it feels like we’ve been abandoned after a release that doesn’t work for a number of people. I think just an acknowledgement that this is being looked at, or even a clarification on the issue and any known workarounds.
I know HA is a toy/hobby to the majority of users, but a number of us really rely on it; personally particularly for security for a property that’s susceptible to break ins.
As always, go to github to report issues.
Reporting issues will not get any attention here, especially 2 months after the release.
An FYI if you don’t particularly like the inbuilt picture glance/entity cards for viewing cameras. I was previously running go2rtc with webrtc custom card. I have disabled the go2rtc but kept the webrtc add-on. You can configure the webrtc custom card to use the integrated go2rtc server which runs on a default port of 11984. For example this worked for me:
type: custom:webrtc-camera
url: camera.camera_name_here
server: http://localhost:11984
muted: true
I’ve just risked updating to 2024.12.4, and my onvif camera streams were still very broken, could only get still images, but this time, instead of giving up on the thing and taking the easy path of rolling back, I fought back, I tried the generic camera integration, still no joy. I tried different transport settings on the generic camera entities config, no improvement, and sometimes broke it even more.
I was sure I tried a different browser before, I can’t remember; surely I’d not be so stupid as to not eliminate my browser? So I cranked up Chrome, as much as I detest it, and the camera streams are only working perfectly. I tried on the companion app on my phone, again, the camera feeds were fine, so I had a big WTF?? moment, and went back into Firefox, still broken. I disabled all my firefox addons and lo the camera streams started working. I re-enabled the addons one by one and found the culprit, ‘WebRTC leak shield’. Well, who’d have thought that? That an addon designed to disable WebRTC would mess up stuff that uses WebRTC to create camera streams. So it seems I was even more stupid than I thought I ever could be.
Setting “media.peerconnection.enabled” to false in about:config, which disables WebRTC, also thoroughly breaks the camera streams, again who’d have thunk it?
Works like a charm now, and I even have audio on the one camera that provides it.
From reading a comment of yours in the 2024.12 thread, I believe yours spontaneously started working properly after you poked a few unrelated entities and then restarted HA? I think it was you anyway. Did you by chance do anything to your browser settings at the same time?
Am I the only person who has issues with new “live” Log?
Imho it became very unreliable.
I got ONE feedback from a dev team so far.
If this change is “noteworthy”
it is supposed to be checked a bit more.
I haven’t had any of these issues. Are you running HAOS/supervised or some other installation method?
I don’t have these problems either.
But I have problems as well. Search and filtering in detailed log is only gambling now if it shows something, even if it is in the log if I scroll back manually.
I don’t think I’ve tried that. I usually just use them as a quick look. Otherwise I go to the logfiles themselves via samba share & LogExpert
I am running HA in docker…
Checking the Log was the only way to investigate issues. Now I simply have to guess…
Cleaning cache several times a day.
Both in Chrome in FF.
Sometimes Log looks like it should:
these messages first:
2025-01-16 16:36:51.122 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration xxxxxxxxxxxxx which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
next smth like
2025-01-16 16:38:55.127 WARNING (MainThread) [homeassistant.setup] Setup of command_line is taking over 10 seconds.
next other messages after HA started.
But in MOST cases the 1st part may be somewhere in the middle, before Log may contain messages from the earlier run.
Or even worse - the 1st part is repeated several times - this is what I meant by “mixed” in some of my issues:
12:36 xxx
12:37 xxx
12:01 xxx
12:02 xxx
and so on.
But even this mixed Log it is still possible to analyse. The worst case (described in some issue) - a message is not present in Log, although it is present in “short” Log.