Looking for driver MHCOZY Zigbee Temperature & Humidity Controller

[jaycenornin (JC)]

I found this device on Amazon and it is EXACTLY what I need for a number of applications, but mostly just to have a functional outdoor temp/humidity sensor that won’t have batteries that die the first time it snows.
Link Amazon.com: MHCOZY Zigbee Temperature & Humidity Controller, Extendable Probe Sensor, Tuya App Remote, 10A Relay Switch (T&H, 220, Volts) : Industrial & Scientific

The device has temperature and humidity sensors and a relay switch.

There is also a related version which only has the temperature probe (which I want to use for monitoring my pond temperature).
Link: MHCOZY Zigbee Temperature Sensor Controller with Waterproof Probe,Tuya app Remote 16A Smart Switch(tuya zigbee hub needed) - Amazon.com

Does anybody know if there is an existing driver for this device type before I buy it? I’m already using Mariano’s drivers, but I’m not sure if this would fall under the “switch” or “sensor” category and without a fingerprint I don’t know how I would even tell. I’ve tried a quick glance over the code on Mariano’s github and didn’t see anything that stood out to me as a “yes”. I also searched these forums and the internet in general with no success, so figured I should ask before buying one.

IF anyone would like to write a driver for this device, I’d be happy to pay for an extra so they have one to work with. I am mostly interested in the sensor features, since I already have functional relays and switches.

[Andreas_Roedl]

Just buy it and if it’s not supported out of the box, depending on how standard the clusters are, it can be added to one of the existing drivers.

[Casabas (Andy)]

Hi JC,

I purchased the same temperature sensor from Amazon. Did you manage to find a solution? I watched some YouTube about Smartthings and it sounded like you can connect anything to the hub, hence buying this module without confirming first…

The module does connect as a relay and the app happily switches on and off… that’s it though, it just shows up as a relay!

Thanks,

Andy

[jaycenornin (JC)]

I did not. I’m pretty disappointed that the only response I got was “Spend $50 and find out”.

I did spend the $50 and learned.

These are not supported by Mariano’s drivers, which otherwise work with a lot of Tuya-type devices.

The “suggested” driver when I asked if Mariano could add support is Wesley’s “[ST Edge] Personal Tuya Devices - Generic EF00 Device” driver. The driver does not have direct support for this device type and the “Advanced” setup doesn’t work. The driver is also no longer in active development so new device support is basically “Write the device support yourself and Wesley may approve the pull request”. In that driver thread I’ve asked if Wesley could add support for this device, but so far they haven’t replied.

If all you need is a waterproof sensor probe, I did eventually find this product (link: Amazon.com: Smart ZigBee 3.0 Temperature Sensor w External Waterproof Temperature Probe : Automotive ), but I guess I bought the last one because it’s not available anymore? It claims to be SmartThings compatible but it hasn’t arrived yet so I can’t say. It does not include the relay or the humidity sensor, just the temperature probe. It’s battery powered so may not be suitable for outdoor use without some hacking.

On a slightly related note, I’m planning to eventually move off of SmartThings. Samsung’s support is lackluster at best, their privacy policy keeps changing (and getting worse), and device support is spotty. These MHCOZY devices do have community-made drivers for Hubitat and HomeAssistant.

If Wesley responds to the driver thread, I might be able to finagle writing the device support for these myself to integrate with that driver, but there are ZERO promises there. I really do not want to get bogged down in driver development with all the other unfinished projects on my plate.

[Mariano_Colmenarejo]

@jaycenornin

These are not supported by Mariano’s drivers,

If you post the CLI logs of the device when it sends temperature and humidity messages I can try to add it to my driver, but you will have to send logs for debugging if it doesn’t work properly.

the request messages from the EF00 cluster where byte 3 of the genericBody is Hex 66 or 67 (102 or 103 in decimal)

[jaycenornin (JC)]

Did you ever know that you’re my hero?

But let’s hold up a second.

The last time I played with this was Dec 25th. The temperature was still reporting way off (400+ something). I tried adjusting the “rate” setting in Wesley’s driver but it didn’t seem to be changing anything, so I left it and went to bed and ignored it until just now.

The temperature is reporting accurately now

Looking at the history for the device, it started reporting accurately at 3:23 AM local time, which is around 10-12 hours after I last made any changes.

So I guess the sensors are working now?
@Casabas for your reference (screenshots below)

