So, I have dropped a PEQ motion sensor like 50 times, and this last time has disabled the motion sensor. Took it apart, no obvious damage (solder joints), so I presume something is just busted inside the motion detector: bummer.
So, I had a spare, replaced it, but now I have what is effectively a big temperature sensor (and tamper detector, I suppose). I've repurposed it by ziptying it to my water main to warn me if it's ever close to freezing (a problem I've had before).
My question: what is the best way to ensure this motion sensor doesn't show up as a motion sensor for automations? I bet at some point, the device will randomly send out a motion report (with my luck) and set off something that uses "all motion sensors", especially since during my diagnostics, it randomly did it once. I'd like to remove the capability from that device, so when picking "motion", it's not an option.
The other option is to source the sensor and replace it, but with no visible model numbers, it doesn't seem like that's realistic.
Hmmm, I don't see a "generic zigbee temperature sensor" option, but I like the idea of just using a device that is only temperature capable. I'll have to see if one of the manufacturer specific ones works.
Ok, so no built-in handler that is "just temperature" works. Is there a way to extract the Hubitat default handler for a "generic zigbee motion sensor" and modify it so temperature (and tamper, maybe) are the only capabilities exposed? I can do the modifications, probably, but not sure how to get the base driver to start from.
You could try the “Generic Zigbee Contact Sensor” as it reports temperature as well. And it shouldn’t accidentally trigger a contact sensor event. Hopefully it will still report temperature.
As for extracting Hubitat!s driver code? That’s a no-go. You could try porting a ST DTH to Hubitat, and removing the Motion Capability from it.
So, contact sensor also doesn't seem to work; tried putting my finger on the temp sensor to force it to update, but nothing happens. If I change back to the motion driver, it updates like normal again.
Yeah, using a device with different capabilities might resolve the "random motion might happen" issue, but then I have the same situation where I have a humidity sensor that shows up.
Coincidentally, I'd have loved this device to have a humidity sensor also; that would have worked well :).
Maybe not? I was sure I did, but now it's working as a contact sensor. So, random motion events look to be impossible now, but now I have a contact sensor that shows up in potential automations.
Less annoying, so I'm Ok with this for now. I am going to try and source the motion sensor and fix this thing I think. Looks like the sensor is a Panasonic, and looks to be pretty easy to source off Mouser/Digikey/etc. I wanted to get a ZWave USB stick for updating firmware anyways, so this is as good an excuse as any :).
