[EDIT: All of these now work natively with Hubitat. As of 2020, most/all are also getting difficult to find as Samsung appears to be shifting around their hardware business, but that's another story. Still good devices if you can find them! Hopefully whatever they or their partners release next will also work well.]
As many of you know, Samsung released a few new "2018" sensors and devices in the last week or so, including:
- 2018 Multipurpose Sensorr (GP-U999SJVLAAA)
- 2018 Motion Sensor (GP-U999SJVLBAA)
- 2018 SmartThings Outlet (GP-U999SJVLDAA)
- SmartThings Water Leak Sensor (GP-U999SJVLCAA)
- SmartThings Button (GP-U999SJVLEAA)
...in addition to a new hub (though nothing impressive unless built-in WiFi is appealing). I was wondering if anyone has tried using any of these devices with Hubitat and what your experience is with them. As we learn more, perhaps we can update the Compatible Devices Wiki (or the incompatible devices thread) as appropriate.
I'll start: I bought the three devices that were most appealing to me from the above, the multipurpose sensor (curious how vibration works), the button (almost cheap enough to give Xiaomi a run for its money, and supports press, hold, and double-tap), and the motion sensor (cheaper than Iris and comes with a magnetic mount, unlike most ZigBee sensors I've used). The motion sensor just arrived today and I'm able to pair it, but it unsurprisingly just pairs as a "Device." I tried changing the driver to "Generic ZigBee Motion Sensor," but so far nothing is reported.
Anyone have any luck with any others? I seem to remember reading that they are ZigBee 3.0, so hopefully these won't be too much work to support on Hubitat if that's the case.
EDIT: Things have, of course, changed since I originally wrote this post. Hubitat has added support on the generic drivers for most/all of these devices (all I've tried and seen below). Experience varies; in my experience, they take a long time to pair (minutes--I almost gave up, especially when I moved them to a different hub and back to get a firmware update; I can't remember if the very first pair was also this slow or if it's just subsequent ones).
As of the time of this update (December 2018), nobody seems to have reported terrible problems, but there are a few things you'll want to be aware of: (1) many users report duplicate events sent from the button if it's been dormant for a while (a firmware update on the button should fix this, but you'll need an ST hub to get that; a community workaround driver is also posted below); (2) the multisensor supports vibration on ST, but the Hubitat driver does not support that (nor is it clear that the device even sends those events when paired to Hubitat); (3) as noted, in many people's experience, these devices take a long time to pair, and sometimes you need to try multiple times.
If you want my recommendation, I say go for it if you think the price is right. They are both cheaper than previous-generation ST sensors and are competitively priced in general (some probably as cheap as you can go without going non-standard like Xiaomi). You may need patience when pairing or re-pairing (I almost gave up after moving them to ST and trying to get them back on Hubitat after a firmware update i wanted for the button and just decided to do on the other devices anyway since one was available). I will probably not buy more in the future due to the difficulty in pairing them unless it's a device with a unique form or function that I really want, like the button. (Iris motion sensors, for example, are just as cheap and even the "v3" ones are a bit smaller, though I'm not sure if they come with a mount like ST's.)
