[ST Edge] Personal Tuya Devices - Generic EF00 Device

Hi @w35l3y

I use your driver with the zigbee ceiling variant of this presence sensor.

Zigbee Wifi Mmwave Menselijke Aanwezigheid Bewegingssensor Met Luminantie/Afstandsdetectie 5/110/220V Tuya Smart Life Domotica - AliExpress

The presence sensor is recognized and it works fine, but I can only use it in a routine, to switch lights or whatever. I cannot use it to trigger an alarm in security mode. Is it possible to add an option that you can also use the driver as a motion sensor instead of a presence sensor. I think I then can select it as a sensor for the alarm?

1 Like

Hello,

Thanks for all your work building the driver. One of the devices i use with your driver is zigbee garage opener. Button works fine, it opens and closes the door and contact sensor is accurate. When someone uses the the physical garage door button or a remote clicker, door state goes out of sync even though contact sensor shows correct state. Is there a way to sync garage door and contact sensor states?

Thanks.



Open it in generic mode, keep looking the datapoints list in the app and press the remote control.

Then let me know the results of the test above.

Hello,

I put it in Generic mode, pressed the wall switch and clicker a few times. below are the screenshots. The only change i see is datapoint 3 changing between true and false depending on garage door position. Little more info on my setup, my opener is connected to a remote as shorting the contacts on the back of my garage door nothing. Pressing this remote button didnt add any more datapoints.



It explains the reason why the driver didn’t sync.
The driver bahaves based on received informations.
If it doesn’t receive anything, it can’t do much other than wait.

Hi, could you please tell me how you did this. Mine only recognizes this same device as “thing”

Hi Wesley,

I have come across a thermostat radiator valve.
TZE200 p3dbf6qs

Played with device and i see that DP
2 is mode (2 off, 1 is auto, 0 programmed) (not completely sure about these though)
3 is heating (1 off, 0 on)
4 is set temp * 10
5 is current temp * 10
7 is childlock ( true is locked, false unlocked)

please help

Hi @w35l3y !

I have a ZG-205Z/A (Zigbee human presence sensor - TS0225 | _TZE200_2aaelwxk), and i’m using your beta driver.
The luminance works just fine (it updates and reports correct values)… but the presence sensor is locked in “present” and doesn’t update (i even tried diferent settings with no results)…

Can you help me?
Thank you very much! Your work in the Smartthings community is extraordinary!

The DP is defined correctly.
Probably, it has something to do with your settings, but I can’t help you with this.

@w35l3y I understand and thanks anyway for all the help…
The strange is that the presence sensor never worked (even with the standard settings)…
And with the new driver update (that removed the TZE200_2aaelwxk profile), the presence sensor now doesn’t show anything (even with a manual DP = 1), and the illuminance shows the correct value (if i manual select the illuminance DP = 106)…
Maybe @iquix can add this Zigbee human presence sensor - TS0225 | _TZE200_2aaelwxk to his driver?

@w35l3y have you changed anything in driver in last 24hrs?
Mine presence sensor worked fine with lux readings. Now i tried do remove and readd and still no lux readings.

Tnx

It is advised NOT TO USE beta version in production.

It is only for testing purposes.

Yes, I recently changed the beta version.

Uninstall the beta version if you don’t have any device being tested.

Uninstalled beta driver and readded the device. Again everything is working except lux readings. And i get that message about device still not updated…

Can logs help? The one upon pairing?

Main version was updated 3 weeks ago.

Yes, logs help a lot. Thanks.

Hello.
Please help. I have zemismart touch curtain that I can control and cant calibrate. Properly.

I also have this from the manufactorer.

DP ID DP Name Identifier Data Transfer Type Data Type Properties Remarks
1 Curtain Switch 1 control Send and Report enum Enum Value: open, stop, close
2 Percentage 1 percent_control Send and Report value “Value Range: 0-100,
Pitch: 10, Scale: 0,
Unit: %”
8 Motor steering 1 control_back Send and Report enum Enum Value: forward, back
10 Quick Calibration 1 tr_timecon Send and Report value “Value Range: 10-1200,
Pitch: 1, Scale: 0,
Unit: s”
101 Percent State percent_state Report Only value “Value Range: 0-100,
Pitch: 1, Scale: 0,
Unit: %”

Can someone help with this.
I want the driver to work and I could open and close the shutter.
It also says allways its partly open

Hi Wesley,

The irrigation device is detected like in the pic.
The problem is that when the switch is “on” and I try to put the valve in “open” it immediately return to “close”.

Is this a know issue?

Thank you.

Consider using the generic mode to calibrate it.

Otherwise, you may buy a tuya hub just to configure the settings and then pair the device with ST. Your settings will be kept the same.

It probably has something to do with “Datapoint Value”
Fill it with some value like “5” and try again.

Hi @w35l3y!

Is it possible to add the WZ-M100-Z Zigbee Human Presence Sensor (a 5.8GHZ mmWave sensor) to your collection of “Presence Tuya Devices - Tuya Presence Sensor” driver?

Here’s the “fingerprint” and the “Tuya datapoints” (accordingly to https://github.com/Koenkk/zigbee2mqtt/issues/17483) - is very similar to the TZE204_sxm7l9xa (included in your driver) but not quite the same:

fingerprint: tuya.fingerprint(‘TS0601’, [‘_TZE204_e5m9c5hl’]),
model: ‘WZ-M100-Z’,
vendor: ‘Wenzhi’,
description: ‘Human presence sensor’,
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tzDatapoints],
onEvent: tuya.onEventSetTime,
configure: tuya.configureMagicPacket,
exposes: [
e.illuminance_lux(), e.presence(),
e.numeric(‘radar_sensitivity’, ea.STATE_SET).withValueMin(1).withValueMax(10).withValueStep(1),
e.numeric(‘distance’, ea.STATE).withValueMin(0).withValueMax(10)
.withDescription(‘target distance’).withValueStep(0.01).withUnit(‘m’),
e.numeric(‘fading_time’, ea.STATE_SET).withValueMax(1500).withValueMin(5).withValueStep(5).withUnit(‘s’)
.withDescription(‘presence timeout’),
e.numeric(‘far_detection’, ea.SET).withValueMin(0).withValueMax(9.5)
.withDescription(‘maximum detection range’).withValueStep(0.1).withUnit(‘m’),
e.numeric(‘near_detection’, ea.SET).withValueMin(0).withValueMax(9.5)
.withDescription(‘minimum detection range’).withValueStep(0.1).withUnit(‘m’),
e.numeric(‘detection_delay’, ea.STATE_SET).withValueMin(0).withValueMax(10).withValueStep(0.1).withUnit(‘s’)
.withDescription(‘detection delay’),
],
meta: {
tuyaDatapoints: [
[105, ‘presence’, tuya.valueConverter.trueFalse1],
[104, ‘illuminance_lux’, tuya.valueConverter.raw],
[106, ‘radar_sensitivity’, tuya.valueConverter.raw],
[109, ‘distance’, tuya.valueConverter.divideBy100],
[110, ‘fading_time’, tuya.valueConverter.divideBy10],
[107, ‘far_detection’, tuya.valueConverter.divideBy100],
[108, ‘near_detection’, tuya.valueConverter.divideBy100],
[111, ‘detection_delay’, tuya.valueConverter.divideBy10],

A big thanks in advance! You’re the best!

Currently, I am not adding similar devices anymore.
Instead, I am guiding those interested to add by themselves.
Or simply use the new device referencing to the similar one.

2 Likes