@dnewell73 thank you for the logs!
I don't see something unusual, it seems like there may be a connectivity issue...
Please update the driver to the new version 0.7.0 - here the ping() button measures the RTT (round-trip time) between sending a simple command and receiving the answer from the device. If you see "timeout!", this means that the device has left the Zigbee network ...
If you pair the device again, click on the ping() button a few seconds apart for a minute or two. If you see RTT values in the first minute, but then you get timeouts - this is the typical case when some new Zigbee 3.0 devices will not stay connected to C-8.
MHCOZY 2 Channel 5V 85-250V ZigBee Smart Relay Switch,Adjustable Selflock and Momentary Working Mode,Works with SmartThings, Alexa, Google Home (ZigBee Hub Required) https://a.co/d/bp9saI5
Using it to control my 2 garage doors. It was recognized instantly by my C-8 as a Generic Zigbee Multi-Endpoint Switch, and paired quickly and without any issues. I was nowhere near the hub - I paired it where I intended to use it - in my detached garage. It was already configured for garage door use (momentary) right out of the box, so this went pretty easy and smooth. The description indicates Zigbee 3.0.
Posted in case someone is looking for confirmed working multi endpoint device for C-8.
Well, just got a new 2CH one of these off Amazon. Par for the course, the manufacturer looks nothing like any of the 4 other variants I have.
endpointId: 01
application: 53
inClusters: 0003,0004,0005,0006,E000,E001,0000
isMultiEP: true
manufacturer: _TZ3000_ruldv5dt
model: TS0002
outClusters: 0019,000A
softwareBuild: <HASN'T SHOWN UP YET.
BUT here's the new permutation which frankly I'm surprised to see because I have had good luck with these in the past.
I have paired this, set the driver to the generic multi-endpoint, set the mode on the device such that when I press the buttons on the device it functions in latch as I wish, AND the device page shows that SINGLE press latch on, latch off.
BUT....when I go to control it from the device pages turning ONE of the two channels on or off I end up with both channels acting on that instruction....and I see that command in the logs.
I have un-paired and re-paired, still same behavior. EDIT ADD: I will note that I think I am seeing the PARENT getting the same command as the sub/child device.
I'm on a C5 on .147 of the recent HE upgrades.
EDIT ADD: Just checked another one of these 2CH MHCOZY devices I have on this hub. It's not operational right now due to running Xmas lights but boy...have things changed. I'm pretty sure this came from the SAME seller that has sold this line for awhile on Amazon.
I appreciate that...@mike.maxwell was doing pretty well accommodating these relays. It's a frustration having to give this version this driver, that version another driver, (or going back and swapping them all for consistency's sake even if they are working) and to worry about having to keep up with that as HE changes and the devices change with the solar winds.
At some point...maybe they'll get that this is not doing them any favor market-wise.
EDIT ADD: I am just glad I didn't act out of confidence that this relay was going to be a piece-of-cake swap for the 1CH I have in place right now. I would be livid having pulled all that out of it's enclosure and reworked all the wiring only to find this not behaving right! BENCH TESTING is the way!
I don't think that Tuya will ever encourage the fully local use of their cheap devices with other Zigbee coordinators. They will be missing the cloud data collection, also the income for their cloud servers usage (paid by the manufacturers).
Ah, good point.
Their resellers like to taut the compatibility with the prevailing home automation platforms but you are right, the manufacture has it's own agenda.
