[OBSOLETE] Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc)

[KellyDarren (Darren)]

Well said luke. Well done lads on bringing these sensors to the next stage and sharing with us.

[AlecM (Alec McLure)]

None - it’s all about how you angle it/ point it I’m afraid

[thearchitectuk (Jon)]

Awesome DHs! Thank you for all the work. I have a slight pairing issue with 2 new non-aquara temp/humidity sensors. I have the latest DH’s for these sensors from the GIT bspranger repository. But in pairing mode, I can only get a catchall method (which I’m avoiding). Any ideas? I’m doing the pressing ever 5 seconds as suggested in the OPs thread. I should note I have about 10 other sensors and they were added in the normal way (not catchall method).

[veeceeoh (Keith G)]

@thearchitectuk

I have a slight pairing issue with 2 new non-aquara temp/humidity sensors. I have the latest DH’s for these sensors from the GIT bspranger repository.

Note that there’s nothing that can be done in the device handlers to help with pairing Xiaomi sensors, other than what’s called a “fingerprint Id” (used to recognize a specific ZigBee device when SmartThings is matching the device handler to the device being paired."

If you’re only seeing a catchall message, and never see “zbjoin”, then your hub is just having trouble completing the pairing process. I only have 4 “original” Xiaomi sensors, and they are door/window sensors, not the Temp/Humidity one.

I’ve been able to pair every one of my “original” door/window sensors using the “Pair a Thing” method, but when doing testing with the new device handler version, if I didn’t see it show up in my ST mobile app ready to rename within 90 seconds, I would start over with the long-press of the reset button.

I do have one Xiaomi device that I have never been able to pair using the “Add a Thing” method, which is my Mi Cube controller. In that case, I used the catchall method, but I also discovered that if you keep trying to pair a device that doesn’t appear, eventually a message will show up in the hub events log (the same log where you find the catchall message) that has the ZigBee device ID.

All of my Xiaomi devices have a ZigBee device ID that start with 00158D and from what I have read, that stays the same for all of their devices because it’s the manufacturer code part of the ID. So if you don’t have luck with the normal pairing process and have to use the “catchall” method, then try looking for that ZigBee ID. It will be a 16 hex digit string, like this: 00158D0001111111. That string can be copied and pasted in when you create the device, like I did for my Mi Cube here:

From what I understand, having the ZigBee ID can help the hub to reestablish a lost network connection, and assign a new Device Network ID if needed. I should mention that my Mi Cube has never lost its connection with my hub, for over two months now.

[AlecM (Alec McLure)]

I’ve had a non-Aqara temp/humidity for a while - it’s the only device I have that I have to go the catchall route these days - never had any luck with a zbjoin - I don’t think anyone’s ever found a fingerprint for them, which means it will not be identified as anything but a thing. - Even so, I’ve found it to be pretty solid even w/o the full Zigbee device id. Even so, I’ll try @veeceeoh’s method to find the full ID.

[thearchitectuk (Jon)]

That’s REALLY useful, I will have a go with that tonight - esp with the finding of the Zigbee ID! I think that was the main shortfall of the catchall method for me so thank you for explaining

[thearchitectuk (Jon)]

That makes sense, I tried for hours on and off! I’m going to use @veeceeoh’s method!!

[mckenph (phil)]

I have 6 or so round and and 6 or so square temp sensors that I am willing to get rid of since I can’t keep them on the network. Yesterday I shut off my hub for a few hours in order to get them to latch on to my S2B repeaters and they did. But once I turned my hub back on now I can’t get them to stay on the network. Yes I did shut down ALL my ZigBee devices during the repairing. What was interesting is those square temp sensors, which stayed on for weeks and have never been able to keep the round ones on, now will not even stay on the hub. So I am looking for 6 Visonic Door/Window Sensor and willing to trade. Heck I will even throw in two wall switches that I think are still in the box.

[veeceeoh (Keith G)]

@thearchitectuk

I will have a go with that tonight - esp with the finding of the Zigbee ID!

Just make sure to also copy the Device Network ID from the catchall message as well and enter that in when creating the device. Without the network ID, it won’t work at all.

[pjam73 (Paul)]

@veeceeoh

Added daily high/low temperature & humidity tracking

This doesn’t seem to be working for me on a few original Temperature/Humidity sensors that I’ve enabled it for. The min and max are nearly always the same as the current temperature.

Could it be reseting the values too often (like once an hour rather than once a day)? I’m using Celcius and my date format is DMY if that makes any difference.

Edit: one device has a state of “currentDay: 38”. If that’s day of year then that’s a week behind? Also, the code is using Date.format(‘mm’)… I’ve not used Java in years but ‘mm’ doesn’t seem valid - ‘D’ is what gives day of year - ‘mm’ would just give you the minute in the hour twice.

[vmocherla]

Hi

I have been facing difficulties staying connected Aqara DWS to a Samsung Connect Home (MIMO router & ST hub)… My setup has a Samsung Connect Home connected to a Verizon FiOS router with 2.4 GHz deactivated.

I am able to connect to the Hub with the right catchalls, open/close status (during the first few min), battery status, etc. That said, in about an hour’s time or so, I am losing the connection.

I went through the detailed instructions from bspranger (i.e., switching off 2.4 GHz, bluetooth, etc.) and I continue to drop the connection. I am not sure if a similar situation was encountered by anyone in the group but I wanted to check for insights from the rest of you.

These are probably elementary questions for some of the more experienced minds here but::

a) Are Zigbee routing devices simply ST hubs / Zigbee enabled routers? Could any of my neighbor’s hubs be causing issues?

