[ST Edge] Personal Tuya Devices - Generic EF00 Device

The idea of the driver is to be generic, so I can reuse the profiles as much as possible.
It would require 2 different profiles to do the exact same thing but in different order.
Your use case is too specific, so I can’t do this.

OK. I understand. Thanks for creating what you have.

@RebelMagpie
You can use this drive’r’s
[ST Edge] vEdge Creator: a virtual device generator for end users - Devices & Integrations / Community Created Device Types - SmartThings Community
temp/humidity device.

In setting is possible to select to dashboard humidity value.

Then you need Rules API rule that copies humidity measurement from real device to virtual device.
Here is link to Rules API rule that is copying Zigbee humidity measurement to virtual temp/humidity device.
Integration Solutions using MQTT - Devices & Integrations - SmartThings Community

Quite complicated but possible

1 Like

Seems i have same thermostat (or very similar) to @Daniel2_Kusterer and have same issue.
Here’s driver log:

Log

2023-03-10T21:59:01.824260687+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T21:59:21.386518030+00:00 PRINT Personal Tuya Devices - main start: 2023-03-09 20:28:55, uptime: 25:30:26, memory: 1183 KB, devices: 1
2023-03-10T21:59:21.387987697+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T21:59:31.834833702+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T21:59:37.033852037+00:00 TRACE Personal Tuya Devices - main Received event with handler zigbee
2023-03-10T21:59:37.035358371+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD741, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x92, rssi: -62, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x26, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, ZCLVersion: 0x03 > > > >
2023-03-10T21:59:37.040817371+00:00 TRACE Personal Tuya Devices - main Found ZigbeeMessageDispatcher handler in personal-tuya-devices → Signal Strength
2023-03-10T21:59:37.045225037+00:00 INFO Personal Tuya Devices - main Executing ZclClusterAttributeValueHandler: cluster: Basic, attribute: ZCLVersion
2023-03-10T21:59:37.052472704+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> emitting event: {“attribute_id”:“rssi”,“capability_id”:“signalStrength”,“component_id”:“main”,“state”:{“value”:-62},“visibility”:{“displayed”:false}}
2023-03-10T21:59:37.073800704+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> emitting event: {“attribute_id”:“lqi”,“capability_id”:“signalStrength”,“component_id”:“main”,“state”:{“value”:146},“visibility”:{“displayed”:false}}
2023-03-10T21:59:37.092324704+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T21:59:45.705636041+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T21:59:45.708342041+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T21:59:45.758207708+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:45.781379042+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:45.782725042+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:45.783913708+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:45.785091375+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00
2023-03-10T21:59:45.787544042+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T21:59:46.597993042+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T21:59:46.603330042+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T21:59:46.680726375+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:46.684561042+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:46.692060709+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:46.692922375+00:00 WARN Personal Tuya Devices - main Similar device not found (parent) normal_thermostat_v1
2023-03-10T21:59:46.695512042+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00
2023-03-10T21:59:46.697661709+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:00:01.844295049+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:00:21.396135059+00:00 PRINT Personal Tuya Devices - main start: 2023-03-09 20:28:55, uptime: 25:31:26, memory: 1182 KB, devices: 1
2023-03-10T22:00:21.401015059+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:00:31.849668397+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:00:40.533412401+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T22:00:40.592362401+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T22:00:40.646422734+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00 → Model
2023-03-10T22:00:40.666945401+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:00:41.383249735+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T22:00:41.384501401+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T22:00:41.399292735+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00 → Model
2023-03-10T22:00:41.474404735+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:01:01.873574411+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:01:10.922010415+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T22:01:10.926465749+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T22:01:10.932052749+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00 → Model
2023-03-10T22:01:10.933280082+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:01:21.405580567+00:00 PRINT Personal Tuya Devices - main start: 2023-03-09 20:28:55, uptime: 25:32:26, memory: 1185 KB, devices: 1
2023-03-10T22:01:21.409361457+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:01:31.874562446+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:02:01.884600351+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:02:13.850732023+00:00 TRACE Personal Tuya Devices - main Received event with handler device_lifecycle
2023-03-10T22:02:13.862012690+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received lifecycle event: infoChanged
2023-03-10T22:02:13.870397690+00:00 TRACE Personal Tuya Devices - main Found DeviceLifecycleDispatcher handler in personal-tuya-devices → GenericEF00 → Model
2023-03-10T22:02:13.873673023+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:02:16.122459357+00:00 TRACE Personal Tuya Devices - main Received event with handler zigbee
2023-03-10T22:02:16.123707024+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD741, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TuyaEF00 >, lqi: 0x8C, rssi: -67, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x27, ZCLCommandId: 0x02 >, < DataReport || seqno: 0x0003 (BE), < DatapointSegment || dpid: 0x67, DatapointSegmentType: Value, length: 0x0004 (BE), value: 0x000000E6 (BE) > > > >
2023-03-10T22:02:16.181154024+00:00 TRACE Personal Tuya Devices - main Found ZigbeeMessageDispatcher handler in personal-tuya-devices → GenericEF00 → Model
2023-03-10T22:02:16.193957357+00:00 INFO Personal Tuya Devices - main Executing ZclClusterCommandHandler: cluster: TuyaEF00, command: DataReport
2023-03-10T22:02:16.195648691+00:00 WARN Personal Tuya Devices - main Simulating device TS0601 _TZE200_4hbx5cvx2023-03-10T22:02:16.196834024+00:00 WARN Personal Tuya Devices - main Datapoint not found. Using default 103
2023-03-10T22:02:16.204764358+00:00 WARN Personal Tuya Devices - main Unexpected component for datapoint 103 103 230 [string “st/device.lua”]:121: attempt to index a nil value (local ‘component’)
2023-03-10T22:02:16.221029691+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:02:21.414675693+00:00 PRINT Personal Tuya Devices - main start: 2023-03-09 20:28:55, uptime: 25:33:26, memory: 1185 KB, devices: 1
2023-03-10T22:02:21.416374027+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:02:31.895689365+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:03:01.893844379+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:03:21.418201055+00:00 PRINT Personal Tuya Devices - main start: 2023-03-09 20:28:55, uptime: 25:34:26, memory: 1185 KB, devices: 1
2023-03-10T22:03:21.422127389+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:03:31.890552727+00:00 DEBUG Personal Tuya Devices - main driver device thread event handled
2023-03-10T22:03:32.902756727+00:00 TRACE Personal Tuya Devices - main Received event with handler capability
2023-03-10T22:03:32.942907394+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2023-03-10T22:03:32.944262061+00:00 TRACE Personal Tuya Devices - main Found CapabilityCommandDispatcher handler in personal-tuya-devices
2023-03-10T22:03:32.945471727+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xD741, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-03-10T22:03:32.949207061+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled
2023-03-10T22:03:36.359892062+00:00 TRACE Personal Tuya Devices - main Received event with handler zigbee
2023-03-10T22:03:36.363190729+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xD741, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x96, rssi: -83, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x37, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, ZCLVersion: 0x03 > > > >
2023-03-10T22:03:36.441546396+00:00 TRACE Personal Tuya Devices - main Found ZigbeeMessageDispatcher handler in personal-tuya-devices → Signal Strength
2023-03-10T22:03:36.442424062+00:00 INFO Personal Tuya Devices - main Executing ZclClusterAttributeValueHandler: cluster: Basic, attribute: ZCLVersion
2023-03-10T22:03:36.444125062+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> emitting event: {“attribute_id”:“rssi”,“capability_id”:“signalStrength”,“component_id”:“main”,“state”:{“value”:-83},“visibility”:{“displayed”:false}}
2023-03-10T22:03:36.455842062+00:00 INFO Personal Tuya Devices - main <ZigbeeDevice: d8223620-075f-4e3a-a481-1a473552ff84 [0xD741] (Grzejnik sypialnia)> emitting event: {“attribute_id”:“lqi”,“capability_id”:“signalStrength”,“component_id”:“main”,“state”:{“value”:150},“visibility”:{“displayed”:false}}
2023-03-10T22:03:36.488068062+00:00 DEBUG Personal Tuya Devices - main Generic EF00 Device device thread event handled

