Wait, proximity sensors show the distance in meters of the device tracker or person from a zone and recalculate anytime that device tracker or person does right? On a decent length drive I would expect hat to update as frequently as your phone reports in. And it doesnt look like you have a time throttle on there so are you sure it’s not polling too frequently?
You might want to consider adding a condition like one of the ones I showed here to add a time throttle and ensure it’s never able to run too frequently. Even if one of those devices starts reporting in faster then expected for some reason.
Once my instance of 2022.12.2 initializes, one of the python processes never stops churning away. It never drops below 40% of one core. This did not happen previously.
Apparently devs decided what colors we need to use?
Would be better they just made a tool to let use define the colors ourselves. I know, you can still change colors, but a simple theme editor would be nice. A leave the choice up to the users. And, … Let each dashboard have it’s own theme.
I have dashboards that are used mostly on PC, but also a dashboard special for my mobile…
Just in case you are not aware: You can set already a different theme for each individual view of a dashboard. So the last point was already possible before…if you define or import different themes.
What I find really really good is the option to modify name, area and icon in the UI for an entity if it has an unique id. It’s so easy and user friendly that I don’t understand that this functionality can’t be used to set up the colours for the entity as well. In general there are no more then 4 states (on, off, unavailable, unknown). I hope our Devs read this . That would be for me the ultimate solution. The (custom) themes set the global colours and you modify the entity colours to your liking to suit your dashboard.
I am still on 2022.11.5 because the updates after are still a small disaster to me.
so this doesnt get buried in a sidetracked topic, the title of the somewhat subjective I dislike the 2022.12 color changes has been changed to the more succint 2022.12 Color states are broken/unusable
We feel it is important this is discussed in a broader context of community members.
puzzling here, would it be feasible to write that condition so it doesnt retrigger within a set timeframe, per trigger entity?
I mean, if a trigger moves around a bit, but the others are only infrequent travelers, Id want the condition to count for the one that changed a lot, and be sparse in updating, but do allow the less frequent trigger entity to cause an update
edit
it would need to fallback to indivual last_changed ?
From another side, this is an open source project where everybody (devs, testers, users-who-help-and-share-solutions, moderators, …) are doing this for free. And everyone should just respect each other and listen to others’ opinions. And may be people should not be strict to some particular person(-s), everyone can make an error, just keep on moving.
For sure. As I said in general. The guys were be able to make nice drop lists when you make an automation or script with the possible states. I would say that also can be used for setting a colour to them…
Still on 2022.11.5. This mornings update had nothing to offer on colour settings. I keep hoping
For all who are willing to update to latest core 2022.12.4 and expecting to climate color state be fixed: it’s still unfixed, rolling back to 2022.11.5, again.
. That would be for me the ultimate solution. The (custom) themes set the global colours and you modify the entity colours to your liking to suit your dashboard.