Z-Stack 3 on CC2531/CC2530 adventures #1445

Koenkk · 2019-04-18T17:05:28Z

This issue is created in order to gather feedback of users using the CC2531/CC2530 AND Z-Stack 3.0 (= Zigbee 3.0)

You are about to enter a highly experimental area (no guarantees)

Notes

Zigbee 3.0!
Firmware can be found here in the bin folder: https://github.com/Koenkk/Z-Stack-firmware/tree/dev/coordinator/Z-Stack_3.0.x
It's not possible to migrate your Zigbee 1.2 network (requires repairing)
The network restore trick that we used in Zigbee 1.2 doesn't work anymore (due to better security policies). A backup of the CC2531/CC2530 is taken at every shutdown of zigbee2mqtt, file can be found under data/coordinator_backup.json. This backup is automatically restored when starting with a new flashed CC2531/CC2530.
Requires latest zigbee2mqtt dev branch.

Known issues

Pan ID and extended pan ID can't be set (probably not something to worry about)
Pairing only seems possible during the first 180 seconds (even with permit_join: true, a workaround is to restart zigbee2mqtt.

The text was updated successfully, but these errors were encountered:

jarrah31 · 2019-04-23T09:28:16Z

What are the benefits of Zigbee 3.0 for zigbee2mqtt? Will it allow more than the default 15 devices on a CC2531 coordinator (and if so how many)? Do we need new firmware on the CC2531 routers as well?

btw, thanks @Koenkk for a fantastic product and all the effort you put into this project, it is very much appreciated!

Koenkk · 2019-04-23T19:08:24Z

@jarrah31 it also has a direct children limit of 15. No new router firmware is needed (zigbee 1.2 devices can join a zigbee 3.0 network). More about zigbee 3.0 changes can be found here: http://www.ti.com/lit/an/swra615/swra615.pdf

I've just released a new firmware 20190423 (https://github.com/Koenkk/Z-Stack-firmware/tree/dev/coordinator/Z-Stack_3.0.x/bin).)

Increased stability
Try to fix issue that kicked of Xiaomi devices from the network
Increased number of direct children from 10 to 15

Z0l · 2019-04-27T21:02:46Z

Hey, I'm new to this whole Zigbee thing but I got this one up and running with the future intent of integrating with Openhab to finally make my Hue Tap do things Philips never dreamed of :) Is there documentation available how GPP devices can be paired? Perhaps something specific for Hue Tap? I'm running 20190423 with the latest dev Docker container.

Koenkk · 2019-04-28T18:55:37Z

@Z0l you can try to pair it, setup procedure seems to be here: https://huetips.com/tutorials/how-to-add-a-hue-tap/ (10 seconds press a button).

runningman84 · 2019-04-28T21:05:47Z

I have flashed my cc2531 with CC2531ZNP-with-SBL.hex:

sudo ./cc-tool -e -w CC2531ZNP-with-SBL.hex                                                                                                                                            ±[●][master]
[sudo] Passwort für phil: 
  Programmer: CC Debugger
  Target: CC2531
  Erasing flash...
  Completed       
  Writing flash (241 KB)...
  Completed (17.97 s.)

but the stick does not seem to work with zigbee2mqtt anymore:

> [email protected] start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 4/28/2019, 9:59:45 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-04-28.21-59-45'
  zigbee2mqtt:info 4/28/2019, 9:59:46 PM Starting zigbee2mqtt version 1.3.1 (commit #39d6a8e)
  zigbee2mqtt:info 4/28/2019, 9:59:46 PM Starting zigbee-shepherd
  zigbee2mqtt:info 4/28/2019, 9:59:51 PM Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds)
  zigbee2mqtt:info 4/28/2019, 10:00:51 PM Starting zigbee-shepherd
  zigbee2mqtt:error 4/28/2019, 10:00:56 PM Error while starting zigbee-shepherd!
  zigbee2mqtt:error 4/28/2019, 10:00:56 PM Press the reset button on the stick (the one closest to the USB) and start again
  zigbee2mqtt:error 4/28/2019, 10:00:56 PM Failed to start
        {"message":"rsp error: 2","stack":"Error: rsp error: 2\n    at rspHdlr (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/controller.js:309:29)\n    at CcZnp.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:264:13)\n    at Object.onceWrapper (events.js:277:13)\n    at CcZnp.emit (events.js:189:13)\n    at CcZnp._mtIncomingDataHdlr (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:366:14)\n    at Immediate._onImmediate (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:342:22)\n    at runCallback (timers.js:705:18)\n    at tryOnImmediate (timers.js:676:5)\n    at processImmediate (timers.js:658:5)"}
  zigbee2mqtt:error 4/28/2019, 10:00:56 PM Exiting...
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-04-28T21_00_56_252Z-debug.log

after pressing the reset button on the stick I get this error:

pi@raspberrypi:/opt/zigbee2mqtt $ npm start

> [email protected] start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 4/28/2019, 10:03:41 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-04-28.22-03-41'
  zigbee2mqtt:info 4/28/2019, 10:03:42 PM Starting zigbee2mqtt version 1.3.1 (commit #39d6a8e)
  zigbee2mqtt:info 4/28/2019, 10:03:42 PM Starting zigbee-shepherd
  zigbee2mqtt:info 4/28/2019, 10:03:44 PM Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds)
   zigbee2mqtt:info 4/28/2019, 10:04:44 PM Starting zigbee-shepherd
  zigbee2mqtt:error 4/28/2019, 10:04:45 PM Error while starting zigbee-shepherd!
  zigbee2mqtt:error 4/28/2019, 10:04:45 PM Press the reset button on the stick (the one closest to the USB) and start again
  zigbee2mqtt:error 4/28/2019, 10:04:45 PM Failed to start
        {"message":"request timeout","stack":"Error: request timeout\n    at CcZnp.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:261:22)\n    at Object.onceWrapper (events.js:277:13)\n    at CcZnp.emit (events.js:189:13)\n    at Timeout.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:240:18)\n    at ontimeout (timers.js:436:11)\n    at tryOnTimeout (timers.js:300:5)\n    at listOnTimeout (timers.js:263:5)\n    at Timer.processTimers (timers.js:223:10)"}
  zigbee2mqtt:error 4/28/2019, 10:04:45 PM Exiting...
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-04-28T21_04_45_888Z-debug.log

the same stick worked fine with the old version:

pi@raspberrypi:/opt/zigbee2mqtt $ npm start                  

> [email protected] start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 4/28/2019, 8:29:24 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-04-28.20-29-24'
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Starting zigbee2mqtt version 1.3.1 (commit #39d6a8e)
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Starting zigbee-shepherd
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM zigbee-shepherd started
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Coordinator firmware version: '20190223'
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Currently 1 devices are joined:
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3): AB3257001NJ - OSRAM Smart+ plug (Router)
  zigbee2mqtt:warn 4/28/2019, 8:29:25 PM `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 4/28/2019, 8:29:25 PM Allowing new devices to join.
  zigbee2mqtt:warn 4/28/2019, 8:29:25 PM Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 4/28/2019, 8:29:25 PM Connecting to MQTT server at mqtt://192.168.178.71
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM zigbee-shepherd ready
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM Connected to MQTT server
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":78}'
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM MQTT publish: topic 'homeassistant/switch/0x7cb03eaa00a6f7a3/switch/config', payload '{"payload_off":"OFF","payload_on":"ON","value_template":"{{ value_json.state }}","command_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3/set","state_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3_switch","unique_id":"0x7cb03eaa00a6f7a3_switch_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3","sw_version":"Zigbee2mqtt 1.3.1","model":"Smart+ plug (AB3257001NJ)","manufacturer":"OSRAM"},"availability_topic":"zigbee2mqtt/bridge/state"}'
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM MQTT publish: topic 'homeassistant/sensor/0x7cb03eaa00a6f7a3/linkquality/config', payload '{"unit_of_measurement":"-","value_template":"{{ value_json.linkquality }}","state_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","json_attributes_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3_linkquality","unique_id":"0x7cb03eaa00a6f7a3_linkquality_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3","sw_version":"Zigbee2mqtt 1.3.1","model":"Smart+ plug (AB3257001NJ)","manufacturer":"OSRAM"},"availability_topic":"zigbee2mqtt/bridge/state"}'
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.3.1","commit":"39d6a8e","coordinator_firmware":20190223,"log_level":"info","permit_join":true}'
  zigbee2mqtt:info 4/28/2019, 8:29:26 PM Successfully configured 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3)

runningman84 · 2019-04-28T21:10:09Z

Btw. the same error happens in the dev branch (commit #4472c01)

Koenkk · 2019-04-29T06:19:46Z

Can you provide the output of DEBUG=* npm start (on https://pastebin.com/)

Z0l · 2019-04-29T08:30:18Z

For me it works with the dev version:

4/28/2019, 8:58:36 PM - info: Logging to directory: '/app/data/log/2019-04-28.20-58-36' 4/28/2019, 8:58:36 PM - info: Starting zigbee2mqtt version 1.3.1 (commit #unknown) 4/28/2019, 8:58:36 PM - info: Starting zigbee-shepherd 4/28/2019, 8:58:38 PM - info: zigbee-shepherd started 4/28/2019, 8:58:38 PM - info: Coordinator firmware version: '20190425' 4/28/2019, 8:58:38 PM - info: Currently 0 devices are joined: 4/28/2019, 8:58:38 PM - warn: 'permit_join' set to 'true' in configuration.yaml. 4/28/2019, 8:58:38 PM - warn: Allowing new devices to join. 4/28/2019, 8:58:38 PM - warn: Set 'permit_join' to 'false' once you joined all devices. 4/28/2019, 8:58:38 PM - info: Zigbee: allowing new devices to join. 4/28/2019, 8:58:38 PM - info: Connecting to MQTT server at mqtt://localhost 4/28/2019, 8:58:38 PM - info: zigbee-shepherd ready 4/28/2019, 8:58:38 PM - info: Connected to MQTT server 4/28/2019, 8:58:38 PM - info: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online' 4/28/2019, 8:58:38 PM - info: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.3.1","commit":"unknown","coordinator":20190425,"log_level":"info","permit_join":true}'

However nothing happens when I keep pushing the button for 10 sec (I tried pushing all 4). Is the limitation on pairing has to happen in the first 180 seconds still in place? Also, is that normal that the led turns off after some time (didn't measure how long, but when I plug the USB in and start the docker container, the LED turns off).

lolorc · 2019-04-29T09:46:11Z

@Z0l the pairing limitation is actually a zigbee 3.0 feature :-)
https://www.ti.com/lit/an/swra615/swra615.pdf "Permit join can no longer be enabled forever as networks will automatically close joining after a maximum of 254 seconds."
just resend the mqtt cmd permit_join true when the 254s have passed.

runningman84 · 2019-04-29T11:22:38Z

@lolorc it would be cool if zigbee2mqtt would expose a switch like "permit_join" to homeassistant.

lolorc · 2019-04-29T13:21:13Z

@runningman84 a hack is probably already possible. using zigbee2mqtt/bridge/config/permit_join as a mqtt switch with retain true. I guess it would also be possible to tell home assistant to set it to false 254s after it has been set to true.
but I agree it would better to be able to read from zigbee2mqtt/bridge/config/permit_join and get the updated status, and also having z2m setting it to false after 254s

Koenkk · 2019-04-29T13:38:07Z

@runningman84 @lolorc don't spend time on this. Soon I will implement something that zigbee2mqtt does this automatically.

runningman84 · 2019-04-29T17:31:49Z

@Koenkk

Can you provide the output of DEBUG=* npm start (on https://pastebin.com/)

https://pastebin.com/h0hFLEuA

Koenkk · 2019-04-29T19:36:14Z

@runningman84 after updating, did you do a rm -rf node_modules && npm install?

runningman84 · 2019-04-29T19:52:50Z

I just run rm -rf node_modules && npm install and flashed the firmware once again. Now it seems to start:

pi@raspberrypi:/opt/zigbee2mqtt $ npm start

> [email protected] start /opt/zigbee2mqtt
> node index.js

  zigbee2mqtt:info 4/29/2019, 8:49:59 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-04-29.20-49-59'
  zigbee2mqtt:info 4/29/2019, 8:50:00 PM Starting zigbee2mqtt version 1.3.1 (commit #a54e256)
  zigbee2mqtt:info 4/29/2019, 8:50:00 PM Starting zigbee-shepherd
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM zigbee-shepherd started
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM Coordinator firmware version: '20190425'
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM Currently 1 devices are joined:
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3): AB3257001NJ - OSRAM Smart+ plug (Router)
  zigbee2mqtt:warn 4/29/2019, 8:50:02 PM `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 4/29/2019, 8:50:02 PM Allowing new devices to join.
  zigbee2mqtt:warn 4/29/2019, 8:50:02 PM Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM Connecting to MQTT server at mqtt://192.168.178.71
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM zigbee-shepherd ready
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM Connected to MQTT server
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":0}'
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM MQTT publish: topic 'homeassistant/switch/0x7cb03eaa00a6f7a3/switch/config', payload '{"payload_off":"OFF","payload_on":"ON","value_template":"{{ value_json.state }}","command_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3/set","state_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3_switch","unique_id":"0x7cb03eaa00a6f7a3_switch_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3","sw_version":"Zigbee2mqtt 1.3.1","model":"Smart+ plug (AB3257001NJ)","manufacturer":"OSRAM"},"availability_topic":"zigbee2mqtt/bridge/state"}'
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM MQTT publish: topic 'homeassistant/sensor/0x7cb03eaa00a6f7a3/linkquality/config', payload '{"unit_of_measurement":"-","value_template":"{{ value_json.linkquality }}","state_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","json_attributes_topic":"zigbee2mqtt/0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3_linkquality","unique_id":"0x7cb03eaa00a6f7a3_linkquality_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x7cb03eaa00a6f7a3","name":"0x7cb03eaa00a6f7a3","sw_version":"Zigbee2mqtt 1.3.1","model":"Smart+ plug (AB3257001NJ)","manufacturer":"OSRAM"},"availability_topic":"zigbee2mqtt/bridge/state"}'
  zigbee2mqtt:info 4/29/2019, 8:50:02 PM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.3.1","commit":"a54e256","coordinator":20190425,"log_level":"info","permit_join":true}'
  zigbee2mqtt:warn 4/29/2019, 8:50:14 PM No converter available for 'AB3257001NJ' with cid 'genBasic', type 'devChange' and data '{"cid":"genBasic","data":{"manufacturerName":"OSRAM","modelId":"Plug 01","powerSource":1}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:14 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:14 PM No converter available for 'AB3257001NJ' with cid 'genBasic', type 'devChange' and data '{"cid":"genBasic","data":{"zclVersion":1,"appVersion":12,"stackVersion":2,"hwVersion":1,"dateCode":"20140331DEOS****","swBuildId":"V1.04.12"}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:14 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM No converter available for 'AB3257001NJ' with cid 'genBasic', type 'devChange' and data '{"cid":"genBasic","data":{"deviceEnabled":1}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM No converter available for 'AB3257001NJ' with cid 'genIdentify', type 'devChange' and data '{"cid":"genIdentify","data":{"identifyTime":0}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM No converter available for 'AB3257001NJ' with cid 'genGroups', type 'devChange' and data '{"cid":"genGroups","data":{"nameSupport":0}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM No converter available for 'AB3257001NJ' with cid 'genScenes', type 'devChange' and data '{"cid":"genScenes","data":{"count":0,"currentScene":0,"currentGroup":0,"sceneValid":0,"nameSupport":0}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:15 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:info 4/29/2019, 8:50:16 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":84}'
  zigbee2mqtt:warn 4/29/2019, 8:50:16 PM No converter available for 'AB3257001NJ' with cid 'haElectricalMeasurement', type 'devChange' and data '{"cid":"haElectricalMeasurement","data":{"measurementType":8,"activePower":400}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:16 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:warn 4/29/2019, 8:50:16 PM No converter available for 'AB3257001NJ' with cid 'manuSpecificOsram', type 'devChange' and data '{"cid":"manuSpecificOsram","data":{"0":0}}'
  zigbee2mqtt:warn 4/29/2019, 8:50:16 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
  zigbee2mqtt:info 4/29/2019, 8:50:16 PM Device incoming...
  zigbee2mqtt:info 4/29/2019, 8:50:16 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}'
  zigbee2mqtt:warn 4/29/2019, 8:50:53 PM Failed to configure 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3) ('Error: Timed out after 10000 ms') (attempt #1)
  zigbee2mqtt:warn 4/29/2019, 8:50:53 PM This can be ignored if the device is working properly

But the OSRAM plug does not seem to work well with this firmware or software. State changes are not reported and there are these timed out error messages.

runningman84 · 2019-04-29T19:55:16Z

I just removed the plug from the outlet and put it back in... now the state change is recognized:

  zigbee2mqtt:warn 4/29/2019, 8:50:53 PM Failed to configure 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3) ('Error: Timed out after 10000 ms') (attempt #1)
  zigbee2mqtt:warn 4/29/2019, 8:50:53 PM This can be ignored if the device is working properly
  zigbee2mqtt:info 4/29/2019, 8:53:20 PM Successfully configured 0x7cb03eaa00a6f7a3 (0x7cb03eaa00a6f7a3)
  zigbee2mqtt:info 4/29/2019, 8:53:22 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"OFF","linkquality":86}'
  zigbee2mqtt:info 4/29/2019, 8:53:24 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":84}'
  zigbee2mqtt:info 4/29/2019, 8:53:25 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"OFF","linkquality":86}'
  zigbee2mqtt:info 4/29/2019, 8:53:26 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":81}'
  zigbee2mqtt:info 4/29/2019, 8:53:27 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"OFF","linkquality":86}'
  zigbee2mqtt:info 4/29/2019, 8:53:28 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"ON","linkquality":84}'
  zigbee2mqtt:info 4/29/2019, 8:53:28 PM MQTT publish: topic 'zigbee2mqtt/0x7cb03eaa00a6f7a3', payload '{"state":"OFF","linkquality":89}'