I have an Aeotec Smartthings wall plug which has the same icons available. I see what driver it is using.

Hi!

I have a ZigBee smoke detector from aliexpress.

Something like this altho I couldn’t find the exact one I have.
https://www.aliexpress.com/item/1005004000436532.html
Titled: Tuya Smart Zigbee Smoke Detector Smart Fire Fire Protection Home Security Alarm Work With Tuya Zigbee Hub

When I press the test button on the smoke detector the Datapoint 1 value changes from 1 to 0.
Right now I’m using this datapoint as a contact sensor. So by default, it’s open but when I press the test button on the smoke detector(aka when smoke is detected) it changes the “contact sensor” to a closed state. Now I can run an automation based on this change.

Would be a nice touch to have a “Smoke detector” listed with a nice icon where these datapoints could be punched in. That way when setting up home monitoring I could select it as a device in the correct categorie. But I guess this works well enough for now.

Thanks!

Hi @w35l3y, thank you for adding the mode switch to the irrigation profile. You are doing a fantastic job with this drover.

I have, however, found one minor issue. The main tile shows the mode switch (DP 1), and thinks it’s turning on/off the valve.

image

This valve is off, but has the mode switch set to on. Looking at the tile, you would assume the valve to be open.

The mode switch, while useful for when one wants to set how much water to disperse, isn’t something that would be changed very frequently. I think it makes more sense for the tile to show the valve control (DP 2).

