The instructions for setting up deconz development on Linux is documented in the readme as:

sudo apt install deconz-dev
(clone repo)
(build)

But one also need the "build-essential" package. One solution is to update the readme. Seeing as there is already a deconz-dev package, perhaps a better way is to update that package with a dependency on "build-essential"?

After searching a lot on the HA Forum how to maintain the status of my zigbee2mqtt devices after restart, I was pointed to a specific mqtt configuration.
It does work for me and if it is correct, I feel it can probably help others if it is document in the readme here rather than only on the zigbee2mqtt website.
https://www.zigbee2mqtt.io/integration/home_assistant.html

mqtt:
  discovery

I like to suggest fleshing out README.md with inspiration from zsmartsystems/com.zsmartsystems.zigbee

https://github.com/zsmartsystems/com.zsmartsystems.zigbee/blob/master/README.md

This to make README.md contain more informative information about its functionality and capabilities.

My thinking is that a more explanatory README.md might attract more developers?

Good idea to update README.md with some description copied from com.zsmartsystems.zigbee or?

• https://github.com/zsmartsystems/com.zsmartsystems.zigbee

com.zsmartsystems.zigbee has fleshed out its own README.md with a lot of detailed information.

• https://github.com/zsmartsystems/com.zsmartsystems.zigbee/blob/master/README.md

Silicon Labs Ember EM35x / EFR32

The library suppor

Documentation says expected values are ("AP", 0) ("AP", 1) ("AP", 2)
I think there should be a snippet of code showing that it only works as:
set_parameter("AP", bytearray("\x00","utf8"))
set_parameter("AP", bytearray("\x01","utf8"))
set_parameter("AP", bytearray("\x02","utf8"))

The dependencies of the integrations are currently managed through docstring on class level in a specific format. Use a manifest file instead - it makes dependencies management and parsing faster and more robust.

For more complex plugins it might be necessary to include a separate documentation besides the README. It's easy to do that with the web interface but it would be more conclusive to have an additional button in the plugins overview of the backend plugin.

Additionally it would be perfect to directly link from that site to a blog entry on the smarthome webpage. Either by URL (direct links to the

Currently users must set supported clusters through both the Network Manager set supported cluster commands, and also through the Transport options. This is obviously messy and error prone and everything should be done through the network manager.

Should be fixed along with #411

What hardware would you recommend someone to buy for Z-Stack 3.x Zigbee coordinator firmware?

• https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator

Personally I am low on funds right now so thinking of just waiting for someone like Electrolama to start mass-producing and selling plug-and-play CC2652-based adapters such as their [Zig-a-zig-ah ("ZZH") USB-stick](https://electrol

currently most ZDO and ZCL request/response do not handle well properties that are list. They rely on the Object.ToString() method that just print the type of the list:

[14:21:10 DBG] RX CMD: NetworkAddressResponse [20978/0 -> 0/0, cluster=32768, transId=, status=SUCCESS, ieeeAddrRemoteDev=17880104E15812, nwkAddrRemoteDev=20978, startIndex=0, nwkAddrAssocDevList=**System.Collections.Generic.Li