[Deprecated] Generic Zigbee Drivers with Presence and Recovery

markus · November 20, 2020, 8:34am

Thank you, then I will have an edit similar to that code as part of the next release.

BlackCatPeanut · November 20, 2020, 9:30pm

Yes, it’s the generic one - Zigbee - Generic Switch (with Presence).

markus · November 23, 2020, 4:27am

Announcement

Updated all my Zigbee drivers to include the change needed for 2.2.4 since the previous way of doing it, as communicated to me by them earlier, turned out to have been incorrect.

gadget · November 27, 2020, 10:00am

I just got some ST outlets and paired them using your generic outlet driver @markus. I did not see any power usage from the plug and was wondering if the drivers supported power monitoring?

Rxich · November 28, 2020, 4:26am

Hey Markus, I’m not surprised they gave you incorrect info, either on purpose or they’re figuring it out as they go along…
And I’m not seeing the errors that @Mike sees, at all. I have your driver on my 2 tradfri repeaters and 4 Xbees. My hub is on 2.2.0.126( C4) and zero errors, so…
I suspect it’s actually a change HE made in the newer release platforms, not your driver

AnubizDK · November 30, 2020, 2:15pm

Hi @markus

I’m using your "Zigbee - Generic Switch (with presense) on a LLKZMK11LM Aqara Dual relay (model: lumi.relay.c2acn01) with great success.