• Use Wesley’s “Personal Tuya” main driver
• Use the “Generic” profile (should be the default since the fingerprint isn’t recognized)
• Open the device in the app and go to Settings
• Set temperature DP to “102”
• Set humidity DP to 103
• Leave the MHCOZY device and confirm child devices were created
• Open the Temperature child device and go to Settings
• Set Rate to “1000”
• Wait at least 12 hours? I guess?
• If you need switching capability, combine this with a separate switch device
  
  
  
  
  
  
  
  

I’m only testing with the USB-powered “Temperature and Humidity Controller” device. The other “Temperature only” device is only AC powered and my bend power cord is plugged into another device right now. I was able to switch the temperature probes back and forth and the USB device worked with both. The humidity seems to be accurate out of the box. The temperature sensor updates regularly, ~1x per minute, and is responsive once it starts reporting correctly.

If I switch the driver profile for the main device, the child devices stop receiving updates. The Temperature and Humidity profiles for the main device still don’t work, only the Generic profile with the manual datapoints. I still can’t get the switch to work.

Mariano’s drivers don’t work because they only support the standard Zigbee clusters. It can control the switch on standard cluster 0x0006 but cannot interpret the Tuya EF00 data. (I don’t know what a “cluster” is in this context, I presume it’s just a word the Zigbee protocol uses for a collection of data and control signals.)

I think Wesley’s driver doesn’t work because it only supports the Tuya EF00 cluster, and not the standard Zigbee clusters. It can interpret the Tuya EF00 cluster data, but doesn’t seem to know the 0x0006 cluster exists.

I’m going to get the second MHCOZY device plugged back in and see if it starts behaving, too.

Mariano, thank you so much for your offer to help, but it seems like we don’t need it anymore. I can still send you any data you need if you want to go forward with adding EF00 support to your drivers, but that’s of course up to you.

[Mariano_Colmenarejo]

@jaycenornin

I can still send you any data you need if you want to go forward with adding EF00 support to your drivers, but that’s of course up to you.

Send me the logs and I’ll see if I can integrate them completely into a profile.
Is the rate (divisor) you chose 1000 for temperature and humidity?

[Mariano_Colmenarejo]

@jaycenornin @Casabas @Devin_McCormick

You can try with this TEST driver version from my channel.

You need uninstall device and re-install it with this TEST driver, you do not perform a driver change

The driver has three profiles, which are chosen from preferences:

• Switch Only: Tile shows “Switch and Power” and works like others switches
• Switch and Temperature: Tile shows “Switch and Temperature”
• Switch, Temperature and Humidity: Tile shows “Switch, Temperature and Humidity”

By default it pairs with “Switch Only” and is configured to work with the profile you choose later from preferences. You may have to clear the App cache when you change profiles for the first time.

I’ve set a divisor of 1000 for temperature and 100 for humidity.

Try to see if it works and if you can send me logs of the pairing it would be perfect for debugging.

───────────────────────────────────────────────────
 Name         Zigbee Switch Mc-TEST
 Version      2024-12-30T18:46:36.793790889
───────────────────────────────────────────────────
- id: "_TZ3218_7fiyo3kv/TS000F"
    deviceLabel: MHCOZY 16A Switch
    manufacturer: _TZ3218_7fiyo3kv
    model: TS000F
    deviceProfileName: mhcozy-switch

[milandjurovic71 (Milan)]

@Mariano_Colmenarejo this device looks like perfect candidate for “thermostat” profile.

[jaycenornin (JC)]

I’ve tested the driver and it works great! Both sensors report and the switch is controllable.

The temperature displays a number that appears to be celsius but with a degrees F label.
The humidity looks to be off by a factor of 10, I think? Other sensors in my home report around 15% right now.

Screenshot and CLI logs below. I had to cut the CLI log short to fit within the forum character limit, but it should have updates for both sensors and the switch. Let me know if you need more.

