danieledwardgeorgehitchcock

Thanks, I'll look into it. I'm guessing that it may be something to do with the install code. Hopefully, Bosch don't do anything too clever with it. Any ideas how...

That didn't work unfortunately however, I have found the documentation from the Zigbee chip manufacturer on how they implement install codes in their SDK. I am going to do some...

This looks promising: > To derive a link key from the installation code and store that into the key table on the Z3 Gateway, which acts as the Trust Center...

So, I feel that I am dangerously close to this, but I cannot quite figure out what I am doing wrong. Based on the documentation, the install code is a...

I have the Sonoff ZBDongle-P running Z-Stack 3

I already run the Dev branch (latest-dev) in Docker. Tried updating it just now via docker-compose but it said that it was up-to-date..? I proceeded to add the extension and...

So, the above was me being an idiot. I dropped the container and re-created it. The function loaded successfully and.... WE HAVE A SUCCESSFUL JOIN!!!! ``` [Function: Buffer] { Zigbee2MQTT:debug...

I am guessing the extension above is just a proof of concept to see if we could successfully join the devices to Z2M. If I was to see this working...

It Looks like the install code functionality was added to the Deconz API in [this commit](https://github.com/dresden-elektronik/deconz-rest-plugin/commit/24c7ff9d3047b7a6bde698e56d734120b63025ee) As for Zigbee2MQTT support (it is quite a recent feature), I think it has...

Just done some further digging on this.. Looks like the function was stubbed out when adding install code support for EZSP and Z-Stack [Here are the lines](https://github.com/Koenkk/zigbee-herdsman/blob/12fea9e30f0d4f603c8b317ab354e1a581a24432/src/adapter/deconz/adapter/deconzAdapter.ts#L187-L189)