GlitchHound · 2019-05-07T20:32:56Z

I've got this running, I took the plunge straight into Z-Stack 3 since I don't have any of my network setup. No bugs to report yet, but are there any instructions on how to use touchlink in this? Or is the whole point that we now could make touchlink work, rather than that it already is working?

My hue bulbs don't even like resetting with the API touchlink trick on the original bridge, but using my Conbee (which I'm hoping to replace for the more open zigbee2mqtt) I was able to reset them and then get them onto zigbee2mqtt, so I'd love to see touchlink without any other device.

Only a couple of devices so far, and I'm not doing anything sophisticated, but it is working with what I've paired up (a GE switch and a hue bulb)

Koenkk · 2019-05-08T06:34:21Z

@GlitchHound good idea! I will look into this, please keep an eye on #1509

sehraf · 2019-05-19T06:49:48Z

Do i understand this correctly:

The network restore trick that we used in Zigbee 1.2 doesn't work anymore (due to better security policies). A backup of the CC2531 is taken at every shutdown of zigbee2mqtt, file can be found under data/coordinator_backup.json. This backup is automatically restored when starting with a new flashed CC2531.

Does this imply that i can even change the hardware without the need to repair all devices? Or does this "only" cover firmware changes?

Koenkk · 2019-05-19T08:54:27Z

