Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Release Firmware for Conbee II and Raspbee II Radios #132

Open
meremortals70 opened this issue Sep 25, 2020 · 23 comments
Open

New Release Firmware for Conbee II and Raspbee II Radios #132

meremortals70 opened this issue Sep 25, 2020 · 23 comments

Comments

@meremortals70
Copy link

image

Has anyone had an opportunity to test the firmware with ZHA as yet?

Interested to hear any results if any before I give it a whirl
@Adminiuga
Copy link
Collaborator

You would get more feedback by asking on discord channel. This firmware works with 0.115.2

@meremortals70
Copy link
Author

Thanks for the quick response

@Adminiuga
Copy link
Collaborator

The main highlight of the new firmware -- setting a static source route is currently not implemented and currently there's no UI in ZHA to facilitate that. But automatic source routing is implemented in firmware so it would work independently of zha.

If you are on ConBee/Raspbee, the 0.115.2 uses new version of zigpy-deconz library which properly restores child devices connected directly to Conbee.

@meremortals70 meremortals70 reopened this Sep 28, 2020
@meremortals70
Copy link
Author

Gents just to let you know the new firmware for the Conbee II does not let any new devices join the network. Logs show a permit join however nothing joins.

I rolled back to the March firmware and was able to join devices again.

@Adminiuga
Copy link
Collaborator

Debug Logs? What device you tried to join?

Version:

2020-09-27 21:28:31 DEBUG (MainThread) [zigpy_deconz.api] Read parameter protocol_version respon
se: [268]
2020-09-27 21:28:31 DEBUG (MainThread) [zigpy_deconz.api] Command Command.version (0,)
2020-09-27 21:28:31 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x0d0300090000000000
2020-09-27 21:28:31 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0d0300090000053726
2020-09-27 21:28:31 DEBUG (MainThread) [zigpy_deconz.api] Version response: 26370500

New device joining:

etworkParameter.permit_join: 33>, b'<')
2020-09-27 21:29:54 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x0b320009000200213c
2020-09-27 21:29:54 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0b32000800010021
2020-09-27 21:29:54 DEBUG (MainThread) [zigpy_deconz.api] Write parameter permit_join: SUCCESS
...
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x17360032002b002202f
dff0004e4eef14a95feff57b41400000013000c0081e4eef14a95feff57b4148e00afefa3000102c3
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, <De
viceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NW
K address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xeee4>, 0, 
0, 19, b'\x81\xe4\xee\xf1J\x95\xfe\xffW\xb4\x14\x8e', 0, 175, 239, 163, 0, 1, 2, -61]
2020-09-27 21:30:14 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xeee
4, 14:b4:57:ff:fe:95:4a:f1
2020-09-27 21:30:14 INFO (MainThread) [zigpy.application] Device 0xeee4 (14:b4:57:ff:fe:95:4a:f1
) joined the network
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy.zdo] [0xeee4:zdo] ZDO request ZDOCmd.Device_annce:
 [0xEEE4, 14:b4:57:ff:fe:95:4a:f1, 142]
2020-09-27 21:30:14 INFO (MainThread) [zigpy.device] [0xeee4] Requesting 'Node Descriptor'
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy.util] Tries remaining: 2
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy.device] [0xeee4] Extending timeout for 0x21 reques
t
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request 
with tsn 33 under 34 request id, data: b'21e4ee'
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <D
econzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xeee4>, ep: 0, profile: 0x0000, clu
ster_id: 0x0013, data: b'81e4eef14a95feff57b4148e'
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (18, 
34, 0, <DeconzAddressEndpoint address_mode=2 address=0xEEE4 endpoint=0>, 0, <ZDOCmd.Node_Desc_re
q: 0x0002>, 0, b'!\xe4\xee', 2, 0)
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x12370019001200220002e4ee00000
0020000030021e4ee0200
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x123700090002002222
2020-09-27 21:30:14 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <Device
State.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 34]
2020-09-27 21:30:24 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x1f38000e000700e4ee1
258140004
2020-09-27 21:30:24 DEBUG (MainThread) [zigpy_deconz.api] Received simplified beacon frame: sour
ce=0xeee4, pan_id=0x5812, channel=20, flags=0x00, update_id=0x04
...
2020-09-27 21:30:25 DEBUG (MainThread) [zigpy.endpoint] [0xeee4:1] Manufacturer: IKEA of Sweden
2020-09-27 21:30:25 DEBUG (MainThread) [zigpy.endpoint] [0xeee4:1] Model: TRADFRI bulb E26 WS cl
ear 806lm

@meremortals70
Copy link
Author

meremortals70 commented Sep 28, 2020 via email

@Adminiuga
Copy link
Collaborator

Adminiuga commented Sep 28, 2020 •
edited
Loading

🤷
new firmware hasn't supposedly changed anything about joining. Don't think anyone on deconz complained about anything

@meremortals70
Copy link
Author

meremortals70 commented Oct 2, 2020 via email

@Adminiuga
Copy link
Collaborator

If restart/worm reboot does not fix it, then the problem is not with zigpy-deconz. If you have to cold boot it, then something is going on with the stick, i'm pretty sure re-plugging the stick and re-starting should fix it too.

https://www.home-assistant.io/integrations/zha/#debug-logging
if joining device is nearby, then you should see some messages. Compare the logs when it works and when it doesn't work