It’s purely a display request. My routines still open and close the valve correctly.

(And thank you for adding the battery level to the soil sensor :+1::+1::+1:)

It seems you haven’t defined DP 103 in the Configuration menu.

Send screenshot of Detail view, Configuration menu and Driver menu.

You will need to figure it out what is the meaning of each datapoint, so I could map them to the right capabilities.
You found the meaning of DP 1, what about the others DPs ?

I will try to reorder capabilities tomorrow, but I am not sure it will work because I remember I read years ago the switch capability takes precedence over other capabilities.

1 Like

I did set it up, that’s why it’s strange.
When using generic driver it was showing DP 103 as the one for temp setpoint.

What is interesting, is that i’m getting this message (“device have not updated all information”), and nothing works, except for main on/off button. I can switch the thermostat on and off using it, and it’s correctly reflected on the device itself.

1 Like

Hi!

Haven’t figured out what the other datapoints are and I don’t think I have the brains to do so. It’s a smoke detector so there’s not that much functionality besides switching states when smoke is detected. Maybe a battery level indicator there somewhere but not really sure how to go about it.

But I found a somewhat good enough solution.

I decided to change the “1” datapoint from contact sensor to generic value to just reflect the number when the state of the smoke detector changes.
Then I created a virtual smoke detector and created routines to trigger its state when the datapoint changes from 1 to 0. This will make the virtual smoke detector trigger and as the virtual smoke detector is as good as a regular smoke detector in the eyes of smartthings it gets picked up by smartthings home monitoring.

Also created a routine where the datapoint changes from 0 to 1 for the virtual smoke detector to get out of the triggered state.

That’s all I need for now but it would be awsome if the virtual devide stepp was cut out as it just creates clutter.

Thanks again!

1 Like

AirBnk M510 zigbee door lock:

I get this when I connect the device to smartthings and use this EF00 driver:

There are no datapoints listed and not really sure how to go about figuring this out but I did start a thread for this device some time ago:

Going back and forth with some nice people the closest I got to some hints about datapoints for this device:

In this protocol we can read that:
#57
Lock motor state
Can be sent and reported
bool
If you want to implement
Alexa or Google voice to open
the door, the dp must be
reported. The dp is of type
bool, true
for unlocking, false to lock.

… not really sure if this helps with anything but maybe it inspires someone to dig into the protocol further and hopefully figure out what numbers to punch where.

Thanks!

1 Like

Datapoints list should update as you trigger the door lock actuators/sensors.
Just let this view open in the app and take note of changes made when you unlock or lock the door lock, for example.

1 Like

This is the same error I get for that thermostat

I was able to find the problem.

Thanks to @Felix2021 that sent the log.

Fix was sent already. :tada:

1 Like

Luckily, the precedence of switch is only for the detail view.
I reordered the capabilities and valve state is in the dashboard now.

1 Like

Now i’m able to see setpoint, but… it’s currently 230 centigrades :slight_smile:
Also lost switch, and still cannot see current temp.

You probably are using the wrong profile.

Tried all of them a guess, at least thermostat profiles.
I’ll check the logs now to see if there’s something relevant.