New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming power entity via Integrations page not persistent after restart #257
Comments
Do you have discovery enabled and/or shelly cloud integrated ? Simone |
Hi, |
Thank you for investigating. Anyway list of fixes/enanchement for 0.1.8 is already closed. Simone |
ShellyForHass does not support the renaming of entity_id from integration. I need to have a look at that and see if it can be solved. You can rename the entity_id in config.yaml until fixed. |
renaming the entity_id in yaml will affect all entities coming from that device correct? One of my shelly devices controls couch lights via automation but is actually powering my entertainment center (relay disabled). If I edit the name in yaml it will affect both but I want to specify them separately to sensor level not device level. |
I'm having the same issue with the Shelly 1PM. The switch & total_consumption entities stay renamed but the power sensor goes back to default when restarting HA. |
This is just a note for anyone new experiencing this issue. Upgrading to 0.1.8 does not fix this issue, it was never expected to. I hope the developers include it in the next release. This issue is preventing me from adding a bunch of sensors, shelly or not. Not the end of the world in the short term. |
Using the entity_id: setting in configuration.yaml still will not solve the issue for suffixes. |
@mandelflanders - Same here. Renaming the power entity each time I restart is getting annoying. I've had to turn off a few automations that are expecting these devices to be working. |
Please update to latest beta (0.1.9.b1) and recheck. Simone |
I'm installed through HACS, but I downloaded the beta release... https://github.com/StyraHem/ShellyForHASS/releases/download/0.1.9.beta.1/shelly4hass.zip Extracted into the /custom_components/shelly directory, restarted. Entities changed back to the default names. I updated them again, restarted HA, same result. They changed back to default. |
Please install, upgrade and downgrade always via HACS: FAQ5:-Enable-beta-in-HACS Simone |
Yea, as soon as I posted my message I remembered I could do the beta via HACS. Ok, I've restored back to previous version and I can confirm the previous version is functioning. Will update via HACs. |
After upgrading to the beta, I changed the entity id and name of the sensor. Restarted, it still got set back to the default. Maybe I'll uninstall the integration and start from scratch. |
1 - Uninstalled Integration At that point it started to slowly discover my devices. Doesn't have them all yet, but I can't configure the integration. It doesn't show any text. |
Also, for the devices it did find they didn't retain their entity names or names after restarting HACS. Is there a better way to uninstall? I did it from HACS. Seems like something is cached somewhere. |
@ericvitale Delete the Shelly integration from HA gui and all entries will be removed. |
Yes, I just tried that. I deleted the latest install via HACS and deleted the integration via "Integrations" page. When I click add integration without installing via HACS, shelly shows up in the integration list. Should that be there? |
Also do you recommend installing 1.8 before upgrading 1.9? |
Yes Shelly should always show up under integrations. It does not matter if you install 0.1.8 before installing 0.1.9. |
Same result, setup screens don't have any text. |
Uninstalled, went back to 0.1.8, same thing. Blank text on setup screens. |
I took a backup of my shelly folder before all this started (or I started it). I noticed that the new shelly install does not have a pycache folder. Not sure if that matters or not. |
Do you have the translations folder including en.json? It is strange the pycache is not created. Check permissions on files and folders. |
en.json exists. It was the first thing I checked. I also restored the old shelly folder, same issue. Permissions look like they did before. Here is a screenshot. Also, going to try restarting the whole machine. The other thing that is weird is that it hasn't discovered all of my shelly devices yet. And for the couple it did find, some of them it "remembered" the device names, not the entities and others it didn't. See the other image. I didn't have to rename the Garage Door and Miner08. But the other shelly should should Miner03. |
Restarting didn't help. |
TLDR; Working now Progress... ---Text on the setup page, yay!--- 7 - Setup ran fine. ---Still missing a device--- 8 - Upgraded to 1.9 via HACs --- Entity rename worked, yay! 12 - Renaming the rest now --- I hope for the last time!!! |
Im glad it working for you now! |
Thank you for making the changes. |
When renaming
current_consumption
entities (Name Override & Entity ID) via Integrations Page, everything seems to save correctly, but after a restart reverts again to standard name & Entity IDIssue seems to happen to both
current_consumption
(Wattage) entities of my Shelly EM and not to any other sensors on Shelly EM or Shelly 2.5After naming:
After HA-core restart:
FYI:
Home Assistant 0.108.1
Supervisor v 214
ShellyForHASS v 0.1.7
All settings via Integrations Page
The text was updated successfully, but these errors were encountered: