Zigbee binding

[weakfl]

@Kim_Andersen

Does anyone actually have a working Zigbee network?
If yes, which hardware (coordinator) ?

Sure do, running for weeks without issues:
Telegesis, BJ 6711U (x2), BJ 6715U, BJ 6735, BJ 6735/01, BJ 6736 (x2), Tradfri

[amarpulli (amarnathreddy)]

hi chris,

Yes finally bundles are gone into active state in my workspace. I am currently using eclipse

smarthome 0.10- SNAPSHOT. I have been set COM PORT in Paper UI. But CC2531MEK

Coordinator not goint to ONLINE State. I have connected CC2538 device to COM Port. I got error

in log files.

11:47:46.317 ERROR [safeCall-14] An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.zigbee.cc2531.handler.CC2531Handler@7d56725f': com/zsmartsystems/zigbee/ZigBeeKey
java.lang.NoClassDefFoundError: com/zsmartsystems/zigbee/ZigBeeKey
        at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.initialize(ZigBeeCoordinatorHandler.java:231) ~[?:?]
        at org.openhab.binding.zigbee.cc2531.handler.CC2531Handler.initialize(CC2531Handler.java:45) ~[?:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [123:org.eclipse.smarthome.core:0.10.0.201808211930]
        at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [123:org.eclipse.smarthome.core:0.10.0.201808211930]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
        at java.lang.Thread.run(Thread.java:745) [?:?]
11:47:46.325 ERROR [safeCall-14] Exception occurred while initializing handler of thing 'zigbee:coordinator_cc2531:eb379b38': com/zsmartsystems/zigbee/ZigBeeKey
java.lang.NoClassDefFoundError: com/zsmartsystems/zigbee/ZigBeeKey
        at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.initialize(ZigBeeCoordinatorHandler.java:231) ~[?:?]
        at org.openhab.binding.zigbee.cc2531.handler.CC2531Handler.initialize(CC2531Handler.java:45) ~[?:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [123:org.eclipse.smarthome.core:0.10.0.201808211930]
        at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [123:org.eclipse.smarthome.core:0.10.0.201808211930]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
        at java.lang.Thread.run(Thread.java:745) [?:?]
11:47:46.326 INFO [safeCall-12] 'zigbee:coordinator_cc2531:eb379b38' updated: UNINITIALIZED (HANDLER_INITIALIZING_ERROR): com/zsmartsystems/zigbee/ZigBeeKey
11:47:46.339 INFO [safeCall-14] 'zigbee:coordinator_cc2531:eb379b38' changed from INITIALIZING to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): com/zsmartsystems/zigbee/ZigBeeKey

Anything I have left in configuration in PaperUI.

Best Regards,

Amar.

[chris (Chris Jackson)]

Probably you have some sort of incompatibility between the libraries (the com.zsmartsystems.zigbee files) and the openhab binding bundles. The current binding is not compatible with the latest libraries - I’m waiting for this change to be merged into openHAB (the PRs were made a week or more back, so we just have to wait).

If you want to test with the latest sources, then as I suggested previously, using the console is a LOT easier as there are a lot less parts of the machine that you have to get working.

[amarpulli (amarnathreddy)]

Can I use previous libraries (com.zsmartsystems.zigbee-1.1.0 files).

[chris (Chris Jackson)]

No - the current version that works with the binding is 1.0.14 I think. The changes were made in 1.1.0.

[amarpulli (amarnathreddy)]

Currently am using OpenHAB zigbee bindings are 2.4.0.qualifier.

Can you please tell us which have to use.( OpenHAB zigbee bindings)

[chris (Chris Jackson)]

@amarpulli

Can you please tell us which have to use

I just did.

If you want to use the binding, then you need to use the versions that are currently used with the binding. This is 1.0.14.

I continually recommend to you to use the console, but you do not want to do this and you make things a lot more complicated for yourself.

I suggest that we stop the discussion on this thread since it is not really related. If you require further help, let’s discuss elsewhere.

[amarpulli (amarnathreddy)]

Sorry about that… I will switch to console.

But really didn’t get understand console. If you give some information about that for me easy to learn.

How to access the console.

[chris (Chris Jackson)]

Please lets stop the discussion here. Please start another thread specific to your issue, but please try and ask specific questions - not just “give me some information” or “how to access console” as I have already told you this yesterday!

You need to work through the issue and try and solve your problems. If you have specific questions, then I’m happy to try and answer them, but please be specific.

[amarpulli (amarnathreddy)]

chris i am new to this zigbee console application environment . I didn’t get understand properly.So that’s why asking continuously. I followed the your suggestion. I tried my self, how to run zigbee console application. But unable to run console application. I saw doc here. Do you mean run the console application in Command Prompt. Initially i can work in console application.
Then I will start work with openhab bindings.

[chris (Chris Jackson)]

Yes - using the console is a LOT easier. There is a LOT less infrustructure required to get it working. openHAB required a lot of additional bundles and debugging the low level zigbee libraries from within OH is very difficult.

Please let’s take this conversation to another thread. Please!

[Kim_Andersen]

@chris
Is it possible to delete a thing which has been added but not fully discovered (meaning, it´s unknow). I cant seem to remove this by deleting the thing. The binding/coordinator still announce it next time I run the discovery.

[Kim_Andersen]

@chris

@Kim_Andersen

The Presence detection works, almost!. But It doesnt seem like it will release the trigger again.

ZigBee does set a flag to notify if it will reset the motion/presence after some time. Currently the binding doesn’t do anything with that flag, but it could use it if needed.

Maybe I’ll get the device out of the box and have a look when it arrives…

@chris would it be too much hassle to add this flag (or set it, or whatever), so I can test if thats whats needed for the Trust motion sensor? I cant get it to release the trigger.

(I just started all over again, but this time I will not try add any Xiaomi devices, just to see if it continues to run for more than 2 days. Sofar I have the Philips Hue motion sensor, Trust motion sensor and Osram plug added without any problems).

[nibi79 (NB)]

hi,

I use the following components:

• a CC2531 stick with CC2531ZNP-Pro-Secure_LinkKeyJoin (from Z-Stack_Home_1.2.2a)
• ZigBee Binding 2.3.0
• these two Xiaomi Aqara devices:
  https://www.aliexpress.com/item/New-Updated-Xiaomi-Aqara-Door-Window-Sensor-Zigbee-Wireless-Connection-Smart-Mini-door-sensor-Work-With/32816037464.html?spm=a2g0s.9042311.0.0.67634c4d6hcrRN
  and
  https://www.aliexpress.com/item/New-Original-Xiaomi-Aqara-Temperature-Humidity-Sensor-Smart-Home-Device-Air-Pressure-Work-With-Android-IOS/32887275362.html?spm=a2g0s.9042311.0.0.67634c4d6hcrRN

Both devices are dicovered but without battery channel and the door/window sensor ist discovered as a switch not as a contact:

Can I do something or is it up to the devices and/or the binding?

[chris (Chris Jackson)]

@nibi79

Can I do something or is it up to the devices and/or the binding?

There is probably nothing that you can do.

The binding searches for a set list of features - if the device doesn’t support those features, then you don’t get to see them.

It looks like the device is reporting a binary switch, so the binding provides a switch. It is not reporting the more standard sensors from what I see here.

[nibi79 (NB)]

hi Chris,

thank you for your awnser.

Ok I understand that the the devices reports that it is a binary switch -> so it is a switch.

I’ve tested the devices with the CC2531stick in IoBroker and there I have the battery status:

So it is really not supported by the device? (perhaps the list of supported feature is no ‘standard’ so it’s not provided by the binding)

[chris (Chris Jackson)]

It looks like it should show both battery percent and also voltage. The binding does support both of these channels (assuming of course they are the standard attributes, but I guess they are).

However, if the device was not awake when the binding did the discovery, then it may not have received the responses it needed to decide that this channel was supported.

These sensors tend to just send the data periodically - it may be that IoBroker is just displaying what it receives where the binding needs to scan the device to find out in advance what channels to present in ESH/OH.

[nibi79 (NB)]

While the binding did the discovery I pressed the button on the device all 3 seconds.

I removed the thing and tried to discover it again. That’s the output in the log:

2018-09-03 17:36:18.280 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00124B0014D9DE5F: Node SVC Discovery running

2018-09-03 17:36:18.282 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementRoutingRequest [0/0 -> 0/0, cluster=0032, TID=75, startIndex=0]

2018-09-03 17:36:18.284 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=50, addressMode=DEVICE, radius=31, sequence=117, payload=00 00]

