Zigbee binding

zigbee
beginners
Tags: #<Tag:0x00007f0144b29930> #<Tag:0x00007f0144b297f0>

(Kim Andersen) #1385

Are these problems unique for Ember coordinators? I think it could explain some of my problems.


(Chris Jackson) #1386

Yes, I also fixed the default on the channel in the PR I referenced earlier.

If you have an error with the boost mode then please can you post this here?

Thanks


(Chris Jackson) #1387

What problems specifically? If I remember correctly, your system was initialising fine, and coming online? If so, it’s not related to this.


(dbadia) #1388

Hi -
Would like to start testing the Zigbee binding with an Orbit hose timer I have. Where can I get the latest build?

I skimmed through this post but didn’t see anything. The one link I found was broken.

Thanks
Dave


(Scott Rushworth) #1389

The latest is in the snapshot builds.


(Kim Andersen) #1390

It did/does initialise (partly)
But as mentioned a coupple of days back, it breakes communication after a few days (latest it ran for aprox 12 day, where I was on a vacation. Normally it manage to run for 2-4 days then all Zigbee communication seems to stop).

After rebooting (cold start of the Rpi, warm reboot does not work) the coordinator comes back to live, and lately also found my Philips Hue devices as well. But the Trust motion sensor is still offline . And I have not been able to get it back online again.

Why I ask if this could be related, is because I use an Ember coordinator as well, (Elelabs Rpi Shield). And I really have a feeling there is something wrong somewhere, either with the shield itself, the binding or something. It can´t possibly be the intention, that I would have to restart (could start) the Rpi every few days, just to make sure it continues to work?


(Chris Jackson) #1391

This is what I thought, and in this case it DOES initialise, and it works. Then the issues discussed above are in no way related since these prevent the device being used at all.

Ok, but just because you use the same hardware does not mean it’s related :confused:. The issues are completely different - as mentioned, the issues we were discussing above relate to the initialisation of the dongle - setting the channel, and setting the PANID - this is not an issue that you had.

I’m not saying that you don’t have issues, and it would be really useful if you could provide sniffer logs as mentioned some time back as this is really the only way to see what is happening in your system.


(Kim Andersen) #1392

I did see you message regarindg a sniffer log, but honestly, I have no idea how to make this sniffer log. I may have missed some messages though. But since I´m using the Elelabs Rpi Shield, I would probably need some help/guide on how to anyway.


(Kim Andersen) #1393

@chris

Found the message about the Sniffer log. And as far as I understood, Wireshark runs on mac or windows.
But, if I get this correctly, the sniffer log part (the actual sniffer jar) can run in Linux (openhabian) and can log to a wireshark compatible logfile… (option -w). I guess I could use that, log the communication and send you this log or?

I really do want to participate in eliminating all kinds of issues there may be.


(Chris Jackson) #1394

Yes - that would be perfect. Note though that you need an extra dongle - ie you can’t use the sniffer at the same time as the coordinator/binding.

There is a new option in the sniffer as well that I’ve probably not documented yet, and this allows the file to be truncated at a certain length (eg start a new file every 10MB). With this it should be possible to log permanently without files getting too big.

If you don’t have another stick, I might be able to send you one to borrow while we debug this.

It really would be appreciated. Silabs were not very useful - they agreed the documentation is not usable, and said they would have to look at the sourcecode to work out how it works, but have not come back to me to tell me what the options mean (despite me asking a number of times now). If we can get some logs, then I can use this to prompt them to look at this issue again.

Thanks.


(Kim Andersen) #1395

Hmm I dont have another stick… I use the Elelabs Rpi Shield, remeber :slight_smile: I have thought about getting an USB stick, since this Rpi shield cant be moved to another platform, if I want to. And it was mainly bought for testing Zigbee only.

It´s really bad silabs isn´t answering your requests. One would have thought they would be interessted in this community as well.


(Chris Jackson) #1396

It would be great if you could get one so we can start to debug this :slight_smile:


(Kim Andersen) #1397

I will. Just need to figure out which one. Tried searching for the Telegesis, but couldn´t fine anyone in europe.


(Chris Jackson) #1398

These ones are probably the best -:

https://www.digikey.co.uk/product-detail/en/silicon-labs/RD-0002-0201/336-3333-ND/5399115

Unfortunately they don’t come with firmware, so it needs programming. If you wanted to go for this, I could get one and program it for you.

This is fundamentally the same chip as on the Pi board you have.


(Kim Andersen) #1399

If you say it´s the best, then thats the one we´ll go for :slight_smile:
And yes, I would probably need you to get one and programm it, as I have no idea how to…

