Hi @jshimota , Happy New Year! 
I am afraid, that changing the driver logic related to the identification of the child devices as it is now may result in backward compatibility problems with the previous versions.
Isn't the Dashboard picking the device label, not the automatically created device name?
I only use HD+ - no other dashboard meets me needs. In the case of HD+, it pulls Name by default. I can hand edit, and have - I was hoping to get HE to work cleanly in case of a future rebuild so I didn't have to track them down - it's a small thing - no worries sir!
All other HE apps use the device label if set by the user. Only if the device label is empty, the app should use the device name. So the best approach would be to ask the HD+ developer for a change, it may be a global option in the HD+ app.
NOT trying to argue - but I've always thought that HE recognized devices by the device ID, the name and labels are really superfluous - of all my drivers none hard-lock the name. @jpage4500 does indeed allow the user to decide what he/she wants - no need there. However, I just wanted the freedom not to be hardcoded when it seems to me to be unncessary. In the case of a child device, I get how it occurs, I just wish it didn't,
So you know - you're in my top 5 dev's ... 
You've solved numerous issues for me and allowed me a wider array of devices because of your work - my HE does more for me, because of you!
I am currently working on a very big new project, that may change the way that any new Tuya gadgets are accessible in HE :
lol. I remember - I pay attention when you speak! I'm sooo looking forward to being able to really dive into Tuya devices - they are cheap, effective and readily available - I'm hoping a central libary ... well - anyways. I'll watch with a weathered eye !
You know what is the problem with the Tuya devices - every manufacturer implements its own protocol (Tuya Datapoints), so it is very time-consuming to keep up with the new devices that become available on the market every new month. I have a waiting list of probably 10 or more devices to add to my existing drivers... : (
A Tuya Zigbee -> Matter Gateway should (theoretically) make the new devices available in Hubitat immediately, without making any changes in the HE drivers. Of course, it has a lot of limitations (and bugs at the moment), but I don't see another way to continue. The Tuya device specifics should be handled in the Tuya Gateway.
FWIW I had to check since I was curious and by default HD+ picks the label if it's set. Then, the name if not set. You can override both though and it'll use that instead.
There is a setting though to switch the order -- so name would come before label - but that's not the default
The name of the central library is 'Matter Gateway'. Did you order your Zemismart M1 Matter Gateway hub already?
ARGH! tried too! unavailable in USA and Aliexpress has it late February.... crap. Great price tho!
I tried to pair Zemismart 4-gang zigbee wall switch to HE. I selected 'Zemismart zigbee wall switch multi-gang' driver and found one one switch was shown and even the switch is not working. The finger print is:
What is this message meaning?
IMPORTANT
In order to operate normally, please pair the device to HE after changing to this driver!
After changed to this driver I cannot pair without removing device because it is already paired.
Please help.
Following is the log:
dev:4282024-03-07 01:57:54.552 PMdebugMain Lights Parent createChildDevices
dev:4282024-03-07 01:57:54.550 PMinfoMain Lights model: TS0601 gangs:1 child devices: 0
dev:4282024-03-07 01:57:54.547 PMdebugMain Lights Parent deleteChildren
dev:4282024-03-07 01:57:54.546 PMdebugMain Lights Parent setupChildDevices
dev:4282024-03-07 01:57:54.541 PMdebugMain Lights sendZigbeeCommands : [he raw 0x4480 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x4480 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x4480 0x01 0x01 6 {A4C13827EA1605D1} {}, delay 2000, he cr 0x4480 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x4480 0x01 6 0 {}, delay 2000]
dev:4282024-03-07 01:57:54.534 PMdebugMain Lights configure()..
dev:4282024-03-07 01:57:54.524 PMinfoMain Lights InitializeVars()... fullInit = true
dev:4282024-03-07 01:57:54.522 PMdebugMain Lights Initializing...
dev:4282024-03-07 01:57:50.609 PMinfoMain Lights initialize aborted! (str=--- Select ---)
dev:4282024-03-07 01:57:36.544 PMdebugMain Lights sendZigbeeCommands : [he raw 0x4480 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x4480 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x4480 0x01 0x01 6 {A4C13827EA1605D1} {}, delay 2000, he cr 0x4480 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x4480 0x01 6 0 {}, delay 2000]
dev:4282024-03-07 01:57:36.539 PMdebugMain Lights configure()..
It's really confusing which driver to use with all these Tuya 100 different variations ...
You have a new device whose fingerprint is not in the Martin's driver yet.
First install the "Moes ZigBee Wall Switch 1/2/3-Gang" driver, then manually change your device driver to this one.
Then, obligatory, pair the device again to the hub. Although the fingerprint is missing, the driver should create 4 child devices (if not already created). Let me know if this will work.
Hi, kkossev, thanks for your help.
I tried to use the driver you suggested.
I recognized number of buttons(4) correctly and showed 4 child devices.
But, all 4 child devices showed blank 'Current States' in the device pages and on and off buttons were not working. The wall switches were not responding.
Actually I bought the wall switch about a year ago. So, I thouhgt there is a driver for the wall switch. Following is the log:
dev:4282024-03-07 03:09:21.066 PMdebug{executed} 0xF975 0x01 0xEF00 0x00
dev:4282024-03-07 03:09:21.034 PMdebugcomponent refresh 428-02 Main Lights EP02
dev:4282024-03-07 03:09:20.090 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000101}
dev:4282024-03-07 03:09:20.086 PMinfoMain Lights EP02 is ON
dev:4282024-03-07 03:09:20.085 PMdebugcomponent state is ON - Main Lights EP02 {428-02}
dev:4282024-03-07 03:09:18.775 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000100}
dev:4282024-03-07 03:09:18.772 PMinfoMain Lights EP02 is OFF
dev:4282024-03-07 03:09:18.771 PMdebugcomponent state is OFF - Main Lights EP02 {428-02}
dev:4282024-03-07 03:09:17.138 PMdebug{executed} 0xF975 0x01 0xEF00 0x00 {00010201000101}
dev:4282024-03-07 03:09:17.135 PMinfoMain Lights EP02 is ON
dev:4282024-03-07 03:09:17.133 PMdebugcomponent state is ON - Main Lights EP02 {428-02}
dev:4282024-03-07 03:07:51.753 PMinfoRefreshing...
dev:4282024-03-07 03:07:51.691 PMinfoChild device 428-04 already exists (Main Lights EP04)
dev:4282024-03-07 03:07:51.687 PMinfoChild device 428-03 already exists (Main Lights EP03)
dev:4282024-03-07 03:07:51.684 PMinfoChild device 428-02 already exists (Main Lights EP02)
dev:4282024-03-07 03:07:51.678 PMinfoChild device 428-01 already exists (Main Lights EP01)
dev:4282024-03-07 03:07:51.673 PMdebugParent createChildDevices
dev:4282024-03-07 03:07:51.671 PMinfomodel: _TZE200_1n2kyphz buttons: 4
dev:4282024-03-07 03:07:51.665 PMdebugParent deleteChildren
dev:4282024-03-07 03:07:51.663 PMdebugParent setupChildDevices
dev:4282024-03-07 03:07:51.662 PMwarnDebug logging will be automatically disabled after 30 minutes!
dev:4282024-03-07 03:07:51.661 PMinfoInitializing...
Wait one more day, and I will add this device fingerprint to the driver, and then you can try again.
Some weird Tuya devices will not work in HE if their fingerprints are not in the driver.
Thanks for your kindness.
I'll look forward to update.
Yes.
I paired the wall switch to Zemismart M1 matter hub, which was paired to Homekit and HE, but I could see it in neither Home app nor HE. Very weird device.
That's why I want to pair HE directly.
Download the Hubitat app
