Yep, this is what I’m doing. Although I have an extra layer for zwave multicast.
1 Like
I’ll have to DM you on that. I think I saw one of those posts I have a bank of 6 shades that constantly acts up and needs to be moved to multicast. But I digress.
So for the rgb etc in the template just throw an average across the numeric attributes (hue/sat. Brightness or x, y color as appropriate) figure out how I want to handle multiple states (or, xor etc) and call it a day then? Seems simple enough.
1 Like
RGB will be a pain in the ass. Same with XY color. Brightness will be easy.
RGB will be easier than xy. But you’ll average each r g b value and combine them. XY… I have no idea how those numbers work so I’m not sure if averaging them will work.
1 Like
I’ll let you know after this weekend? 
1 Like
I don’t know if this is related to 2024.4.2 or my change (I commented out the deprecated parameters ‘retry_on_empty’ and ‘close_on_comm_error’) and the modbus integration is working again.
Zigbee2MQTT is not longer working with this version. Rollback to 2024.3.3 via backup and all is working fine again…
Zigbee2MQTT works fine with 2024.4.x . What errors did you get ?
Not exactly true…
1 Like
All heating thermostats are not longer available. The icon shows a “?” on it. BUT - I installed now again and now it looks all good. I don’t know what happened. You can ignore my last post…
1 Like
Well kinda glad this update didn’t happen last month or I never would have gotten frustrated with managing all my automations and forced myself to move everything to Node-Red, which I’ve become a fan of now.
Did notice that the Blink Wired Floodlight Cameras now have a lot less functionality, although that very well could be a Blink update that caused this. A couple weeks ago you could control the light itself and no longer can. Now they look like any other Blink camera. Same is true of the door bells, they used to be able to sense a button push, now they are just a plain, relitively featureless camera.
Thank you for the new organisational structure. I’ve started labelling all my devices, scripts and helpers according to which automations use them instead of my previous unwieldy naming conventions. I was just wondering if there’s a way to see everything with a particular label - automations, devices, the lot - in one place? It would be so much easier than having multiple browser tabs open. I can’t see one though. Or any way to filter by label when creating a dashboard.
I use groups of groups to do that. For example some lights are controlled in the stitch domain, and some lights in the lights domain. I have a switches group and a lights group and an all group containing the switches and lights group.
It’s early. I don’t know if I made any sense yet.
whenever i upgrade to Core 2024.4.x, after reboot the CLI is available but no dashboard or config etc. happened both with 2024.4.2 which i had to roll back before and now with 2024.4.3 which i just rolled back also. currently on 2024.3.0.
is there a known issue with upgrade to 2024.4.x from 2024.3.0?
thanks.
Not that I know of or it would be more widely reported. It is something specific to your setup.
thanks. whats the best steps to debug? familiar with CLI but never have had to do that with HA before.
Upgraded instead to 2024.4.1 from CLI and restarted. Seems to be running OK after restart.
Will let it run for a couple of days before upgrading to 2024.4.x latest.
Upgraded to 2024.4.3 and the Mobile App is no longer reflecting Desktop front-end changes (similar to what was happening when selecting “Sections” when adding a new tab to the dashboard. Anyone else having issues with the mobile app reflecting front-end changes?
Did you try clearing the app frontend cache?
How do you do that on the mobile app?
iOS or Android?
iOS it is: Settings → Compaion App → Debugging → Reset frontend cache. Then back to your dashboard and pull down to refresh.