Trouble getting zigpy_znp to install

[caylor93]

I'm trying to migrate from a Conbee II to a Nortek HUSBZB-1. I have tried this on my production HA OS 7.2 and also on a clean install of the HA OS 6.6 both using a SD Card in a RPI-4B.

I have tried to install this following the directions located here:
https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#network-backup-beta

Also tried bellows following directions located here:
Both fail with the following error: errors:

error: command 'gcc' failed: No such file or directory
ERROR: Failed building wheel for pycryptodome

Any thoughts on how to get past this is greatly appreciated.

[puddly]

You probably can't do this from within HA OS if it doesn't provide a C compiler. Set up a Python virtual environment on any other platform, there are installation instructions at the top of the documentation you linked to.

Migrating to a HUSBZB-1 is a little tricky because its IEEE address can only overwritten one time (unless you have access to a hardware debugger to completely re-flash it). It's also beta quality so it should work but I haven't fully tested that exact codepath.

All of the new migration code is tracked in zigpy/zigpy-cli#2. Follow the instructions in that pull request after setting up your Python environment to create a backup of your Conbee.

Open up the backup JSON file. If the network key frame counter is 0, your Conbee is running old firmware and should be upgraded to the latest and the backup should be performed again.

Edit the backup JSON file and add the following stack_specific key to it, in order to replace the HUSBZB-1's IEEE address with the Conbee's:

{
  "metadata": {
    ...
  },
  "stack_specific": {
    "ezsp": {
      "i_understand_i_can_update_eui64_only_once_and_i_still_want_to_do_it": true
    }
  },
  ...

Finally, write the backup JSON to your HUSBZB-1:

$ zigpy -vv radio ezsp /dev/serial/by-id/... restore deconz.json

At this point, the Conbee cannot be used in proximity to the HUSBZB-1 because it would be forming an identical network. If you want to re-use the Conbee at your home, edit the backup JSON yet again and slightly change the IEEE address of the coordinator (e.g. increment the last octet by 1), the PAN ID, and the extended PAN ID. Then restore it to the Conbee.

Let me know if you have any questions or if something doesn't work. You're the first to try this migration so I'm hoping everything works 😄.

[Hedda]

I'm trying to migrate from a Conbee II to a Nortek HUSBZB-1.

@caylor93 Have you also upgraded firmware on the Nortek HUSBZB-1 before getting started? See tools in https://github.com/walthowd/husbzb-firmware and maybe even later versions from https://github.com/grobasoz/zigbee-firmware/tree/master/EM3581/%40walthowd

Also, while off-topic I'm wondering why you are migrating to Nortek HUSBZB-1 which is based on an old EM3581 chip that is today considered obsolete by Silicon Labs for new implementations. Though it should still work fine if use newer firmware than it ships with, it would be more future-proof to buy a Zigbee Coordinator with a newer chip. I can however not advise on a newer Silicon Labs based Zigbee Coordinator adapters as Silabs has suffered during the current worldwide chip shortage so availability is scarce (but I read that Elelabs is planning on releasing new models soon to replace their existing models).

[MattWestb]

deCONZ is not so "user friendly" but good hardware with payed "without prepared" support for end users.
HUSBZB-1 is old but its still running strong and i thing you cant finding one better power / reliever Zigbee chip and its also is having one OK ZW chip and its normally very stable and is not so tricky with interference from USB 3 and so on.

Its little as baying one Audi Q7 (2023 model) for chopping in the city then one A1 (2010 model) is more then enough and is much easier to parking.

[caylor93]

why you are migrating to Nortek HUSBZB-1 which is based on an old EM3581 chip

I was trying to get down to a single dongle for Zigbee and ZWave. Didn't look at the firmware or think to consider that the chip might be older. I'm about 80% through a manual migration of both Zigbee and ZWave networks. Gave up on trying to migrate the way puddly recommended.

[MattWestb]

The original Zigbee firmware is normally old and have some nasty bugs so upgrade it to EZSP 6.7.8.0 or test the newest if you like but its not tested so much and is not flagged stable.

Also if you is having good routers around you can blocking the coordinator having direct children so end devices must using routers and not getting problem then the coordinator is offline.

zha:
  zigpy_config:
    source_routing: true
    ezsp_config:
      CONFIG_MAX_END_DEVICE_CHILDREN: 0

PS: You must have least one router joined before you is doing this setting or you cant joining any devices at all.

[Hedda]

I was trying to get down to a single dongle for Zigbee and ZWave. Didn't look at the firmware or think to consider that the chip might be older.

Ah, you are going by the old "a jack of all trades is a master of none, but oftentimes better than a master of one" saying. While that does sound like a good idea on paper it is generally a relatively bad idea in practice, especially when it comes to MCU radio adapters for IoT low-power communication protocols. At least the best practice today is to have one MCU radio USB adapter per protocol.

I would not recommend Nortek HUSBZB-1 for a new purchase, however the old EM3581 chip used for Zigbee in it still keep up with the latest firmware can all Zigbee 3.0 devices released so far in the world, but the firmware is no longer getting new features and new functions so it will not be future-proof, however, it is easy to backup your Zigbee network to file and restore that to newer hardware with a newer Zigbee chip.

But you should know as well that Nortek HUSBZB-1 does also not have the latest Z-Wave chip. I only have a Z-Wave 500 series chip for its Z-Wave Controller, and the latest chips today is Z-Wave 700 series chips so again it is not future-proof. New devices using Z-Wave 700 series chips are backwards compatible with a Z-Wave 500 but you will not get all the benefits (like longer range and better battery management), however, it is easy to backup your Z-Wave network and restore that to new hardware with a newer Z-Wave 700 chip.

PS: If you are looking to try out more protocols in the future then keep in mind that will soon probably want a third MCU radio USB adapter for the new Matter over Thread protocol standard, (it will require a MCU radio USB adapter based on a new chip that supports OpenThread, which also happen to be the same type of newer MCU radio chips that can also support Zigbee 3.0 if just using a different firmware).