[Deprecated] Xiaomi / Aqara / Opple Drivers with Presence!

[markus]

@dwspmail

Any plans to include the on/off features for this?

Sure, that's a simple one, I've created a new thread for these types of drivers:

[Release] Generic Zigbee Drivers with Presence and Recovery

NOTE: These are NOT the Official Hubitat Generic Zigbee drivers, these are my take on how to do Generic Zigbee devices, they all include a Presence feature some people have liked. More device types will be added when inspiration strikes and time permits. Supported Devices Generic Zigbee Device Toolbox (can generate fingerprints, remove child devices, clean the Data, Preferences and State Variables sections of the device.) - Import URL Generic Zigbee Repeater (works with IKEA Trådfri Repeater…

[simon]

Any chance that the Zigbee Heiman Smoke Detectors are on your driver to-do list?

Hubitat has an official Heiman Gas Sensor driver but it does not work for the smoke detectors.

Thanks, Simon

[nutcracker]

@markus

Any device in particular you're looking for?

If I may ask (and I believe you’ve got it on your “todo” list) and that’s a driver for the vibration sensor (replacement to veeceeoh‘s version).

Thanks

[markus]

@simon

Zigbee Heiman Smoke Detectors

The only Zigbee smoke detectors on my list are the Aqara Honeywell ones. I don't have any others. Send me one (I'm in China and don't know where to get one of those) and I'll add it

@nutcracker

vibration sensor

I've written the driver, it has been tested and seems to work as expected, I'll push it to the development repo later today as Beta.

EDIT: It's in the repo, see the first post for the URL.

[nutcracker]

Thank you sir!

[reine.edvardsson]

@markus
Noticed one small issue with the pressure offset for the Xiaomi/Aqara Temperature & Humidity Sensor (not important, but thought you should know).

Seems like it doubles the offset to the pressure, when I look in the code, it doesn't make sense to me why it does that.
It measures 1011mbar, I am about 7 mbar of compared to the readings from close airports, so I add 7 and ends up at 1025. I change it back to 0, and is back at 1011. Tried 4 and ended up at 1019.
For me, that is close enough, but still an interesting issue

Other then that, thanks for the nice work!

[markus]

@reine.edvardsson

Seems like it doubles the offset to the pressure, when I look in the code, it doesn't make sense to me why it does that.

Nicely caught Don't think many saw this one. There was a bug that is still present in the Release version, this should be fixed in the current Beta, please test that one from the development branch.

[reine.edvardsson]

Nice, works perfectly in the beta

[simon]

Marcus PM me your snailmail address and I'll get you one.....

many thanks

[markus]

Announcement
Aqara Cube drivers are now released as Beta. The default button order is a bit different than the old driver. Turning Left is now lower button numbers than turning Right. If you want the old order, choose the Legacy button layout from the dropdown.

There is a dimmer feature which increases/decreases when turning left/right. This can be mirrored to actual lights or a volume control to make easier use of the turning motion.

In order to get the button order to be compatible with the old driver I did look at it, but the structure of this driver is very different. I do credit @veeceeoh's driver as a source of information, but it really isn't much more than maybe 1 or 2 lines of code that truly are the same, if that.

This is very much an untested driver, I just wrote it today. With that said, I believe it to be rather complete, but logging is still rather verbose and there may be uncaught clusters. The Flip event can be improved so as to use the actual source side reported by the device, there might also be other events that could be made to be better.

[brianspranger]

I just started to transition to your drivers. The first one was a temp/humidity sensor.

I got this in the log:

dev:8852020-07-12 07:00:17.543 pm warnUnhandled Event PLEASE REPORT TO DEV - description:catchall: 0104 0402 01 01 0040 00 B2C4 00 00 0000 01 01 | msgMap:[raw:catchall: 0104 0402 01 01 0040 00 B2C4 00 00 0000 01 01 , profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B2C4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:]

more info:

• endpointId: 01
• application:
• driver: v0.7.1.0701
• model: lumi.weather
• modelType: Aqara WSDCGQ11LM
• hasPressure: True
• manufacturer:

[markus]

@brianspranger

I got this in the log:

Thank you for reporting, I also want to take the opportunity to mention that there are no clusters that are important to catch which are not caught in any of my drivers. The reason I don't just catch and silence unknown clusters is that there may be some variation of a firmware somewhere sending data in some way I didn't know about. That is why I want to know about it, there is nothing that will break because of these messages.
The current Beta is already filtering this since there is nothing in the data sent that can be used.

[brianspranger]

do I grab the betas from github directly?

[markus]

@brianspranger

grab the betas from github

Yes, from the development branch. There is so far no way of submitting Betas only to HPM, and many of these don't have Release builds yet since I've not had enough feedback to be sure I should move them there.

[jwjr]

Just had this one, from your "Temperature & Humidity Sensor" driver:

dev:869 2020-07-12 09:00:31.470 pm warn Unhandled Event PLEASE REPORT TO DEV - description:catchall: 0104 0402 01 01 0040 00 2EA3 00 00 0000 01 01 | msgMap:[raw:catchall: 0104 0402 01 01 0040 00 2EA3 00 00 0000 01 01 , profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:2EA3, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[]]

Device data:

endpointId: 01
application: 03
driver: v0.7.1.0701
model: lumi.weather
hasPressure: True
manufacturer: LUMI

[markus]

@jwjr

Just had this one, from your "Temperature & Humidity Sensor" driver:

Thank you for reporting, same as above post, and filtered in the Beta version.

[Tarmacsurfer]

@markus - apologies if this is a stupid question, I've checked github and searched the forums but I can't find mention of this.

I've received the GZCGQ01LM and paired it with no problem, the hub recognises it and installs the driver with no issue. However, there's no mention of current lux attached to the device. I've tried resetting and pairing again, same problem. Here's the device info as displayed. Am I missing something in the setup?

[markus]

@Tarmacsurfer

I've tried resetting and pairing again, same problem.

When you did this, did you see this in the log:
Device confirmed LUX Report configuration ACCEPTED by the device

If not, press the button on the device and look for it in the logs. If that doesn't work something went wrong with the pairing. WITHOUT deleting the device from HE, run pairing again and look for that message in the logs.

[Tarmacsurfer]

Done, now working as expected. I'm not sure what was causing it to do that, third pairing (without deleting) gave a very different log return.

Thank you for the blindingly fast response.

[markus]

@markus

Xiaomi Smoke Detector (works with model JTYJ-GD01LM/BW) - Import URL

The Xiaomi Smoke Detector also has a driver now, that makes the Natural Gas Sensor the last device on my Xiaomi/Aqara list. The Wall Switches may still need some adjustments for some models which haven't ahd enough testing, but in general all should be considered fully functional and ready for use.

I will be moving most of my drivers currently only available as Beta into Release now, after this they will be available in HPM, if there are any issues with installing though there, please report them.