Andrea G.

Results 25 comments of Andrea G.

https://github.com/ottoszika/node-red-contrib-ewelink/issues/110

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 ![image](https://github.com/user-attachments/assets/1ba4935c-7c27-4cfc-90da-8c7430b5def6) ![image](https://github.com/user-attachments/assets/b7675398-c89b-4a6a-bdca-0c13f0b1ee9c) ![image](https://github.com/user-attachments/assets/0a2376d9-7e8c-444e-82b6-b2980e4fc948)

Yes, I tested it and confirm that it takes the form sensor.friendlyname ![image](https://github.com/user-attachments/assets/53952043-6dd1-41be-837e-12971b69b49a) ![image](https://github.com/user-attachments/assets/f1c90b0d-6b44-40d8-9c82-00c8f37939fe)

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...

Currently I solved it by deleting and reconnecting the device on the ewelink App and disabling the Energy entity. For now I prefer not to touch anything anymore. However I...

> > Currently I solved it by deleting and reconnecting the device on the ewelink App and disabling the Energy entity. For now I prefer not to touch anything anymore....

@vegos In my case it kept deactivating until I disconnected and reconnected on the App. The strange thing is that I have been using it for 3 years without problems...