Do you mean that when using the Zemismart ZigBee Wall Switch Multi-Gang" driver you can't control individually the outlets, but they all switch on/off at once?
Correct.
Just trying to delete the device from HE and re-pair one more time.
Should I update the driver code? Or is it unchanged?
Wait 5 minutes. I am modifying the Muxa's driver to apply a similar 'TuyaBlackMagic' initialization as in the Tuya Metering plug driver.
k.
ATM
Zemismart ZigBee Wall Switch Multi-Gang 0.2.12
Tuya Zigbee Metering Plug 1.6.2
Update the Zemismart ZigBee Wall Switch Multi-Gang to ver. 0.2.13 2022-11-12 - tuyaBlackMagic() for Xenon similar to Tuya Metering Plug.
The Zemismart driver was not assigned automatically… so most probably the Xenon fingerprint is wrong.
Checking
Found it, please update again - same version, timeStamp 2022/11/12 11:10 PM
Got the update, browser is now stuck on spinning circle mode....
Switching to Device, clearing everything.
While saving the driver? I have had similar slowdowns in the last few days also.
1 Like
Back to the driver, saving....
So far so good.
Save Preferences.....
Spinning...
Nothing in the logs.
Still spinning... aka waiting for 192....
I am reading the Github comments on the same device issues - there are 37 comments on ZHA and 110 (!!) comments on Zigbee2MQTT implementation ...
So, the implementation in HE will definitely take much more time than usually.
Clicking on Configure or Initialize seems to do nothing, it's only when I click on Save Preferences that it goes into limbo.
This screenshot from HomeAssistant ZHA thread sounds scary to me :
I will stop for now, going deeper will require a lot of time that I don't have at the moment.
Controlling this XENON 4AC+2USB power strip from HE will be too tricky and too risky.
Well if I switch to the Generic driver I have control of 2 components now. 
1 Like
Last kick for tonight...
Using this driver to initialize, then switching to the Generic Multi gives me control of the four outlets, no USB's.
I think... too much clicking. 
1 Like
I have the same strip in an different layout. Using zigbee multi endpoint driver and it works, but changes its 16 bit address almost everyday. When I start pairing for other zigbee devices, this strip often shows up as wanting to pair again, like its in a pairing loop. Maybe some cluster is not being bound properly?
Here's my data section
Data & Child Devices
- endpointId: 01
- application: 42
- isMultiEP: true
- manufacturer: _TYZB01_vkwryfdr
- model: TS0115
Component Devices * Strip Plug 1 (Generic Zigbee Multi-Endpoint Switch EP01) - Strip Plug 2 (Generic Zigbee Multi-Endpoint Switch EP02)
- Strip Plug 3 (Generic Zigbee Multi-Endpoint Switch EP03)
- Strip Plug 4 (Generic Zigbee Multi-Endpoint Switch EP04)
- Strip USB Ports (Generic Zigbee Multi-Endpoint Switch EP07)
I pulled the trigger and while the AliExpress 11/11 discounts are still active, ordered the EU version of hopefully the same or very similar in it's behaviour device : https://www.aliexpress.us/item/3256802155363913.htm
I will come back when I receive it and have it fully working.
2 Likes
The UK one works with the generic zigbee multi endpoint driver. It recognised as the zemismart driver as a single - change the driver to generic and child devices marked EP0x pop up. 4 sockets plus USB working.
There is something weird though, an extra device marked Zigbee EPF2. Only thing I can think of is the press button for pairing?
I received my power strip yesterday. The bad news is that for now, after a lot of attempts and experiments I can not make it work with HE.
Listening to the Zigbee communication to HE radio shows unusual high number of repeated packets on transport level.
The device doesn't finish the Zigbee pairing procedure with HE, sends a 'leave' command, and changes its NWK address.
| Manufacturer: | _TZ3000_cfnprab5 |
|---|---|
| Endpoint 01 application: | 64 |
| Endpoint 01 endpointId: | 01 |
| Endpoint 01 idAsInt: | 1 |
| Endpoint 01 inClusters: | 0000,0006,0003,0004,0005,E001 |
| Endpoint 01 initialized: | true |
| Endpoint 01 manufacturer: | _TZ3000_cfnprab5 |
| Endpoint 01 model: | TS011F |
| Endpoint 01 profileId: | 0104 |
| Endpoint 01 stage: | 4 |
| Endpoint 02 endpointId: | 02 |
| Endpoint 02 idAsInt: | 2 |
| Endpoint 02 inClusters: | 0000,0006,0003,0004,0005,E001 |
| Endpoint 02 initialized: | true |
| Endpoint 02 profileId: | 0104 |
| Endpoint 02 stage: | 4 |
| Endpoint 03 endpointId: | 03 |
| Endpoint 03 idAsInt: | 3 |
| Endpoint 03 inClusters: | 0000,0006,0003,0004,0005,E001 |
| Endpoint 03 initialized: | true |
| Endpoint 03 profileId: | 0104 |
| Endpoint 03 stage: | 4 |
| Endpoint 04 endpointId: | 04 |
| Endpoint 04 idAsInt: | 4 |
| Endpoint 04 inClusters: | 0000,0006,0003,0004,0005,E001 |
| Endpoint 04 initialized: | true |
| Endpoint 04 profileId: | 0104 |
| Endpoint 04 stage: | 4 |
| Endpoint 05 endpointId: | 05 |
| Endpoint 05 idAsInt: | 5 |
It's rather unusual that the reported number of outClusters is 0.
Searching for information on the SoC manufacturer for this device doesn't find a registered manufacturer company. MAC Address Lookup - MAC Lookup Online defaults to the Ieee Registration Authority.
It is the same problem as with the UK plug TS01F _TZ3000_okaz9tjs
The SoC is from the same unknown manufacturer (MAC address starting with 70B3D52)
2 Likes
