emoncms integration is not creating unique ID's for feeds/sensors

[MikeBookham]

The problem

The sensor feeds are not allocated a unique ID, therefore cannot be edited in the Entities list under Settings, the following message is shown:

This entity ('sensor.emoncms_energy_calculated') does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.

I can work around this by using the MQTT (http://homeassistant.local:8123/config/integrations/integration/mqtt) integration and creating all of my own sensors with unique ID's instead of using the emoncms integration.

It appears that the file:

• homeassistant/components/emoncms/sensor.py

needs re-work to resolve this

What version of Home Assistant Core has the issue?

core-2023.12.4

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @borpin, 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)}}

[devdems]

This fix is really needed for the integration.
@borpin @ArnyminerZ would you be able to make the update?

[ArnyminerZ]

I may be able to work on it, but only from mid-late february, I'm pretty busy with exams until then. If @borpin wants to take the lead though, feel free to 😉

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.