I’m trying to get the SmartThings Multipurpose Sensor working correctly with Hubitat. Haven’t had full luck yet. Paired as “Device” and I changed it over to SmartSense MultiSensor, Temperature started reporting approximately correct, but no Contact status. Same with the V4 and Generic. Tried to unpair and re-pair with ST (worked correctly) then back to Hubitat, without luck. Any advice on getting it to work?
Is this the Gen 1 aaaa battery ones?
No, it’s the newer Samsung SmartThings Sensors, with a CR2450.
It’s detected as the CentraLite 3321-S, in the “fingerprint” but nothing else.
I think I got it. Tried it another round. Working once I changed to the correct Driver. Didn’t Auto-Identify
Here’s the Data:
endpointId: 01 application: model: 3321-S manufacturer: CentraLiteWhile we’re on the topic, I have one of the first-gen SmartSense Mutli Sensors (the AAAA-battery model), and I couldn’t even get it to pair–Hubitat didn’t recognize a device at all, even a Generic ZigBee device. Are they supposed to work with Hubitat? I had the same issue with the first-gen (AA or USB) SmartSense motion sensor as well. I figured there was something different enough about ST’s first-gen (Kickstarter-era plus the next year or so, pre-rebranded-Centralite) sensors that they are difficult to make work with other ZigBee controllers. I’d love to hear that I’m wrong. 
I did get the latest-gen (third gen? not sure where they are now) Multi to pair and might just replace my old one with this if I can’t get it to work, but it’s worth a try.
EDIT: As of recent firmware (March 2018), both my first-gen SmartSense Motion Sensor and first-gen SmartSense MultiSensor are working with Hubitat!
Yeah, I couldn’t get my AAAA battery models working, but really didn’t try too hard. I did hear rumors that they modified them beyond the normal ZHA profile but never dug into it. Same thing with the motion sensors. It’s probable we can get them to work, just haven’t had the time.
I have been able to get everything after the 1st gen to work without issue. Occasionally the fingerprint won’t match up and have to choose a correct driver.
Please open a ticket at support@hubitat.com for the 1st gen sensors. That way we can track who’s using them and see if we can figure it out.
Also, you can email support with the email subject #fingerprint and send them the fingerprint of any device that didn’t match up. Provide them the make, model and a link to any documentation you can find. Also add if any built in or user created driver works. That will automatically get routed to our Driver team.
1 Like
They had a proprietary implementation of Zigbee in that device. I will not work with Hubitat, or any non-ST Zigbee system.
2 Likes
Thanks Bruce! Good to know. Is the same true for the ST First Gen Motion Detector?
I actually don’t know. I have one sitting around here somewhere, I’ll try it.
1 Like
It finds it, but it won’t join right. Well, it won’t actually join at all, just hangs…
Thanks for testing. I wonder if a list should be maintained of devices that don’t work with Hubitat?
Update: Nevermind - I see it was created about an hour ago!
Anyone tested the ST 1st gen outlet? I believe it was made by Centralite, so I am hoping it is a standard Zigbee HA device.
Pretty sure I have one of those working. There was the rounded ones that were out briefly, those were “gen 1” and then the square ones, and now the oval ones. I haven’t had a single plug in outlet not work. I have about a dozen different ones, Zigbee and Z-Wave.
1 Like
One other thing I’m trying to figure out… Whenever I open or close the sensor, it reports the new state correctly, then bounces to the opposite, then correct.
For ex:
contact changes to open
*reports open
*reports closed
*reports open
Tried a couple of different drivers (modified Lowe’s Iris for ex) with no luck.
Is this for just one sensor or all of them? I haven’t seen that behavior with mine. What’s the type and make of the sensor?
It’s the same SmartThings CentraLite 3321-S as above. Worked flawlessly with ST.
I only own 2 multipurpose sensors, the other (mailbox) will not be transferred until towards the end, as it’s the most important. I’m taking it slowly
Is the sensor routing through a Zigbee repeater? I have found (by experimenting) if I move a sensor that has been paired through a repeater to within marginal range of both the hub and repeater and activate it (without doing a 'heal' or giving it time to stabilize) I will see what appears to be echoes of the open/closed log messages from the repeater (sometimes two consecutive 'close' messages for a single open/close event (like: open open close open open close close). I suspect its a side effect of some dynamic routing happening. At least, this is my theory. I'm still trying to put together a coherent mental model of how Zigbee works (@JDRoberts taught me 99% of what I think I know) 
!
I've attached a screenshot log of three consecutive open/close events from a contact sensor that was paired through a repeater and moved closer to the hub (so it is in range of both). Notice there are duplicated open/close messages in the log (6 open messages, 5 close) for three ope/close events). Apparently one close message didn't make it to the repeater. This actually gives me confidence that Zigbee routing is working with this hub. I've never had good luck with relocating Zigbee stuff that have been paired in a SmartThings environment without major pain-- it just seems to remain dead until I pull batteries or shutdown the hub to do a heal, rather than dynamically re-routing itself like you would expect.
1 Like
You might be onto something. I took a “leap of faith” and paired my mailbox sensor. In initial testing, it’s performing quite well. The Sensor that’s having problems is likely connected to the mesh in a couple of ways. I’ll investigate some more tonight. Including taking down the hub for 10-15 mins, seeing if that helps.
1 Like
I just noticed the coincidence that you were working with a sensor for your mailbox as well… that’s the first thing I tried to get running on ST.
To force a heal and updated neighbor tables, leave the hub off power for at least 15 minutes while all the other zigbee devices remain on power. It can take a while for all the changes to propagate, so you may not see improvements until the next day.
2 Likes
@JDRoberts You are awesome! I tried doing the force update, no immediate result but hopefully tomorrow will be better.
1 Like