b) I also read that we could move the wifi channels to not interfere with Zigbee… How do we know what channels does Zigbee operate in?

These might be very basic but I wanted to be less stupid by asking them than not asking at all… I have been trying different permutations over the last few weeks before this SOS call. Any answers / suggestions will be great!!

Thx

V

[veeceeoh (Keith G)]

@pjam73

Could it be reseting the values too often (like once an hour rather than once a day)?

You are correct!!

When testing the min/max reset function, I used a reset of every minute!

This was supposed to be changed to every day before release, but apparently the “original” Temp/Humidity sensor device handler didn’t get updated somehow.

I have fixed this, and the updated “original” Temp/Humidity sensor device handler is now version 1.0.1 and can be grabbed from the bspranger/Xiaomi repository, here, immediately.

My apologies for missing that, and thank you for reporting it!!

[veeceeoh (Keith G)]

I’ve heard this story before…

Xiaomi vs Aqara door/window sensors

I am having a hard time to keep the the door sensors stay online thou I got the battery report. Sometimes it shows as offline, sometime it shows either open/close without reporting the door being opened or closed. I am using the Samsung Connect Home as the hub, so it is next to the WiFi router. And the other device that I have is the Hue lights only. What is your suggestion here? Can’t really move the router away from the hub since the two needs to be connected.

[OBSOLETE] Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc)

I’m in a similar boat. I bought a Connect Home thinking I can kill 2 birds with 1 stone… But I’m just having a heck of a time getting those Aqara sensors to stay online. Firmware is not the same as the hub V2. Not even sure if the hardware smartthings hardware is the same as V2 either. I’ve pretty much given up and about to by the Smartthings Hub V2 from the Smartthings shop. Promo goin on now Hub V2, 2x Sengled A19 bulbs, and a motion sensor for $99… Not too bad a deal. Only catch is that I live in Canada. Shipping is 15 extra, + duties and taxes when it crosses the border.

Personally, I bought a SmartThings Link for NVIDIA Shield as my hub last November, and it never worked with any of my Xiaomi sensors. I decided to switch to a v2 hub in late December and they paired quite easily and have never dropped their connection.

Since Xiaomi sensors aren’t officially supported, SmartThings support won’t offer any help based on them not keeping a connection. I did find out that the SmartThings Link hub uses different firmware and very likely a different ZigBee radio, and support confirmed that the Link is on a different development schedule than the v2 hub. The Samsung Connect Home also runs on different firmware from what I understand. This is something to consider - it may just not work with Xiaomi devices at all. Maybe with a future firmware update? Who knows.