@sehraf yes, hardware can be changed without repairing (was also possible with 1.2). Note that when going from zigbee 1.2 to 3.0 you have to re-pair.

drbios · 2019-05-20T18:29:42Z

everything Working fine but when i stop the zigbee2mqtt service with availability_timeout: option in the configuration.yaml this is the log:

May 20 11:50:54 hassbian systemd[1]: Stopping zigbee2mqtt...
May 20 11:50:54 hassbian npm[11064]: #33[32m zigbee2mqtt:info#033[39m 5/20/2019, 11:50:54 AM MQTT publish: topic 'zigbee2mqtt/0x00158d0001c9affc/availability', payload 'offline'
May 20 11:50:54 hassbian npm[11064]: #33[32m zigbee2mqtt:info#033[39m 5/20/2019, 11:50:54 AM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
May 20 11:50:54 hassbian npm[11064]: #33[32m zigbee2mqtt:info#033[39m 5/20/2019, 11:50:54 AM Disconnecting from MQTT server
May 20 11:50:54 hassbian mosquitto[3833]: 1558367454: Client mqttjs_0943bd74 disconnected.
May 20 11:50:54 hassbian systemd[1]: zigbee2mqtt.service: Main process exited, code=killed, status=15/TERM
May 20 11:50:54 hassbian npm[11064]: #33[32m zigbee2mqtt:info#033[39m 5/20/2019, 11:50:54 AM MQTT publish: topic 'zigbee2mqtt/0x00158d0001c9affc/availability', payload 'offline'
May 20 11:50:54 hassbian npm[11064]: events.js:174
May 20 11:50:54 hassbian npm[11064]: throw er; // Unhandled 'error' event
May 20 11:50:54 hassbian npm[11064]: ^
May 20 11:50:54 hassbian npm[11064]: Error: client disconnecting
May 20 11:50:54 hassbian npm[11064]: at MqttClient._checkDisconnecting (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:370:26)
May 20 11:50:54 hassbian npm[11064]: at MqttClient.publish (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:408:12)
May 20 11:50:54 hassbian npm[11064]: at MQTT.publish (/opt/zigbee2mqtt/lib/mqtt.js:95:21)
May 20 11:50:54 hassbian npm[11064]: at DeviceAvailability.publishAvailability (/opt/zigbee2mqtt/lib/extension/deviceAvailability.js:146:19)
May 20 11:50:54 hassbian npm[11064]: at zigbee.getDevices.filter.forEach (/opt/zigbee2mqtt/lib/extension/deviceAvailability.js:106:39)
May 20 11:50:54 hassbian npm[11064]: at Array.forEach ()
May 20 11:50:54 hassbian npm[11064]: at DeviceAvailability.stop (/opt/zigbee2mqtt/lib/extension/deviceAvailability.js:106:14)
May 20 11:50:54 hassbian npm[11064]: at extensions.filter.forEach (/opt/zigbee2mqtt/lib/controller.js:177:64)
May 20 11:50:54 hassbian npm[11064]: at Array.forEach ()
May 20 11:50:54 hassbian npm[11064]: at Controller.stop (/opt/zigbee2mqtt/lib/controller.js:177:47)
May 20 11:50:54 hassbian npm[11064]: Emitted 'error' event at:
May 20 11:50:54 hassbian npm[11064]: at MqttClient._checkDisconnecting (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:370:12)
May 20 11:50:54 hassbian npm[11064]: at MqttClient.publish (/opt/zigbee2mqtt/node_modules/mqtt/lib/client.js:408:12)
May 20 11:50:54 hassbian npm[11064]: [... lines matching original stack trace ...]
May 20 11:50:54 hassbian npm[11064]: at Controller.stop (/opt/zigbee2mqtt/lib/controller.js:177:47)
May 20 11:50:54 hassbian systemd[1]: zigbee2mqtt.service: Succeeded.
May 20 11:50:54 hassbian systemd[1]: Stopped zigbee2mqtt.