@meremortals70
Copy link
Author

meremortals70 commented Oct 2, 2020 •
edited
Loading

Thanks for the advice. My logic says if there was a problem with the radio than other functions would also fail however it is currently working as a coordinator quite happily.

Warm reboot doesn't work and neither does unplugging. Has to be a cold boot.

I will continue trying to diagnose.

@Hedda
Copy link
Contributor

Hedda commented Jan 27, 2021

@meremortals70 is your issue really a problem with that firmware version? Note that there is now newer firmware available as well:

http://deconz.dresden-elektronik.de/deconz-firmware/?C=M;O=D

deCONZ_ConBeeII_0x26680700.bin.GCF 30-Nov-2020 18:03 164387
deCONZ_ConBeeII_0x26680700.bin.GCF.md5 30-Nov-2020 18:05 69

deCONZ_RaspBeeII_0x26690700.bin.GCF 19-Dec-2020 11:19 164255
deCONZ_RaspBeeII_0x26690700.bin.GCF.md5 19-Dec-2020 11:20 70

I understand that dresden-elektronik is now recommending people to upgrade to latest firmware on both ConBee and RaspBee?

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually

@MattWestb
Copy link

MattWestb commented Jan 27, 2021 •
edited
Loading

@meremortals70 My experience of RaspBee I is that its needs one cold reboot then being used in deCONZ for pairing new devices after running for some time.
Perhaps is the bug fixed in newer firmware i dont knowing (have converted) but if not is one "personality" of the Rasb/Cornbee adapters.

@andir
Copy link

andir commented Feb 25, 2021

I am seeing the same error. The permit_join command succeeds and then no new devices can be discovered.

Feb 25 10:58:40 crappy x[7903]: 2021-02-25 10:58:40 DEBUG (MainThread) [zigpy_deconz.api] Command Command.write_parameter (2, <NetworkParameter.permit_join: 33>, b'<')
Feb 25 10:58:40 crappy x[7903]: 2021-02-25 10:58:40 DEBUG (MainThread) [zigpy_deconz.uart] Send: 0x0b130009000200213c
Feb 25 10:58:40 crappy x[7903]: 2021-02-25 10:58:40 DEBUG (MainThread) [zigpy_deconz.uart] Frame received: 0x0b13000800010021
Feb 25 10:58:40 crappy x[7903]: 2021-02-25 10:58:40 DEBUG (MainThread) [zigpy_deconz.api] Write parameter permit_join: SUCCESS

I tested this on version 0x26660700 & 0x26680700 on a ConBee II.
The device I tried to pair was an Aqara Temperature sensor (WSDCGQ11LM)

@andir
Copy link

andir commented Feb 25, 2021

After unplugging the ConBee II for about 30s and replugging it I was able to pair another device... Very frustrating :(

@MattWestb
Copy link

MattWestb commented Feb 25, 2021 •
edited
Loading

Its the "personality" of the deCONZ adapters. After some time online they need one cold boot for executing the permit_join command OK (and not only replaying with "SUCCESS" and not execute the command) and i have seeing that symptom for around 4 years in native deCONZ.

Post one issue in the deCONZ git and they may perhaps taking on look on it and perhaps fixing it in the future.

@meremortals70
Copy link
Author

Its the "personality" of the deCONZ adapters. After some time online they need one cold boot for executing the permit_join command OK (and not only replaying with "SUCCESS" and not execute the command) and i have seeing that symptom for around 4 years in native deCONZ.

Post one issue in the deCONZ git and they may perhaps taking on look on it and perhaps fixing it in the future.

100% agree Matt, but everyone denies it. It drives me nuts.

@MattWestb
Copy link

And i 110% agree with you !!

@gemolnar
Copy link

It's topical again. A new ConBee II firmware (0x266b0700) was released by the end of April 2021.
The question is the same as in the original post:

Has anyone had an opportunity to test the firmware with ZHA as yet?

Also, has anyone found a changelog for these firmwares? I did for the Phoscon software but not for the firmwares.

image

@MattWestb
Copy link

DE is normally not saying so much what they is doing in the closed source parts then its strictly secret.
But normally they is writing some line in the deCONZ release notes then rolling the firmware out.

@MattWestb
Copy link

Upcoming FW release is having some changes that DE is having implemented in de(F)CONZ but the serial protocol doc is not updated but little can being understand from the code implementation.
dresden-elektronik/deconz-rest-plugin#5080

If making problem for zigpy-DC or can using the new futures its better to knowing its in the pipe and users start getting problems.

@Adminiuga
Copy link
Collaborator

Feel free to update and share the results.

@MattWestb
Copy link

Sorry they have updated the dock but i have not reading it so not knowing if all the things is in side.
deCONZ-Serial-Protocol-en_1.21.pdf

@Hedda
Copy link
Contributor

Hedda commented Mar 16, 2022

FYI, deCONZ firmware changelog is available in the wiki for deconz-rest-plugin found here:

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog

(from https://github.com/dresden-elektronik/deconz-rest-plugin/wiki )

Can this be closed as zigpy-deconz should work with latest deCONZ firmware on ConBee, ConBee II, RaspBee, and RaspBee II?

https://deconz.dresden-elektronik.de/deconz-firmware/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@andir @Adminiuga @Hedda @gemolnar @MattWestb @meremortals70