2018-09-03 17:36:18.421 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=32818, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 00]

2018-09-03 17:36:18.423 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ManagementRoutingResponse [0/0 -> 0/0, cluster=8032, TID=NULL, status=SUCCESS, routingTableEntries=0, startIndex=0, routingTableList=[]]

2018-09-03 17:36:18.429 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00124B0014D9DE5F: Node SVC Discovery ManagementRoutingRequest returned CommandResult [SUCCESS, ManagementRoutingResponse [0/0 -> 0/0, cluster=8032, TID=NULL, status=SUCCESS, routingTableEntries=0, startIndex=0, routingTableList=[]]]

2018-09-03 17:36:18.431 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - 00124B0014D9DE5F: Routing table NEW: []

2018-09-03 17:36:18.433 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - 00124B0014D9DE5F: Routing table OLD: []

2018-09-03 17:36:18.435 [DEBUG] [com.zsmartsystems.zigbee.ZigBeeNode ] - 00124B0014D9DE5F: Routing table unchanged

2018-09-03 17:36:18.436 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00124B0014D9DE5F: Node SVC Discovery request ROUTES successful. Advanced to null.

2018-09-03 17:36:18.438 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00124B0014D9DE5F: Node SVC Discovery running

2018-09-03 17:36:18.444 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=32818, addressMode=null, radius=0, sequence=0, payload=00 00 00 00 00]

