matt-hammond-001 / hubitat-code Goto Github PK

A I have tested the model: TS1101 / manufacturer: _TZ3000_7ysdnebc just by adding the lines below in the modelConfigs:

"_TZ3000_7ysdnebc": [
    numEps: 2,
    joinName: "Tuya Zigbee 2-Gang Dimmer module"
]    

This is the device data:

It is working flawlessly, however I think it is a good idea to check if more changes are needed in the driver. If everything is ok, I believe you could add this new model to this driver so other users will able to use it also.

Thanks in advance

When a new child app is created for the Lighting Schedules app, the user provided title is ignored. It is subsequently set correctly when, later, the user opts to edit the settings for that child app and set the title again.

I recently bought some modules and got different fingerprints. Adding these to the modelConfigs works, but I still have to select the driver for newly joined devices.

2 CH code:
"_TZ3000_zjtxnoft": [
numEps: 2,
joinName: "Tuya Zigbee 2-Gang Dimmer module"
],

2 CH info:
endpointId: 01
application: 44
inClusters: 0003,0004,0005,0006,E000,E001,0008,0000
manufacturer: _TZ3000_zjtxnoft
model: TS0052
outClusters: 0019,000A

Is it possible to add a Power On option to select the power state after a power loss?

The function that parses a lighting timing string gets stuck in an infinite loop if the string is empty. This results in the Hubitat hub reporting severe/high load and some applications becoming unresponsive.

To reproduce

1. Create a lighting schedule
2. Add at least one device to the lighting schedule, but leave the text box for entering its timings empty

Observed
Hubitat reports high/severe CPU load and some applications become unresponsive.

Specify a lighting timing interval:

2300-0000

Expected behaviour - light comes on between 11pm and midnight
Actual behaviour - light never comes on.

Code is confused because it thinks 0000 is the start of the day. Need a more sophisticated heuristic to guess the user's intentions