I don;t know how to explain this but after few hours now the same values are in Polish again (without, restart or other action from my site)
Regarding issue with SMS Gateway, still the same 
I have 5 cameras: 3 - H265 (Dahua) & 2 - H264 (Hikvision) with
picture-entity cards for direct video output from cameras.
Frigate ver. 0.14.1 is installed (incl. go2rtc).
HAOS, generic-x86-64, bare metal system.
Everything works fine on version 2024.10.4.
After the update on 2024.11.2, picture-entity cards do not work for H265 streams, even through the existing go2rtc in MSE(mp4) mode.
Picture-entity card shows ordinary snapshot picture, but on tab/click it just minimizes to āonly header-showā mode.
There are no errors in the logs.
H265 cameras only work with a ācustom:webrtc-cameraā after installation of a WebRTC Camera, but this does not suit me.
How can I configure go2rtc or something else so that picture-entity cards will work with H265 streams at 2024.11.2 core?
Today i have upgraded to HA 2024.11.2 and wanted to try the logs streaming live!. Is this new feature reserved for HAOS or supervised installations? My installation is just HA in a docker container.
Has anyone else had trouble with Zigbee since upgrading to 2024.11.2? ZHA integration completely failed to the point I thought my SkyConnect had died. The integration failed to load and all Zigbee devices were unavailable. I tried reboots, a different USB extender, different ports on my RPi, and finally in desperation replaced my install from a backup from before the last update. That fixed the problem immediately.
I tried looking through the logs to find any errors, but because the integration wouldnāt initialize the ZHA integration page couldnt access the logs, and I couldnāt figure out what to look for in the log viewer in System. Anybody have any thoughts?
Are you using the build in integration or Webrtc as custom integration?
Well, never mind. Rolling back to an old backup worked for a few hours, and then the ZHA integration failed again and Iāve lost connection to everything. Guess itās not the new update, at least? Iāll start a new thread elsewhere.
No, thatās in the release notes.
I have checked and now I know why issue with gateway is, becasue mnot exist python3 in lib:
Are you able to verify if you have the same situation?
I just use the built-in integration. All my camera cards are some variation of:
show_state: true
show_name: true
camera_view: auto
type: picture-entity
entity: camera.g4_instant_medium
name: G4
All RTSP connections: Amcrest, Reolink, Tenvis, Unifi, Wyze, Yi. A veritable dogās breakfast of camera brands and models.
And you are not using things like Reolink integration ?
back to some experimenting with the slick dashboards, and trying to feel some love for the new badges.
I so wish we could set the icon size to a few more pixels.
practically impossible to see the 64 in the processor badge.
this seems out of balance, particularly because there is so much empty space left.
the icon is set with the generic --mdc-icon-size, so we can not set it in a theme either (because it sets the size for all regular icons too.)
since card-mod cant touch it either, my older eyes are lost on thisā¦
unless there could be an introduction for eg --ha-badge-icon-size ofc, and use that in the themes.
imho this should have a place in the accessibility contemplations of the Frontend team.
please.
so at least the users with +4 glasses (ā¦) can do:
notice how the increase of the icon-size (In Inspector, not card_mod) hardly impacts the total size of the badge. cant be a reason not to do so
funny thing is we Can do
ha-badge-size: 48px
which blows up the badge, but leaves the icons untouchedā¦
2 Likes
With mod_card and hui it should be possible. Fairly sure, you have posted this on your own already back some time.
Actually, it WAS NOT possible to style new 2024.8 badges with card-mod.
But it became possible with a bit hacked card-mod (was explained in card-mod thread).
Anyway, probably Marius wants to have a possibility to style new 2024.8 badges with a custom theme - i.e. properties for these badges should be covered by CSS variables.
Might be. But he wrote, that card mod cannot do it. And this is not the case anymore.
it was not my main pointā¦even though we still can not (unless you would know how to, using the release version of card-mod v3.4.3, and not the hacked version)
my main point is, that the icons are too small for some people to be able to distinguish them, and my second point would be that I hope we would get the option to adjust that in HA Frontend natively (indeed, with a theme variable), and not have to rely on a compound set of custom cards which havent been updated in a long time)
1 Like
@Lode1 Thatās a good question, I had to āremindā myself of the answer:
Amcrest(1)*: Dahua integration
Reolink(2)*: yes, Iām using the Reolink integration
Tenvis(1): Generic Camera Integration
Unifi(1)*: Unifi Protect Integration
Wyze & Yi (9 total): all specified in configuration.yaml as platform: ffmpeg
ā¦for example:
# Wyze V2 Front
- platform: ffmpeg
input: -rtsp_transport tcp -i rtsp://USERID:PASSWORD@IPADDRESS/live
name: Wyze Front
* I use camera specific integrations whenever I need access to āeventsā for building useful automations.
had a private chat with @arganto , and learned that it is possible to mod the badges after all, see š¹ Card-mod - Add css styles to any lovelace card - #7453 by Mariusthvdb for further exploration as itās off topic hereā¦
thanks to @Ildar_Gabdullin too!
Anyone else having a problem with constant reboots about every 30min?
Previously with automations:
- Create a blueprint.
- Create an automation.
- Edit the blueprint.
- Reload automations.
- OK.
Now with template sensors:
- Create a blueprint.
- Create a template sensor.
- Edit the blueprint.
- Reload template sensors.
- We still use the old blueprint - have to reboot HA.
Really weird. Probably it depends on a particular change in a blueprint.
For instance, changing āconditionsā ā āconditionā and then reloading templates does not reload a blueprint ā still same error about āconditionsā comes.
Issue here
Sad but seems that blueprints for sensors are buggy.