2018-09-03 17:36:18.446 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ManagementRoutingResponse [0/0 -> 0/0, cluster=8032, TID=NULL, status=SUCCESS, routingTableEntries=0, startIndex=0, routingTableList=[]]

2018-09-03 17:36:18.448 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00124B0014D9DE5F: Node SVC Discovery complete

2018-09-03 17:36:18.450 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - 00124B0014D9DE5F: Node 0 update

2018-09-03 17:36:18.453 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 00124B0014D9DE5F: Discovery notification

2018-09-03 17:36:18.458 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.

2018-09-03 17:36:18.556 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.

2018-09-03 17:36:19.492 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 03 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:19.494 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=3, commandId=10]

2018-09-03 17:36:19.496 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=03, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:19.498 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:20.716 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 04 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:20.719 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=4, commandId=10]

2018-09-03 17:36:20.722 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=04, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:20.725 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:21.894 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 05 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:21.898 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=5, commandId=10]

2018-09-03 17:36:21.901 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=05, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:21.905 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:23.959 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 06 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:23.963 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=6, commandId=10]

2018-09-03 17:36:23.967 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=06, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:23.972 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:28.618 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 07 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:28.619 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=7, commandId=10]

2018-09-03 17:36:28.621 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=07, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:28.623 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:29.691 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 08 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:29.694 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=8, commandId=10]

2018-09-03 17:36:29.696 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=08, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:29.699 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:33.103 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 09 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:33.106 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=9, commandId=10]

2018-09-03 17:36:33.109 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=09, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:33.112 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:41.218 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/1, destinationAddress=0/1, profile=0104, cluster=0, addressMode=null, radius=0, sequence=0, payload=1C 5F 11 0A 0A 05 00 42 16 6C 75 6D 69 2E 73 65 6E 73 6F 72 5F 6D 61 67 6E 65 74 2E 61 71 32 01 FF 42 1D 01 21 BD 0B 03 28 1E 04 21 A8 01 05 21 2E 01 06 24 00 00 00 00 00 0A 21 00 00 64 10 01]

2018-09-03 17:36:41.219 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=true, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=4447, sequenceNumber=10, commandId=10]

2018-09-03 17:36:41.221 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Basic: 53963/1 -> 0/1, cluster=0000, TID=0A, reports=[Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=5, attributeValue=lumi.sensor_magnet.aq2, Attribute Report: attributeDataType=CHARACTER_STRING, attributeIdentifier=65281, attributeValue=!½

2018-09-03 17:36:41.223 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - 53963/1: Unknown attribute 65281 in cluster 0

2018-09-03 17:36:52.862 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45cb

2018-09-03 17:37:06.653 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zigbee:device:616d64f3:00158d0002286a02' has been removed.

2018-09-03 17:37:06.668 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider}={service.id=419, service.bundleid=238, service.scope=singleton} - org.openhab.binding.zigbee

