Device Request: MHCOZY ZG-005-RF

[ebaauw]

Is there already an existing issue for this?

• I have searched the existing issues and there is none for my device

Product name

MHCOZY 4-Channel Dry Contact Smart Wireless Zigbee Switch Relay Module

Manufacturer

_TZ3000_u3oupgdy

It uses the Tuya convention for the Manufacturer Name, but the device itself shows MHCOZY.

Model identifier

TS0004

It uses the Tuya convention for the Model Identifier, but the device itself shows ZG-005-RF.

Device type to add

Other

Four relays, to be exposed as four /lights resources, of type On/Off Output.

Node info

Note that the common info is already provided by my DDF in the works.

Endpoints and clusters

This looks particularly good: four On/off light endpoints (should have been On/off output imho), each with On/Off, Groups, Scenes and Tuya Specific clusters. Each endpoint controls and reports the corresponding relay. There are some special device-wide features on the first endpoint.

Basic

No SW Build ID nor Date Code, but Application Version seems to encode the firmware version in Tuya style, so 0xXYZZ for X.Y.Z. So 80 = 0x50 = 1.1.0.

Further relevant clusters

On/Off

0x8001 and 0x8002 are only supported on the first endpoint. 0x8001 doesn't seem to do anything; 0x8002 just sets the poweron behaviour (0xE001/0xD010) on all four endpoints.

Tuya Specific

0xD010 sets the poweron behaviour of the corresponding relay to Off, On, or Previous, similar to the standard 0x0006/0x4003 attribute on other devices. Note that Previous uses value 2, however, instead of 0xFF.

0xD030 is only supported on the first endpoint. It controls the behaviour of the four physical push buttons on the device, controlling the four relays. Values 0 (Toggle) and (State) cause the relay to toggle on press/release; value 2 (Momentary) causes the relay to be on, only while the button remains pressed.

There is a fifth physical push button on the device, that switches between self-locking, interlock, and jog mode. I haven't been able to get this mode reported nor controlled over Zigbee.

Other Remarks

All relevant attributes support attribute reporting, and by default report to the coordinator. Even after a Write Attributes, a report is sent. However, I see no reports (nor any other Zigbee message) when changing the device mode.

In interlock mode, only one relay can be on at a given time. The other relay turns off first, before the relay controlled turns on. The reports are sent in revese order, though (first the endpoint of the relay controlled, then the other endpoint).

In jog mode, each relay switches off automatically after ~0.5 seconds. The documentation suggests that this period would be configurable from the app, but it's not clear how the device supports that. I did capture an attribute report with more attributes than currently defined in general.xml, not sure if that was on 0xE001 or on 0xE000.

[Mimiix]

Erik and a Tuya device. Wauwie

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[ebaauw]

Ping

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[ebaauw]

Ping

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.