ConBee implementation #72
Comments
|
Hi! Could you perhaps contact me on telegram (@Koenkk)? |
|
I did some updates
serial:
port: null |
|
@Koenkk Is Conbee 2 support considered to be working as of now? I am currently pretty displeased with the CC2531 in my environment using HA 1.2 firmware (unable to pair more than 20 routing devices (ubisys), loosing devices from time to time and ended up splitting my network, also tried source routing variant, but that seemed to make it even worse). And since the Zigbee side used to work fine and appeared to be very stable with deCONZ and a Conbee (1) for about 1 year before switching to zigbee2mqtt (besides incomplete support for the ubisys window covering devices 😉), being able to use a Conbee (2) might be another option for me to try... Thanks, |
|
@felixstorm no it's not supported yet, you might want to give the CC2652R a try though Koenkk/zigbee2mqtt#1429 (which is fully supported in latest dev). |
|
@Koenkk Thanks, the CC2652R would also have been my next option - I will order one from TI and try it. The ConBee (1) was really stable in the past and the CC2652R is pretty new, that was the only reason for preference 😉. |
Just fyi for anybody following - I switched to the CC2652R and it has been working flawlessly for a few weeks now. |
|
Should this one be closed if Conbee/deconz is supported now as suggested by your answer... Sorry I have been and out of domotic and try to make progress on free time so I have been poking you on this topic here and there, sorry about that... Difficult to keep up will all the fork redirect I fall on and understand where the train is going exactly... :D |
|
Any news, expected timeline ? Looking forward to test this out |
|
u/potedesballj posted this on Reddit |
|
New reddit post says that Dresden Elektronik estimated that support will be ready mid-March 2020 https://www.reddit.com/r/homeassistant/comments/f8v81p/conbee_2_support_for_zigbee2mqtt_confirmed/ I wonder if this will only work with the newer ConBee II (ConBee 2) adapter or if it will also work with the older first-generation ConBee and RaspBee adapters as well? I know that both the new and the old ConBee adapters support the same serial UART protocol: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/158 |
|
It should work with ConBee I / II and RaspBee I / II since the protocol for all is the same. The difference is the device path:
|
|
Is this also working on windows? I have a conbee II plugged into my windows PC which I use for testing. It is connected as COM3 in device manager. How can I use it with zigbee2mqtt? |
|
Is it possible to test the Conbee build using the deconz branch? |
* Start on conbee * Updates. * conbee -> deconz. #72 * Initial suppport for reading parameters - Add basic frame parser - Handle slip protocol and crc calculation - Add queue for read and write parameters * Add dummy function DeconzAdapter.supportsLED() * Start working on write parameters * supportsLED() returns false * Implemented getCoordinator() * Added deCONZ adapter dummy functions * Implemented getCoordinatorVersion() * Implemented getNetworkParameters() * Added constants for APS layer * Startet APS layer Added readReceivedStateRequest, deviceStateRequest, deviceStateResponse, readReceivedDataRequest * Added APS layer parser functions parseDeviceStateResponse, parseReadReceivedDataResponse, parseReceivedDataNotification, * Added parser for APS responses * Refactored some deCONZ adapter functions * Added sendZclFrameNetworkAddress, sendZclFrameNetworkAddressWithResponse and sendZclFrameGroup * Added constants for deCONZ adapter * Added deCONZ driver functions for sending APS commands * Added discoverRoute, supportsDiscoverRoute dummy functions * Implemented NodeDescriptor * Added constants * Reworked debug messages and fixed send unnecessary device state requests * Some smal fixes * Implemented permit join * Fixed check DeviceStatus variables * implemented Active Endpoint request * Implemented simple descriptor * Removed reading request_id if data confirm fail * Fixed reading payload of data indication * Fix nodedescriptor devicetype * Added waitFor dummy function * Implemented lqi() * Implemented routingTable() * implemented bind() * implmented unbind() * Implemented removeDevice() * Changes at driver.ts * Fix for resolve aps request error * ieeeAddr to String now add '0x' prefix * Get correct APS data payload * Fixes for some adapter functions * Delete old code * Added constant * Added support of timeout for aps requests * Refactored deCONZ adapter functions * Added constants * Refactored driver functions and debug logs * Refactored frameparser debug logs * Updated deCONZ adapter to newest adapter version * Added device state intervall wand tweaked watchdog * Removed unused code * Removed unused code * Added received msg event, removed discoverRoute * Added catch for devicestaterequest * Handle default response when sending zcl message * Refactored debug print * Added /* istanbul ignore file */ Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
|
This has now been integrated and is available in the latest zigbee2mqtt dev branch. Many thanks @ChrisHae ! Keep in mind that this is not ready for production yet. It seems to start fine but unfortunately I couldn't pair any devices, nothing appeared in the log after resetting a device (tried with some Xiaomi plugs, sensors and an Innr bulb), log: https://pastebin.com/gBLANJHn |
|
I will update this over time and try to eliminate bugs, improve performance and add features. |
|
@Koenkk It seems devices not joining is a fw problem. Please try FW version deCONZ_ConBeeII_0x264a0700.bin |
|
Another thing to improve USB startup was found today by disabling Linux MTP probes and Network Manager messing with serial interface. This might be useful for the CC2531 too. Source: dresden-elektronik/deconz-rest-plugin#2419 (comment) MTP probes and Network Manager access for ConBee II can be disabled by following udev rules: After creating this file the udev rules needs to be reloaded: The difference should be visible in journald when plugging the USB dongle: |
|
@ChrisHae Thank you for your work on the ConBeeII support. I have a ConBeeII stick an I plan to use it with zigbee2mqtt. As mentioned, it starts correctly now on the |
|
I uploaded a fix to this problem to the deconz branch. In addition to the zdp permit join request there is now also a write parameter request that sets the permit join parameter. I created a pull request for the master branch. Then you can test if it works. |
|
@johras, unlikely you'll find many people who use Symphonisk to give you an opinion. Both Symphonisk and MI Aqara cube (in rotation) are quite weird zigbee devices as zigbee is not designed to handle multiple same messages to produce steps rotation. Zigbee made to guaranty delivery, not sequence nor low latency... you are quite lucky if it works well for you with CC2652RB. If you need a dimmer, better look for something transferring value instead of "pulse". Ideal example is Google Assistance - "Hey google, set brightness to 83" - works 100 of 100 attempts regardless. |
|
Guys, how have you updated the firmware on ConBee II? What is the stable way to do that? |
|
@amaciuc I followed the guide at https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually this worked flawlessly: ConBee You need to install the |
|
So what is the situation with the implementation? Is it stable? Does not seem like it is anymore in development. |
|
Mine works perfectly and has been rock solid. @ChrisHae does get involved if you have a potential bug otherwise not sure what other development is required? |
|
The only problem with Conbee II is LQI doesn't work for 99% of users... fix require coordination between Z2M and deCONZ which has never happened. Otherwise there is nothing to fix: mine works "in prod" for more than year with zero issues, cannot say that for my failed CC2652P experiment. |
|
It is working without any problem for me too. There are other implementations to be made? |
|
Rather not. Experimental means "buggy - we don't like it" :) |
Mine seems to be report close to 255 for most devices close by. There's one about 210 but that's the furthest out. So all appears to be ok for me in any case. |
|
Well I've tried z2m with my Conbee II on HA and despite following all instructions (setting up mosquitto, changing to the correct path `[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
I read through https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start but nothing helped. |
|
serial: |
|
i've some problems regarding reachability i get random timeouts in iobroker. Even for devices just 5m away and nothing in between while using the latest deconz firmware for conbee II. While older Firmware like 0x26680700 seems to work fine. @ChrisHae @manup @Smanar can we expect any updates from dresden electronic for newer firmwares? |
|
Ok, well that fixed it for me, thanks
… serial:
port: /dev/ttyACM0
adapter: deconz
|
|
finished I do not update everything works perfectly with the firmware: deCONZ_ConBeeII_0x26680700.bin |
|
@kwetnico: Only for you my friend! only for you :) Same firmware, and map works as it uses another attribute, the one collected during map request And on the list of devices it always 255 as this one built based on info from latest packet received a Conbee II sends something odd
|
|
Ok but for me no problem : |
|
I don't know if this should be posted under this, but why do I get for TouchLink scan that it's not supported? It should be according to deCONZ rest api at least. Using RaspBee 2. |
|
Some brave zigpy user (devs of jeedom) have making one future request for it dresden-elektronik/deconz-rest-plugin#3485 and is have being moved to there forum https://forum.phoscon.de/t/feature-request-touchlink-support-on-conbee-ii/340. Pleas posting more in the request issue and perhaps DE is implanting it so its not being one half product comparing with the first gens. |
|
So Dimmer Switch it is... :/ |
|
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 |
|
Any news regarding LQI? |
|
Nope |
Do not use the latest firmware |
I use this version of firmware |
|
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 |
and others
Hello, I have noticed you started on implementation of the conbee adapter. I am from dresden elektronik and we'd like to help with the implementation. What do you think is the best way to synchronize the workflow?
We could contribute the code for the following tasks, to start with:
... in the files driver.ts and conbeeAdapter.ts.
Furthermore if you need any documentation or hardware to proceed just drop me a line. E.g. a ConBee II stick or the deCONZ serial line protocol documentation.
Note that this adapter not only work with the ConBee USB stick but also with the RaspBee Zigbee module for Raspberry Pi, because they share the same serial protocol. A more generic adapter name, like phoscon or deconz adapter, might be more fitting.
The text was updated successfully, but these errors were encountered: