Test this with Personal Tuya beta driver - default or similar only. I started off by adding to add this to Wesley’s driver and eventually wth his help, got this added in but it wasn’t working to my satisfaction as the status shows ‘device tested’ always. Also, I did not find any value for the ppm so returned this device. If it works for you, then let me know.
Heiman has begun releasing some new Matter over Thread smoke and CO sensors, which should work with SmartThings without requiring any custom code, although I’m not 100% sure that device class is supported yet. But definitely that would be a long-term option if you are in the EU or UK. They don’t match the US smoke alarm acoustic pattern, so probably not a good fit to that market.
It uses the same case as their Zigbee version, and they just copied over most of the English product description from that model, so some of the pictures will say it needs a Zigbee hub, but it doesn’t. It’s a matter over thread device.
The model number for the Zigbee version will be HS1SA-M
The Z wave version is HS1SSA – Z.
I’m not sure what it will be for the thread version, some of the documents say it is also – M, but that may just be a cut and paste error from the Zigbee model. 
2 Likes
I was waiting for this device for weeks and just last week I bought a Zigbee smoke detector.
Gonna get the Heiman as soon as it’s available in Germany.
1 Like
I take a note to add it to the driver in August, when I have access to the CLI
Hey @Mariano_Colmenarejo.
Your “Zigbee Contact MC” driver might be causing rapid battery drain in my Visonic MCT-350 contact sensor (or the sensor could be defective, of course). It gets empty in 2 months, as opposed to 6 months in other identical sensors I have at my home.
I started a thread here and was then pointed by someone to your own thread so I’m trying my luck here.
Interestingly, the three other identical sensors I have, which do not have that battery drainage issue, still use a generic, legacy SmartThings driver:
Unfortunately, the SmartThings app or web dashboard won’t let me revert the problematic sensor to that legacy driver, so it seems like I must use yours. I tried now to lower the temperature report frequency to the bare minimum, trying to rule this out as the cause of battery drain.
If you have any other suggestions I would love to hear them!
1 Like
Hi,
The fingerprints of your device do not exist in the stock driver, they only exist in the Mc driver.
Your device had to be paired with the stock driver in the automatic migration as a generic device, so you cannot perform a manual driver change from the Mc driver to the stock driver.
Changes to reporting intervals reduce battery usage.
All my devices with CR2450 batteries last a minimum of 7 or 8 months and those that use CR2 last more than a year.
For the change in the reporting configuration to be accepted by the device, you must wake it up at the time of sending the configuration and on some devices it must be in pairing mode.
This link describes a method to reinstall the device and configure it with custom intervals without having to lose the routines
3 Likes
Many thanks. Assuming I don’t want to reinstall the device but just wake it (will have to learn how to do that…) up for the settings to take effect, how can I then check whether the device accepted the changes or not?
For the devices that configure the IASZone cluster, the only way to check it is with the CLI, looking at the response to the device configuration in the logs and checking that the device does not report open or closed every 5 minutes, which is the default configuration of smart devices.
I have the Frient smoke detectors all around the house. These have well maintained Edge drivers that actually work. They have a temperature reading that can be used as a trigger, and the alarm siren is available as an action. Also, SmartThings Home Monitor actually sees them as smoke detectors.
Frient do not carry a CO detector, so I simply bought one that (1) is a flat device for wallmount (CO detectors do NOT go under the ceiling!) and (2) is a Zigbee device. There are no Matter CO detectors actually available today, at least until Heiman’s C1-M arrives.
1 Like
Amigo! tudo bem? Conseguiu configurar a YDF? acabei de comprar e estou perdido… rs
sim amigo… tem bastante tempo
Vc tem o módulo zigbee nela e sabe instalar os drivers?
yes dude… long time ago.
do you have the zigbee dongle for it? Knowledge on edge drivers?
Hello, I am planning to buy an outdoor irrigation valve (Zigbee) from Amazon:
Could someone please confirm if this would work with Smartthings and does it also supports volume based control?
Hi,
I don’t know, without knowing the fingerprints and the clusters it is impossible.
Maybe sonoff has a driver or integration for it
Hi @Mariano_Colmenarejo, I got the device today, with the Smartthings default driver it is being detected as Zigbee Switch.
I have attached the screenshot below:
Well, you can use it to open and close the valve and do control routines.
I don’t think the rest of the functions work on smartthings
According to:
More features can be supported like flow metrics and battery percentage, since SONOFF are using ZCL they can easily be added to your driver. If @Mayank_Gupta can change the driver to Zigbee Thing MC and check history and take a screenshot , then you will have all required information.
1 Like
Reading the link you published, the part is easily added, I think it’s superfluous, hahahaha.
Hi @Mariano_Colmenarejo /@dotan_shai,
Are you after the below details:
<table style='font-size:75%'> <tbody><tr> <th align=left></th> <td><em style= 'font-weight: bold;'> Manufacturer: </em>SONOFF<BR><em style= 'font-weight: bold;'> Model: </em>SWV<BR><em style= 'font-weight: bold;'> FingerPrinted_EndPoint.Id: </em>0x01<BR><em style= 'font-weight: bold;'> App Version: </em>0x10<BR><em style= 'font-weight: bold;'> ZCL Version: </em>0x08<BR><em style= 'font-weight: bold;'> Network ID: </em>0x3D85<BR><em style= 'font-weight: bold;'> Zigbee EUI: </em>0CEFF6FFFE17E1A5<BR><em style= 'font-weight: bold;'> Device ID: </em>c2b8b5b7-9650-4706-a3ec-574c882d4d3a<BR><BR><em style='color:Red;font-weight: bold;'> Server Cluster: </em><BR><b>Ep: </b>0x01={ 0000,0001,0003,0006,0020,0404,0B05, <BR>FC57,FC11 }<BR><BR><em style='color:Green;font-weight: bold;'> Client Clusters: </em><BR><b>Ep: </b>0x01={ 000A,0019 }<BR><BR><em style='color:Blue;font-weight: bold;'> Signal Metrics: </em><BR><em style= 'font-weight: bold;'> LQI: </em>206 .... <em><b>RSSI: </em></b>-71 dbm<BR></td></tr></tbody></table>
The history page shows the on/off events of the original Smartthings driver. I am currently using Edge-Drivers-Beta
If developer format removed can see the text
| Manufacturer: SONOFF Model: SWV FingerPrinted_EndPoint.Id: 0x01 App Version: 0x10 ZCL Version: 0x08 Network ID: 0x3D85 Zigbee EUI: 0CEFF6FFFE17E1A5 Device ID: c2b8b5b7-9650-4706-a3ec-574c882d4d3a Server Cluster: Ep: 0x01={ 0000,0001,0003,0006,0020,0404,0B05, FC57,FC11 } Client Clusters: Ep: 0x01={ 000A,0019 } Signal Metrics: LQI: 206 .... RSSI: -71 dbm |
2 Likes