v0.1.0

New Features

• zigpy_znp.tools.nvram_reset resets a device.
• zigpy_znp.tools.nvram_write takes a -r argument to reset a device after writing new firmware.
• zigpy_znp.tools.nvram_write now allows firmware downgrades back to unsupported versions of Z-Stack.
• If a TRACE logging level exists (must be equal to 5 or named TRACE, and be more verbose than DEBUG), zigpy-znp will log very verbose messages with that level. Otherwise, DEBUG will be used.

Changes

• Increase minimum zigpy version to 0.23.0.
• Drop the attr package as a dependency.
• Add autodetection for the CC2531 and slae.sh's CC2652R USB stick
• Limit concurrent requests to 2 for CC2531 and 16 for more capable coordinators (can be overridden with the max_concurrent_requests setting). Future releases may intelligently limit requests in response to memory errors.
• VERBOSE and TRACE logging is available in all command line tools, defaulting to INFO.

Bugfixes

• Fixed bug where a callback responding to one of multiple ZDO requests of the same type would be erroneously accepted by all.
• Networks formed with a channel mask and a fixed channel did not always use the fixed channel. ` is used in the configuration

v0.0.11

Changes

• Add a tool to scan Zigbee channels: zigpy_znp.tools.energy_scan. More information is in the README.
• Move DEBUG verbosity in all tools behind a -v flag. Default is now INFO.
• Re-add an endpoint with the ZLL profile.

Bugfixes

• Some data confirmation messages were not being handled properly when sent from certain endpoints.
• Bind/unbind ZDO commands were not working for certain endpoints.

zigpy-znp is nearly finished and will probably move from "alpha" to "beta" status in the next release.

v0.0.10

Changes

• Add the coordinator itself to the device list, allowing Zigbee groups to work in HA after a restart (issue #27)
• Rewrite HA custom component to inject much earlier and thus more reliably (234b1f2).
• Condense all unnecessary endpoints into a single endpoint with multiple in/out clusters (0b6100c).
• Remove the custom TRACE log level and instead use DEBUG (e9c1aef).
• Add a converter for ZDOCmd.Mgmt_Permit_Joining_req and an explicit error message for missing converters (65269da).
• Support both old- and new-style zigpy structs (zigpy/zigpy#440)

v0.0.9

Global changes

• Support Zigbee groups and multicast requests
• Expose the current Zigbee channel on startup, not just the channel mask.
• Implement LED control. Set it with led_mode: one of (off, on, blink, flash, toggle)

Preliminary CC2531 support!

• Network formation and simple commands have been superficially tested
• Validate binary firmware CRCs before firmware flashing with python -m zigpy_znp.tools.flash_write
• Skip the 60 second bootloader delay
• Support NVRAM backup/restore. Warning: don't mix CC2531 backups with ZZH and LAUNCHXL backups. It will not work and you might softlock your device and need to reflash.

v0.0.8

Changes

• Add OTA update support.

v0.0.7

Changes

• Read current logical channel on startup. Can be accessed with app.channel.

• (Experimental) Allow setting the current logical channel directly in the NIB.

• Allow optional schema parameters for variable-length Z-Stack commands.

• Rename NVRAM commands to nvram_read and nvram_write.

• Implement flash reading and writing for CC2531:

  $ python -m zigpy_znp.tools.flash_read /dev/serial/by-id/radio -o flash.bin
  $ python -m zigpy_znp.tools.flash_write /dev/serial/by-id/radio -i flash.bin

v0.0.6

Changes

• Add omitted coloredlogs dependency for NVRAM backup and restore commands.

v0.0.5

Changes

• Add installation instructions for Home Assistant to README.
• Implement NVRAM backup and restore commands.
• Fix network formation bugs.

v0.0.4

Changes

• Update README.md with a summary of different chips mentioned @Hedda (#18)
• Reset the controller on startup to close any pending join requests from a previous run.
• Implement ZDOCmd.Bind_req
• Fixed bug where device removal failed halfway through (#17)

v0.0.3

• 100% test coverage.
• Requires zigpy>=0.20.1a2.
• Network formation and device joining fully tested with a freshly flashed CC26X2R.
• Broadcast requests are not required to receive a DataConfirm response any more.