But i’m getting a lot of traffic in the logs with some “PLEASE REPORT TO DEV” so here goes:

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 15:01:39.246 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 15:00:39.218 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:59:39.221 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:58:49.253 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:read attr - raw: 09530100009001FF4244032824052118000727000000000000000008212312092103176410006510006E20006F200094200095390000603E96398AAE13459739F029243C9839006C843C9B210000, dni: 0953, endpoint: 01, cluster: 0000, size: 90, attrId: FF01, encoding: 42, command: 0A, value: 44032824052118000727000000000000000008212312092103176410006510006E20006F200094200095390000603E96398AAE13459739F029243C9839006C843C9B210000 | msgMap:[raw:09530100009001FF4244032824052118000727000000000000000008212312092103176410006510006E20006F200094200095390000603E96398AAE13459739F029243C9839006C843C9B210000, dni:0953, endpoint:01, cluster:0000, size:90, attrId:FF01, encoding:41, command:0A, value:[raw:[deviceTemperature:24, RSSI_dB:0018, unknown2:0000000000000000, unknown3:1223, unknown4:1703, openClose:00, switch2:00, unknown10:00, unknown11:00, unknown9420:00, consumption:3C2429F0, voltage:4513AE8A, power:3C846C00, unknown9:0000], deviceTemperature:36, RSSI_dB:24, unknown2:0, unknown3:4643, unknown4:5891, openClose:false, switch2:false, unknown10:0, unknown11:0, unknown9420:0, consumption:0.010019764, voltage:2362.9087, power:0.01616478, unknown9:0], clusterInt:0, attrInt:65281]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:58:49.234 [warn](http://192.168.0.100/device/edit/113)PLEASE REPORT TO DEV - The Xiaomi Struct used an unrecognized tag: 0x94 (type: 0x20) (struct: 44032824052118000727000000000000000008212312092103176410006510006E20006F200094200095390000603E96398AAE13459739F029243C9839006C843C9B210000)

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:58:39.210 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:57:39.234 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:56:39.205 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:55:39.227 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:54:39.178 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:53:39.174 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000 | msgMap:[raw:catchall: 0104 000A 01 01 0040 00 0953 00 00 0000 00 00 0000, profileId:0104, clusterId:000A, clusterInt:10, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0953, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00]]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:53:17.249 [info](http://192.168.0.100/device/edit/113)Unhandled Event IGNORE THIS - description:read attr - raw: 09530100009001FF4244032823052118000727000000000000000008212312092103176410006510006E20006F200094200395390000603E96390D7E14459739F029243C98392052AB3D9B210000, dni: 0953, endpoint: 01, cluster: 0000, size: 90, attrId: FF01, encoding: 42, command: 0A, value: 44032823052118000727000000000000000008212312092103176410006510006E20006F200094200395390000603E96390D7E14459739F029243C98392052AB3D9B210000 | msgMap:[raw:09530100009001FF4244032823052118000727000000000000000008212312092103176410006510006E20006F200094200395390000603E96390D7E14459739F029243C98392052AB3D9B210000, dni:0953, endpoint:01, cluster:0000, size:90, attrId:FF01, encoding:41, command:0A, value:[raw:[deviceTemperature:23, RSSI_dB:0018, unknown2:0000000000000000, unknown3:1223, unknown4:1703, openClose:00, switch2:00, unknown10:00, unknown11:00, unknown9420:03, consumption:3C2429F0, voltage:45147E0D, power:3DAB5220, unknown9:0000], deviceTemperature:35, RSSI_dB:24, unknown2:0, unknown3:4643, unknown4:5891, openClose:false, switch2:false, unknown10:0, unknown11:0, unknown9420:3, consumption:0.010019764, voltage:2375.8782, power:0.083652735, unknown9:0], clusterInt:0, attrInt:65281]

[dev:113](http://192.168.0.100/logs#dev113)2020-11-30 14:53:17.215 [warn](http://192.168.0.100/device/edit/113)PLEASE REPORT TO DEV - The Xiaomi Struct used an unrecognized tag: 0x94 (type: 0x20) (struct: 44032823052118000727000000000000000008212312092103176410006510006E20006F200094200395390000603E96390D7E14459739F029243C98392052AB3D9B210000)

Please let me know if you need anything else and THANK YOU for these drivers…!

// Kenneth

badcatgary · December 2, 2020, 11:56pm

Hello,

Any plans to add a driver for the NEO / Tuya Water Leak Sensor? Ive’ tried some other generic moisture/leak drivers without success.

expo tuya com/product/599465

Thanks!

badcatgary · December 3, 2020, 11:36pm

Never mind… I was able to hack up the siren driver to work with the water sensor.

epw · December 9, 2020, 5:54pm

COPY AND PASTE THIS ROW TO THE DEVELOPER: fingerprint model:“SP 224”, manufacturer:“innr”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006,0008,0B05,1000,FC82”, outClusters:“000A,0019”, application:“10”

This particular variant of the Innr smart plug seems to generate some extra log spam, e.g.:

dev:5342020-12-09 12:38:25.187 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 01 01 0040 00 F7C0 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 01 01 0040 00 F7C0 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F7C0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:5342020-12-09 12:38:14.573 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 01 01 0040 00 F7C0 00 00 0000 0B 01 0100 | parseMap:[raw:catchall: 0104 0006 01 01 0040 00 F7C0 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F7C0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

Other than that it seems to work fine with v1.0.1.1123b

Rxich · December 21, 2020, 3:23pm

Hi Markus, This is info from a Linkind button, included with the LInkind zigbee plug, from amazon.
Can you include in generic button driver?

dev:74712020-12-21 10:19:41.324 am infoCOPY AND PASTE THIS ROW TO THE DEVELOPER: fingerprint model:“ZBT-DIMSwitch-D0001”, manufacturer:“lk”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0001,0003,0B05,1000,FD01”, outClusters:“0003,0004,0006,0008,0019,1000”

dev:74712020-12-21 10:19:41.320 am traceApplication: null

dev:74712020-12-21 10:19:41.316 am infoNOT IMPORTANT: Application ID is missing for the fingerprint. Try again.

dev:74712020-12-21 10:19:41.313 am traceModel: ZBT-DIMSwitch-D0001

dev:74712020-12-21 10:19:41.309 am traceManufacturer: lk

Product on amazon
https://smile.amazon.com/Linkind-Control-Wireless-Controlled-Expandable/dp/B08FDD99VD/ref=sr_1_1?dchild=1&keywords=linkind+plug&qid=1608564154&s=electronics&sr=1-1

fsjpm · December 23, 2020, 9:54pm

Hello Markus,

This is from a MOES plug linked below:

fingerprint model:“TS0112”, manufacturer:“_TYZB01_b1ngbmlm”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0003,0004,0005,0006,0702,0B04”, outClusters:“0019”, application:“43”

Works great, the socket and USB ports (as a set) can be individually switched.

markus · December 28, 2020, 2:17am

Thank you everyone, I’ll add these fingerprints to the driver and update some catch-all parts.

markus · December 28, 2020, 2:19am

This is an info log, just turn off info logging if you don’t want these in your logs.

alexandruy2k · January 11, 2021, 5:03pm

Hi Markus,

Can you please add this device to the driver as well?
fingerprint model:“TS011F”, manufacturer:"_TZ3000_00mk2xzy", profileId:“0104”, endpointId:“0B”, inClusters:“0000,0003,0004,0005,0006”, outClusters:“0019,000A”, application:“42”

It’s an Outlet from LIDL.

Also not sure if this is a bug or intended, while the on and off commands are working the toggle command does not. Nothing happens when I try the toggle command. Physically the outlet doesn’t toggle and the status doesn’t update.

Finally I noticed something a bit unexpected with the logs. When I send the on and off commands as expected I see this appearing in the info log. However when the physical button on the outlet is pressed nothing shows up in the info log. It does show up in the list of events and the state is updated correctly.
Not a big deal, but my expectation based on other devices and drivers was that there would be info level logs for status changes.

Rxich · January 18, 2021, 7:20pm

Hello, which driver is allowing control of the USB ports? I have Markus’s latest generic outlet(w/ presence) and don’t see USB control
Thanks

Rxich · January 29, 2021, 1:21am

Hey Markus, Very excited for the new oh-lalabs product.
Anyway using the generic driver for tuya valve & my xbee, I’m getting the "hubaction delay"errors below

sys:12021-01-28 08:06:13.131 pm Unable to execute hubAction:delay 2000 sent from Valve zig 3.0, invalid or unspecified protocol.

app:41732021-01-28 07:51:41.072 pm infoDelay Over: Off: Plug Washing Light → delayed: 0:03:00 (cancelable)

sys:12021-01-28 07:50:05.119 pm Unable to execute hubAction:delay 2000 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.

app:41732021-01-28 07:48:40.973 pm infoAction: Off: Plug Washing Light → delayed: 0:03:00 (cancelable)

app:41732021-01-28 07:48:09.884 pm infoAction: Cancel Delayed Actions

sys:12021-01-28 07:41:19.048 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:41:19.046 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:40:52.139 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:40:52.135 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:12:57.064 pm Unable to execute hubAction:delay 2000 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:12:19.057 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:12:19.055 pm Unable to execute hubAction:delay 200 sent from XBEE3_UFL_ADTN_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:11:52.074 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:11:52.068 pm Unable to execute hubAction:delay 200 sent from XBEE_S2C_2_PC_VFD, invalid or unspecified protocol.

sys:12021-01-28 07:06:13.100 pm Unable to execute hubAction:delay 2000 sent from Valve zig 3.0, invalid or unspecified protocol.

Shawn · February 2, 2021, 7:10pm

I use this driver for Xbee3 devices to able to have presence. When I mentioned the driver on the site I found it on, I was informed the driver is no longer maintained or whatever. The driver I have installed seems to work fine, is this the same as the driver in Package manager or should I use this driver from this site?

april.brandt · February 3, 2021, 12:47am

Welcome to the community! The drivers are the same. Markus is not currently doing much to maintain them because we are not able to update our hubs. But, he does what he can to help where he is able.

Shawn · February 3, 2021, 4:46am

Thank you for the welcome and info, I look forward to seeing what you guys come up with for your own platform. If I’m not mistaken, that’s the plan to release your own Hub/Controller? Can’t update your hubs wow its like that, Crazy.

markus · February 3, 2021, 9:40am

yes, we are blocked form updating. As for those issues you’re having, they are related to changes I can’t check since they are in a newer FW than what I can run. I have some changes that may fix parts of it, I’ll see if I push something new in a few days if I get some time, just very hard at work coordinating all our other internal projects.