It would be good if when this comes in, it doesn’t change the UUIDs already assigned by the entry_id 
Thanks Brian. Maybe I’ll do the update one day. It’s an unattractive prospect to deliberately break a working system 
Yes but for a system like HA that is still evolving, it is unavoidable. Equally leaving HA and not updating regularly can be more problematic.
You just need to grasp the nettle.
In addition, this may help. You can rename the new entity to match the old name. Everything should then work as before.
Thanks but I don’t understand the cure! If I go to Developer Tools I see a screen with a menu oftabs at the top and YAML is selected. I don’t see anywhere there to type in anything like
{{ states.sensor | selectattr('entity_id', 'search', 'sensor.emon')
| map(attribute='entity_id')
| list
| join(', ') }}
and if I select every other tab in turn I don’t see anything else that immediately leaps out as the place to do it. I do wonder about Template editor, but there’s no links to any idiot’s guide?
I braved it and put it in the template and that worked, so that’s good 
My Home Assistant updated and i’m now having to go through migrating my old YAML to the new module.
One gotcha for me is that some of my feeds are so old they never had any unit of measurement set in emoncms. So when I tried adding them into the new emoncms module, the integration crashed.
* 2024-11-02 20:29:13.103 DEBUG (MainThread) [homeassistant.components.emoncms] Finished fetching emoncms_coordinator data in 0.039 seconds (success: True)
* 02/11/202420:29:13
2024-11-02 20:29:13.104 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up emoncms platform for sensor
* 02/11/202420:29:13
Traceback (most recent call last):
* 02/11/202420:29:13
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform
* 02/11/202420:29:13
await asyncio.shield(awaitable)
* 02/11/202420:29:13
File "/usr/src/homeassistant/homeassistant/components/emoncms/sensor.py", line 164, in async_setup_entry
* 02/11/202420:29:13
elem["unit"],
* 02/11/202420:29:13
~~~~^^^^^^^^
* 02/11/202420:29:13
KeyError: 'unit'
I fixed this by going back into emoncms, giving the feed a unit of measurement (watts) in the case of this first broken one, then restarted the integration to pick that up.
Hope this helps someone else out if they see similar.
Thanks for the hardwork put into this.
PS, is there anyway to change the entity prefix from [email protected] ?
1 Like
Short answer is no It’s and HA thing rather than exclusive to this integration. At some point when the UUID changes come in, you could pick a specific user on a specific instance to pull the feeds from and that will be the device ID.
1 Like
FWIW, I haven’t upgraded yet. It occurred to me that what I find “wrong” is that this is a breaking change. So IMHO, it should leave the original functionality in place and supply the new functionality in addition (and separately if need be). I can still use ext2 filesystems in linux, not to mention FAT etc etc.
It is utterly impossible for it **not ** to be a breaking change. It is a design feature of HA and eventually, the component would have been removed had it not been updated as it broke the current design guides for HA. Get over it.
The difference being that Linux and ext2 have a bit more of manpower and users behind them to justify (and actually require) not deprecating things too soon. In Home Assistant, there’s breaking changes all the time. Even more so in integrations that have one or very few maintainers. The breaking change was due to the old integration not having uuids which was not good, now this is fixed. So the code now adheres to better standards and the checks HA website 277 active users will have to deal with it.