Just tell me when and how to pay, and I´ll pay!


(Ole Kristian Lona) #1400

Hello, Chris!

I just installed some Osram Lightify GU10 bulbs (PAR16 50 TW) in my home. These only dim down to 5%, and completely refuse to turn completely off. The binding only sees a dimmer and color temperature.

Is this something you would know anything about? When googling, I saw that there was some kind of hack at some point to make them turn off when using them with a Hue gateway and binding. (Osram PAR16 50 TW OnOffState not managed correctly?)

I can obviously create logs when I get home, if needed.


(Chris Jackson) #1401

I have not had any problems with Osram bulbs, and I’ve tested with many different ones, so please provide a debug log and I will have a look.


(Ole Kristian Lona) #1402

Ok. I will. For obvious reasons, the bulbs are currently powered off, so I cannot reach them until this evening.


(Ole Kristian Lona) #1403

I have a greater problem than I first thought, that needs sorting. Is there any procedure to completely wipe all ZigBee information from OpenHab and the cc2531 stick? I have two devices that always show up in my Inbox, which I have just ignored for a while. After I added one IKEA bulb and the three Osram bulbs, all ZigBee communication in the other side of my living room stopped working.

I did also try out the zigbee2mqtt module with a different stick, on a separate Raspberry, but I assume that shouldn’t interfere with the OH ZigBee binding? The devices that stopped working have never been connected to this second ZigBee environment.


(Ole Kristian Lona) #1404

Ok, Chris, would you like the debug log from adding the device, to see properties, or just when adjusting level to 0? Here is the log after I first set it successfully to 44%, and then reduced it to 0. As you can see, it stepped down to 12, and then went to 5. After it goes to 5, it stays there, and to me, it looks like it keeps sending commands to go to 5, but I don’t really know what to look for in these logs…

