Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration from Conbee to Conbee II #1441

Closed
steeriks opened this issue Apr 18, 2019 · 4 comments
Closed

Migration from Conbee to Conbee II #1441

steeriks opened this issue Apr 18, 2019 · 4 comments
Labels

Comments

@steeriks
Copy link

Hi,

What is the recommended way to migrate from Conbee to Conbee II?
I asume I have to reset all devices and repair it with the new gateway. Or is there an easy way to do it?

@manup
Copy link
Member

manup commented Apr 18, 2019

I asume I have to reset all devices and repair it with the new gateway.
This for sure is the most clean way.

There is one simpler way (cloning).

Two important notes:

  1. There is no Zigbee related technical advantage in replacing ConBee with ConBee II
  2. After the following cloning procedure the ConBee can't be used next to ConBee II since they are clones on Zigbee level and would fight each other. This can only be fixed by assigning a new or random mac address in deCONZ.

Cloning

  • Pull out the ConBee and replace with ConBee II (must be on the same machine).
  • In the Phoscon App gateway settings open the hidden Zigbee configuration page and load the last configuration, this is shown in the following release notes

https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_59

After this ConBee II should use the same Zigbee network parameters as the setup of the ConBee.

@steeriks
Copy link
Author

Thanks,

will make it a try :-)

@ooii
Copy link

ooii commented Jul 24, 2019

Hi,

Pull out the ConBee and replace with ConBee II (must be on the same machine). is that supposed to be done while deConz is running?

@stale
Copy link

stale bot commented Nov 21, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants