Repository navigation
DDF for OWON THS317-ET Multisensor (temp probe support) - #5777
Conversation
This is a DDF I created for this sensor with the help of @Smanar and @Mimiix. It actually works pretty well for reading the temperature cluster, the battery and the sw version, but this sensor is supposed to report humidity and is also a PIR sensor. As you can see on the screenshots provided in issue #5738 it probably lack some cluster for these other features to be supported by deCONZ so if someone have a sniffer and this device, feel free to contribute to make other commands usable. As requested the DDF has been set up to Bronze status.
|
Hmmm think I messed up when I wanted to rename PR #5676 and then I tried to delete it as it was named patch-1 by default. Do I have to open a new one or it's ok as we can still see the file here |
|
IDK, we can't found the branch Stim04:ddf_for_OWON_THS317-ET but the PR look valid. |
|
yes I deleted the patch-1 branch because after I renamed it ddf_for_OWON_THS317-ET it automatically closed PR #5776. That's what I should not have done I think, as it also seems to have deleted this branch in repository |
|
Don't worry, if it don't work, someone will react here. |
|
All right thanks. Also not sure how to link this to issue 5738, the commands from the help section don't seem to work in preview mode. Probably only authorized people like you can do it |
|
Done. |
|
Hi so I guess this one can be merged or does another PR need to be merged first? |
|
For me you can merge it. https://www.zigbee2mqtt.io/devices/THS317-ET.html And they are no more usable cluster, so can be a firmware/hardware issue too. |
|
Hello, probably need to use one of the OWON gateways to be able to use all functions. |
|
Yep lol, what does mean "optionnal" for them ? I don't think you can add sensors the to device ? |
|
I have no idea but according to the pdf everything is "optional" even the temp probe.. so I guess you could buy a multisensor that does... Zigbee only with no sensors at all, which is interesting. |
|
@Smanar |
|
Hello @Smanar , Unfortunately I have bad news about this device (mine is still working fine with february beta firmware.. i'm not home so no updates). Concerning the difficulty to pair it to the Conbee 2 I think we narrowed the problem pretty well and the only solution that seems to work in case battery or temperature isn't showing correctly on Phoscon is to reset it and pair it again, as many times as it takes to make it report everything correctly. Sometimes it takes up to an hour or more to make everything readable when you pair it. However, I have at least two persons on the Jeedom forums that have a totally different problem that we could not solve. Their device is constantly reporting every 3 seconds. Battery last only a week due to this behaviour. Of course they tried to tweak the min max and change values. Any clue? Was their any change on the ddf values format (like the number of zeros in the change 0x0.. values or something similar in latest updates?) |
|
For the pairing issue, prevent the device going to sleep during the inclusion is a good method. But deconz have some watchdog, if the inclusion is not finished (for exemple a binding is not finished) deconz can detect it and retry later, so the device can work itself later (the device is sleeping, so deconz wait for the device is awake to retry to send the request) For the 3s reporting, I m seing the issue on your jeedom forum. But take care if the DDF is not active BEFORE the inclusion, the legacy code can make some config, and later the DDF make another one. On your DDF, the only part that can "hurt my eyes" is the battery binding/reporting. And here can try to increase the mini, but value are standard, it the one used by defaut on deconz. |
|
From my perspective, the reason for such an intense battery drain is that the device gets hammered by battery and temperature reads, due to the configuration. You shouldn't apply read functions without any
|
|
Thanks for your help guys i'm going to let them try those changes.
There is a reset procedure -> Hold button for 10 seconds. |
|
Ok so better to use the full procedure with the reset one. On the Swoop DDF, I think for battery bind, better to use the attribute 0x0021 (battery percentage) as it's the one you use on the DDF above. And can add the To try to force a poll every hour if reporting is not working. |
|
yea I get it. One of them already saw my message and is trying your changes. About the refresh interval I'm going to write a little something to make sure they try this. PS: one thing I did not understand is the min 1 sec on the temperature reading on @SwoopX 's DDF. |
|
Please stop fiddling around with reads and refresh intervals for battery powered sensor nodes, as this can horribly go wrong as you already experienced, unless you know wxactly what you're doing. The legacy device code NEVER polls any data from battery powered devices. From my experience, there's only very rare cases where you actually need to deviate from the above. Min 1 is: fire the temperature report instantly, when the temp changes +/- 0.5. With 60, it waits 1 minute. It's just more crisp. |
|
As i can't try myself the changes (very far from home until august) we will have to wait for the feedbacks from the people that have the problem. Both of them read my message about your suggestions on Jeedom forums. |
|
Someone know waht is the status for this device ? |
|
Hey, |
|
Lol. Someone with battery issue have tried the Swoops DDF ? #5777 (comment) To check if it's better ? |
|
Oh I'm sorry but I didn't express myself well enough. Mine is out of order. I was saying that considering the jeedom post they can manage to read the temperature fine but some have battery issue and/or refresh rate issue (too fast, like every second or so). I read some of them tried the Swoop DDF but with no change on battery and/or refresh rate. Mine was working perfectly until dog and water came in the equation. |
|
I m sorry but I can do nothing for your dog ^^ Link on jeedom forum https://community.jeedom.com/t/owon-ths317-et-avec-deconz-appairage-non-visible-dans-jeedom/81301 I have read the link (fastly) and I don't understand how it can work on some users and not others .... No sures all are using the same one. |
|
Hi all, Sorry to unearth this topic, but i still don't manage to make this device work. Any idea on what to do next ? |
|
Next here > #5738 |

This is a DDF I created for this sensor with the help of @Smanar and @Mimiix. It actually works pretty well for reading the temperature cluster, the battery and the sw version, but this sensor is supposed to report humidity and is also a PIR sensor.
As you can see on the screenshots provided in issue #5738 it probably lack some cluster for these other features to be supported by deCONZ so if someone have a sniffer and this device, feel free to contribute to make other commands usable.
As requested the DDF has been set up to Bronze status.