Is anyone using the Visonic MCT-350 contact sensors? I just tried to add one and it was detected as a Generic Zigbee Moisture Sensor. I changed to Generic Zigbee Contact Sensor but not luck. I also tried to remove and readd to the hub.
Did you click on the Configure button after changing it to Generic Zigbee Contact Sensor? Can't skip that step.
2 Likes
what platform version are you running?, a fingerprint for an MCT-350 was added to the Generic Zigbee Contact in platform 2.1.5...
Ahh that's it... I haven't upgraded yet but will this week. Thanks! I'm sure that will resolve it.
1 Like
@mike.maxwell I just upgraded to 2.1.5.123 this morning. I then removed the sensor and factory reset it. I tried to re-add and it was picked up again as a Generic Zigbee Moisture Sensor. I tried changing to a contact sensor and hit Configure. The only state variables I have are sensorTemp and tempOffset. The model that is displayed is MCT-350 SMA. Not sure if the SMA is reference to some different model?
Yup..hit Configure. 
interesting, can you do the following?, replace the driver with a system driver named "Device", then open a live logging window and click the Get Info command in the driver details, if you could take a screen shot of those logs, maybe there's another fingerprint out there for this same contact sensor...
Sure thing... I just removed, reset, re-added, and performed the steps outlined below. Lots of stuff dumped to the logs but I think I captured what you're looking for from Get Info. Let me know if you need more. Thanks!
yes, that's what I needed thanks, and indeed, yet another distinct fingerprint for the same device, I'll get this one added too...
In the mean time if you change this over to the generic zigbee contact sensor does it work?
You don't need to join it again, just switch drivers, you shouldn't even need to hit configure after the swap in this case...
can you open live logging (be sure that debug logging is enabled), then trigger an open close on the device and post the live logs for that activity?
Ok..so now I'm seeing the Open/Closed status for the device. I'm not sure why it's different this time?
dunno, but your recent logs do support what I expected to happen...
1 Like
Thanks..I'll run with it... I had done "Configure" before and waited without luck. Is it possible switching to "Device" and then back to "Generic Zigbee Contact Sensor" could have helped? or just coincidence?
Having a similar issue with a sercomm SZ-ESW02 getting paired as a smartthings presence sensor V2. Changing it to generic zigbee outlet doesnt work. Wierd thing is, I had one of these paired and working a few months ago on my old hubitat hub.
Yes, this...
1 Like
We don't have the fingerprint for this device, if you go through the steps listed above using "Device" and post it, ill be happy to add it...
That's strange, as it was working a few months back as generic zigbee. ItIts the device with I'd 1 in the list.
Is there anyone out there using the MCT-350 as a %humidity sensor?
How sensitive is it?
How quickly does it measure a change in humidity?
Which driver are you using?
