Closed driagi closed 1 month ago
Is there something wrong with the issue?
What does the state for those two entities show in the developers tools in HA?
They don't exist, but I think they've changed names. For example: from sensor.nr_consumo_totale_2 to sensor.consumo_totale it seems to have changed to the Friendly name
Yes, I tested it and confirm that it takes the form sensor.friendlyname
The first time you create an entity from NR it will attempt to create an entity ID from the friendly name field. If the friendly name field is blank the entity id will default to sensor.nodered_<node id >
. After the entity has been created in HA for the first time, the friendly name field controls only the friendly name in HA. It will not change the entity ID field. That has to be done through HA.
But the entity name changed on day 7 after the update (4.0.1 Comapanion version). I didn't create or change anything, i in fact the energy panel worked well for months until day 7
I have Node-RED version 4.0.2 and I solved reading via API from SolarX in the following way:
This solution works very well, I did it about a week ago and I don't have any problems with it so far, all values are transferred correctly, except that HA shows data at 5-minute intervals, so I think that it would be possible to easily reduce API polling to 1x every 4- 5 min. The green "debug" blocks are only for testing in case of read failure
Solved by renaming the entity
Describe the bug
After updating to version 4.0.1, the Energy panel stopped working (undefined entity) My configuration: Node-Red Companion: 4.01 Core: 2024.7.2 Supervisor: 2024.06.2 Operating System: 12.4
To Reproduce
Expected behavior
No response
Screenshots
Example Flow
No response
Environment Information
Version: 0.65.1
Home Assistant version: 2024.7.2 Companion version: 4.0.1
Node-RED version: 4.0.2 Docker: yes Add-on: no
Node.js version: v18.20.3 arm64 linux OS: Linux 6.6.31-haos-raspi arm64
Additional context
No response