emonCMS integration loses names of sensors during installation

[garethhowell]

The problem

When a new instance of the emonCMS integration is added, you get prompted for which sensors to track. However, once added, all sensors have generic names (e.g. emaoncms.domain.org.humidity) and lose the specific sensor name.

What version of Home Assistant Core has the issue?

System Information version | core-2024.10.2 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.46-haos arch | x86_64 timezone | Europe/London config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1505 Downloaded Repositories | 26

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.10.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 30.8 GB disk_used | 26.7 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Grafana (10.1.1), Duck DNS (1.18.0), InfluxDB (5.0.1), Home Assistant Google Drive Backup (0.112.1), File editor (5.8.0), NGINX Home Assistant SSL proxy (3.11.0), AirSonos (4.2.2), AirCast (4.2.2), AdGuard Home (5.1.4), Terminal & SSH (9.15.0), Studio Code Server (5.17.1), Mosquitto broker (6.4.1), MariaDB (2.7.1), ESPHome (2024.9.2), AppDaemon (0.16.7), Glances (0.21.1), HassOS SSH port 22222 Configurator (0.9.3), Docker Wyze Bridge (2.10.3)

Dashboards

dashboards | 5 -- | -- resources | 21 views | 10 mode | storage

Recorder

oldest_recorder_run | 17 July 2024 at 15:45 -- | -- current_recorder_run | 12 October 2024 at 15:52 estimated_db_size | 5908.91 MiB database_engine | mysql database_version | 10.11.6

What was the last working version of Home Assistant Core?

2024.10.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

emonCMS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/emoncms/

Diagnostics information

See attached screenshot

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @borpin, @alexandrecuer, mind taking a look at this issue as it has been labeled with an integration (emoncms) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `emoncms` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign emoncms` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

emoncms documentation emoncms source _{^{(message by IssueLinks)}}

[alexandrecuer]

entity name is now fixed by default as follow : emoncms@{sensorip}-{feed_name}

Previously, default naming, when not fixed by the user, was something like that : EmonCMS{id_for_name} {feed_name} or EmonCMS {feed_name} if you had only one emoncms instance where id_for_name was something defined by the user in the YAML conf which is no more allowed through the UI

Please note you can now change the name manually through the UI if you want to, which was not the case previously (You could only do that in YAML)

If you have lost your stats through the migration, indeed this is known problem but it can be solved : see https://github.com/home-assistant/core/issues/127470

[garethhowell]

Thanks, @alexandrecuer . In that case, there appears to be a bug. The attached image shows what is reported in the Developer/States pane. As you can see, the second part is not the feed name, but rather it is the sensor type - with a suffix where it's the second or third example.

[alexandrecuer]

what is your emoncms version ? can you provide a screenshot if what yu have in emoncms ? in feed/view if feed names are the name, I think HA add a number at the end as the tag was not included in the entity name by the previous version of the integration, I did not add it...moreover some users told me to keep names as short as possible....

[garethhowell]

low-write 11.0.9

[garethhowell]