I’m experiencing many synchronization problems for the devices status, delays in refreshing, etc in the last days.. maybe some issue in the cloud services.
Hi @dotan_shai, Apologies, I missed to respond.
I tried @Mariano_Colmenarejo driver and it support valve on/off but not the volume based controls, unless I am missing something.
Thank you @Mariano_Colmenarejo for the support that you provide to the community.
I just purchased the MOES Zigbee Fingerbot Plus which I’m using as a ‘click’ switch instead of a SmartThings default On/Off switch. I cable tied the Fingerbot to a spare garage door opener remote which made a 25 year old Marantec garage door opener assessable to SmartThings, Alexa, and Google Home.
2 Likes
Thank you for your excellent drivers.
I have a new Zigbee device that I hope you can add to one of your existing collections.
Namrom Stove Guard. It’s sold by Elektroimportøren in Norway as Namron with Namrom firmware. I’s also sold/created by Firefence
Namron Manual: https://www.elektroimportoren.no/docs/lib/1402793-Brukerveiledning-5.pdf
This is a switch with power consumption, temperature, dry cooking alarm and more
Manufacturer Code: NAMRON AS
Model: 1402790
Device Name: switch-power-energy-plug
Clustersinfo:
“-Ep:0x0A={ 0000 }-Ep:0x01={ 0000,0003,0006,0702,0B04,0001,0402 }-Ep:0x02={ 0000,0003,0006,0005,0004 }”
“App Version: Unknown, ZCL Version: 0x08”
“FingerPrinted_EndPoint.Id: 0x01”
@nokiaas Hi, unfortunately Mariano is no longer active on this forum and is not actively maintaining or enhancing his excellent drivers.
There are instructions in this and other threads if you want to give it a go yourself though… 
1 Like
OK, thanks for the update
If @Mariano_Colmenarejo Zigbee Switch Power MC driver is not working (should work since Mariano made it generic), You can also give a try to @w35l3y Default Clusters driver. This can be found here:
1 Like
Hi,
Zigbee Switch Power MC is working for showing Power Consumption and On/Off
I was hoping for adding more functionality 
1 Like
If you need more functionality you can temporarily remove from ST hub, connect to Tuya hub config what ever you need. Then remove from Tuya hub and re-connect to ST hub. The configuration will remain.
3 Likes
Hi Mariano,
I hope you’re doing well.
I have a Tuya Zigbee gas sensor with the following fingerprint, and I’d like to request adding it to your Zigbee Smoke/CO Detector Mc driver if possible:
-
Manufacturer:
_TZE204_uo8qcagc -
Model:
TS0601 -
Profile ID:
0x99B3 -
Device ID:
0x0051 -
Clusters:
-
Server: Basic (0x0000), Groups (0x0004), Scenes (0x0005), TuyaEF00 (0xEF00)
-
Client: OTAUpgrade (0x0019), Time (0x000A), BindRequest (0x0021)
-
This device is currently working with the Generic EF00 driver but only shows as a generic sensor without mapped capabilities.
Please let me know if you need the full fingerprint log or DP values from a test trigger. I can run those and share the results.
Thank you for your time and for maintaining these great drivers!
Unfortunately Mariano is no longer active in this community and is not creating or updating driver’s.
You can still use @w35l3y Generic EF00 driver. Change in setting the profile to Gas Detector and use the following DP for configure the device:
Hello Mariano,
I’ve added an Aqara Water Valve to SmartThings, and it was recognized as a generic Zigbee switch.
I’ve installed your Zigbee Valve Mc driver, but it doesn’t show up as compatible with this device.
Could you please add support for the following fingerprint?
• Manufacturer: Aqara
• Model: lumi.valve.agl001
• Fingerprint ID: genericSwitch
Thank you very much!
Hello,
Can anyone help me with a support for the following fingerprint?
• Manufacturer: Aqara
• Model: lumi.valve.agl001
• Fingerprint ID: genericSwitch
I added an Aqara water valve to SmartThings and it was recognized as a generic Zigbee switch.
I installed the Zigbee Valve Mc driver, but it does not appear to be compatible with this device and I do not see the battery status.
Thank you.
Battery status sometimes take hours (6 or more, don’t know exactly what os the logic) to update, you just need to wait.
Suggestion: if you paired the device first as a generic switch and then changed the driver to Valve MC. Put the device in pairing mode again (without removing it from the app) and do the process to add the device again. This time it will be added directly with the Valve MC driver and the previously defined name, and will be initialized correctly.
Driver changes don’t run all the lifecycle actions, so, sometimes the device is not initialized correctly.
1 Like