09:37:53.049 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=25, apiId=44 81, data=FE 19 44 81 00 00 08 00 23 4B 03 01 00 0A 00 EA 44 60 00 00 05 08 2A 0B 04 00 23 4B 1D 27, checksum=27, error=false
09:37:53.058 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=19235/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=08 2A 0B 04 00]
09:37:53.063 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=false, manufacturerCode=0, sequenceNumber=42, commandId=11]
09:37:53.068 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: DefaultResponse [Level Control: 19235/3 -> 0/1, cluster=0008, TID=2A, commandIdentifier=4, statusCode=SUCCESS]
09:37:53.363 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 13 49 60 00 00 07 18 29 0A 00 00 20 71 23 4B 1D 94)
09:37:53.370 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 13 49 60 00 00 07 18 29 0A 00 00 20 71 23 4B 1D 94, checksum=94, error=false
09:37:53.382 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=19235/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=18 29 0A 00 00 20 71]
09:37:53.387 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=41, commandId=10]
09:37:53.392 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Level Control: 19235/3 -> 0/1, cluster=0008, TID=29, reports=[Attribute Report: attributeDataType=UNSIGNED_8_BIT_INTEGER, attributeIdentifier=0, attributeValue=113]]
09:37:53.397 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0000149A: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=113, lastReportTime=Fri Sep 28 09:37:53 UTC 2018]
09:37:53.403 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0000149A: Channel zigbee:device:ab2573ab:7cb03eaa0000149a:7CB03EAA0000149A_3_switch_level updated to 44
09:37:53.408 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0000149A: Updating ZigBee channel state zigbee:device:ab2573ab:7cb03eaa0000149a:7CB03EAA0000149A_3_switch_level to 44
09:37:53.826 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 70 4E 60 00 00 07 18 2A 0A 00 00 20 1E 23 4B 1D 9C)
09:37:53.834 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 70 4E 60 00 00 07 18 2A 0A 00 00 20 1E 23 4B 1D 9C, checksum=9C, error=false
09:37:53.843 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=19235/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=18 2A 0A 00 00 20 1E]
09:37:53.850 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=42, commandId=10]
09:37:53.858 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Level Control: 19235/3 -> 0/1, cluster=0008, TID=2A, reports=[Attribute Report: attributeDataType=UNSIGNED_8_BIT_INTEGER, attributeIdentifier=0, attributeValue=30]]
09:37:53.868 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 B9 C6 03 01 00 07 00 8C 4E 60 00 00 07 18 58 0A 00 00 20 0C B9 C6 1D 0D)
09:37:53.868 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0000149A: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=30, lastReportTime=Fri Sep 28 09:37:53 UTC 2018]
09:37:53.880 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 B9 C6 03 01 00 07 00 8C 4E 60 00 00 07 18 58 0A 00 00 20 0C B9 C6 1D 0D, checksum=0D, error=false
09:37:53.887 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0000149A: Channel zigbee:device:ab2573ab:7cb03eaa0000149a:7CB03EAA0000149A_3_switch_level updated to 12
09:37:53.892 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=50873/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=18 58 0A 00 00 20 0C]
09:37:53.897 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0000149A: Updating ZigBee channel state zigbee:device:ab2573ab:7cb03eaa0000149a:7CB03EAA0000149A_3_switch_level to 12
09:37:53.901 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=88, commandId=10]
09:37:53.914 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Level Control: 50873/3 -> 0/1, cluster=0008, TID=58, reports=[Attribute Report: attributeDataType=UNSIGNED_8_BIT_INTEGER, attributeIdentifier=0, attributeValue=12]]
09:37:53.928 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 5B 77 03 01 00 05 00 B3 4E 60 00 00 07 18 35 0A 00 00 20 0C B9 C6 1C 0F)
09:37:53.935 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 5B 77 03 01 00 05 00 B3 4E 60 00 00 07 18 35 0A 00 00 20 0C B9 C6 1C 0F, checksum=0F, error=false
09:37:53.928 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA000018B9: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=12, lastReportTime=Fri Sep 28 09:37:53 UTC 2018]
09:37:53.941 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=30555/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=18 35 0A 00 00 20 0C]
09:37:53.945 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA000018B9: Channel zigbee:device:ab2573ab:7cb03eaa000018b9:7CB03EAA000018B9_3_switch_level updated to 5
09:37:53.947 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=53, commandId=10]
09:37:53.951 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA000018B9: Updating ZigBee channel state zigbee:device:ab2573ab:7cb03eaa000018b9:7CB03EAA000018B9_3_switch_level to 5
09:37:53.954 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Level Control: 30555/3 -> 0/1, cluster=0008, TID=35, reports=[Attribute Report: attributeDataType=UNSIGNED_8_BIT_INTEGER, attributeIdentifier=0, attributeValue=12]]
09:37:53.962 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA00002089: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=12, lastReportTime=Fri Sep 28 09:37:53 UTC 2018]
09:37:53.969 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA00002089: Channel zigbee:device:ab2573ab:7cb03eaa00002089:7CB03EAA00002089_3_switch_level updated to 5
09:37:53.974 [DEBUG] [ing.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00002089: Updating ZigBee channel state zigbee:device:ab2573ab:7cb03eaa00002089:7CB03EAA00002089_3_switch_level to 5
09:37:54.849 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 4A 5A 60 00 00 07 18 2B 0A 00 00 20 0C 23 4B 1D A1)
09:37:54.856 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 23 4B 03 01 00 0A 00 4A 5A 60 00 00 07 18 2B 0A 00 00 20 0C 23 4B 1D A1, checksum=A1, error=false
09:37:54.865 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=19235/3, destinationAddress=0/1, profile=0104, cluster=8, addressMode=null, radius=0, sequence=0, payload=18 2B 0A 00 00 20 0C]
09:37:54.872 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=43, commandId=10]
09:37:54.883 [DEBUG] [rtsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Level Control: 19235/3 -> 0/1, cluster=0008, TID=2B, reports=[Attribute Report: attributeDataType=UNSIGNED_8_BIT_INTEGER, attributeIdentifier=0, attributeValue=12]]
09:37:54.892 [DEBUG] [531.network.impl.CommandInterfaceImpl] - <-- AF_INCOMING_MSG (FE 1B 44 81 00 00 08 00 B9 C6 03 01 00 05 00 9F 5A 60 00 00 07 18 59 0A 00 00 20 0C B9 C6 1D 09)
09:37:54.892 [DEBUG] [.converter.ZigBeeConverterSwitchLevel] - 7CB03EAA0000149A: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=12, lastReportTime=Fri Sep 28 09:37:54 UTC 2018]
09:37:54.905 [DEBUG] [531.network.impl.CommandInterfaceImpl] - Received Async Cmd: Packet: subsystem=null, length=27, apiId=44 81, data=FE 1B 44 81 00 00 08 00 B9 C6 03 01 00 05 00 9F 5A 60 00 00 07 18 59 0A 00 00 20 0C B9 C6 1D 09, checksum=09, error=false
09:37:54.908 [DEBUG] [.converter.ZigBeeBaseChannelConverter] - 7CB03EAA0000149A: Channel zigbee:device:ab2573ab:7cb03eaa0000149a:7CB03EAA0000149A_3_switch_level updated to 5