So, for some devices their IDs were changed. Is it about those human-unreadable UUIDs? If yes - never use them myself, always believed that they are kind of “low-level” and may be changed any time.
1 Like
I’m guessing that you meant to say “add the ‘Local To-do’ integration, via the [Add Integration] button on the Settings > Devices & Services page” ?
yes, that seemed to do the trick.
Same here. My partner will probably only ever want Shopping List, and doesn’t want to go hunting for it.
Nifty trick I learnt elsewhere … start with an underline (or other character which comes before “a” in ASCII)
Yes me too
Automation visual editor always seems to use/put those hex-numeric device IDs, so how do you avoid this? Use only yaml editor? I also got the error with few automations, luckily easy to fix. They still worked fine before 2023.11 version. Not sure how, if the IDs already were wrong before this.
1 Like
Don’t use device triggers. Use State triggers.
3 Likes
Failed automations used time trigger, but had ‘if conditions’ and those had the ID problem devices.
Still basically the same answer.
Don’t use device conditions, use state conditions.
OK, I’ll try to remember that when adding new automations.
Worth mentioning: ShellyForHASS closes. It was the first Shelly integration in Home Assistant. Many thanks to Håkan Åkerberg as author and main developer. His recommendation is to use Home Assistant’s own Shelly integration.
2 Likes
Here’s a helpful Community Guide explaining the pros and cons of Device Triggers/Conditions/Actions versus other kinds of Triggers/Conditions/Actions.
4 Likes
I’m running Home Assistant;
- Core 2023.11.1
- Supervisor 2023.10.1
- Operating System 11.1
- Frontend 20231030.1
Since upgrading to Core 2023.11.0, the “Refresh” button on the “Developers Tools/State” tab hasn’t functioned correctly. If I select an “entity” from the list of those shown, then click on the “Refresh” button, the area showing the entities attributes (Set State) clears rather than updating entity details.
I’ve only noticed this behaviour since upgrading to Core 2023.11.0. Prior to the upgrade, pressing the refresh button would update the entities attributes. I’ve restarted HA and rebooted the server in hopes of correcting the issue but it remains. Is anyone else experiencing this behaviour?
Regards
Good day,
I have a slight problem, after I upgrade the core to 11.1 there are errors to do with no platform sensor.average, also homeassintant.util.temperature, how can I overcome this because it prevents restarting, when I restore the previous version I do not have issues. It does not point to a line in the config or to any automation.
Regards
Caswell
I didn’t see this upgrading from 2023.11.0 to .11.1 thankfully.
I have added a photo of the error, how can I resolve this, I am afraid to reboot.
Regards,
Caswell
You are using a custom integration that needs to be updated
There’s already a PR to fix that. It may be available in the next fix release
1 Like
Since updating to 2023.11 I no longer seem to be able to theme the colours of sliders. e.g. in my theme:
paper-slider-knob-color: '#e45e65' # red
paper-slider-active-color: var(--paper-slider-knob-color)
However the inspector shows:
This is the same in firefox and chrome.
Is anyone else seeing this?
Then I would have to do that on all devices for all users. Not what I asked for. I want to clean up the system and make it easier to use for all users so there isn’t a lot of unused stuff in the menus.
I think Energy Dashboard date selector change made it worse to use. Before there were direct shortcuts for week, month, year etc. But now I have to do extra click to open the calendar to see those. Bring them back to the main page or allow to customize the view via yaml edit.