Just a heads-up for anyone using HA emoncms.
After upgrading HA to 2024.9.3 my emoncms entities have new names which include the local IP address.
I have commented out the config for emoncms. I still have config for emoncms history which is sending some additional properties from HA.
For others - see this thread Home Assistant 2024.10 - update to emoncms core module - Integrations - OpenEnergyMonitor Community
Unfortunately, the old integration did not generate UUIDs which is why these have disconnected. It is an unfortunate side effect, but it is necessary in order to bring the integration in line with the latest designs of HA.
I’d just like to emphasise the level of effort @alexandrecuer has put into this. If you are interested this is the GitHub link Migrate emoncms to config flow by alexandrecuer · Pull Request #121336 · home-assistant/core · GitHub and the number of discussions including one that involved the HA Dev team eventually allowing something they normally don’t (they wanted all available sensors/Feeds imported automatically - they saw sense). There were some other associated changes as well.
This is a major step so many thanks.
Just to clarify, as I was confused when reading this, do you mean ‘After upgrading HA from 2024.9.3’ ? Because I am running 2024.9.3 and my (old school) yaml EMONCMS integration is running OK, and I don’t (yet) see these warning messages or new names with IP addresses.
I’m just doing an analysis on the changes in 2024.10 to see what I have to do in relation to the 36 feeds I am currently passing from EMONCMS to HA before I update.
I too appreciate this effort. Have been looking forward to an enhanced integration process. Those pesky missing uniqueIDs were frustrating.
The upgrade will require me to do a few changes to my setup but sometimes it takes a little work to climb the tree to get a better view 
