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.
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:
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?
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 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.
