That would be hugely appreciated.
I was going to post that I use the custom WebRTC, go2rtc and LG ThinQ components all of which seem to have moved to Core with this release. It’s great to see them included in core but instructions on what people who have been using custom components for months/years without any issues need to do would be much appreciated, ideally documented in the release notes.
Hm… maybe i’m doing something wrong, but in my case these two cards are still appr. 5 seconds apart - web-rtc camera card is still way faster in live picture:
#fast one:
type: custom:webrtc-camera
streams:
- entity: camera.prusa_mainstream
mode: webrtc
media: video
#and slower one:
type: picture-entity
entity: camera.prusa_mainstream
camera_view: live
Hi all.
Bug or feature?: With release 2024.11 the tibber sensor called electicity.price is gone.
Related to * Clean up Tibber service tests (@functionpointer - #127334)?
Has anyone got an idea how get that sensor back?
Thanks
For those wondering, as of now, the HACS LG ThingQ component is more robust and has more features to offer than the core component.
That’s not to say the LG core version won’t eventually offer more and/or better features as time progresses. It’s new. Got to give it time to develop.
Hello,
what exactly is new about WebRTC? I am currently still using GO2RTC, is that no longer necessary? Do I have to make any additional settings?
Can someone post des yaml code for showing the camera in the Dashboard? I habe die Eufy Camera wich support only PSP Stream.
Regards
Philipp
How strange, I just updated to 2024.11 yesterday and wanted to start converting my pages to sections but I still see the “sections (experimental)” and get the following message while trying to switch:
You can not change your view to use the ‘sections’ view type because migration is not supported yet. Start from scratch with a new view if you want to experiment with the ‘sections’ view.
I checked the versions and I do am on 2024.11. I also had the camera local_file message so that worked.
With new Sections layout I really miss one function; ability to reorganize whole dashboard depending on the screen size. While it is possible to show/hide individual sections based on screen type, it is very hard to use this functionality to properly order cards in landscape vs. mobile layout. It requires to virtually duplicate all of the cards (in extreme case), order half of them for normal and half of them for mobile view with conditions to hide unused ones… Any chance to have something similar to mediaquery + grid definitions in layout card? Or I’m missing something…
Really happy to get rid of one of the HACS for an official integration. I use it only for the ACs, so while the new integration is more limited, I’m not missing anything critical.
Too bad though that it still works through their cloud rather than locally.
I took a while to finish starting for me as well but there still was a problem with history and stats. Problems were gone when “upgrading” to 2024.10.4 again.
case closed. restarting HA did the trick for me.
Hello 
Can you provide an example of the layout you’re trying to achieve?
You should clean the cache of your browser.
Hey, i see with this option below, you can enable the go2rtc admin to edit the go2rtc.yaml file …But after a restart HA , the file is restored again to defaults … is it possible to make the changes in there sticky ?
go2rtc:
debug_ui: true
Amazing work! Big Thank you to all the contributors!!! 
Really would like to know that, too.
Uninstalled my Go2rtc and webrtc card addons/hacs which were working flawlessly, but now I’m stuck with a laggy webrtc stream, that starts quickly.
With Go2rtc I was using the ffmpeg (http) stream of my reolink doorbell which is flawless. The integrated go2rtc seems to use RTSP which is quite problematic on any Reolink camera. So I’d really like to change that.
Edit:
This is the line in the go2rtc config that delivered crystal clear video and audio, perfectly in sync and lagfree:
camera.doorbell_audio:
- "ffmpeg:https://192.168.20.157/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=XXX&password=XXX#video=copy#audio=opus"
RTSP was as sluggish in go2rtc before as it is now.
UPDATE: tried to change to http (flv) in Reolink configuration and it crashed my whole Home Assistant Green shortly after.
Any news about the iCloud integration fix? It seems like we are just missing the patches to be integrated in new release iCloud integration stopped working (due to Apple SRP-6a implementation) · Issue #128830 · home-assistant/core · GitHub
Otherwise, great work on this new release thanks guys !
I REALLY like what you guys have been doing with the sections, making dashboards more personalized and original without having to go into YAML, templating etc.
One thing I have been waiting on for YEARS (literally) and I really hope you will start to address, is some basic card contents lay-outing options within the GUI, notably for font size.
I have painstakingly created a dashboard where the most important sensors need to be legible from a distance. For instance, if I want to know when the next bus comes round, I want to be able to see that from the other end of the kitchen while cleaning up; or if I’m on the couch, I do not want to head over to the wall mounted tablet to check current energy usage. For this reason, I have been using sensor cards with card mod, putting core sensor values in a 65px font. But the approach is convoluted, requiring you to use browser development tools to look for the exact element you want to change, the syntax is difficult for non-specialists, and things often go wrong. For example, since a few months, my cardmod syntax gets ignored after a while, until I restart the app.
So here’s my question: if we can now specify card sizes in fancy ways, can we please please finally have a way to adjust at least the font size of what is inside those cards, in other words integrating cardmod functionality? By the way, increasing card sizes is fun, but if the font stays the same, that’s not very aesthetic either.
Have not installed .11 yet.
For me these features are very promising: blueprints for template sensors and “live log” (it is not convenient to scroll up, refresh, scroll down).
Can confirm this. Using Stream from Door Camera with old webrtc and the new one in a picture-entity.
3 seconds difference!
Update: adding go2rtc: to configuration.yaml solved it. No delays anymore