New Would-Be Driver Developer - Basic Info Requested

I'm a UK-based Hubitat user, and a few days ago took a punt and bought a Frient Zigbee motion sensor:

https://smile.amazon.co.uk/gp/product/B08WXSZ56Z/

I've had very limited success at getting this set up; it can be added as a new device, but no driver's automatically picked up and even after manually setting it to be a Generic Zigbee Motion Sensor (with and without temp) it doesn't seem to be interacting with the hub in any way. No response to Configure, no events, no log entries (everything's been turned on). The device's dome does flash when there's motion, suggesting it's active, but AFAICS nothing makes it through to the hub.

After a bit of Googling it looks like other people have hit similar problems with Frient devices. There doesn't seem to be a Smartthings-based starting point for the Frient motion sensor in the (presumably) same repository referred to in that earlier smoke detector post.

My day job is software development, and I've dabbled in Groovy apps on SmartThings so I'm happy to give driver creation a go, but am a little stymied on where to start. The native Hubitat drivers are suggesting no traffic from the sensor at all, and there's no obvious custom driver to switch to.

Any suggestions/links on how best to get going with this would be appreciated! (Or, failing that, if anyone can confirm that what I've found indicates a fundamental incompatibility between the sensor and HE, please let me know!)

In case it's of use, these are the Device Details generated when the sensor's first connected to the hub - these are currently the beginning and end of what I have to work with:

ID: 30DA
Manufacturer:
Product Name:
Model Number:
deviceTypeId: 210
manufacturer :
idAsInt : 34
inClusters :
endpointId : 22
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 35
inClusters :
endpointId : 23
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 38
inClusters :
endpointId : 26
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 39
inClusters :
endpointId : 27
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 40
inClusters :
endpointId : 28
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 41
inClusters :
endpointId : 29
profileId :
application :
outClusters :
initialized : false
model :
stage : 0
manufacturer :
idAsInt : 1
inClusters : 0003,0005,0006
endpointId : 01
profileId : C0C9
application :
outClusters :
initialized : false
model :
stage : 1

It says it works with smarthings, so it should work with Hubitat out of the box. Sorry, not much help other than try some other motion drivers that are pre-loaded in the hubitat.

Thanks for the suggestions, but my understanding was that any device will only work for a hub if there's a driver available for it. With the Frient sensor that's - apparently - the case for Smartthings hubs, which have a built-in driver, but not Hubitat which will connect to the Frient but can't find any built-in drivers that match. (And none of the ones I've tried assigning manually work either. :frowning_face:)

The fact that the Frient works with Smartthings only means it can probably work Hubitat in principle, not that it will automatically do so out of the box. (AFAICS some devices, like the Ikea buttons, require Zigbee firmware functionality that Smartthings supports but Hubitat doesn't.)

There doesn't seem to be a Frient/Hubitat driver at present, but hopefully that is something I can come up with given a bit more head-scratching over the Zigbee Cluster Library basics. :crossed_fingers:

Seems to match the Frient MOSZB-141 but probably won't work as-is with Hubitat even after following https://community.hubitat.com/t/app-and-driver-porting-to-hubitat/

You'll likely need to figure out with a ZigBee Sniffer what each endpoint is doing, typically Frient devices use separate endpoints for each feature so you'll probably find motion (via IAS), temperature, battery, light, etc are spread across the reported endpoints so they will need configuring appropriately.

1 Like

I cleared out the firmware update capability, tiles, and changed the physicalgraph entries and was able to save it. This should give you a good starting point.

https://raw.githubusercontent.com/heidrickla/Hubitat/main/Drivers/smartsense-motion-sensor.groovy

Thanks @martyn and @lewis.heidrick - that's a very good place to start from.

While it's tempting to try to fathom out endpoint/feature relationships by trial and error (there aren't that many of each!) getting a Zigbeee Sniffer will be the proper way to do it. Plus it'll give me a new gadget that could be useful in future too, and both of those have to be a good thing.

CC2531 ordred from Amazon, and flashing plus setup, followed by driver work, scheduled for this weekend...

Download the Hubitat app