Koenkk · 2019-05-20T18:44:44Z

@drbios fixed in latest dev.

ruimarinho · 2020-06-13T16:12:32Z

Even in router mode? Would there be any advantage?

Koenkk · 2020-06-14T08:58:09Z

@ruimarinho see Koenkk/Z-Stack-firmware#153

Westcott1 · 2020-06-16T19:52:03Z

No (cc2530 == cc2531 without usb)
?
I have one of these on order -
https://www.aliexpress.com/item/4000060995530.html?spm=a2g0s.9042311.0.0.40694c4dsHFJuu

hahmann · 2020-06-16T20:23:27Z

@hahmann could you post a sniff of a case were it works and one where it fails? https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

@Koenkk unfortunately I don't have a spare CC2531 to do sniffing, will arrange one and get back to you with more details. So far the lock still connected only to the coordinator so I'm not seeing any errors so far.

hahmann · 2020-06-24T20:27:39Z

@Koenkk, another thing to add is that I can't get the reports of the lock/unlock when the lock is locked/unlocked from the keypad/panel, only when it is done from zigbee. If I lock from Zigbee2mqtt and open from the keypad it will show as locked. In the past (previous version and z-stack 1.2) I used to get one message for every lock/unlock, with a number explaining from where is was locked/unlocked.