? Select a driver. 5358c7b0-f549-4a8a-b75c-86d2651b1b7e
connecting... connected
2024-12-31T04:15:02.966198615Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:02.967555061Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -49, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x49, ZCLCommandId: 0x06 >, GenericBody:  00 6E 67 02 00 04 00 00 00 13 > >
2024-12-31T04:15:02.981401260Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc -> tuya MHCOZY
2024-12-31T04:15:02.982956898Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
2024-12-31T04:15:02.984770241Z PRINT Zigbee Switch Mc-TEST  <<<< Tuya handler >>>>
2024-12-31T04:15:02.988711561Z PRINT Zigbee Switch Mc-TEST  <<<< tuya_handler_humidity >>>>
2024-12-31T04:15:02.989426870Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":0}}
2024-12-31T04:15:03.005762448Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:08.485755998Z DEBUG Zigbee Switch Mc-TEST  driver device thread event handled
2024-12-31T04:15:25.520213901Z INFO Zigbee Switch Mc-TEST  hub handled command: 7744c593-dcfe-4bd7-af24-229932949cf1:main:switch:on []
2024-12-31T04:15:25.521007443Z INFO Zigbee Switch Mc-TEST  hub sending: Zigbee message (7744c593-dcfe-4bd7-af24-229932949cf1): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x6faf, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 01]>
2024-12-31T04:15:25.654625859Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:25.655389234Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -44, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x41, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2024-12-31T04:15:25.671226526Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-12-31T04:15:25.672988526Z INFO Zigbee Switch Mc-TEST  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-31T04:15:25.675566526Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-31T04:15:25.695414734Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:25.696078984Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:25.696630693Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -44, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2024-12-31T04:15:25.703052943Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-12-31T04:15:25.704591526Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-12-31T04:15:25.707653276Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"2024/12/31 Time: 04:15, LQI: 255 ... rssi: -44"},"visibility":{"displayed":false}}
2024-12-31T04:15:25.722931818Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-12-31T04:15:25.731566026Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-12-31T04:15:25.739020443Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:30.054227776Z INFO Zigbee Switch Mc-TEST  hub handled command: 7744c593-dcfe-4bd7-af24-229932949cf1:main:switch:off []
2024-12-31T04:15:30.054877276Z INFO Zigbee Switch Mc-TEST  hub sending: Zigbee message (7744c593-dcfe-4bd7-af24-229932949cf1): <src_addr: 0x00, src_endpoint: 0x1, dest_addr: 0x6faf, dest_endpoint: 0x1, profile: 0x104, cluster: 0x06, data: [01, 00, 00]>
2024-12-31T04:15:30.196273360Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:30.196989235Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -44, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x42, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2024-12-31T04:15:30.202743985Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-12-31T04:15:30.204382943Z INFO Zigbee Switch Mc-TEST  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2024-12-31T04:15:30.210135860Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-12-31T04:15:30.226017776Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:30.226575193Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:30.235743485Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -44, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2024-12-31T04:15:30.252981401Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-12-31T04:15:30.254532235Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-12-31T04:15:30.257480485Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-12-31T04:15:30.266908193Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-12-31T04:15:30.275431610Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"energy","capability_id":"energyMeter","component_id":"main","state":{"unit":"kWh","value":0.0}}
2024-12-31T04:15:30.284063568Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"powerConsumption","capability_id":"powerConsumptionReport","component_id":"main","state":{"value":{"deltaEnergy":0.0,"energy":0.0}}}
2024-12-31T04:15:30.295744693Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:38.489698569Z DEBUG Zigbee Switch Mc-TEST  driver device thread event handled
2024-12-31T04:15:38.924200069Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:38.924928861Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -53, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4C, ZCLCommandId: 0x06 >, GenericBody:  00 6F 67 02 00 04 00 00 00 1B > >
2024-12-31T04:15:38.940164986Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc -> tuya MHCOZY
2024-12-31T04:15:38.941721528Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
2024-12-31T04:15:38.943550861Z PRINT Zigbee Switch Mc-TEST  <<<< Tuya handler >>>>
2024-12-31T04:15:38.945178861Z PRINT Zigbee Switch Mc-TEST  <<<< tuya_handler_humidity >>>>
2024-12-31T04:15:38.948693528Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":0}}
2024-12-31T04:15:38.958840361Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:41.921359653Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:41.935669528Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -54, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4D, ZCLCommandId: 0x06 >, GenericBody:  00 70 66 02 00 04 00 00 00 D8 > >
2024-12-31T04:15:41.952566236Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc -> tuya MHCOZY
2024-12-31T04:15:41.954243736Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
2024-12-31T04:15:41.957904528Z PRINT Zigbee Switch Mc-TEST  <<<< Tuya handler >>>>
2024-12-31T04:15:41.962731903Z PRINT Zigbee Switch Mc-TEST  <<<< tuya_handler_temperature >>>>
2024-12-31T04:15:41.963460278Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":0.216}}
2024-12-31T04:15:41.975746486Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:15:42.133458945Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:15:42.134159403Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -54, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4E, ZCLCommandId: 0x06 >, GenericBody:  00 71 67 02 00 04 00 00 00 2B > >
2024-12-31T04:15:42.151914195Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc -> tuya MHCOZY
2024-12-31T04:15:42.153454445Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
2024-12-31T04:15:42.155315778Z PRINT Zigbee Switch Mc-TEST  <<<< Tuya handler >>>>
2024-12-31T04:15:42.157753653Z PRINT Zigbee Switch Mc-TEST  <<<< tuya_handler_humidity >>>>
2024-12-31T04:15:42.160168570Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"humidity","capability_id":"relativeHumidityMeasurement","component_id":"main","state":{"value":0}}
2024-12-31T04:15:42.168730028Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled
2024-12-31T04:16:05.936018614Z TRACE Zigbee Switch Mc-TEST  Received event with handler zigbee
2024-12-31T04:16:05.936734364Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -44, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x59, ZCLCommandId: 0x06 >, GenericBody:  00 7C 66 02 00 04 00 00 00 E8 > >
2024-12-31T04:16:05.945705989Z TRACE Zigbee Switch Mc-TEST  Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc -> tuya MHCOZY
2024-12-31T04:16:05.946331447Z INFO Zigbee Switch Mc-TEST  Executing ZclClusterCommandHandler: cluster: 0xEF00, command: 0x06
2024-12-31T04:16:05.947248197Z PRINT Zigbee Switch Mc-TEST  <<<< Tuya handler >>>>
2024-12-31T04:16:05.947838531Z PRINT Zigbee Switch Mc-TEST  <<<< tuya_handler_temperature >>>>
2024-12-31T04:16:05.948549281Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","component_id":"main","state":{"unit":"C","value":0.232}}
2024-12-31T04:16:05.958089322Z DEBUG Zigbee Switch Mc-TEST  MHCOZY 16A Switch device thread event handled

