I am trying to follow your first post but I dont have access to the following directories
I do not have the “.” directories.
The lowest level that I have and my ( non dot) Home Assistant directories are attached.
I was also trying to folly remove Shelly4hass earlier ( I am running a second test machine) but had the same issue that it requires accessing the “.” directories.
Can you please let me know how i can access this ?
When trying to remove shelly4hass i remover manually all of its files but that was not good enough to enable the native integration .
Thank you for your help
Jeremy
in .homeassistant/.storage/core.config_entries:“domain”: “shelly4h”,
and
“title”: “Shelly4hass”,
in .homeassistant/.storage/core.device_registry:
“identifiers”: [[“shelly4h”,…]]
in .homeassistant/.storage/core.entity_registry:
“platform”:“shelly4”
in configuration.yaml:
shelly: → shelly4h: (if you have that)
i am trying to migrate my shelly4hass to native integration
after doing all the changes
indeed i can see 2 shelly integrations
however i seems my old shelly entities exist but no longer available
and now i got new entities with default shelly names such as (switch.shelly_XXX before it was switch.parents_room_main_light)
so now i have both
switch.shell_XXX (working)
and
switch.parents_room_main_light (unavailable )
any ideas why this might happen?
note that when i added the shellys devices back in the day i did change the entity ids to meaningful names such as switch.parents_room_main_light
If HA is still running, it will overwrite your changes. I will not work. You have to edit the files without HA running. How to do this depends on your configuration and installation method.
Interesting ! Givne the unti is on then HA will be running , and I would have no idea how to edit the files other than via file editor!
Given this is a total show stopper I have to find a way to do this so if anyone who has done it can tell me how i can edit the files but not have the system running I would appreciate it
I miss one feature from shelly4hass that is not in the HA integration. Shelly4hass can listen to double click on the shelly dimmer, and the HA integration cannot do this. Anyone know a workaround I can do in the HA integration do get double press working?
So … I managed to get both to show even with HA running. First step forward.
The Shelly devices all show and have the option to add. Great.
The Shelly for hass now has double the devices. The old devices with names ( which are all unavailable ) and then a new set of devices it has discovered with the native names dimmer 95994560r059 etc .
I need to change the enity ID to the same as the existing entity or the automations will all need rewriting.
Change the entity ID to the old one and it says already exists. Fair enough. Goto the old entity and change it. Go back to the new one and change it to the old one - still the same error that the entity already exists. No it doesnt!
The only way round this would then seem to be to delete Shelly for Hass and from my old system ( I am running 2 systems at present - live and the one to try and sort out this mess) pick up the entity names and edit them .
The issue with this is as far as i can tell i i delete Shelly for Hass then all of the automations go blank as the entity does not exist and this i believe is not recoverable - so I then have to recreate all scene and automations.
My system is large - i have 80 Shelly and some 120 automations and scipts so this is not really a viable option.
Any ideas how to get HA to agree that the entity name has been changed?.
What you did: you just added native shelly integration and shelly4hass was deactivated. If you do it right, shelly4hass and native shelly run in parallel and both work.
Spook is very helpful to find all sorts of things with missing entities (after renaming or similar)
I think your devicemismatch comes from you deleting/reinstalling shelly4hass. i would restore a backup. No such problemswith my 8 shellies.
You could try what naming happens if you change the shelly name in the devices web interface.