Just enabled debug here but there is nothing coming from the lock when I lock/unlock from the keypad or knob.
Any ideas?

Koenkk · 2020-06-27T10:41:24Z

@hahmann try to reconfigure the lock via https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure (make sure to wakeup the device right before executing this)

hahmann · 2020-07-03T16:20:14Z

@hahmann try to reconfigure the lock via https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure (make sure to wakeup the device right before executing this)

Excellent! Doing a configure for the lock solved the issue, it is reporting every lock/unlock now, coming from the bridge, knob or keypad as expected! Thank you so much.

reedstrm · 2020-07-31T15:11:05Z

PSA: for those following along, TI moved the descriptive PDF re: zigbee3 to here: https://www.ti.com/lit/an/swra615a/swra615a.pdf
and Heda's issue Koenkk/Z-Stack-firmware#153 contains a nice summary of some of the new features

aromanro · 2020-08-18T09:30:14Z

Hi,

I have a CC2530+CC2592 device connected to serial on a raspberry pi, using the firmware from here (3.0.x). Seems to work, but I was trying to re-initialize it and it failed when trying to commission the network.

The app cnf bdb start commissioning request (mode: 0x4 - BDB_COMMISSIONING_MODE_NWK_FORMATION) failed with an app cnf bdb commission notification with status 0x8 (BDB_COMMISSIONING_FORMATION_FAILURE).

