Non standard device?

Add-ons Bindings
1

Hi,
I just bought a Xiaomi Aqara vibration sensor and zigbee binding successfully discovered it.
The binding created a thing with a single switch channel and I expect that it was switched to ON shaking the sensor. Unfortunately it isn’t.
This is the log when I move the sensor

2020-05-16 10:06:57.407 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX EZSP: EzspIncomingMessageHandler [networkId=0, type=EMBER_INCOMING_UNICAST, apsFrame=EmberApsFrame [profileId=0104, clusterId=0101, sourceEndpoint=1, destinationEndpoint=1, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=60], lastHopLqi=255, lastHopRssi=-46, sender=BB85, bindingIndex=255, addressIndex=255, messageContents=18 08 0A 55 00 21 01 00]

2020-05-16 10:06:57.411 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=BB85/1, destinationAddress=0000/1, profile=0104, cluster=0101, addressMode=DEVICE, radius=0, apsSecurity=false, ackRequest=false, apsCounter=60, rssi=-46, lqi=FF, payload=18 08 0A 55 00 21 01 00]

2020-05-16 10:06:57.415 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX ZCL: ZclHeader [frameType=ENTIRE_PROFILE_COMMAND, manufacturerSpecific=false, direction=SERVER_TO_CLIENT, disableDefaultResponse=true, manufacturerCode=0, sequenceNumber=8, commandId=10]

2020-05-16 10:06:57.418 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: ReportAttributesCommand [Door Lock: BB85/1 -> 0000/1, cluster=0101, TID=08, reports=[AttributeReport [attributeDataType=UNSIGNED_16_BIT_INTEGER, attributeIdentifier=85, attributeValue=1]]]

2020-05-16 10:06:57.422 [DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: ReportAttributesCommand [Door Lock: BB85/1 -> 0000/1, cluster=0101, TID=08, reports=[AttributeReport [attributeDataType=UNSIGNED_16_BIT_INTEGER, attributeIdentifier=85, attributeValue=1]]] 

2020-05-16 10:06:57.426 [DEBUG] [.zsmartsystems.zigbee.zcl.ZclCluster] - BB85/1: Unknown Server attribute in 85 cluster 257

This mean that the device isn’t zigbee standard? Can I solve in any way?

2

The Xiaomi Aqara Sensors are 100 Percent Zigbee Devices. What is your Gateway?

3

I checked the latest ZCL and this attribute isn’t listed. What’s worse is that this isn’t flagged as manufacturer specific, so yes, this looks to me to not be compliant.

In theory we could create a static definition that adds these features. If you look at the sourcecode in the binding there are other examples of this so maybe you can come up with a PR to add this support.

1 Like
4

Where can I find the source code? Folder /usr/share/openhab2/addons is empty (I installed openHab on raspberry via repository)

5
6

Do you refer to “lumisensor86sw2.xml”? I don’t understand what I can do to solve the problem

7

Yes - well, probably not that file, but a similar file will need to be generated for the new device with the appropriate attributes, and then there’s another discovery.txt file that also needs to contain the discovery information for the device - that will also need to be updated to point at the thing type XML file.

8

And do you think is possible to generate this file for the vibration sensor? Can I provide some kind of info to help you?

9

I’m still trying to add Aqara Vibration sensor to the binding.
This device (called DJT11LM) works with zigbee2mqtt.

In these files messages from the sensor are explained, but I still didn’t understand what file I have to modify/create on the zigbee binding.

https://github.com/Koenkk/zigbee2mqtt/files/2364518/fromZigbee_changes.txt
https://github.com/Koenkk/zigbee2mqtt/files/2364517/devices_changes.txt

10

I’m not sure what this is or how to interpret it. This is clearly source code from another project, but I have no idea what the data structures mean - sorry. I can’t directly link these to how this works within the ZigBee porotocol.