Oops, 2016.. 
1 Like
Same here, way too many devices and flows to start over
+1
+1
Would like to have SHS the main brain using my homey bridge
I have SHS installed using VMware Workstation for backups etc. There is just way to many devices and flows setup on my Homeypro 2023 to transfer it all at once but for now to do some testing, i will start by moving the WIFI and LAN Devices first since they are easy to reinstall and leave my Zigbee and Zwave for last since i have a lot of those in my flows.
I hope someday they also make all deleted devices still show up in the flows so you can remember why and what you were using it for when you see the outline of “ ? CARD unavailable “ 
1 Like
+1
+1
+1
- Migration from Homey to SHS: ideally on a flow by flow basis. I have just installed SHS and it would be a shame if a migration would erase new flows on SHS.
- Please include a migration option from SHS to Homey
- @Peter_Kawa After migration to SHS, I would like to use my LAN-connected HP2023 as a satellite for z-wave: maybe perhaps HomeyLink is workable or does it add too much delay?. This would be much better than Homey Bridge and give me some time to slowly migrate from 50+ z-wave devices to matter devices.
- Please include SHS backup/restore to Homey cloud (with subscription as with HP today) or Google drive or NAS.
+1
There just needs to be a clear pathway and direction of the SHS platform.
Personally new to the Smart Home Environment and recently looked at Home Assitant and Homey.
I went with Homey due to the ease of use. But always thought a open software architecture to be run on an server would be better for speasd and space.
But bought a Homey Pro and Homey Bridge. Personally I would love an easdy way to use them both… I am sure it is either possible now or in the future.
+1
+1
+1
Won’t happen I presume, it’s all or nothing. BUT you can export new flows as JSON, and import those after the possible-to-be-published migration.
HomeyLink doesn’t add a noticable delay in my setup (Pro1 < > Pro2), it uses local connection when both Homeys reside in the same subnet.
As example,
Zigbee2mqtt devices < > wifi < > Homey
responds even quicker than native Pro 2019 zigbee. When using LAN for z-wave I can’t imagine it adds a noticable delay.
SHS is just a (few) file(s), probably already auto-included in your server backup job.
Otherwise you could add a separate backup job for it, or you can use snapshots (if available on your SHS flavour).
1 Like
+1
+1
+1
+1
+1
+1
+1