I tried various settings for the channels mask, setting a particular pan id or letting it unset (that is, to be randomly generated), with the same result.

Is it possible to re-commission a network with this firmware?

mgrom · 2020-08-19T07:08:39Z

Hi there,

I'm testing CC2531 with z-stack 3. I've got few CC2531 with router firmware either.
On firmware 1.2 I was able to pair devices through routers, this means I didn't need to go near coordinator, I could be behind many walls as long routers were being seen by coordinator.
Unfortunatelly this doesn't work with z-stack 3. I've tried many times to pair through router with no success, first attempt near coordinator and done.

Is it expected behavior?

aromanro · 2020-08-20T06:35:47Z

Routers should allow other nodes to join through them. I hope you have z-stack 3 on both the coordinator and routers.

mgrom · 2020-08-20T06:43:42Z

Routers should allow other nodes to join through them. I hope you have z-stack 3 on both the coordinator and routers.

As mentioned in this thread already routers can work on 1.2.

aromanro · 2020-08-20T06:51:17Z

Yes, they do. There is backward compatibility but I wouldn't be so sure about joining.
Especially not about joining zigbee 3 devices.

Even for joining directly connected to the coordinator, for many 'legacy' devices I had to set a 'link key exchage' flag in the coordinator to false in order to have them join, otherwise they were kicked out of the network.

