I have over 20 Aqara devices, paried to an E1 hub. I have just installed the S1 Magic Panel which has a more advanced hub than the E1, so I want to migrate all my devices to the S1. However in the Hub Migration option in the E1 device settings, my S1 doesn’t appear. Has anyone managed to migrate devices to the S1 without manually unpairing and repairing each device? I fear this manual method will also lose all my automations.
4 Likes
Hello @mrphil
S1 plus does not support migration, you cannot migrate from E1 to s1 plus.Perhaps in the future more hubs will support migration.
4 Likes
I’m having the same problem right now. I want to migrate devices from an E1 hub to the G5 Pro Camera Hub.
When I try to do this with the E1, I can select “Hub Migration”, but then “No hub available” is displayed, so I assume that the G5 Pro is not supported either. If it is supported, please contradict me. I hope it works somehow! 
As an alternative, I have started removing every sensor from the E1 and adding it to the G5. The name and settings of the card are obviously restored. I only had to correct the room assignment. Automations with the sensors in the Aqara Home app also seem to be retained without me having to do anything, which is great. However, I think automations in Apple Home are lost.
I also use the Matter add-on from Home Assistant. It doesn’t always seem to be the same there. My temperature sensor was reassigned to HA without any problems after the migration, but my window contact was not.
So, I still have some work to do. 
When a migration is not possible I have found the easiest way of migrating was to press 3 times on the new hub to put into manly pairing mode (not sure panel S1 can do this).
I then remove the device from the app which generally places the devices back into pairing mode (powered only normally).
The hub in manually pairing then brings the device back in with same name etc.
For end devices like sensors I repeat the process but press and hold the reset button on the device that removed if from the original hub and again is picked up by the destination hub in manual pairing mode.
Additional advice do all the powered devices first, leave the end devices till after all powered devices are back on the system.
3 Likes
Thanks for the tip! I’ll give that a try!
Unfortunately, I have to correct myself. The automation seems to be set up correctly in the app, but it’s not triggering properly. Specifically, the automation triggered once when the window was closed, even though it should have triggered when the window had been open for more than an hour. However, it didn’t trigger again after the window was opened. It seems as if the sensor attached to the automation is stuck in the ‘open’ state.
Just edit the automation and save it should refresh it
1 Like
Thanks again. After saving, the “Execute Gateway” is also corrected from E1 to the G5 Pro hub. Very nice.
Thanks for the replies, I’ve learned a few new things. I went ahead to test a small number of devices (2 smart switches and a door sensor) by migrating them from the E1 to the S1, but I was surprised to observe that the performance was a lot worse.
My assumption is that I now have 2 separate Zigbee mesh networks, therefore the 3 devices I migrated are in their own mesh, with all other 17 devices on their own ‘stronger’ mesh. But this is just an assumption. Is anyone able to confirm?
Just migrating those 3 devices took 30 mins (uncluding documenting automations as backup and reconfiguring Apple Home etc)… therefore I fear of spending a few hours migrating all other 17 devices to find that there was no benefit.
The issue I’m trying to resolve is the following… One of my H1 smart switches is in “decoupled” mode, and it remote controlls the second H1 via an automation within the Aqara app (IF - THEN automation). It takes almost 2 seconds for the automation to trigger when I press the switch. Far slower than a door sensor automation, which feels instant. My suspicion was down to the E1 hub, and migrating to the S1 hub would lower the latency. But the S1 was worse so I’ve had to migrate the devices back to the E1 
Have you tried deleting and redoing your automation or disabling the automation and created a new one first?
I migrated some devices from an E1 to an m 100 hub and the m100 was noticeably slower than the E1.
Perhaps your S1 panel is using the same processor as the m100 Hub