I found this on internet.
| DP | Description |
|---|---|
| 1 | temperature (celsius, divided by 10) |
| 2 | humidity (%) |
| 3 | battery state (0=low, 1=medium, 2=high) |
| 9 | temperature unit (0=celsius, 1=fahrenheit) |
You may use profile “Temperature & Humidity” without battery.
ST doesn’t have capability for battery state (low, medium, high), only battery level (0-100%)
I could convert battery state as 0=33%, 1=66%, 2=100%, but you wouldn’t get any % other than those 3 values.
What do you mean exactly?
In other words, what exactly did you do with the device and app to reach this assumption?
I need full screenshot of detail view.
Hi,
I mean that it seem the device has been recognised and connect properly but I could not Open or Close the door
Here some screen shots of the details
Thanks for the info?
Could you add the conversion of the values to the driver?
Actually i have a bunch of those so it would je very helpfull to know that the battery is low. ( they are a pain in the ass to pair)
Thanks in advance
Hamza
Did you send the command to open/close the door?
ST only enables the commands from the app when it receives some data from the device.
Hi,
yes, but nothing change.
When i open the device, I have a pup up say “this devices has not yet updated the state information, try later”
But I have assblled the device on a testing evironment since more that 24 hours and nothing changed.
Thanks
Ciao
Hi Wesley,
I do not why, but just now it start working … bah mistery of technology…
Anyhow thaks for your support
Ciao
Hi Wesley,
Another Tuya mmwave presence sensor please.
It already works in Similarity mode for presence and illuminance under the Normal + Illuminance profile if I update the DPs (to 104 and 105), but the rest of the settings don’t work
With a lot of searching and trial + error I figured out the datapoints:
Can you add to the Presence Sensor stock please?
Also any chance of adding DP 109 to the device tile? It reports the actual distance of the target from the sensor in real time (I can see the value ticking up and down when I go to and from the sensor), which is cool I suppose, but no problem if you can’t as I am not sure how I can use it (if at all).
Thanks for a great driver!
This is the exact device requested right above yours.
It already was added.
It should be available in the next 12 hours.
I grabbed the beta driver, but it looks like the presence is not working.
smartthings devices 22
Main Info
─────────────────────────────────────────────────────────
Label Generic EF00 Device
Name generic-ef00-v1
Id 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0
Type ZIGBEE
Manufacturer Code _TZE204_sxm7l9xa
Location Id xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Room Id d797666a-23a3-4b28-983d-ce43f511e9c2
Profile Id 261bcb8c-c43b-3e81-a2f3-6b3c90f0b23e
Capabilities presenceSensor
illuminanceMeasurement
valleyboard16460.settings
signalStrength
refresh
valleyboard16460.debug
─────────────────────────────────────────────────────────
Device Integration Info (from zigbee)
──────────────────────────────────────────────────────────
Eui A4C138A2B6C6F610
Network Id 3FD5
Driver Id 585328e6-ac85-4ac5-bce4-286efd0ab980
Executing Locally true
Hub Id 7824742b-0d42-4b87-bfdb-25fa57db978c
Provisioning State DRIVER_SWITCH
──────────────────────────────────────────────────────────
I pulled the driver logs… Not sure if they are any help.
2023-05-26T01:30:58.301378330+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T01:30:58.302039953+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T01:30:59.867815033+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -57, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x09, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x0051 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T01:30:59.891596626+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T01:30:59.911973101+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T01:30:59.918850079+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T01:30:59.920701338+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T01:30:59.923055098+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T01:31:01.481046830+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -57, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x0A, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x0052 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T01:31:01.491177601+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T01:31:01.495211575+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T01:31:01.500703070+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T01:31:01.501181017+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T01:31:01.501848767+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
Happy to provide any debug info.
Thanks…
Just in case the beta had not update I also installed it locally.
Here are more logs:
2023-05-26T02:11:11.530811414+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 5 110 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:11.531657914+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -110
2023-05-26T02:11:11.532340747+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:11.536844164+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x89, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00BF (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T02:11:11.546990414+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:11.548036706+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T02:11:11.562151706+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:11.566076497+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T02:11:11.566726706+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:11.573562789+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8A, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C0 (BE), < DatapointSegment || dpid: 0x69, DatapointSegmentType: Enum, length: 0x0001 (BE), value: 0x00 > > > >
2023-05-26T02:11:11.577062831+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:11.578086789+00:00 INFO Personal Tuya Devices - beta Default datapoint 105 0
2023-05-26T02:11:11.587184956+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> emitting event: {“attribute_id”:“presence”,“capability_id”:“presenceSensor”,“component_id”:“main”,“state”:{“value”:“not present”}}
2023-05-26T02:11:11.593621289+00:00 INFO Personal Tuya Devices - beta Additional event… 1 105 contactSensor
2023-05-26T02:11:11.602139914+00:00 WARN Personal Tuya Devices - beta Attempted to generate event for 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0.main but it does not support capability Contact Sensor
2023-05-26T02:11:11.602896039+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 1 105 nil false Attempted to generate event for 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0.main but it does not support capability Contact Sensor
2023-05-26T02:11:11.603657164+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -105
2023-05-26T02:11:11.604302914+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:12.137201581+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8B, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C1 (BE), < DatapointSegment || dpid: 0x68, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x0000001C (BE) > > > >
2023-05-26T02:11:12.146925956+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:12.147900789+00:00 INFO Personal Tuya Devices - beta Default datapoint 104 0
2023-05-26T02:11:12.152972622+00:00 INFO Personal Tuya Devices - beta Too quick! Do nothing. 104 28 1685067072 1685067062 12.0 10
2023-05-26T02:11:12.154632914+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -104
2023-05-26T02:11:12.156272664+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:12.740650914+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8C, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C2 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T02:11:12.750597622+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:12.754635247+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T02:11:12.760143164+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:12.760615414+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T02:11:12.761292706+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:14.340701789+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8D, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C3 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T02:11:14.349024748+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:14.349995039+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T02:11:14.358008748+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:14.358479248+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T02:11:14.359161748+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:15.937632623+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8E, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C4 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T02:11:16.001814956+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:16.002791414+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T02:11:16.029066831+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:16.036235998+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T02:11:16.040021373+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
2023-05-26T02:11:17.546959331+00:00 INFO Personal Tuya Devices - beta <ZigbeeDevice: 119e096d-e0b2-4f11-ac86-f3dbdb42b5c0 [0x3FD5] (Generic EF00 Device)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3FD5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0xFF, rssi: -41, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x8F, ZCLCommandId: 0x02 >, < DataReportClient || transid: 0x00C5 (BE), < DatapointSegment || dpid: 0x6D, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x00000000 (BE) > > > >
2023-05-26T02:11:17.556588290+00:00 INFO Personal Tuya Devices - beta Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReportServer
2023-05-26T02:11:17.560470123+00:00 WARN Personal Tuya Devices - beta Datapoint not found. Using default 109 2
2023-05-26T02:11:17.569002623+00:00 WARN Personal Tuya Devices - beta Unexpected component for datapoint 109 109 nil [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’) nil
2023-05-26T02:11:17.570941956+00:00 INFO Personal Tuya Devices - beta Datapoint negative. -109
2023-05-26T02:11:17.574967165+00:00 DEBUG Personal Tuya Devices - beta Generic EF00 Device device thread event handled
Can you confirm whether it is working or not, @skinnypope ?
If you want to know why the device didn’t send enum 1 for DP 105, then I don’t know but I would say 9 seconds of logs isn’t enough to confirm anything.
What I can say is the driver is emitting event as expected for DP 105.
And if you are worried about these warning messages, they also are expected and doesn’t represent a problem in the driver.
It is just warning that the driver tried to emit a event to a inexistent component, but it is only for the settings.
It happens because settings use the exact same capability and they must be in separate components.
DPs 104 and 105 are present in the “main” component.
Yes it is working with your beta driver. Is the main driver updated and should I switch back to double check?
Yes, switch back to the main and remove the beta.
Otherwise, you may pair a new device and be recognized by the beta version first.
You don’t need to double check as the code is exactly the same at the moment. Thanks.
All done, and working well
Hi @w35l3y , I think there is a display anomaly with the device card for the presence sensor.
I have my settings set thus:
With 0 Detection Delay, Near Detection at 0 and Far Detection at 25 (it detects whether I am sitting at my desk up to 2.5m away from the sensor).
On the device card itself, it shows:
The figures it shows here do not match what is in the Settings.
It does appear to work appropriately according to the Settings, though.
Thank you again for all your work.
It doesn’t match and it won’t either.
ST doesn’t allow changing settings programmatically.
With that said, I just can’t sync the values presented in the detail view and settings.
So don’t bother trying to understand what is happening with it.
This use case is the reason why I decided not to include settings to other devices anymore.
Ok, thanks Wesley. Good to know.
Could the following device be added?
It’s the outdoor motion sensor of philips hue with lux and temperature options. The previous driver stopped functioning unfortunately. (Constantly goes offline)
I checked the list of devices on this driver…presense sensors are there, but motion sensors are not in the list.
