Thanx, I tried just now but it didn’t work out. Even after selecting the right profile presence+ illuminance it is worse than “your” driver. Hmm any idea how I can proceed? It looks like there’s only a minor issue left. I mean everything works but only when the presence sensor is activated the lux value becomes updated
I can help and I’m a developper, but I don’t have experience with this kind of stuff…
@Mariano_Colmenarejo unfortunately it does not offer me the option.
Probably, you haven’t configured the driver properly… as you were running it in “similarity mode”.
Currently, _TZE200_3towulqd only is in beta channel.
You may test it if you want to.
Just make sure to repair the device after installing the driver.
Version: 2023-07-20T11:05:31.241510474
It does not offer you the option because your fingerprints are not in the driver.
What I was referring to is that if I add the fingerprints, your device is a gas sensor and in the smartthings stock driver there are only smoke and CO sensors, so I don’t know if it would work
Hi - Give me 5 days. I am looking into this. Just installed the CLI and Lua I already know. Seems pretty straight forward for me to put out a custom edge driver for this.
Hi. I just now spoke to the company. They said should work. Can you please?
Should it work as smoke or CO sensor?
You are right. It is limited to 1 update every 12 seconds.
I just updated the illuminance.
I just got a bunch of alerts that all of my Quirky Tripper contact sensors were removed from Google Home… always a bad sign. I checked SmartThings and sure enough all of the trippers were listed as Zigbee Things. I assume ST made some edge driver change to the standard zigbee driver today 7/21/23 14:15 which killed all the trippers. Is there a fuming emoji?
I began my ST community search and found this thread. I installed your Zigbee Contact Mc driver and now my trippers are happy again.
Thank you for providing the driver to the community!
@Mariano_Colmenarejo can you please? Let me try. Called the manufacturer who said should work similarly.
In August when I have access to the cli I will add it to the Z-wave Smoke Alarm Mc driver and try to see if it works.
Hi @gapao
I take note to do it in the month of August, until then I do not have access to the CLI or a pc
If you try to pair it with my driver or the stock driver zigbee switch, it may pair as a generic dimmer
hi @Mariano_Colmenarejo , can you add this to the window treatment driver. Many thanks from Canada!
DeviceInfo:
Manufacturer: _TZE200_xuzcvlku
Model: TS0601
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x44
ZCL Version: 0x03
Network ID: 0x2A4D
Zigbee EUI: 5C0272FFFE8C70FE
Device ID: cfce683d-9b88-4d10-ac94-61332f6f2364
Server Cluster:
Ep: 0x01={ 0000,0004,0005,EF00 }
Client Clusters:
Ep: 0x01={ 0019,000A }
Signal Metrics:
LQI: 255 … RSSI: -44 dbm
Based in what tests ?
What was your results ?
Do you have any evidence to share ?
Where did you see this being done exactly ?
The driver can make some operations with the raw data before sending the event to be displayed by the app.
This is what the driver was doing before you said it was wrong.
Then I changed to display the raw data because some devices work with raw data.
The guy tells in the comments on the page I shared that he has done some measurements with a lux meter.
I see he could not find a formule to fit the data. However if I discard the first valuepair you can find this first order fit:
Lux value= 4.572*raw value - 329.7
Or even better:
Lux value = 0.086* e^(0.00735*raw value)
Indeed If you ask me this luminance sensor is pretty worthless. It tops at a way too low raw value of 1000 which is only about 125 lux.
This device use cluster EF00 and does not work with my driver.
maybe it will work with the @iquix driver
Should work with @iquix driver. You can join his channel from here:
https://bestow-regional.api.smartthings.com/invite/qWjB0pNyY62y
Contact sensor support please.
The device information is as follows.
Manufacturer Code
TUYATEC-ydcwf5m2
Model
RH3001
how do i add the quirky tripper edge driver ?
