# Homey pro 2023 - zwave too much traffic error?

**URL:** <https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036>\
**Category:** Questions & Help\
**Tags:** z-wave, homey-pro\
**Created:** [July 5, 2023, 9:16pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036 "2023-07-05T21:16:23Z")\
**Posts on this page:** 1\
**Showing post:** 440

<div class="post-metadata">

**Author:** ![Jonathan\_Draper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_draper/32/33978_2.png) [@Jonathan\_Draper](https://community.homey.app/u/Jonathan_Draper)\
**Post date:** [September 8, 2023, 3:50pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/440 "2023-09-08T15:50:59Z")

</div>

It was standard practice during early access phase [[HowTo] Homey Pro (Early 2023) - Migrating from Homey (Pro) (Early 2016-2019) (With Early Access) - #16 by Cuprani](https://community.homey.app/t/howto-homey-pro-early-2023-migrating-from-homey-pro-early-2016-2019-with-early-access/77516/16)

My understanding of how this works is that the migration from 2019 → 2023 means that the z-wave network on 2023 is an exact carbon copy of the z-wave network on 2019. So the 2023 doesn’t “take over pairing of your devices”; as far as the devices are concerned, it _is_ your old z-wave controller. This is also why you cannot have both the 2019 and 2023 powered on at the same time after migration without serious issues - you would essentially have two identical controllers trying to run at the same time.

---

_[View the full topic](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036)._