To answer your questions:

@vmocherla

a) Are Zigbee routing devices simply ST hubs / Zigbee enabled routers? Could any of my neighbor’s hubs be causing issues?

Yes on the first question of A). However, it’s better to refer to a ZigBee hub as a “coordinator”, because that’s what they’re called. A ZigBee router is actually what a lot of people refer to as a “repeater”. Each ZigBee network can only have one hub/coordinator, and multiple repeaters and end devices. But ZigBee coordinators use something called a PAN-ID, which makes each ZigBee network unique from others. Coordinators/hubs self-assign their PAN-ID, but will use a different PAN-ID if they find another local coordinator/hub using the ID that was chosen. So this means there can be more the one unique ZigBee network in the same location. In theory, you should not have problems if your neighbor(s) also have a hub with ZigBee.

@vmocherla

b) I also read that we could move the wifi channels to not interfere with Zigbee… How do we know what channels does Zigbee operate in?

FAQ: Networking and Reducing Channel interference between WiFi and Zigbee

Continuing the discussion from [RELEASE] Keenect V1.1.0, pressure protection release: Wanted to start a thread on best practices, tools and general discussion on wifi networking and channel interference… I am using several Android apps to manage my network, but I am no RF engineer so it’s always good to hear from others on how they manage their networks. To get started, here is the diagram I’ve been using to limit the interference in my home… [image] source: http://fosiao.com/content/zigbee-and-wifi-rf-channels Also, another interesting article, is this:

[vmocherla]

Thanks much!! I already see a difference with my setup that my Samsung Connect Home is not setup as a repeater but as a separate network…

I will go through the best practices for Wifi Channels as well and let the group know…

Thanks much for the brilliant response.

V

[veeceeoh (Keith G)]

Update: “Original” Xiaomi Temp/Humidity sensor DTH to v1.0.2
in the bspranger/Xiaomi GitHub repository, direct link here.

I have added a couple additional fingerprints (the data that SmartThings uses to match a device being paired with the appropriate DTH) because I see that many people have never had luck pairing the (round) “Original” Xiaomi T/H sensors.

I have based the fingerprints based on a few sources by people who’ve learned a lot of technical information on Xiaomi devices.

For anyone having trouble keeping their connection to their round T/H sensors, I encourage you to give this updated DTH a try. I can’t promise it will work, but it would be great if it does!

Tagging @AlecM & @thearchitectuk because you’ve both mentioned troubles pairing these using the “Add a Thing” method

[D_Lev]

When creating v1.0.2 I get this error - Original” Xiaomi T/H sensors
Smartthings V2 Hub

Org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: script_dth_metadata_ed12b29b_ded4_477b_b340_f0ff1a02cc75: 45: Duplicate named parameter ‘outClusters’ found. at line: 45 column: 14. File: script_dth_metadata_ed12b29b_ded4_477b_b340_f0ff1a02cc75 @ line 45, column 14. fingerprint profileId: “0104”, deviceId: “5F01”, inClusters: “0000,0003,0019,FFFF”, outClusters: “0000,0003,0019, FFFF”, outClusters: “0000, 0004, FFFF”, manufacturer: “LUMI”, model: “lumi.sensor_ht”, deviceJoinName: “Xiaomi Temp Sensor” ^ 1 error

[thearchitectuk (Jon)]

This looks great, thanks!! However, when I try and update the DH from REPO I get this:

Error 500: Internal Server Error
URI /ide/device/doRepoUpdates
Reference Id 247963a0-4801-4496-bc91-cdde6f84ad94
Date Fri Feb 16 10:33:28 UTC 2018

Any idea @veeceeoh

[joelw135 (Joel W)]

@thearchitectuk

y and update the DH from REPO I get this:

Same here.

[bobbles (Bob)]

Me too…

[veeceeoh (Keith G)]

@thearchitectuk

This looks great, thanks!! However, when I try and update the DH from REPO I get this:

There was a typo! It’s fixed and definitely no errors (I tested in my own IDE). No change in version number this time. Available here.

Apologies, @bobbles, @joelw135, @thearchitectuk, @D_Lev