Thanks, but i’m not that of a pro… i don’t even know how to use that…
I guess i’ll just adapt all my cards, it will be quicker. Luckily most of them are custom button card, where this can be done. I’m feeling bad for those who use stock cards where in many occasions setting decimals is not possible…
But please, do warn users about such changes in the future BEFORE doing it !!! This has now been done (at least) three times this year alone!
If you’re not using them already it would be a good idea to start using the custom button card’s templates. So, for a given type (device class), make a template, and add that template to all the cards that is of that type.
A small meta note: With YouTube having essentially banned users who are not logged in to a Google account from watching embedded videos, I’d kindly ask you to put a link near the video that opens the video on YouTube.
Cause as you can see in the screenshot below, there is no link to the video anywhere, not even one provided by YT within the embed (the playbutton in the bottom right just leads to the YT home page).
Has anyone successfully used the Voice yes/no blueprint that came in the blog with this release?
It would seem we need to provide data for the variables when firing off the script but there isn’t anything explaining what those need to be. My guess is ‘preannounce’ and ‘entity_id’ but when I tried this I still got errors.
Has there been a change with the modbus integration recently? I’ve two systems with issues, reading wrong and inconsistent numbers. When rebooting one system, numbers are coming back for a short periode, but suddenly getting inconsistent again.
state_class: measurement as well as state_class: total_increasing
input_type: holding
data_type: uint64 as well as data_type: int32
device_class: energy (W, Wh and kWh)