Skip to content

added TS110E driver for#1350

Open
PiTRiS87 wants to merge 1 commit into
JohanBendz:SDK3from
PiTRiS87:SDK3
Open

added TS110E driver for#1350
PiTRiS87 wants to merge 1 commit into
JohanBendz:SDK3from
PiTRiS87:SDK3

Conversation

@PiTRiS87

@PiTRiS87 PiTRiS87 commented Mar 5, 2026

Copy link
Copy Markdown

"_TZ3210_ngqk6jia",
"_TZ3210_weaqkhab"
Tested for "_TZ3210_ngqk6jia" second one should be same Removed "_TZ3210_ngqk6jia" from dimmer_1_gang and dimmer_1_gang_2

"_TZ3210_ngqk6jia",
"_TZ3210_weaqkhab"
Tested for "_TZ3210_ngqk6jia" second one should be same
Removed "_TZ3210_ngqk6jia" from dimmer_1_gang and dimmer_1_gang_2
@PiTRiS87
PiTRiS87 requested a review from JohanBendz as a code owner March 5, 2026 20:05
@PiTRiS87

PiTRiS87 commented Mar 5, 2026

Copy link
Copy Markdown
Author

little bit of vibe coding, but it finally works... after years with just on/off :D

@JohanBendz

Copy link
Copy Markdown
Owner

Hi @PiTRiS87.
I see you moved _TZ3210_ngqk6jia from 1 gang to 2 gang and just wanna make sure you have the device and have verified it's working as a 2 gang. If s, moving it will break any current device using it as a 1 gang unit, but it might be worth the trouble if one get both gangs to work :)

@PiTRiS87

Copy link
Copy Markdown
Author

@JohanBendz just tested based on your comment and you are right, I messed up something and even though that hellish light (1 gang _TZ3210_ngqk6jia ) that wasn't dimming for couple of year now works, I messed up something with the 2 gang dimmer :D not really using it on those extra, os overlooked that...
Will fix it and push update... sry... :(

@JohanBendz

Copy link
Copy Markdown
Owner

@PiTRiS87, I was thinking you moved the id from the 1_gang device to the 1_gang_2 device but I now see you moved it from both those drivers to a new light driver. Hmm, this will break on/off for those who use it today. I'll have a look at what you do in the new driver to see if I can fix the old one instead.

@PiTRiS87

PiTRiS87 commented Mar 28, 2026

Copy link
Copy Markdown
Author

@JohanBendz That might be the best. :D Honestly, no experience with homey/zigbee development, so this was an hour long vibe coding excercise with gemini, based on that implementation for home assistant and... magic. Anyways _TZ3210_ngqk6jia works great, tested.
Anyways now not sure why it broke my 2 gang, as that one is "_TYZB01_v8gtiaed" TS110F... And I think I have not touched that... oh my... sorry for that :D :D

dlnraja pushed a commit to dlnraja/com.tuya.zigbee that referenced this pull request Jun 8, 2026
Forum issue JohanBendz#1350 (_TZE204_ztqnh5cg presence sensor):
- Removed wrong 'air_purifier' entry from driver-mapping-database.json
- Device was routed to air_purifier instead of pir_mmwave_sensor
- pir_mmwave_sensor compose.json already had correct registration

Forum issue JohanBendz#1400 (_TZ3002_pzao9ls1 4-gang button):
- Fixed MFR typo: _TZ302_pzao9ls1 -> _TZ3002_pzao9ls1 in device.js
- Added _TZ3002_pzao9ls1 (3 case variants) to switch_4gang compose.json
- Device was not matched by compose.json, relied on database routing

Forum issue JohanBendz#1100 (water sensor alarm):
- Already fixed in v5.5.803 (invert_alarm setting + IAS alarm2 support)
- User needs to update app version

Forum issue JohanBendz#1400 (2-gang switch both gangs):
- Already fixed in v5.9.23+ (_removeGroupMemberships + broadcast filter)
- User needs to update and re-pair

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants