# Migratie Homey (Pro) (Pre-2023) naar Homey Pro (Early 2023)

**URL:** <https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694>\
**Category:** Vragen & hulp\
**Tags:** homey-pro, homey-pro-2023\
**Created:** [February 20, 2023, 2:53pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694 "2023-02-20T14:53:28Z")\
**Posts on this page:** 19\
**Page:** 2

<div class="post-metadata">

**Author:** ![JeeHaa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeehaa/32/29849_2.png) [@JeeHaa](https://community.homey.app/u/JeeHaa)\
**Post date:** [March 8, 2023, 11:53am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/21 "2023-03-08T11:53:44Z")

</div>

I have a HP2019 with mainly Zigbee devices using the Deconz app (so not native Homey Zigbee), but also Somfy RTS and a couple of wifi devices. On HP23 I would like to switch to using Homey native Zigbee (bulbs) and apps like Aqara (sensors) and Tuya (plugs).

Ideally I’d like to keep all advanced flows & Vars on the HP23, even though they might be broken. From there I would start moving sets of related functionality to HP23 by reconnecting zigbee devices one by one to Homey. For example sets of lights + motion sensors first.

I am curious if someone knows if this is a feasible scenario, without initially loosing functionality on the old Homey? If this gets too messy I guess I’ll just take a day off when nobody is at home and start from scratch. 🙂

BTW: How is zigbee stability in general on the HP23 (Aqara motion + generic bulbs)?

**[Update]** Performed the migration to HP23 in the mean time, works as expected. Just replaced all the failed Deconz devices by re-adding them to Homey.

---

<div class="post-metadata">

**Author:** ![Menne\_Talsma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menne_talsma/32/8752_2.png) [@Menne\_Talsma](https://community.homey.app/u/Menne_Talsma)\
**Post date:** [March 20, 2023, 11:06pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/22 "2023-03-20T23:06:46Z")

</div>

How did you do that test-migration? I have a HomeyPro Backups account so first thing I treid was tried a HomeyPro-2019-Backup onto my HomeyPro-2023.

That didn’t work wel, every device got a little red triangle and nothing worked. (This was 5 days ago)

How did you manage to get (some) devices working?

---

<div class="post-metadata">

**Author:** ![Slof](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/slof/32/1318_2.png) [@Slof](https://community.homey.app/u/Slof)\
**Post date:** [March 21, 2023, 6:12am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/23 "2023-03-21T06:12:59Z")

</div>

And @JeeHaa how is the Zigbee behaving?

---

<div class="post-metadata">

**Author:** ![JeeHaa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeehaa/32/29849_2.png) [@JeeHaa](https://community.homey.app/u/JeeHaa)\
**Post date:** [March 21, 2023, 8:32am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/24 "2023-03-21T08:32:10Z")

</div>

In general great, but some Aqara motion sensors skip detections every now and then during the evening. But I suspect this is due to wifi interference (neighbors wifi is on Ch1, I had this with deconz as well). I’m waiting for the zigbee channel change option te become available in developer settings on HP23 to change zigbee Ch11 → Ch15.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [March 21, 2023, 9:41am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/25 "2023-03-21T09:41:09Z")

</div>

> [@Menne\_Talsma](#):
>
> How did you manage to get (some) devices working?

Just the same as you, i migrated with a backup, pulled the old out of the power and let the new one boot up.  
Most of my devices did not have a triangle, altho i must admit, i didn’t really test all devices and apps, just checked generally the availablility.

This was with the earlier rc version.

I haven’t tried a migration in a while now.

---

<div class="post-metadata">

**Author:** ![Robin\_De\_Lange](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_de_lange/32/25173_2.png) [@Robin\_De\_Lange](https://community.homey.app/u/Robin_De_Lange)\
**Post date:** [March 21, 2023, 4:51pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/26 "2023-03-21T16:51:55Z")

</div>

ik ben gister gemigreerd naar HP23, mijn apparaten en flows/logica zijn netjes over genomen. echter nu zie ik dat de “normale flows” niet aanpasbaar zijn of getest kunnen worden. ook doen sommige flows niks, ik laat bijvoorbeeld mijn licht schakelen op een logica en bij het omzetten van de logica gebeurd er niks.

bij het aanpassen/testen van de flow geeft hij de melding: ontbrekende droptoken

iemand dit ook gehad en een eventuele oplossing?

---

<div class="post-metadata">

**Author:** ![Twan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/twan/32/63153_2.png) [@Twan](https://community.homey.app/u/Twan)\
**Post date:** [March 21, 2023, 5:10pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/27 "2023-03-21T17:10:21Z")

</div>

Misschien een doekje voor het bloeden: ik heb hetzelfde probleem.

---

<div class="post-metadata">

**Author:** ![Ranney](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@Ranney](https://community.homey.app/u/Ranney)\
**Post date:** [March 21, 2023, 6:35pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/28 "2023-03-21T18:35:15Z")

</div>

Bekend probleem in de webinterface. Of het ‘corrupte’ onderdeel van de flow vervangen of in de app doen. Daar kan het wel. (Mijn ervaring)

---

<div class="post-metadata">

**Author:** ![Robin\_De\_Lange](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_de_lange/32/25173_2.png) [@Robin\_De\_Lange](https://community.homey.app/u/Robin_De_Lange)\
**Post date:** [March 21, 2023, 6:37pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/29 "2023-03-21T18:37:18Z")

</div>

jaa ik probeer dit voor sommigen werkt dit inderdaad. voor andere weer niet.

nu zie ik ook dat sommige Tags wel in de Webapplicatie aanwezig zijn en via de mobile app niet aanwezig zijn. heb alles wel doorgespeeld naar Athom.

---

<div class="post-metadata">

**Author:** ![Ranney](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@Ranney](https://community.homey.app/u/Ranney)\
**Post date:** [March 21, 2023, 6:38pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/30 "2023-03-21T18:38:44Z")

</div>

Ook herkenbaar. Dit heb ik opgelost door te switchen van ‘lokale labels’ naar de universele labels. Die die werken hier wel. Misschien kun je dat proberen?

---

<div class="post-metadata">

**Author:** ![JeeHaa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeehaa/32/29849_2.png) [@JeeHaa](https://community.homey.app/u/JeeHaa)\
**Post date:** [March 21, 2023, 6:41pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/31 "2023-03-21T18:41:03Z")

</div>

Ik moest alle variabelen na de migratie eenmalig eenmalig opnieuw opslaan in de web UI (Klik - Enter), daarna werkten der flows weer. Maar wellicht was dat net een ander issue.

---

<div class="post-metadata">

**Author:** ![Robin\_De\_Lange](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_de_lange/32/25173_2.png) [@Robin\_De\_Lange](https://community.homey.app/u/Robin_De_Lange)\
**Post date:** [March 21, 2023, 7:27pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/32 "2023-03-21T19:27:19Z")

</div>

> [@Ranney](#):
>
> switchen van ‘lokale labels’ naar de universele

Ja heb dit al bekeken maar in de telefoon app, staan deze tags helemaal niet in de logica.

Maar heb nu via webapp ingesteld en dan doet die het wel. Maar geeft wel foutmelding op de app

> [@JeeHaa](#):
>
> migratie eenmalig eenmalig opnieuw opslaan in de web UI

Ga ik nog ff proberen dankuu

---

<div class="post-metadata">

**Author:** ![Menne\_Talsma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menne_talsma/32/8752_2.png) [@Menne\_Talsma](https://community.homey.app/u/Menne_Talsma)\
**Post date:** [March 21, 2023, 8:24pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/33 "2023-03-21T20:24:35Z")

</div>

Nope unfortunately peanutbutter,

 ![Schermafbeelding 2023-03-21 om 21.18.47.png](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/7/17d6aea9cf5d36a959e47c275fcf132492deae1d.png)

Only some wifi devices such as sonos and Eufy robovac are responding  
Rest (70 devices) need to be re-paired…  
thats gonna be a job for a rainy Sunday…  
☹  
but thanks for helping

---

<div class="post-metadata">

**Author:** ![Articate](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/articate/32/57311_2.png) [@Articate](https://community.homey.app/u/Articate)\
**Post date:** [March 31, 2023, 2:34pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/35 "2023-03-31T14:34:05Z")

</div>

This is down to Zigbee being Zigbee. Z-wave works, and is simply copied over. As I understand Zigbee, there just isn’t a way to migrate without building up the Zigbee network anew. So it’s sadly just a shortcoming of the protocol, not anything Homey could help.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [March 31, 2023, 3:22pm UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/36 "2023-03-31T15:22:58Z")

</div>

> [@Articate](#):
>
> So it’s sadly just a shortcoming of the protocol

It isn’t a shortcoming of the protocol itself, it is because the chips used differ too much that a migration is just very very hard without re-pairing any devices.

---

<div class="post-metadata">

**Author:** ![Articate](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/articate/32/57311_2.png) [@Articate](https://community.homey.app/u/Articate)\
**Post date:** [April 1, 2023, 10:21am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/37 "2023-04-01T10:21:34Z")

</div>

Thanks for the clarification. I guess I’ve never had a smooth experience with these types of changes with Zigbee, so I assumed something makes that harder than for, say, Z-Wave. Most of my Zigbee devices are IKEA, so I don’t know if it’s IKEA that sucks, or Zigbee, though.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 1, 2023, 10:48am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/38 "2023-04-01T10:48:51Z")

</div>

> [@Articate](#):
>
> I guess I’ve never had a smooth experience with these types of changes with Zigbee, so I assumed something makes that harder than for, say, Z-Wave.

There are more manufacturers of Zigbee SoC’s, and moving between different manufacturer SoC’s usually can’t be done without having to create a new network because of driver differences.

---

<div class="post-metadata">

**Author:** ![B3rt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b3rt/32/9435_2.png) [@B3rt](https://community.homey.app/u/B3rt)\
**Post date:** [April 10, 2023, 10:51am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/39 "2023-04-10T10:51:33Z")

</div>

een kennis van mij heeft de nieuwe homey in bestelling staan, hij heeft recent een mail onvangen dat de migratie problemen van een 2019 naar 2023 model zijn opgelost.

Wat er is opgelost staat niet in de mail, maar weet iemand wat dit inhoud?  
Bedoelen ze hiermee da je nu WEL zigbee devices kunt restoren/migreren vanaf je 2019 model naar dit moel zonder dat je hoeft te repairen?

Dit laatste hebben ze namelijk wel verteld dat dit zou kunnen maar nog niet direct bij de release…

Iemand een idee/ervaring?  
(het niet migreren van zigbee is namelijk 1 van de redenen dat ik hem nog niet besteld heb)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 10, 2023, 10:56am UTC](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694/40 "2023-04-10T10:56:23Z")

</div>

> [@B3rt](#):
>
> Dit laatste hebben ze namelijk wel verteld dat dit zou kunnen maar nog niet direct bij de release…

Niet dat ik me kan herinneren. Wel dat ze het wilden _proberen_ werkend te krijgen, maar gezien de zeer verschillende hardware tussen de oude en de nieuwe Homey is dat praktisch onmogelijk.

[Previous page](https://community.homey.app/t/migratie-homey-pro-pre-2023-naar-homey-pro-early-2023/76694.md?page=1)