sshaikh · 2020-09-09T17:33:01Z

I have read through this thread and am still a little confused as to whether I should replace the 1.2 FW on my CC2531.

I'm using the stick with the 1.2 FW in the native ZHA integration in HA. This works well ordinarily but unfortunately it doesn't with the Aqara QBKG25LM.

I was advised to use ZStack 3 to fix this, but if 1.2 allows me to use the QBKG25LM with Z2M I'll probably go that route instead.

So my question is does FW3 allow more HW to work (in particular the QBKG25LM) independent of the software, or would the Z2M/Herdsman quirks available make the QBKG25LM work with 1.2 FW?

creativtransfer · 2020-09-20T01:49:57Z

I have a question regarding a CC2530 / 2592 module:
Which pins does z-stack use for switching the PA and LNA of the CC2592 module.
Is it always P1.0 (LNA) and P1.1 (PA)?

pepsonEL · 2020-10-02T11:03:55Z

Hi
Is any chance to write firmware serise Z-Stack 3.x to coordinator CC2531 https://www.google.com/search?q=CC2531&sxsrf=ALeKk03fVjyj6WndR0BuMBXenVv3QwnFyg:1601636604597&source=lnms&tbm=isch&sa=X&ved=2ahUKEwiF3oCn4ZXsAhWEl4sKHQFYBZsQ_AUoAnoECAwQBA&biw=1920&bih=1008#imgrc=NW1KZ1PfXbtwbM ??
Which file i must use ?

github-actions · 2020-11-02T00:04:23Z

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

chbarg · 2021-03-30T21:33:01Z

Pardon my ignorance. Does the Z Stack firmware accept AT (like) commands of some sort?

I am trying to use the CC2530 as simple ZigBee transceivers connected thru TX/RX lines

Florissilfhout · 2021-05-11T21:25:40Z

I'm running a CC2531 with latest Z-Stack_3.0.x and it's working great. I've got 9 routers (plugs and light bulbs) and 6 end devices (Aqara Temps, light sensor). Now I'm trying to pair yet another bulb but there is no log of the pairing action. I have restarted Zigbee2MQTT multiple times and tried pairing shortly after the restarts but to no avail.
How can I get past this magic limit of 15 connected devices? Currently there are only 3 end devices directly connected to the coordinator.

Edit: This morning, after a night left alone, I was able to pair the bulb. The mesh network probably changed a bit and now there was room for the extra device. :)

This was referenced Apr 18, 2019

Running on Z-Stack 3.0 #211

Closed

permit_join false not honored #538

Closed

Enddevices unreachable because route not updating #1408

Closed

Koenkk mentioned this issue Apr 23, 2019

Z-Stack 3.0 device limit? have 22 devices (multiple routers) and cant connect more #1458

Closed

Koenkk mentioned this issue Apr 23, 2019

Cannot join Hue dimmer switch anymore #1268

Closed

Koenkk added a commit that referenced this issue May 7, 2019

Reenable joining after 200 seconds. #1429 #1445

2ba62ed

Koenkk added a commit that referenced this issue May 7, 2019

Reenable joining after 200 seconds. #1429 #1445

ba1eca8

Koenkk mentioned this issue May 8, 2019

Implement touchlink #1509

