There is also one that can be installed via HPM called Zigbee Graph.
Thanks jameslslate. I was able to "view as graph (beta) " and it works good. I also downloaded and installed Zigbee Graph but unfortunately it doesn't appear to be working. When I click "Tap Here to go to the Zigbee Graph", I get error 404, page not found.
Sorry I didn’t get a notification but I see the question was already answered. But yes that was the beta and it turns out there’s something rather odd going there: At least one of the devices represented there isn’t even plugged in and, furthermore, has not been plugged in since I upgraded to the version 8 hub. So how can it be passing traffic?
I just got the single channel MHCOZY board. I paired it with HE, no problem. However, I have tried several different drivers, Generic Zigbee Multi-Endpoint, Zemismart Wall Switch, Generic Zigbee Switch, and Generic Zigbee Outlet. Pressing Configure never creates any child devices. And of course, ON and OFF do not do anything. Should I return this and get the 4 channel board? Or any other suggestions? Thanks.
Post the Device Details section as shown on the HE web page - probably it is a new manufacturer and needs the fingerprint added to the driver.
Device Details
| Create Time | 2024-02-26 20:58:54 MST |
|---|---|
| Last Update Time | 2024-02-26 21:03:56 MST |
| Last Activity At | 2024-02-26 21:04:01 MST |
| Controller Type | ZGB |
| Data | * endpointId: 01 |
- application: 53
- manufacturer: _TZ3000_p26flek3
- model: TS0001|
|In Use By||
Thanks!
Manually assign the Zemismart driver (the fingerprint is not there yet!) and pair the switch board once again to your HE hub (is it C-8)? Do not delete the device, just pair it again.
Some Tuya devices need to be paired with the right driver already assigned; otherwise, they may not work by simply changing the driver later.
This is a one-channel device, so no child devices will be created. Use the main device for switching on/off.
Yes, my hub is C-8. I turned off the device and back on and then re-paired it. Still can't control the relay. The "current state" of the device remains "Off".
This is a very new manufacturer and this device is also not supported in Home Assistant at the moment... Troubleshooting it will require a lot of details and debug logs back and forth...
So, if you can simply return it and get a 4-channel board that is known to work with HE - this will be the fastest solution.
- manufacturer: eWeLink
- model: ZB-SW01
These has been serving me well, and I have bought the 1, 2, and 4 channel I think all from the seller "Mic Technology" .
1 Like
Well, I received the board with four relays. When I powered it up, it realized that it was a Zemismart Wall Switch and after pairing, it created the 4 child devices. Unfortunately, I still can't control the relays with HE.
One thing I did notice was after powering the board, the red LED was blinking, After I started Zigbee pairing, and HE saw the device, the LED continued to blink and finally turned off after a couple of minutes. Does this mean that it never actually paired?
Well, I received the board with four relays. When I powered it up, it realized that it was a Zemismart Wall Switch and after pairing, it created the 4 child devices. Unfortunately, I still can't control the relays with HE.
One thing I did notice was after powering the board, the red LED was blinking, After I started Zigbee pairing, and HE saw the device, the LED continued to blink and finally turned off after a couple of minutes. Does this mean that it never actually paired?
Seems like a C-8 Zigbee pairing problem again…. Are you pairing the device very close to the hub,?
Enable the Debug logging and post the live logs that come at the time you pair the relay board. Also, post screenshots of the Device Details section and from the State Variables section.
Pair it very close to the hub. Also, use the option “Try to avoid Zigbee 3.0 repeaters “
I was pairing when the device was mere inches away from the C-8. Here is the log:
dev:4592024-02-29 10:52:52.147debugGarage door switch sending componentOff 459-04
dev:4592024-02-29 10:52:50.831debugGarage door switch sending componentOn 459-04
dev:4592024-02-29 10:52:48.870debugGarage door switch sending componentOff 459-04
dev:4592024-02-29 10:52:46.656debugGarage door switch sending componentOn 459-04
dev:4592024-02-29 10:52:43.080debugGarage door switch sending componentOn 459-04
dev:4592024-02-29 10:49:51.970debugGarage door switch Attribite FFE4 : 01
dev:4592024-02-29 10:49:51.965debugGarage door switch Attribite FFE2 : 30
dev:4592024-02-29 10:49:51.964debugGarage door switch Applicaiton version: 50
dev:4592024-02-29 10:49:51.959debugGarage door switch Parsed descMap: [raw:354F0100001801002050E2FF2030E4FF2001, dni:354F, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:50, clusterInt:0, attrInt:1, additionalAttrs:[[value:30, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:01, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]] (description:read attr - raw: 354F0100001801002050E2FF2030E4FF2001, dni: 354F, endpoint: 01, cluster: 0000, size: 18, attrId: 0001, encoding: 20, command: 0A, value: 50E2FF2030E4FF2001)
dev:4592024-02-29 10:49:42.205debugGarage door switch Parent switch off
dev:4592024-02-29 10:49:42.190debugGarage door switch Parsed descMap: [raw:354F0100060A00001000, dni:354F, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0] (description:read attr - raw: 354F0100060A00001000, dni: 354F, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 00)
dev:4592024-02-29 10:49:40.258debugGarage door switch Garage door switch unprocessed EP: 01 cluster: 0006 attrId: null
dev:4592024-02-29 10:49:40.255debugGarage door switch Parsed descMap: [raw:catchall: 0104 0006 01 01 0040 00 354F 00 00 0000 07 01 00000000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:354F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00, 00, 00, 00]] (description:catchall: 0104 0006 01 01 0040 00 354F 00 00 0000 07 01 00000000)
dev:4592024-02-29 10:49:38.242debugGarage door switch Garage door switch unprocessed EP: 00 cluster: 8021 attrId: null
dev:4592024-02-29 10:49:38.239debugGarage door switch Parsed descMap: [raw:catchall: 0000 8021 00 00 0040 00 354F 00 00 0000 00 00 AA00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:354F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[AA, 00]] (description:catchall: 0000 8021 00 00 0040 00 354F 00 00 0000 00 00 AA00)
dev:4592024-02-29 10:49:38.151debugGarage door switch Garage door switch unprocessed EP: 01 cluster: 0000 attrId: null
dev:4592024-02-29 10:49:38.148debugGarage door switch Parsed descMap: [raw:catchall: 0104 0000 01 01 0040 00 354F 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:354F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]] (description:catchall: 0104 0000 01 01 0040 00 354F 00 00 0000 04 01 00)
dev:4592024-02-29 10:49:37.948debugGarage door switch Model Identifier: TS0004
dev:4592024-02-29 10:49:37.946debugGarage door switch Applicaiton version: 50
dev:4592024-02-29 10:49:37.945debugGarage door switch ZLC version: 03
dev:4592024-02-29 10:49:37.944debugGarage door switch Manufacturer name: _TZ3000_u3oupgdy
dev:4592024-02-29 10:49:37.938debugGarage door switch Parsed descMap: [raw:354F01000068040042105F545A333030305F75336F75706764790000002003010000205005000042065453303030340700003001FEFF003000, dni:354F, endpoint:01, cluster:0000, size:68, attrId:0004, encoding:42, command:01, value:_TZ3000_u3oupgdy, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:50, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0004, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]] (description:read attr - raw: 354F01000068040042105F545A333030305F75336F75706764790000002003010000205005000042065453303030340700003001FEFF003000, dni: 354F, endpoint: 01, cluster: 0000, size: 68, attrId: 0004, encoding: 42, command: 01, value: 105F545A333030305F75336F75706764790000002003010000205005000042065453303030340700003001FEFF003000)
dev:4592024-02-29 10:49:37.904infoGarage door switch device model TS0004, manufacturer _TZ3000_u3oupgdy re-joined the network (deviceNetworkId 354F, zigbeeId A4C1389B85D30352)
dev:4592024-02-29 10:49:37.894debugGarage door switch Parsed descMap: [raw:catchall: 0000 0013 00 00 0040 00 354F 00 00 0000 00 00 004F355203D3859B38C1A48E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:354F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 4F, 35, 52, 03, D3, 85, 9B, 38, C1, A4, 8E]] (description:catchall: 0000 0013 00 00 0040 00 354F 00 00 0000 00 00 004F355203D3859B38C1A48E)
dev:4592024-02-29 10:49:37.876debugGarage door switch sendZigbeeCommands : [he raw 0x354F 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x354F 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x354F 0x01 0x01 6 {A4C1389B85D30352} {}, delay 2000, he cr 0x354F 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x354F 0x01 6 0 {}, delay 2000]
And the Device Details:
Device Information
Zemismart ZigBee Wall Switch Multi-Gang
Device Name *
Garage door switch
Device Label
A4C1389B85D30352
Zigbee Id
11
Event history size, per event type (1-2000)
30
State history size, per attribute (1-2000)
300
Too many events alert threshold, per hour (100-2000)
edit
354F
Device Network Id *
Zemismart ZigBee Wall Switch Multi-Gang
Type *
Garage
Room MainGarageLiving room
Dashboards
Advanced
Device Details
Create Time 2024-02-28 15:01:52 MST
Last Update Time 2024-02-29 10:49:36 MST
Last Activity At 2024-02-29 10:49:42 MST
Controller Type ZGB
Data
endpointId: 01
application: 50
manufacturer: _TZ3000_u3oupgdy
model: TS0004
Component Devices
Zemismart ZigBee Wall Switch Multi-Gang EP01 (Switch EP01)
Zemismart ZigBee Wall Switch Multi-Gang EP02 (Switch EP02)
Zemismart ZigBee Wall Switch Multi-Gang EP03 (Switch EP03)
Zemismart ZigBee Wall Switch Multi-Gang EP04 (Switch EP04)
In Use By
State Variables:
State Variables
- driverVersion : 0.6.1 2024/01/29 7:46 AM
1 Like
@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.
I updated the driver and paired it again. However, the red LED continues to flash. I did a ping, but I get a timeout on the first try.
Do you still have your old C-7 hub?
The board works fine with the C-7. Can the developers work on this?
Just in case anyone is interested in this info -
I just purchased this 2-channel...
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.
1 Like
