[Deprecated] Xiaomi / Aqara ZigBee device drivers (possibly may no longer be maintained)

Thanks @mike - so have a second hubitat hub? and you can link the 2 hubs together? :upside_down_face:? wow, i didn't know you can do such things with hubitat hubs. by now you can guess that I'm a newbie :crazy_face:

Thanks @RogerThat, I'm based in UK this is our version which I guess should perform the same way

Do I have to import a specific driver and discover it?
I guess I need to because hubitat hub needs to know of it's existence in order to link its zigbee mesh even though it won't be use to control anything...well you can't really...

so once it's discovered, it will just be there sitting pretty? correct?

There 's a built-in driver for the Tradfri USB repeater. So just pair away .....

1 Like

Pretty much, but it comes with a USB-A port, so you can use it as a (non-controllable) USB charger/power adapter if you want to. It doesn't have to do nothing. :slight_smile: (My guess is that Ikea did this so you have an easily-accessible USB port to charge the battery pack in their Zigbee blinds, which is their intended use for this repeater, and they recommend having these somewhat close to the blinds.)

As mentioned above, there is a dedicated driver for this device. But there's no need to be too concerned about that--repeating is handled by the device itself, not the driver, so it will fulfill that function regardless. You may still want it for the extra features it provides on the Hubitat side,

1 Like

Are there any featurers, except the repeater side of it, that we get from it when connected to HE?

The "extra features" I meant are just two commands in the driver that let you see (log) devices routing through it and the Zigbee link quality, two things that may be useful for troubleshooting but most of which is also accessible elsewhere if needed (and are not generally needed to begin with). There are no features that Hubitat adds to the device itself.

These two commands, with these drivers, also work with other devices like CC2530 and CC2531 and some Xbees, all mine work, @veeceeoh didnā€™t get replies from his. There is a thread about those drivers and these commands:

Ah, ok, I see.
I like that too, but I really wonder what these devices are though?

dev:355
2020-02-26 07:14:59.221 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.217 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.213 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.198 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.194 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.191 inforoute info- Destination:This Hub, Next Hop:This Hub, Status:Inactive

dev:3552020-02-26 07:14:59.187 traceroute info- Destination:GELDOPTO Kitchen Led, Next Hop:GELDOPTO Kitchen Led, Status:Active

dev:3552020-02-26 07:14:59.182 traceroute info- Destination:Iris 3326-L Motion Living Room, Next Hop:IKEA Outlet Living Room Window

I suspect that the lines that just say Destination:This Hub, Next Hop:This Hub, Status:Inactive, can be the Xiaomi devices.

I have also seen more strange stuff happening with HE after adding two of the IKEA repeaters. I had to reboot this morning, since nothing worked, but I could log in and do a normal reboot. But dashboards did react, but nothing followed the button actions. I think I will try to take them off the network again, to se if they are the reason for hickups I have seen after adding them. Very strange.
Have anyone else felt the same?
They where added together with an IKEA Tradfri LED (250 lm) bulb, so it might be that bulb that made things go wacky... Never before had any issues, so a bit baffeled what has happened latelly. Did the update to 2.9.114 though, so not so easy to put the finger on what is the cause now... Hmmm....

I'd start with removing the bulb

3 Likes

@veeceeoh
I use 3 Aqara Temp & Humidity sensors in my setup & they have been working perfectly for my needs (thanks for the drivers!); I find that the air pressure sensors in them are quite accurate, once adjusted for elevation. 2 days ago (after the most recent HE update)I did a soft reset and started over from scratch after having some issues with a few automations. Upon reinstalling, I no longer have options in the Temp & Humidity Device section for either calibrating the pressure sensor, or setting the pressure sensor to inHG, options that were there prior to the reinstall. The options are still there for calibrating temp & humidity.

The device driver is the same version, 1.01. Did something in the most recent HE update break those settings, or did I overlook something & do something differently?

Thanks, Greg

I got the zigbee Blitzwolf temperature/humidity sensor and I can confirm that it also works with the Aqara Temperature sensor driver

If you use the Konke temperature sensor driver the battery level should also report correctly when adjusted for the aaa voltage ranges.

1 Like

is there a way to get those blitzwolfs to show Fahrenheit by chance?

I believe they are restricted to Celsius because they were not designed with the US market in mind.

https://www.gearbest.com/home-smart-improvements/pp_3005072630691764.html?wid=2000001

1 Like

@veeceeoh Please list the hubitat driver for "Xiaomi Smart Plug" (model lumi.plug) as available in beta in your main list.
This is a fork from the original SmartThings driver from bspranger, edited for Hubitat with the hex order updated for correct power consumption reporting. Temperature reporting only in Celcius but not yet reliable.

https://raw.githubusercontent.com/PabloGux/Xiaomi-1/master/devicetypes/bspranger/xiaomi-zigbee-outlet.src/xiaomi-zigbee-outlet.groovy

I been testing this driver for the last 4 month in five different Xiaomi and Aqara Smart Plugs and it is working reliable without any errors reported in the Logs.

Thanks,

Hi All, I've got some of these wall switches (QBKG04LM).
I'm getting different temp reading compared to my nest thermostats. Just wondering if there's a way to recalibrate the thermostat in them? Cheers

Look for this in the driver code. (Or similar)

 case 0x03: // Temperature
            	values += [ Temperature : Integer.parseInt(dataPayload, 16) - 8 ]  // Just a guess :)

The '-8' is by how much the temperature will be adjusted by.

If yours is showing -8 in the driver code, but on the device page it is reading 2 degrees low, change -8 to -6. Wait a short period and it should change by 2 degrees.

I'm pretty sure this is what I did. Give it a try.

1 Like

Thanks @bobbles!!!
I will surely give this a go. Cheers

EDITED: do I have restart hubitat after the change? or just refresh the device should suffice?

EDITED AGAIN: it's working now! thanks

That's good.
The grey cells still have a bit of life in them. :wink:

1 Like

I'm considering buying the button. It seems like its this or the smartthings one. Can someone deeper in the Aqara world opine on whether its a box worth opening?

The Mijia buttons are nice. Inexpensive and seem to work fine without a compatible repeater if theyā€™re close (within 20 feet or so) of the hub. 5 presses, plus hold.

The Aqara leak sensors Iā€™ve never had a problem with dropping. The Mijia motion sensors seem to hold on longer, and although not impervious to dropping off, less prone to it.

All other Aqara and Miji devices have been problematic when paired directly to Hubitat Elevation, even with compatible repeaters. But when any of the Xiaomi Aqara or Mijia devices are joined to an Aqara or Mijia gateway, they are rock solid and never give me a moment of trouble.

1 Like