2018-09-03 17:37:06.697 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=420, service.bundleid=238, service.scope=singleton} - org.openhab.binding.zigbee

2018-09-03 17:37:06.707 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Initializing ZigBee thing handler zigbee:device:616d64f3:00158d0002286a02

2018-09-03 17:37:06.709 [hingStatusInfoChangedEvent] - 'zigbee:device:616d64f3:00158d0002286a02' changed from UNINITIALIZED to INITIALIZING

2018-09-03 17:37:06.715 [hingStatusInfoChangedEvent] - 'zigbee:device:616d64f3:00158d0002286a02' changed from INITIALIZING to OFFLINE

2018-09-03 17:37:06.717 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Coordinator status changed to ONLINE.

2018-09-03 17:37:06.720 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Coordinator is ONLINE. Starting device initialisation.

2018-09-03 17:37:06.723 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - 00158D0002286A02: NWK Discovery starting node rediscovery

2018-09-03 17:37:06.725 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=76, ieeeAddr=00158D0002286A02, requestType=0, startIndex=0]

2018-09-03 17:37:06.728 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=118, payload=00 02 6A 28 02 00 8D 15 00 00 00]

2018-09-03 17:37:06.741 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Start initialising ZigBee Thing handler

2018-09-03 17:37:06.744 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Checking endpoint 1 channels

2018-09-03 17:37:06.750 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Created 1 channels

2018-09-03 17:37:06.753 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Updating thing definition as channels have changed from [] to [zigbee:device:616d64f3:00158d0002286a02:00158D0002286A02_1_switch_onoff]

2018-09-03 17:37:06.829 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Initializing channel zigbee:device:616d64f3:00158d0002286a02:00158D0002286A02_1_switch_onoff with org.openhab.binding.zigbee.internal.converter.ZigBeeConverterSwitchOnoff@934127

2018-09-03 17:37:06.830 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:616d64f3:00158d0002286a02' has been updated.

2018-09-03 17:37:06.834 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: BindRequest [0/0 -> 53963/0, cluster=0021, TID=77, srcAddress=00158D0002286A02, srcEndpoint=1, bindCluster=6, dstAddrMode=3, dstAddress=00124B0014D9DE5F, dstEndpoint=1]

2018-09-03 17:37:06.840 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=53963/0, profile=0000, cluster=33, addressMode=DEVICE, radius=31, sequence=119, payload=00 02 6A 28 02 00 8D 15 00 01 06 00 03 5F DE D9 14 00 4B 12 00 01]

2018-09-03 17:37:06.989 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:616d64f3:00158d0002286a02 changed to UNKNOWN.

2018-09-03 17:37:08.704 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45a1

2018-09-03 17:37:08.711 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=53963/0, destinationAddress=0/0, profile=0000, cluster=32801, addressMode=null, radius=0, sequence=0, payload=00 00]

2018-09-03 17:37:08.715 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: BindResponse [53963/0 -> 0/0, cluster=8021, TID=NULL, status=SUCCESS]

2018-09-03 17:37:08.728 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ConfigureReportingCommand [On/Off: 0/0 -> 53963/1, cluster=0006, TID=78, records=[AttributeReportingConfigurationRecord: [attributeDataType=BOOLEAN, attributeIdentifier=0, direction=0, minimumReportingInterval=1, maximumReportingInterval=7200]]]

2018-09-03 17:37:08.730 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=CLIENT_TO_SERVER, disableDefaultResponse=false, manufacturerCode=0, sequenceNumber=120, commandId=6]

2018-09-03 17:37:08.732 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/1, destinationAddress=53963/1, profile=0104, cluster=6, addressMode=DEVICE, radius=31, sequence=120, payload=00 78 06 00 00 00 10 01 00 20 1C]

2018-09-03 17:37:12.549 [DEBUG] [e.dongle.cc2531.ZigBeeDongleTiCc2531] - Unhandled ZToolPacket type 0x45c9

2018-09-03 17:37:16.866 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - 00158D0002286A02: NWK Discovery node rediscovery request failed. Wait before retry.

