DDF Update for the Owon THS317-ET

[Smanar]

It seem this device have 2 version, one using the endpoint 0x01 and one other using the endpoint 0x03
So this DDF use the 0x00 endpoint to autoselect the only one available and make bind/report on both.

Some correction to the DDF too, battery and timer.

See #5738 (comment)

IDK if this method is better than using 2 DDF with a Endpoint check ?

[OUARZA]

Good morning,
I have the THS317-ET.
I modified the DDF with the one found here #5738 (comment)
The temperature rises, but not the battery for example.
I also find that the refresh rate is very fast.
Can you help me ?
Thanks in advance.
Mathieu

{
"30": {
"config": {
"battery": 0,
"offset": 0,
"on": true,
"reachable": true
},
"etag": "9643748979f077503c9579d491108b93",
"lastannounced": null,
"lastseen": "2023-10-30T21:07Z",
"manufacturername": "OWON",
"modelid": "THS317-ET",
"name": "Temperature 30",
"state": {
"lastupdated": "2023-10-30T20:54:12.122",
"temperature": 3300
},
"type": "ZHATemperature",
"uniqueid": "3c:6a:2c:ff:fe:d3:ad:79-01-0402"
}
}

[Smanar]

Hello

"uniqueid": "3c:6a:2c:ff:fe:d3:ad:79-01-0402"

So your device have only endpoint 0x01 ?
On your DDF you have only "src.ep": 1 and "ep": 1, ?
The battery can take 24h to appear if the report is not working (it will use the poll)

For refresh rate you are speaking about temperature ?
Setting are

        {
          "at": "0x0000",
          "dt": "0x29",
          "min": 60,
          "max": 300,
          "change": "0x00000014"
        }

min : minimum delay between report
max max delay without report
change : the minimal change needed to trigger a report

As the device is a slepper, better to re-include it for deconz reconfigure it, else need to awake it.

[OUARZA]

Hello @Smanar,
The battery actually went back up this morning.
Regarding the values, are they seconds? Milliseconds?
And for 0x00000014 what does that mean exactly? Is the change happening every 0.2°C?
Mathieu

[Smanar]

Value are seconds.
It's a device configuration, deconz configure a report on the device with this part for battery

    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 60,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },

And if the report don't work, deconz use a poll

"refresh.interval": 86400,

So your device probably have problem with the normal report and deconz have used the 24h poll.

And for 0x00000014 what does that mean exactly? Is the change happening every 0.2°C?

Exactly

[OUARZA]

Hello,
Here is my DDF, is it compliant?

THS317-ET_temperature_sensor2.json.txt

Mathieu

[Smanar]

It works for you ?

It is full configured for endpoint 0x01, so no problem
But

          "min": 7200,
          "max": 7200,

You are using same value for min and max ? not realy usefull, if the min is fine for you, can use bigger for max.
And some devices don't support all values, thoses ones seem good for me.

[OUARZA]

Hello,
yes it seems to work.
The temperature rises well, the battery does too but I don't have the control.
Why doesn't native DDF work?
Is it possible to have a DDF that works with all the information?
Do you need information to be able to do this?

[Smanar]

but I don't have the control.

Me too ^^, at every versions, it works for somes users, but never all.

Why doesn't native DDF work?
Is it possible to have a DDF that works with all the information?

Good question, I m comparing the 2 DDFs

• The native one have status "Silver", so it can be just ignored on some config
• The native one, use "ep": 0, for deconz use the defaut one (0x01 or 0x03), and there bind for both clusters at bottom
• On the native one, the uuid is only with 0x03, in my mind it's only cometic, but perhaps no.
• And ofc you are using other min/max/change.

On my side I haven't all possibles clones of this device to checks all possible DDF, and honnestly IDK what is the missing "thing" on the native one.

[OUARZA]

Hello,
When I said "but I don't have the control." This is because I don't have the battery control in my equipment (see screenshot).

Concerning the native DDF, I had upgraded it to GOLD. After restarting DECONZ, I still did not have the information.

I manually added the command to get the battery.

If necessary, I remain at your disposal.

[Smanar]

The battery actually went back up this morning.

What are you calling the "battery control" ? The battery is working or not ? Because I m seing config/battery = 100 on your 3 th capture (or you mean in "commande" on your 2 nd capture ?)
On the native DDF you miss only the battery too ? the temperature was fine ?

[OUARZA]

In JEEDOM, I added the command concerning the battery.
I feel like everything is working properly now.

[Smanar]

Ha yep, sorry, I know jeedom devs have stopped working on the deconz plugin since long time.