Transition from ShellyForHass to official Shelly integration

Configuration
1

Hi,
I’ve been using ShellyForHass custom integration for quite some, installed through HACS, I now want to change to the official integration which I believe will provide more continuous and durable development.
I’ve updated all my devices and enabled CoIoT with unicast for all of them. I’d like to install the new official integration, and transfer the existing automations/scripts to the new entities. Then once completed remove the custom integration and cleanup.
The issue is that when clicking on “add integration” button, the official Shelly integration is not in the list, other instances of the custom one would be created instead.

How to proceed? Is the custom integration from HACS blocking the new core one? Will the official one appear in the list if I remove the custom from HACS?

Thanks

3 Likes
2

There’s no easy way.

  1. Make a note of all the entity_ids provided by ShFH.
  2. Delete ShFH and any associated config.
  3. Restart
  4. Use the core Shelly integration to add your devices again.
  5. Edit the newly created entity_ids in Configuration/Entities to match the previous ones, if required. These will then align with your previous automations.

If you use device automations it’s even worse. You will have to make a note of your previous device_ids and scan through all your automations replacing them with the new device_ids (a text editor “find and replace” function may help). There is no single place in the UI to edit device_ids like there is for entity_ids.

3

Ouch, I was hoping for a way to smoothen the process and split in more than one go… Instead I will have to do them all in one session otherwise the automations won’t work until I finish…

Thanks for you reply anyway

4

It would be good if there would be any add-on which makes possibility of easy and simple transition from shellyforhass to original shelly integration…

5

are there any news? I also thought to change the integration, but if it is such a huge effort I would not do that until I will have to :wink:

6

I wrote a python program reading the configuration and printing out all shelly devices with their entities.

7

For me it was not that hard.
First say that i first worked with the official shelly integration and then migrated to shellyforHass (because i didn’t know any better).
Then I wanted to migrate back and saw this post.
What I did

  1. I noted all of the entity_ids provided by SHFH (like someone suggested), but I never needed it…
  2. Deleted in the shelly integration all the devices and names provided by SHFH
  3. Went to file editor - custom components - shelly and deleted everything there !
  4. restart
    and it worked. I have all the sensors back that I had with the shelly integration, no more trace on the dashboard of ShFH.
    I noticed that here and there there was still a reference to the sensors of shfh, but when I saw one I deleted it.
    Don’t ask me why this did it for me, I’m no specialist, rather someone of the ‘trial and error’ method :slight_smile:
1 Like
8

how did you delete shellyforhass? I can not do it

9

Thanks for much for posting this. It fixed my Shelly relays too!

10

I did it in the terminal, searched for shelly related files under a folder like ‘add on’ or similar and removed all of them (several directories included)

11

Spent an inordinate amount of time trying to add a gen 3 device to Home Assistant. Deleting a few files and reloading the integration fixed everything. I spent hours trying websocket addresses and MQTT configurations with the mini1g3. Thanks!

12

It is possible to change Shelly4hass to use the domain name “shelly4h” instead of “shelly”. Today I posted how to do that.
Once shell4hass uses domain “shelly4h”, it should be possible to install the native shelly integration in parallel.
Once you have both integrations running, you can migrate 1 device every week.