use a regular button card.
1 Like
Same problem here. For now I switched to getting the price directly via Tibberâs API
1 Like
Yes. Remove the custom integration and then update.
1 Like
Canât even test this update, as soon as the update installs, it rolls back to the previous version. Iâve tried removing lots of things to no avail. I guess Iâm stuck here until the issue is resolved somehow
Checking if just me or are some sensors not reporting since the viessmann vicare update?
Electricity Consumption Today and Heating Consumption Today are remaining on zero.
Node Red no longer deploys (error 413) since the update. Trying to go back to previous core to see if itâs related.
UPDATE: nope. restored to previous core (not sure the supervisor got back though) and still canât deploy on error 413 entity too large
I have a test HA (proxmox) with very little on it. I had installed card-mod and node red companion in HACS. I updated to 2024.11.0 and then noticed I was getting some errors logged when I used check for updates because the âupdate.xxxâ entities for these two were unavailable. When I looked in HACS, they didnât show up under âdownloadedâ, HACS seemed to have forgotten about them. They were still installed and working. I downloaded again in HACS and they look fine now, and check for updates works. But now a bit worried about updating my live system. Anyone else noticed anything like this?
To be clear, when I clicked the refresh arrow under settings/system/updates, I saw this in the log:
2024-11-08 11:28:35.934 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity update.card_mod_update not found.
2024-11-08 11:28:35.935 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity update.node_red_companion_update not found.
The entities WERE there, but showing unavailable.
thanks! I forgot about regular buttons cards
Is there really no way to deactivate WebRTC/go2RTC under Core 2024.11.x? My Dahua cameras and NVR have been running perfectly locally in the LAN under HA for years and I donât want to use WebRTC/go2TRC at all. Regardless of whether this problem - which I also have - is fixed or not.
1 Like
WebRTC changed everything for me!! I have some live camera streams on my primary dashboard (from Wyze cams), and I was constantly having to refresh because the streams would always error out after a bit. There was also at least a 15-second lag that often drifted into minutes as time went on. It also used crash my browser (Chrome or Firefox) regularly.
But now everything has changed! They load instantly and the views are almost real-time! My browser has been open for 24 hours now with no need to refresh, and the cams are all still live!!!
WOW!!! Thank you, thank you, THANK YOU!!!
4 Likes
I like the frigate camera card in HACS. Works even without Frigate though not all options are available.
Thanks to #dermoduffy, he will fix the issue:
1 Like
thx, switched to the included go2rtc for now and see how things goesâŚ
Wow, that is something. Why is it different from the other pages? That is super confusing.
Anyway, thanks for the help
IS there any information at all on what needs to be done for existing go2rtc users to retain their existing setup and still upgrade? I feel like this is going to break a lot immediately on installation
I use the frigate cards with several camera streams and switch between panels with fullscreen views and tile views using motion. I use these with other sensors on dashboards on Android tablets. I tuned hls ll settings to get minimal latency <= 3 sec and smooth video on the tablets with quick switching. After upgrading to 2024.11 the latency is 0 sec, but no smooth streaming, mainly stop motion response and black images. Is it not possible to forse using hls ll with tuning as before? I had to revert to 2024:10 to get decent performance back.
Yes, it is part of default config, so removing it is a case of removing default_config from configuration.yaml and then including what you do want.
Was using the webrtc.create_link function before.
Yaml:
- data:
link_id: "{{ link_id }}"
entity: camera.tuer_sub
open_limit: 1
time_to_live: 60
enabled: true
action: webrtc.create_link
Any hints how I can get similar functionality from the integrated go2rtc?
Thx
Thereâs a conflict with custom integrations & frontend cards that use go2rtc. Typically you have to remove those integrations, nothing else. These people who are having docker issues are likely using an unofficial docker image.
2 Likes
Please elaborate. I am using Eufy cams and they worked fine before the update. Now, IF I can even get them to load, they stop streaming after a couple of seconds. Iâm using the custom:webrtc-camera. What other option do I have?