2018-09-03 17:37:18.369 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - readSync request: ZclAttribute [cluster=ON_OFF, id=0, name=OnOff, dataType=BOOLEAN, lastValue=true, lastReportTime=Mon Sep 03 17:35:39 CEST 2018]

2018-09-03 17:37:18.369 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=79, ieeeAddr=00158D0002286A02, requestType=0, startIndex=0]

2018-09-03 17:37:18.372 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ReadAttributesCommand [On/Off: 0/0 -> 53963/1, cluster=0006, TID=7A, identifiers=[0]]

2018-09-03 17:37:18.373 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=121, payload=00 02 6A 28 02 00 8D 15 00 00 00]

2018-09-03 17:37:18.376 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=CLIENT_TO_SERVER, disableDefaultResponse=false, manufacturerCode=0, sequenceNumber=122, commandId=0]

2018-09-03 17:37:18.379 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/1, destinationAddress=53963/1, profile=0104, cluster=6, addressMode=DEVICE, radius=31, sequence=122, payload=00 7A 00 00 00]

2018-09-03 17:37:28.511 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - 00158D0002286A02: NWK Discovery node rediscovery request failed. Wait before retry.

2018-09-03 17:37:28.645 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Channel initialisation complete

2018-09-03 17:37:28.648 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 00158D0002286A02: ZigBee node property discovery start

2018-09-03 17:37:28.652 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 00158D0002286A02: ZigBee node property discovery using 53963/1

2018-09-03 17:37:28.655 [DEBUG] [scovery.ZigBeeNodePropertyDiscoverer] - 00158D0002286A02: ZigBee node property discovery complete: {zigbee_logicaltype=END_DEVICE, zigbee_powerlevel=FULL, modelId=lumi.sensor_magnet.aq2, zigbee_networkaddress=53963, zigbee_powersource=DISPOSABLE_BATTERY, zigbee_stkversion=2, zigbee_datecode=20161128, zigbee_zclversion=1, vendor=LUMI, zigbee_powermode=RECEIVER_ON_IDLE, zigbee_powersources=[DISPOSABLE_BATTERY], hardwareVersion=2}

2018-09-03 17:37:28.668 [me.event.ThingUpdatedEvent] - Thing 'zigbee:device:616d64f3:00158d0002286a02' has been updated.

2018-09-03 17:37:28.675 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementBindRequest [0/0 -> 53963/0, cluster=0033, TID=7B, startIndex=0]

2018-09-03 17:37:28.677 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=53963/0, profile=0000, cluster=51, addressMode=DEVICE, radius=31, sequence=123, payload=00 00]

2018-09-03 17:37:30.014 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=7C, ieeeAddr=00158D0002286A02, requestType=0, startIndex=0]

2018-09-03 17:37:30.018 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=124, payload=00 02 6A 28 02 00 8D 15 00 00 00]

2018-09-03 17:37:38.808 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Error getting binding table

2018-09-03 17:37:38.818 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Polling initialised at 60220ms

2018-09-03 17:37:38.822 [hingStatusInfoChangedEvent] - 'zigbee:device:616d64f3:00158d0002286a02' changed from OFFLINE to ONLINE

2018-09-03 17:37:38.821 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0002286A02: Done initialising ZigBee Thing handler

2018-09-03 17:37:40.152 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - 00158D0002286A02: NWK Discovery node rediscovery request failed. Wait before retry.

2018-09-03 17:37:41.655 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=7D, ieeeAddr=00158D0002286A02, requestType=0, startIndex=0]

2018-09-03 17:37:41.657 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=125, payload=00 02 6A 28 02 00 8D 15 00 00 00]

2018-09-03 17:37:46.071 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 00158D0002320B4F: Node SVC Discovery running

2018-09-03 17:37:46.078 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: ManagementLqiRequest [0/0 -> 30442/0, cluster=0031, TID=7E, startIndex=0]

2018-09-03 17:37:46.084 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigB

[chris (Chris Jackson)]

I’d need to see the full log to know what’s happening - sorry. This is missing a lot of information.

[Domi]

@chris I got the ZigBee sniffer now (CC2531).

Unfortunately most traffic is shown as plain IEEE 802.15.4 traffic in WireShark when using ccsniffpiper, which I guess is not really useful to you?