Closed

Hedda mentioned this issue Aug 10, 2020

Set different default CONFIG_MAX_END_DEVICE_CHILDREN for each EZSP version or separate for EM35x and EFR32? zigpy/bellows#294

Closed

aromanro mentioned this issue Aug 19, 2020

Coordinator network commissioning and some other stuff Koenkk/Z-Stack-firmware#199

Closed

sshaikh mentioned this issue Sep 9, 2020

[Device Support Request] Xiaomi Aqara D1 double key wireless wall switch WXKG07LM zigpy/zha-device-handlers#394

Closed

github-actions bot added the stale Stale issues label Nov 2, 2020

github-actions bot closed this as completed Nov 10, 2020

Hedda mentioned this issue Feb 16, 2021

[REQUEST] Z-Stack 3.0.x router firmware for CC2530 and CC2531 USB sticks/dongles? Koenkk/Z-Stack-firmware#153

Closed

Boia11 mentioned this issue Apr 10, 2021

CC2530 + CC2592 | Better coordinator firmwares Z-Stack_Home_1.2 vs Z-Stack_3.0.x Koenkk/Z-Stack-firmware#282

Closed

Hedda mentioned this issue May 12, 2021

Support for Z-Stack 3 (Z-Stack 3.0.x and Z-Stack 3.x.x) - Texas Instruments Zigbee 3.0 stack on adapters like CC2652 and CC1352 zsmartsystems/com.zsmartsystems.zigbee#1226

Open

Hedda mentioned this issue Sep 13, 2021

Add "not recommended" note to CC2530 and C2531 in ZHA docs home-assistant/home-assistant.io#19324

Merged

8 tasks

This was referenced Sep 17, 2021

Zigbee 3.0 firmware (on CC2530) for EFEKTA Zigbee Plant Watering Sensor? smartboxchannel/Plant-Watering-Sensor-Zigbee#2

Closed

Zigbee 3.0 firmware (on CC2530) for DIYRuZ Zigbee Plant Watering Sensor? diyruz/flower#38

Open

Z-Stack 3 on CC2531/CC2530 adventures #1445

Z-Stack 3 on CC2531/CC2530 adventures #1445

Comments

Koenkk commented Apr 18, 2019 • edited Loading

jarrah31 commented Apr 23, 2019

Koenkk commented Apr 23, 2019 • edited Loading

Z0l commented Apr 27, 2019

Koenkk commented Apr 28, 2019

runningman84 commented Apr 28, 2019

runningman84 commented Apr 28, 2019

Koenkk commented Apr 29, 2019

Z0l commented Apr 29, 2019 • edited Loading

lolorc commented Apr 29, 2019

runningman84 commented Apr 29, 2019

lolorc commented Apr 29, 2019

Koenkk commented Apr 29, 2019

runningman84 commented Apr 29, 2019

Koenkk commented Apr 29, 2019

runningman84 commented Apr 29, 2019

runningman84 commented Apr 29, 2019

GlitchHound commented May 7, 2019

Koenkk commented May 8, 2019

sehraf commented May 19, 2019

Koenkk commented May 19, 2019

drbios commented May 20, 2019

Koenkk commented May 20, 2019

ruimarinho commented Jun 13, 2020

Koenkk commented Jun 14, 2020

Westcott1 commented Jun 16, 2020

hahmann commented Jun 16, 2020

hahmann commented Jun 24, 2020

Koenkk commented Jun 27, 2020

hahmann commented Jul 3, 2020

reedstrm commented Jul 31, 2020

aromanro commented Aug 18, 2020

mgrom commented Aug 19, 2020

aromanro commented Aug 20, 2020

mgrom commented Aug 20, 2020

aromanro commented Aug 20, 2020 • edited Loading

sshaikh commented Sep 9, 2020 • edited Loading

creativtransfer commented Sep 20, 2020

pepsonEL commented Oct 2, 2020

github-actions bot commented Nov 2, 2020

chbarg commented Mar 30, 2021

Florissilfhout commented May 11, 2021 • edited Loading

Koenkk commented Apr 18, 2019 •

edited

Loading

Koenkk commented Apr 23, 2019 •

edited

Loading

Z0l commented Apr 29, 2019 •

edited

Loading

aromanro commented Aug 20, 2020 •

edited

Loading

sshaikh commented Sep 9, 2020 •

edited

Loading

Florissilfhout commented May 11, 2021 •

edited

Loading