Tuya TS0201/TS0601 combined temp./hum. sensor - how to increase update frequency?

[7wells]

Hello!

I have nine Tuya TS0201/TS0601 combined temp./hum. sensors, and some of them do not seem to update often enough. There are:

1x TS0601 (manufacturer: _TZE200_vs0skpuc)
8x TS0201 (manufacturer: _TZ3000_fllyghyj)

I see sensors that updated 5 minutes ago but also some that updated 1 day ago, 27 minutes ago, 19, 15, or 9 minutes ago.

Is there a default value? If e.g. 30 minutes (a bit too sparse for my taste), what could be the reason that 2 of them show an update of more than 1 day ago? Bad connectivity? (which I doubt, as the network is well spread) All show battery values of 100% (I just installed them).

Can somebody please let me know if/where in deCONZ I can change the update frequency? I understand that a too high value will drain on the battery, but >1 h is just too much. I prefer to get a value every 15 minutes, if that is possible.

Thanks for your help!

Basic:

Identify:

Temperature measurement:

Relative humidity measurement:

Power Configuration:

Tuya specific:

Identify: (appears twice - see above)

Time:

[Smanar]

The _TZE200_vs0skpuc use the tuya cluster, you can do nothing
The _TZ3000_fllyghyj work normaly, setting for reporting are in the DDF

    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0402",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x29",
          "min": 60,
          "max": 300,
          "change": "0x00000064"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0405",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x21",
          "min": 60,
          "max": 300,
          "change": "0x00000064"
        }
      ]
    }

It’s the device that decide reporting according to min/max/change value.

[7wells]

Ah, I see - thanks! So one of my 9 sensors is older/different, and I cannot do much about it. But do I get it right that I can influence the other 8 sensors? I see the same DDT that you posted, but I still do not understand where/what to change (maybe via the GUI cluster info/exec?).

What is the meaning of the min=60 and max=300 intervals and Reportable change=100?

And what is the Interval=86400 s (=24 h) about?

[Smanar]

You are on the “name”: “attr/swversion” attribute, this one is the version, it don’t need fast update (it never change), so there is a “poll” set every 24h.
If you search (it’s not visible where you are seing) there is one too for temperature and humidity, but they are here only for security, the normal way is using the reporting (where values are inferior at refresh.interval).

So yes you can use the GUI, but better to use text editor if you can, sometime the editor make “magic” and change other fields you don’t want.

Min : The minium delay without report
Max: the maximum delay beetween report
Change : the difference value need to trigger a report

With thoses settings , the device need to make a report at every 0.1°C change, at least every 300s and maximum every 60s.

If you change them, the device need to be reconfigured (the config is on the sensor), and as they are lazy device can take so long time, so you can re-include the device, it will be awake and ready to be re-configured.

some that updated 1 day ago

Here I think you have a problem, not possible, battery issue ?
Reporting are not exact, and device can make like they want, but not possible having 24h without report, can take a look on the API with Phoscon/help/API information/sensors.
You will see “lastupdated” and “lastseen” by clusters

[7wells]

Sorry, I’ve not yet managed to look after those renegade sensors. When I know more, I’ll write about it.