Newbie help with OWON THS317-ET multi-Sensor

[Mikeyb]

Hi, new to Hubitat in the last 2 weeks, and have run into 1 issue which i'm struggling to resolve.

I have 3 x OWON THS317-ET Multi sensors with external probes, which I plan to use to measure the bath temps and swimming pool.

I went through the usual Zigbee pair process very easily, and configured them as

1. Generic Zigbee Temp and Humidity sensors
2. Set the interval to 10 mins
3. pressed configure and refresh.

now 1 device is feeding data and shows the temp in the dashboard tile I created for it.

the other two do not, and have tried everything including hard resets for them both and reconnecting/setting

The image includes screenshots of the working device details page and the not working device details page, it just does not seem to be showing activity.

Hoping one of the community can point me in the right direction.

Thanks
mike

[Ranchitat]

Welcome to the community!

To post pics you need to go to Hub owners - Hubitat , join the group and then you'll be able to post lots of stuff.

Often with ZigBee devices it's helpful to run the pairing process a second time without actually deleting the device from Hubitat.
Just put both the device and the hub in pairing mode again and let the clock run down.
And also try changing the distance between the device and the hub, some need to be close.

[Mikeyb]

After testing the "working" one in some hot water, it seems that's actually not updating temp based on the probe, but probably the main unit (room temp) as it didn't change temp reading, but it has been changing marginally (in line with room temp).

So i think this is likely needing a specific driver to ensure it uses the probe.

Really not sure where to go from here.

I will give the pairing a shot for the others but probably need to work out the right setup for the first one before i worry about the other two.

Can anyone suggest a solution?

Cheers

[Ranchitat]

Not a solution, but start with a screenshot of the Data Details section (H in linked page) from your device detail page.

Device Detail

Or...
This driver is always worth a shot for those slightly strange temp sensors.

[RELEASE] Tuya Temperature Humidity Illuminance LCD Display with a Clock (w/ healthStatus)

Vote for the Linptech Human Presence Sensor with 24G mmWave Radar in the Product of the Year Elevated by Hubitat in 2023 ! This driver can be installed from Hubitat Package Manager, search for "Tuya Temperature Humidity Illuminance LCD Display with a Clock" or by Tag 'Zigbee'. The latest stable version code is here: https://raw.githubusercontent.com/kkossev/Hubitat/main/Drivers/Tuya%20Temperature%20Humidity%20Illuminance%20LCD%20Display%20with%20a%20Clock/Tuya_Temperature_Humidity_Illuminanc…

[Mikeyb]

[velvetfoot]

Paging @kkossev

[Ranchitat]

endpointld: 01
application: 04
inClusters: 0001,0020,0000,0003,0402
manufacturer: OWON
model: THS317-ET
outClusters: 0003

That all looks pretty normal...

All three sensors are showing the same?

[Mikeyb]

I added the driver you linked and here are the screenshots.

Its showing the stats in the tile but does not appear to be actually updating data. Its sat at 22.8C and 100% and does not change. (Same as it was doing with the generic driver).

[kkossev]

Hi @Mikeyb , welcome to Hubitat community forum!

This device is rather not standard, that's why the existing drivers will not show any readings from it.
Please do the following :

• Delete the device from its web page (the 'REMOVE DEVICE' red button at the bottom of the page).
• Start the pairing procedure as a new Zigbee device.
• When the device is found, Do not enter the device name immediately!. You will see a hyperlink or button labeled 'Device Info' or something like that. Click on it.
• Copy and paste all the information in that popup window. It should be like this (link)

Based on this extended information available only during the pairing as a new device process, a modification of a custom driver will be needed to support it in Hubitat.

[Mikeyb]

Thats super helpful.

Once done, how do i go about customizing the driver?

Thank you, what a super community.

[Mikeyb]

This is what it shows "pairing info" link.

[kkossev]