[Mariano_Colmenarejo]

@jaycenornin

The temperature displays a number that appears to be celsius but with a degrees F label.
The humidity looks to be off by a factor of 10, I think?

According to the logs:

• the temperature must be divided by 10 and the D8 value would show 70.9ºF (21.6ºC) and value E8 would show 73.6ºF (23.2ºC)

2024-12-31T04:15:41.935669528Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -54, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4D, ZCLCommandId: 0x06 >, GenericBody:  00 70 66 02 00 04 00 00 00 D8 > >
2024-12-31T04:16:05.936734364Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -44, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x59, ZCLCommandId: 0x06 >, GenericBody:  00 7C 66 02 00 04 00 00 00 E8 > >

• I think the humidity would be shown directly: the 1B value would be shown as 27% and 2B would be 43% unless you see that you have to divide by 10 and it would be (2.7) 3% and (4.3) 4%

2024-12-31T04:15:38.924928861Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -53, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4C, ZCLCommandId: 0x06 >, GenericBody:  00 6F 67 02 00 04 00 00 00 1B > >
2024-12-31T04:15:42.134159403Z INFO Zigbee Switch Mc-TEST  <ZigbeeDevice: 7744c593-dcfe-4bd7-af24-229932949cf1 [0x6FAF] (MHCOZY 16A Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6FAF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xEF00 >, lqi: 0xFF, rssi: -54, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x4E, ZCLCommandId: 0x06 >, GenericBody:  00 71 67 02 00 04 00 00 00 2B > >

This is the new driver version

───────────────────────────────────────────────────
 Name         Zigbee Switch Mc-TEST
 Version      2024-12-31T11:12:47.336319867        
───────────────────────────────────────────────────

@milandjurovic71

this device looks like perfect candidate for “thermostat” profile

Hi @milandjurovic71

I’ll look into it, but it will be next year.

Happy new year everyone

[Casabas (Andy)]

Hi Jaycenornin!

Thanks for your response. I’ve just quickly read through the thread here. Great news you’ve managed to get the sensor working with Smartthings. I’m a total novice so will need to wrap my head around the steps to install the driver. I’ll have a go this eve when I have time. Also, thanks for the recommendation of the alternative battery powered ST compatible device.

Thanks also to Mariano and Wesley!

Andy

[jaycenornin (JC)]

HAPPY NEW YEAR INDEED!

That update seems to have come through and now temperature and humidity are both reporting accurately. The switch status reports accurately if I hit the button on the device.

Control also works. It was a little iffy after switching the driver back & forth to make sure the new version was loaded, but after waiting a few hours for it to settle down it’s very responsive.

I’m not sure this device includes energy metering, but the driver does. According to the internet where the datapoints have been posted, the device does not support power metering. Once I get it hooked up to a load I’ll let you know if it reports any new datapoints.

[Mariano_Colmenarejo]

@jaycenornin

I’m not sure this device includes energy metering,

It is an optional virtual energy meter.
If you enter the value in Watts of the load you connect to the relay in preferences, it calculates the energy consumed when it is On.

Have a happy new Year

[Casabas (Andy)]

Hi JC,

Thanks so much for posting all the steps and the screenshots. Being new to this, it took me quite a while to suss all the basics but I finally figured everything out and your steps made perfect sense. About midnight, when most of my fellow country men were celebrating the New Year, I was celebrating the sight of a temperature reading on my ST app.

For anyone who’s trying to do the same. I made some notes summarising the process and links I followed:

By just searching for ‘personal tuya’ on the SmartThings forum site I was able to find a post by Wesley “[ST Edge] Personal Tuya Devices - Generic EF00 Device”

[ST Edge] Personal Tuya Devices - Generic EF00 Device

Since June 24th 2023, I am not able to maintain the driver as I used to because my mother was really interested in automating her house and I think there isn’t any better hub to unexperienced users other than SmartThings, so I gave mine to her. It was ok to me as I have been using another platform exclusivelly for the last 2 years or so. I will try to keep some minor changes, but don’t expect to much. I will work more on documenting and merging than developing things. So, be welcome to fork the repository and support new devices. Just to let people know that I just published in my public channel a very simple and generic way to integrate devices that works with 0xEF00 tuya cluster. It requires a little intuitive skills because the driver exposes a way to control tuya datapoints dir…

At the bottom of the page is a github link to info about Wesleys driver:
EdgeDrivers/personal-tuya-devices at main · w35l3y/EdgeDrivers · GitHub

Within the page is a link to accept the driver:

At the link Samsung account
Click ‘Enroll’
Click ‘Available Drivers’ This takes you to the drivers page
Install the ‘Personal Tuya Devices – main’
I think once the above is done the driver becomes available via the mobile app. Next add the MHCOZY device from scratch and the driver is applied to the device. The variables need to be set as per JCs walkthrough process. JC’s screenshots in the thread above made following the process a lot easier.
I found that the MHCOZY device lost contact with the hub shortly after initial connection. I just reconnected it again and it’s been fine since.

I’m using the temp sensor probe in a freezer and set up a routine to notify when the temperature goes about 1 degrees C. I tested this a few times and it worked well!

Huge thanks to JC, Mariano, and Wesley for his work creating the driver!

Happy New Year, All!

[Mariano_Colmenarejo]

@jaycenornin @Casabas

This driver version merged with TEST version and will updated automatically in 12 hours max

You can perform a driver change to this driver version.

I will delete the TEST version from my channel

───────────────────────────────────────────────────
 Name         Zigbee Switch Mc
 Version      2025-01-02T18:39:03.731390809        
───────────────────────────────────────────────────

[jaycenornin (JC)]

Hey Andy! Glad you got it working! As long as you don’t need the switch feature that driver should work for you.

Mariano has graciously, magnanimously added full support for these to their driver channel, so if you do need the switch functions in addition to the sensors, I recommend switching to that driver now

[dotan_shai]

Greeting @Mariano_Colmenarejo , it is so great that you finally including devices with EF00 cluster in your edge drivers !! I hope you will continue by adding more devices like this one…

My friend @Nadavz257 is trying to use

@Mariano_Colmenarejo

Zigbee Switch Mc

But , according to him. the Temperature and Humidity are missing. Only the ON/OFF section exist. Can you please check your merging with Zigbee Switch Mc-TEST (which is not exist anymore). In addition is it possible to create child devices of the temperature and the humidity sensor?

[Mariano_Colmenarejo]

@dotan_shai

the Temperature and Humidity are missing.

Hi,
please, See the post

@Mariano_Colmenarejo

The driver has three profiles, which are chosen from preferences:

• Switch Only: Tile shows “Switch and Power” and works like others switches
• Switch and Temperature: Tile shows “Switch and Temperature”
• Switch, Temperature and Humidity: Tile shows “Switch, Temperature and Humidity”

By default it pairs with “Switch Only” and is configured to work with the profile you choose later from preferences. You may have to clear the App cache when you change profiles for the first time.