The logs are all in a file that you can search with the normal search tools in any editor, or with grep.
And when home assistant is restarted, it saves the old log.
Yes I know that. But before it was existing and possible in the UI. Now I have to download (or open on server) and search? Not the biggest approvement I Would say so.
4 Likes
Thought, that perhaps .1 is fixing it. But after I have just updated to .1 the whole detailed log (for Core section) is not available anymore. Really? I assume that it only a bug (here or in general) and not really the situation from now). I can now/ always have to only switch to one or the other, but not have it in parallel anymore.
BTW filtering in detailed view is actually now working. Good. 
1 Like
Read the announcement about the faster camera support and upgraded to 2024.11.1 but not sure if I need to do something further.
I use a generic RTSP camera app on an old iPad, it is now perhaps a little faster but still takes 10 seconds to show the first frame.
Do I need to get a camera app that supports WebRTC to get the full benefit?
The device is configured with rtsp://192.168.50.9:8554/live.sdp
Is there someone who can tell us step by step what to do now ?
This is all very confusing.
It should work “out of the box” ??
1 Like
In principle, it is “quite” simple: It is not intended that an integration that is automatically loaded via default_config: can also be excluded. So you have to remove the default_config: entry from the configuration.yaml and then load all the integrations listed here manually into the configuration.yaml. Except for the go2rtc integration. So instead of default_config: then all the individual integrations like e.g.:
assist_pipeline:
backup:
bluetooth:
config:
conversation:
dhcp:
energy:
etc.
There seems to be a problem with Nest doorbells with this release. Intermittently I (and others) get the error (see here and here for example):
I’m happy to raise an issue on GitHub for this if someone can point me where to.
1 Like
Thank you very much.
That’s clear.
So i did what you said but unfortunately my camera’s are much slower now.
Is there something else i have to do .
I use the reolink integreation.
Unfortunately, I can’t answer that. I’ve gone back to Core 2024.10.4 for now, so I don’t have any experience with Core 2024.11.x without go2rtc. I also don’t know if there were any other changes to the camera integration in Core 2024.11.x that might have an impact if you use Core 2024.11.x without go2rtc.
Note: I think the solution of integrating go2rtc directly into the HA core is a rather unfortunate choice/solution, but of course that is just my personal opinion and I know that many users think it is a good thing. However, I am not one of them. 
But there is no need to discuss that here. It is what it is. 
Looks like I’m also seeing the same static image behavior on my doorbell camera which comes through the Reolink integration. At least it logs errors:
Logger: homeassistant.components.go2rtc.server
Source: components/go2rtc/server.py:151
integration: go2rtc (documentation, issues)
First occurred: 8:02:49 AM (15 occurrences)
Last logged: 8:06:46 AM
08:04:40.192 WRN [rtsp] error="streams: dial tcp 192.168.69.190:554: connect: connection refused" stream=camera.doorbell_fluent_orginal
08:04:40.291 WRN [rtsp] error="streams: dial tcp 192.168.69.190:554: connect: connection refused" stream=camera.doorbell_fluent_orginal
08:06:46.231 WRN [rtsp] error="streams: dial tcp 192.168.69.190:554: connect: connection refused" stream=camera.doorbell_fluent_orginal
08:06:46.278 WRN [rtsp] error="streams: dial tcp 192.168.69.190:554: connect: connection refused" stream=camera.doorbell_fluent_orginal
08:06:46.350 WRN [rtsp] error="streams: dial tcp 192.168.69.190:554: connect: connection refused" stream=camera.doorbell_fluent_orginal
Logger: homeassistant.components.stream.stream.camera.doorbell_fluent
Source: components/stream/__init__.py:448
integration: Stream (documentation, issues)
First occurred: 8:02:49 AM (8 occurrences)
Last logged: 8:07:29 AM
Error from stream worker: Error opening stream (ERRORTYPE_111, Connection refused, rtsp://****:****@192.168.69.190:554/Preview_01_sub)
1 Like
I went back to the same version and everything looks ok for now.
Integration of go2rtc directly into HA core is definitely not a good thing.
Maybe there will be an update to fix it.
Thanks for your replies
Hi, I updated from 2024.10 - Am I the only one that noticed color change in history graphs? Prior to the change I had blue, purple and turquoise. Now I have blue, orange, reddish-orange…Is there a way how to change the colors?
I am talking about the most basic history graph…thanks
Hi, I updated from 2024.10 - Am I the only one that noticed color change in history graphs? Prior to the change I had blue, purple and turquoise. Now I have blue, orange, reddish-orange…Is there a way how to change the colors?
This actually changed in 2024.10, you may have gone an entire month without hitting F5
There are multiple posts on the 2024.10 blog thread about how to template these colors.
1 Like
Does the streaming work for a few seconds and then suddenly break/stop?
That’s what happens with my reolink doorbell.
Streaming doesn’t start for me, just a static image.
Update: changing configuration of the Reolink integration from RTSP to FLV made the camera stream work again. Using RTMP also worked, but much less smoothly.
THanks. Any more info though like what integrations? Are there conflicts with keeping the go2rtc addon and running that side by side with the internal webrtc now? I assume not but Just checking.
Also, I am using a frigate card without the frigate backend to view go2rtc streams as I really like the functionality it gives and I don’t need frigate itself. Anyone also doing that successfully with the new update?
It looks like with the new live log screens there is only the option to download a certain amount of lines of the log. Or am I missing something here?
It was kind of convenient to be able to download just the whole logfile at once for analysis in other tools.
It’s really great to see the efforts to improve camera streaming. I’ve been following your custom work for a while, but never set it up, so this is a first for me.
I’ve upgraded to 2024.11.1 this morning.
On 2 of my 3 cameras, I see the time slider. On my third, I don’t, and it does seem to load a bit faster, although it’s hard to say for certain.
I only use built-in cards and they’re all set to camera_view: auto. I know this typically provides a preview that’s only refreshed every 10s, but I’m of course referring to when one is viewing the stream.
I also have a Nabu Casa subscription.
Camera 1:
A Raspberry Pi camera, running video4linux. It’s integrated with HA using the FFMPEG Camera integration, but on top of this I also use the Camera Proxy integration to apply an overlay. This is the one that seems to load faster, but the entity’s attributes indiate frontend_stream_type: hls.
frontend_stream_type: hls
entity_picture: <redacted>
friendly_name: Security Camera
supported_features: 2
Camera 2:
An Amcrest camera, using the built-in Amcrest integration.
model_name: AD110
brand: Amcrest
motion_detection: true
frontend_stream_type: hls
audio: on
motion_recording: on
color_bw: auto
entity_picture: <redacted>
friendly_name: Doorbell
supported_features: 3
The interesting thing here is that the camera feed in my push notification are now showing almost instantly.
Camera 3:
An Imou camera, using the ONVIF integration.
frontend_stream_type: hls
entity_picture: <redacted>
friendly_name: Baby Monitor
supported_features: 2
How can one determine more easily and accurately determine whether RTC is used?
Would any of my above configurations be incompatible?
EDIT: @edenhaus perhaps better to tag you instead of Alex.
If I were you, I would consider using the camera’s sub stream. The resolution won’t be as good but should be much faster. In your case, the sub stream would probably be:
rtsp://192.168.50.9:8554/live2.sdp
Same thing for me. Charts not loading in the Sensor cards (endless spinning wheel), no little history graph in the entity details pop-up. The “history”, “logbook” and (strangely) “energy” tabs also disappeared. Both on the web interface and the app.
No error in the logs, but when going to Developer Tools, Check Configuration, there was a warning saying “Integration error: default_config - Integration ‘map’ not found”.
As I was already using the add-on Default Config Disabler, I add “map” to the stuff I want to disable (others already there are cloud, my, and zeroconf) and everything worked again.