@Mikeyb it seems that there are two variants of this device that have different firmware and behave differently.. : (

Plese update the driver to version 1.3.8 2023/08/10 2:23 PM from this link.
Then click on the Initialize button, next press F5 to refresh the browser if on a PC.
The State Variables 'modelGroup' should now show 'OWON'.

If the temperature from the external probe is still not shown, I will need the debug logs that follow clicking on the Initialize button. Or even better, the debug logs that follow immediately the paring of the device to HE (just pair it again, no need to delete it before).

[Mikeyb]

@kkossev I'm struggling to find out how to update using the link, could you outline the steps i need to take to update to 1.3.8 as your mentioned?

thanks
Mike

[kkossev]

Look at the screenshot from in this post on using the Import button within Hubitat Driver Code editor.

[Mikeyb]

@kkossev thank you so much, these are now working perfectly, reading the temp every 10 seconds from the probe, and showing battery life too.

[christian.busch]

HI,

Just got the device as well but having trouble initializing.
Followed the steps above with driver version ver. 1.3.10 2023-10-23 kkossev

After initialize & refresh it says:

Current States

• _info : installed

State Variables

• lastTx : {"cfgFailure":false,"cfgTimer":0,"humiCfg":"-1,-1,-1","humiCfgOK":false,"tempCfg":"-1,-1,-1","tempCfgOK":false}
• modelGroup : OWON
• lastRx : {"tempTime":1699634976560,"humiTime":1699634976560,"tempCfg":"-1,-1,-1","humiCfg":"-1,-1,-1"}
• stats : {"date":"2023-11-10","rejoins":0,"rxCtr":0,"txCtr":7}
• driverVersion : 1.3.10 2023/10/23 5:57 PM
• notPresentCounter : 0
• configState : 0

Shouldn't it list temp, hum, in the current States?

Log

ev:44392023-11-10 08:54:16.673trace00 owon sendZigbeeCommands(cmd=[he raw 0x42F3 1 0x01 0x0001 {10 00 00 21 00}, delay 200, he raw 0x42F3 1 0x01 0x0402 {10 00 00 00 00}, delay 200, he raw 0x42F3 1 0x01 0x0405 {10 00 00 00 00}, delay 200])

dev:44392023-11-10 08:54:06.189info00 owon Initialization finished version=1.3.10 (Timestamp: 2023/10/23 5:57 PM)

dev:44392023-11-10 08:54:06.186info00 owon manufacturer = OWON ModelGroup = OWON

dev:44392023-11-10 08:54:04.270trace00 owon sendZigbeeCommands(cmd=[zdo bind 0x42F3 0x01 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x03 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x03 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, he cr 0x42F3 0x01 1 33 32 60 3600 {01} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, he cr 0x42F3 0x01 1026 0 41 60 300 {3200} {}, delay 200, he raw 0x42F3 1 0x01 0x0001 {10 00 08 00 2100}, delay 250, he raw 0x42F3 1 0x01 0x0402 {10 00 08 00 0000}, delay 250])

dev:44392023-11-10 08:54:04.257info00 owon initializeDevice...

dev:44392023-11-10 08:54:04.254info00 owon Debug logging will be turned off after 24 hours

dev:44392023-11-10 08:54:04.218info00 owon Debug logging is true; Description text logging is true

dev:44392023-11-10 08:54:04.213info00 owon Updating 00 owon (Device) model THS317-ET manufacturer OWON modelGroupPreference = Auto detect (OWON)

dev:44392023-11-10 08:54:03.089trace00 owon sendZigbeeCommands(cmd=[he raw 0x42F3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x42F3 0x01 0x0000 0xFFDE 0x20 {13} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x03 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x03 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0001 {3C6A2CFFFED3AC64} {}, delay 200, he cr 0x42F3 0x01 1 33 32 60 3600 {01} {}, delay 200, zdo bind 0x42F3 0x01 0x01 0x0402 {3C6A2CFFFED3AC64} {}, delay 200, he cr 0x42F3 0x01 1026 0 41 60 300 {3200} {}, delay 200, he raw 0x42F3 1 0x01 0x0001 {10 00 08 00 2100}, delay 250, he raw 0x42F3 1 0x01 0x0402 {10 00 08 00 0000}, delay 250])

dev:44392023-11-10 08:54:03.077info00 owon initializeDevice...

dev:44392023-11-10 08:54:03.065info00 owon configure()..

dev:44392023-11-10 08:54:02.955info00 owon Statistics were reset. Press F5 to refresh the device page

dev:44392023-11-10 08:54:02.952info00 owon InitializeVars()... fullInit = true

dev:44392023-11-10 08:54:02.942info00 owon installed()...

dev:44392023-11-10 08:54:02.837info00 owon Statistics were reset. Press F5 to refresh the device page

dev:44392023-11-10 08:54:02.832info00 owon InitializeVars()... fullInit = true

dev:44392023-11-10 08:54:02.799info00 owon Initialize()...

[kkossev]

"rxCtr:0" means that nothing is received from this device - the pairing was unsuccessful.

Try pairing it again, very close to your hub (is it C-8 or other model?)
Also, press the F5 on the PC browser to refresh the State Variables when looking again at the stats - these are not refreshed automatically.