[ST Edge] Personal Tuya Devices - Generic EF00 Device

Hey all, I have this presence sensor with illuminance sensor, does anyone have like it?

I cannot manage to set the driver as presence and + illuminance from settings.



See if you have a “rate” option in the configuration of the devices created for humidity and battery

For TZ321C_fkzihax8, these are the DP involved:

                [101, 'entry_sensitivity', tuya.valueConverter.raw],
                [102, 'entry_distance', tuya.valueConverter.divideBy100],
                [103, 'departure_delay', tuya.valueConverter.raw],
                [104, 'entry_filter_time', tuya.valueConverter.divideBy100],
                [105, 'block_time', tuya.valueConverter.divideBy10],
                [107, 'illuminance', tuya.valueConverter.divideBy10],
                [108, 'debug_mode', tuya.valueConverterBasic.lookup({OFF: tuya.enum(0), ON: tuya.enum(1)})],
                [109, 'debug_distance', tuya.valueConverter.divideBy100],
                [110, 'debug_countdown', tuya.valueConverter.raw],
                [
                    111,
                    'scene_preset',
                    tuya.valueConverterBasic.lookup({
                        Custom: tuya.enum(0),
                        Toilet: tuya.enum(1),
                        Kitchen: tuya.enum(2),
                        Hallway: tuya.enum(3),
                        Bedroom: tuya.enum(4),
                        Livingroom: tuya.enum(5),
                        Meetingroom: tuya.enum(6),
                        Default: tuya.enum(7),
                    }),
                ],
                [
                    112,
                    'sensor',
                    tuya.valueConverterBasic.lookup({
                        on: tuya.enum(0),
                        occupied: tuya.enum(1),
                        unoccupied: tuya.enum(2),
                    }),
                ],
                [113, 'cline', tuya.valueConverter.raw],
                [114, 'status_indication', tuya.valueConverterBasic.lookup({OFF: tuya.enum(0), ON: tuya.enum(1)})],
                [115, 'radar_sensitivity', tuya.valueConverter.raw],
                [116, 'shield_range', tuya.valueConverter.divideBy100],
                [117, 'detection_range', tuya.valueConverter.divideBy100],
                [118, 'equipment_status', tuya.valueConverter.raw],
                [119, 'target_distance', tuya.valueConverter.divideBy100],
                [120, 'distance_report_mode', tuya.valueConverterBasic.lookup({Normal: tuya.enum(0), 'Occupancy detection': tuya.enum(1)})],
            ],

I hope this can help you to configure your device setting.

Thanks for your reply, I tried updating the Datapoints but it’s still not working. I am using 112 for presence detection and 107 for illuminance.

Try to create a LOG with CLI. You will some info that might be useful. While creating the log change the illumination and presence. Here are some instructions:



Hi, I am using these nice zigbee soil temperature and humidity meters already for some time. I use the personal tuya devices - main driver. Everything was okay until last Thursday. In the history I noticed something changed (see picture 3) in the morning and since that time temperature is way off with measure over 220°C. It happened at the same time with all these meters. What to do?

@Jonposttib, can you change the temperature rate (factor) in the device setting?
@w35l3y, did you make a change in the driver? I know that you don’t have a hub.

@nayelyz did you change something in the software or firmware that prevent rate function to work?

@w35l3y I didn’t change anything in the driver. And yes I use the aeotec hub.

@dotan_shai no I think I can’t. Added a pic of the settings menu

@nayelyz I didnt change anything in the software or firmware. Something happened on its own.

It was modified for the last time in December 19th, 2023.

This lead to something in ST Firmware or Software. @nayelyz can you please check in your side why Rate definition is no longer works ?

Rate is related to the manufacturer chosen.
As it is defined as “Auto”, try forcing a different one other than _TZE200_myd45weu.

Hi, @w35l3y

Which is the thing that isn’t working? As you’re the developer, I need more details on how the “Rate” works on the backend to see what could be causing the issue, please :smiley:

It is selected based on the manufacturer chosen in the settings.
Different manufacturers use different rates to represent floating numbers.

I don’t remember exactly how the driver handle when manufacturer “Auto” is selected, but I carefully will read the code and explain later today.

When manufacturer “Auto” is selected in the settings, the driver uses the models loaded in cache to determine which one to use as similar device.

Basically, it loops through the models loaded in cache and returns the first model found that matches the condition.

Probably, the device was working based on the situation of the cache at that moment. Then, the cache was cleaned for some reason (hub restart maybe?) and then the cache was loaded in a different order the second time.
To make sure, we would need to know what model the driver was expecting/simulating the first time.

My best advice would be to avoid using manufacturer “Auto” and select an option whenever possible.
When a different manufacturer is selected, it is loaded in the cache.
That is the reason why I asked him to select a different manufacturer.

I tried changing manufacters, but that doesn’t help.

The effect isn’t immediate.
You probably didn’t give enough time to the device report a new temperature after changing the manufacturer.

  • _TZE200_locansqn
  • _TZE200_whkgqxse
  • _TZE200_znbl8dj5

Any of these manufacturers should work for your case.

You are totally right. It took some time. From the manufacturers in the list 3 worked. As shown in the pictures.



All 3 options I informed should work for you, just give a couple of minutes to receive new report.

I don’t recommend using the later 2 options you informed because they also change the rate of humidity and battery, respectively.

Thanks for the help. Somehow _TZE200_yjjdcqsq (1*, 2, 3*) works. The other ones have an influence on the humidity. The DP for humidity is set to 3 and for temperature to 5 as Shai Dotan recommended in the past.

Can you please explain what this numbers and stars mean ?
for example _TZE200_yjjdcqsq (1*, 2, 3*).
Is it?
1, Temperature with star = with rate ?
2, Humidity not star = Without rate ?
3. Battery with star = with rate or another function ?

what the 4 stands for ?

For TZE284_aao3yzhs , which is @Jonposttib device the DP are:

            [3, 'soil_moisture', tuya.valueConverter.raw],
            [5, 'temperature', tuya.valueConverter.divideBy10],
            [9, 'temperature_unit', tuya.valueConverter.temperatureUnit],
            [14, 'battery_state', tuya.valueConverter.batteryState],
            [15, 'battery', tuya.valueConverterBasic.scale(6, 60, 0, 100)],

ok, then it was because the device needed an extra configuration, ok. In case it fails even though the preference is selected correctly and was working well before, we can start an investigation. Thank you for the context, @w35l3y