New Zigbee 3.0 devices from Aqara - easier SmartThings integration?

Aqara is finally making new version of there sensors and switches available, that are based on Zigbee 3.0. For example, the now have a Zigbee 3.0-version of there nice wireless double rocker switch:

First Look
Aqara Wireless Remote Switch H1 Double Rocker (WRS-R02)

Anyone had a chance to try on of these? Any chance to integrated those into SmartThings with a default device handler that is able to run locally?

Would be nice to be able to use the Aqara device without the setup hassle of the old ones.

That particular model is new, but they’ve had some zigbee 3.0 devices out for over a year. The consensus seems to be that they have less of a drop off problem, but many still need custom code.

In this particular case, I think you’re going to run into the same multi endpoint issue that most multi button devices have with smartthings. :thinking:

@johnconstantelo might have more to add.

I wish they’d hurry up and release the T1 zigbee 3.0 sensors.

Sorry, but I’m not familiar with this “multi endpoint issue”. How does this issue make itself felt?

So far that has been my experience, but they really do work well. Like @Automated_House said, hurry up with those sensors!

It’s all related to button presses and how the new app/platform (or can’t) deals them. There are a few topics in the community about that you can search for. I’m not able to look for those at the moment, my apologies.

In this context, a multi endpoint device is a single device that has more than one actionable part. So it might be a key fob with three buttons. It might be a wall switch, like the new Aqara model, which is a double rocker, so essentially A and B but with a single device address on the network. both Zwave and zigbee refer to these as “endpoints.”

There are lots of different styles of these.

Internally, smartthings tends to treat these as “buttons.“. (Or as one button but with many different tap patterns, like saying that the top of the right hand rocker is a triple tap on one button. It isn’t, but that’s how SmartThings will handle it.)

Another problem is that the way in which multi endpoint Devices were handled in SmartThings has changed over time, And to be honest the platform was never great at them anyway. :disappointed_relieved:

The most common symptom you run into is that only one switch on the double rocker will work in smartthings. Or only one button of a multi button switch. So out of the box the device will add to smartthings and you will be able to control The first button/rocker, but the other endpoints will be invisible to smartthings.

There has been much discussion of this in the forums, as was mentioned, and the usual fix is new custom code that will create new constructs that will enable smartthings to work with the additional endpoints.

Technical note

Zigbee also allows for the use of multiple endpoints on a single device to handle different kinds of situations, such as having one endpoint for a ZHA profile and another endpoint for a ZLL profile. (The hue dimmer switch used to do this before the Zigbee 3.0 version.) or you might have a single device which has multiple functions, like a thermostat which has a temperature sensor on one endpoint and a power control on another endpoint. For anybody who’s interested in that technical aspect of multi endpoint Devices, there are lots of references, such as the following:

https://www.eetimes.com/zigbee-applications-part-5-addressing-within-the-node/#

But in a smartthings context, it usually comes up because of a multi button device where only one button works out of the box. :thinking:

3 Likes

Intersting, thanks for going into details on that topic. Wasn’t aware of this issue.

Has there been any word from the ST team regarding this issue? Is it going to be addressed how endpoints are handled on the platform?

They’ve been talking about the issue since 2015, they have implemented a couple of different ways of handling it, but nothing that makes these devices just work out of the box the way they do with other hubs. It must be something in their cloud architecture because, again, other hubs don’t have the same issue. :thinking:

You can usually eventually get it to work with custom code, but that process can be tedious if somebody already hasn’t written one for that specific model.

The t1 sensors are impossible to get right now even in China. I got the vibration sensor which I gave one to @johnconstantelo but if you’re used to the old vibration sensor I can tell you right now it doesn’t work the same way. It’s more of a movement sensor and not a vibration sensor. If you were using it on glass the new model won’t work. I even confirmed this with aqara support.

I want the temperature humidity sensor t1 so we can see if it works locally without a custom DTH but I haven’t been able to get one.

1 Like

Yup, I can confirm everything @mvevitsis said. I’ve tried it on glass with no success, but it’s been fine on pull out drawers, cabinet doors, and some standard size doors. Right now it’s attached to the underneath side of my heavy aluminum mailbox outside. So far it’s been working great detecting whenever our mailbox door is opened/closed, or whenever someone backs into the mail box.

I finally got my hands on one of the new Zigbee 3.0 H1 wireless switches.

However, I’m having trouble getting it to pair with the SmartThings Hub. Even after multiple resets of the switch, the device just won’t register in the ST log:

Instead the switch seems to establish a direct link to all of my Zigbee lights instead. When I push a button on the switch, it turns on every single Zigbee light and smart plug that I have around the house. It looks like the switch bypasses the hub altogether.

Any idea, how to proceed and get the hub to register the switch?

Anyone? I’d really like to add those buttons to my setup but can’t even get the device to show up as a thing.