Migration of devices from Homey (Pro) to Homey Self-Hosted Server

[mbnn]

Hello there,

First of all thank you so much with Self hosted server it makes even more options
Immediatelly installed it on my Mac mini at home.

I have a Homey Pro which is using z-wave, zigbee and thread, is there a way to migrate devices to Self hosted server yet? Would be awesome to be able to use the Homey pro as extender/z-wave/zigbee and other antennas for SHS.

Thank you

[JohnK]

And can we turn a HP2023 into a bridge?

[mbnn]

That is what I was thinking indeed

[Emile]

At this time, there’s no way to transfer your settings.

Maybe in the future we’ll consider bringing the optional paid backups service to Homey Self-Hosted Server.

[mbnn]

Would be very cool and handy to move things from Homey X to SHS and keep specific things like z-wave/zigbee, aka use the Homey hardware as bridge and move things to SHS Thanks.

[Henk_Renting]

I would definitely like a way to migrate from HP23 to HSHS.
If it only were for flows, wifi devices, etc.
Not using Z-Wave, Zigbee (gor Z2M for that) and Thread here. And other ptorocols only very minimal.

[JohnK]

@Emile and what about turning a HP2023 into a Homey bridge? (Also useful to know when buying an new HP2026). This would align Athom in responsable ecologic ethics to limit waste…

[TKroon]

I get your point. But you could easily sell your Homey Pro and buy a bridge if needed.

[Martin_Ahlert]

Without a transfer of settings it is a horrible work to setup SHS again and SHS is worthless
This will hinder me to purchase a licence for SHS.

[Z0tteke]

So i think it’s great there’s finally a SHS function! But i’m a little bit dissapointed….

I was noticing my Homey pro 2023 was more and more “offline” in the app where it was actually just running. And sometimes flows that always worked fine had sometimes hard times doing what they needed to do. Checked memory and there it was: 356.2 MB free
I’ve got a NAS that i could use for the SHS. More space but especially more RAM.

I almost switched to a new rpi board because of the memory issue untill this SHS announcement came. Great news!
My idea: keep all devices on the homey pro 2023 connected and move all other stuff, flows and apps, to the SHS.

BUT…. There’s no migration option:

So i guess here i am to ask for that migration function?

[Henk_Renting]

Vote here:

Vote here for a migration option to Homey Self-Hosted Server

Add your +1s here

[ricercar]

Emile,
SHS is really a good idea but can’t be used by HomeyPro users who have spent hundreds of hours to tune their server. I, for one, have 2HomeyPros with 100+ devices and 50+ flows each and it is out of question that I redo the hard work to use SHS though I’d like so much to do so.

[Z0tteke]

Geez, what a setup xD
But some people already mentioned you can use a homey link app to link to the homey pro. But i haven’t tested it yet.

Now i’m thinking about it: i wonder why the devs didn’t think of a way to migrate in the first place.

[Peter_Kawa]

@Henk_Renting

flows

It’s some work but doable:

Homey Self-Hosted Server (Pre release analysis)

Most probably the flow im-/export functionality works, tested with Pro 2026 and SHS @ linux+Docker [Screenshot_20251217_174501_Google] EDIT: You’ll need a keyboard with an “ALT” key to activate the additional menu items. For Android, a BT or USB keyboard does the trick. To import, hit the ... on the right of a flow folder.

.

@Henk_Renting

wifi devices

You could install the network-using apps + devices on Homey SHS, add them back to Homey Pro per HomeyLink, and repair the flows:

Homey Self-Hosted Server (Pre release analysis)

You just install the related apps to SHS; The apps’ devices should be added yourself again; Because the devices will get different ID’s, you can replace the ‘old’ with the ‘new’ devices in your flows, with this super script by Martijn. → it works in both API playground & Homeyscript. So it’s important to save all device ID’s and -names of the Homey Pro on beforehand.

[ricercar]

I’ve tried that but

• the strain is still on HP23’s CPU and memory
• exporting HP23 flows and importing them into SHS doesn’t work since the devices ids are different

…and I am NOT going to include 100+ devices into SHS

[Peter_Kawa]

@ricercar

since the devices ids are different

Did you even try?
Why would Athom add export and import flow functionality? Usually you don’t export and then import on the same Homey.

Of course you’ll need to fix the flows afterwards to replace the device ID’s.
With the aforementioned script.

[ricercar]

I beg to differ if you consider THAT as having successfully imported a flow

I wouldn’t say it doesn’t work if I didn’t try before (with HomeyLink devices imported in SHS).

[Peter_Kawa]

It’s OK. You like to focus on the negative and impossibilities as it seems (forumwide), I rather like to see what’s still possible given the circumstances.
That said:
Possibly the Flow Exchanger by Arie J. Godschalk is a better tool for this.
It can replace devices & variables on the fly during the import process.

Don’t get me wrong though, I don’t say a migration tool is not needed! But Athom usually takes one step at a time.
Maybe you recall there wasn’t a 2019 - 2023 migration possible at all at the Pro 2023 introduction. After many requests a migration possibility was built.

@Emile

Tiny FAQ

Q: Will I be able to migrate from my current Homey Pro (2016 — 2019) to the new Homey Pro (Early 2023)?
A: This was planned to become available after launch. But reading the comments, maybe we should prioritise that

[ricercar]

“Without the right to criticize, there can be no sincere praise.” (Beaumarchais, Le mariage de Figaro)

SHS is a one of the best things Athom has developped and your gracious comment would have hit the mark if it was not a paying version but a free alpha or beta version open to users suggestions about material extensions…

I don’t know to whom it is meant in its current state : It’s a complex solution if you’re a noob since you have to install the sofware and use a bridge which fails the purpose of having an independant server and is pretty limited. You’re better off buying a mini-HP.

One would have at least expected it open to external Zigbee, Zwave, Matter…controlers and/or using HP as a “bridge”…and I have no doubt Athom will provide those in future versions…and I don’t expect those who have spent months honing their HP’s devices and flows to undo their work in order to switch to a (current) limited server without proper external radio devices.

As to Arie’s tools, they do a life-saving job with a few flows/devices but are not tailored to tens of them and wouldn’t be of any use due to the current limitations (limitations of the bridge or having to rely on Homeylink which uses HP’s CPU and memory).

A migration tool is indeed needed as you mention but it won’t be enough if you have to rely on a bridge or HA to have it running

To sum up my first impressions about SHS : great innovation but lacking essential items in order to be on the market

[J273]

Yeah agree with that. Hopefully they’ll allow you to use external dongles in the future without the need of the bridge. Homey pro and the bridge have poor zigbee performance imo.

You’re getting decent performance with the OS hosted on your own hardware but lacking the zigbee/zwave performance which is a shame.