Nortek Zigbee/Z-Wave Stick with deCONZ

Hey all!

I'm curious --- has anyone gotten their Nortek stick to work with deCONZ? I'm on the fence about ordering one of their Zigbee sticks to do some firmware updates, but would prefer to use the Nortek stick, if anyone knows of a way to get that working :slight_smile:

Or, perhaps someone here knows how to update an OTA firmware via another method that can support the Nortek stick?

Give me a bit, I have another Nortkek stick flying around and can try if it works

1 Like

Thanks! I’ve only tried via Windows 10, so far. I have a few headless Linux setups currently, which don’t allow deCONZ firmware updates, but if it works with Linux I’ll gladly set up a GUI machine and push them out that way :slight_smile:

I am trying to run this docker image


So far, not too much luck connecting to the nortek but still playing with it.
It does state though that firmware upgrade were tested with the conbee stick, it has it's own section in the Readme as you need to start the docker image in a certain way

I'm pretty sure that deconz only works with Conbee, Conbee II and the Rasbee module. Why would you want to flash the Conbee firmware to the Nortek stick? I've been running a conbee for a while now and in all the reading/investigation online I've never seen any documentation about Deconz using another zigbee module.

1 Like

I’m not trying to flash the stick's firmware—I’m doing some flashes to bulbs I have around :slight_smile:

I’ll probably just end up ordering the ConBee—though I was mostly hoping to not need another device to have around with the same purpose as the Nortek.

Yeah, I don't think the Nortek will work with deCONZ...

1 Like

I have a Conbee 2 using the docker image above. You can connect to is over VNC and use the GUI. I have it set to a router and have it joined to my Hubitat network. It maps the Hubitat network.

Also I upgraded the firmware on a Tradfri plug while the plug was joined to the Hubitat network. It was a bit of a challenge as most of the Zigbee devices select the Hubitat as the update server. A few switched to the Conbee but the Tradfri plug wanted to stay with the Hubitat as the update server. I think I disabled the Hubitat radio and unplugged the Tradfri plug and plugged it back in. Then I reenabled the Hubitat radio. The plug then saw the Conbee as the upgrade server. The Conbee lets you read any attribute of a device on the network. There is an attribute with the upgrade server address.

1 Like

Ohh, that’s a good idea! And here, I was dreading removing devices from my Hubitat network...

I'm think it might be faster to remove the device and reconnect but the Conbee was a pain to setup to join the Hubitat network. And I had to reset the plug after the upgrade because it left it in a odd state. I only did one device mostly just to say I upgraded a device while on the Hubitat network but maybe if more people try it can be streamlined.

2 Likes

If you factory reset the device and then pair it to the Conbee to upgrade it, then remove it from the Conbee and rejoin it to Hubitat, that should put the device back into the same "slot" it was in before. You shouldn't have to remove it from Hubitat. That's one of the benefits of zigbee. The address is hardcoded on the device rather than software established when joining to the network.

1 Like

I’ve had Issues with the Iris V1 devices not rejoining properly. I almost always have to factory reset them. :frowning:

Those aren’t what I’m working on, so your advice is super helpful. I’d forgotten all about that.

The end-goal here is to flash some OSRam bulbs to the hue-compatible firmware that they stopped giving to people in the US for whatever reason. They used to help people perform this process, but stopped for whatever reason.

That seems super strange.

One other alternative is to just create a separate zigbee network with your deconz. I am running DIYHue whcih works with the Doconz module so it able to join both ZHA and ZLL devices to it. It then interacts with Hubiat the exact same way that a Hue bridge would. I find this much easier than trying to use a second Hubitat or Hue bridge. DIYHue also supports Tasmota and other esp8266 devices, as well as the Tradfri gateway, the milight hub and others. It can act as a "man-in-the-middle" for a lot of different things. You'll still have the same limitation as far as the Hubitat implementation goes so you won't be able to join sensors to that network and have them show up in Hubitat but it is super useful. I am running mine with 5 different ESP8266 addressable LED strips, 4 Cree bulbs and 3 Sylvania/Lightify Under-Cabinet Lights. You can even run it on a raspberry pi zero w, so it is a very cheap alternative. Or, if you're going to use a regular raspberry pi, you can get the Raspbee module so you don't have to plug anything into the USB ports.

1 Like

Right? They said US Hue compatibility is a year out, but EU devices already have it. It's very strange to me ...

I'll give that a try---thanks for the suggestion! I used DIYHue a while back, but kind of forgot about it. I've been really trying to increase the WAF and fix the bus factor in my home.

1 Like

I was able to upgrade an old Osram Lightify (US market) bulb that had the 0x01020492 firmware to 0x01020509. I believe the bulb is now ZLL and not ZHA. I do not have a Hue hub so I cannot test for sure. Deconz does shows some ZLL attributes. Also the bulb identifies as a Classic A60 TW where as before it was A19.

One thing of interest is the release notes mention a new network stack. Not sure if the Hubitat users in Europe still see routing issues with this version?

RELEASE NOTES - ZLL_MK_0x01020509_CLA60_TW.ota
Date: Wednesday, 13 March 2019

  1. Stack upgrade
  2. Improve network performance

I joined the Osram bulb to the Hubitat. Then I disabled the Hubitat radio. Power cycled the bulb. Re-enabled the Zigbee radio. Then I followed the instructions to use deconz to upgrade the firmware.

how?

Ledvance makes their firmware available here. One has to unpair from HE, pair to a controller that permits firmware updates, and then re-pair to HE.

Oh I guess I thought there was something more that I was missing. Cause I did the firmware update through an Osram hub and the bulbs weren't ZLL.

But I didn't double check the firmware on the bulbs. Maybe I should check.

I haven't read of any ZHA US bulbs being able to update to ZLL unless through the no longer doing it osram customer service.

I left the bulb connected to Hubitat. I have a Conbee 2 joined to my Hubitat Zigbee network.

I'm not sure the US hub would give you the ZLL firmware. I got the firmware image from the EU filter. The US section only has newer bulb firmware. The bulbs I updated are branded Osram Lightify. These are the older bulbs with the Marvell SOC. The bulbs that are notorious bad at routing.

I have the newer bulbs also on my Hubitat network with no ill effect that I can see. I'm not sure I will leave the older bulbs on the Hubitat network. I have a Zigbee2MQTT network that I need some repeaters for.

I’ve had an issue where one or two lights won’t receive an on/off command. That’s my real desire for getting these on Hue. Doesn’t happen when locally attached to SmartThings, though. Not sure why there’s a difference.