THr316D sensor -> eWelink delay in temperature refreshing

[tymczas]

I bought a sonof THR316D sensor to drive a water heater.
But in ewelink refreshing the temperature value works weird,
I added another temperature sensor in the tank placed with the THR316D sensor.
Reading this sensor, I see that the temperature has been changed, but the eWelink app shows something completely different. After opening the app while switching between pages, the temperature refreshes after a while.
I get a notification from ewelink that the status of the THR13D has been changed → ON or OFF, but the temperature displayed in the application is wrong ;((

Any suggestions?

[keithm.thompson]

Mine is the same. I bought it to control pool temperature but find that often the temperature on the display (which is probably accurate) is different to the figure shown on EWeLink (which is up to an hour out of date) and the figure shown in the history is different again… I’m not sure if EWeLink can make accurate switching decisions if it’s data is inaccurate. I’d love to hear if someone has a solution.

[tymczas]

Hi, i think switching works correct just sending data to cloud is working weird. Im now in contact with Ewelink support - we will see.

[keithm.thompson]

Please let me know if you get any useful feedback. It seems crazy to have to go to the actual sensor to get an up to date reading.

[keithm.thompson]

I finally seem to have this fixed - Sonoff sent me a different temperature sensor - WTS01. Now the temperature displays correctly on both the THR and on EWeLink and there is no delay in the EWeLink reading.

[tymczas]

Ok thanks. In my case i had too build my own to put in boiler do i will stay with some delays :).

[sdspecy]

After almost a year the same issue still exists!! PS: switching to a differnet sensor type is not a solution, its just a workaround!
PPS: Im surely not buying any additional Sonoff device untill (if) such basic issues are not being sorted out!

[michael.jacobs]

Same issue here.
I’ve recently purchased my THR320D.
The display of the device marks 21,5° Celsius, however the web display and API accessed via Node-RED both indicate 21,3°. This difference of 0,2° doesn’t disappear after multiple hours. Accessing the device via the Android app, seem to initiate sync between device temp and the web temp.
I’m on Firmware version :1.2.0
An update on this ?
Any workaround to force the synchronization via web ?

[michael.jacobs]

Follow-up on above.

I’m working on NodeRed-InfluxDB-Grafana system to keep track on the pool water temperature when the filtration is active.

Please find more details of my issue illustrated via attached screenshots :

1. Screenshot 2024-10-07 :

• at 13:51:37 shows temperature 17;2° on the Grafana dashboard

• FYI : the temperature is pulled every 2 minutes via “Edit temperature Node” from device “1002181f6f”.

• at the same time, the device displays 17,4° ! (no picture available)

2. Screenshot 2024-10-07 :

• a few seconds later, at 13:52:31, we can still see the same temperature of 17,2° on the EweLink Web screen

• at the same time, the device still displays 17,4° ! (no picture available)

3. Screenshot_20241007

• A few seconds later, at 13:53:01, on my eWeLink Android screen, I can see a 0,2° higher temperature of 17,4° .

• Remark : This increase of 0,2° of the water temperature in only a few seconds, is surely incorrect.

• at the same time, the device still displays 17,4°.

4. Screenshot 2024-10-07 :

• a few seconds later, at 13:53:19, we can suddenly see 17,4° on the EweLink Web screen too.

• Remark : Also, this increase of 0,2° in only a few seconds on the EweLink Web screen is surely incorrect.

• at the same time, the device still displays 17,4°.

5. Screenshot 2024-10-07 :

• Then at 13:55:11, 17;4° is finally displayed on the Grafana dashboard too,

• at the same time, the device still displays 17,4°.

Issue :

1. Why do I need to open the eWeLink Android screen to synchronize the actual device temperature with the EweLink Web screen (the Grafana dashboard too) ?

2. How I can make sure the EweLink Web screen (the Grafana dashboard) synchronize with the device permanently, without having to always open the Android app ?

[ward]

Hey

Thanks for the feedback. The differences were due to the way devices report data to the cloud. For devices like THR320D, they typically only report data when a specific threshold is exceeded to avoid overwhelming your network.

When you open the app and navigate to its device page, the devices will be “activated” and send live data, which is why you notice the difference and synchronization issues.

eWeLink WEB and CAST also support this mechanism, but we need to add support one by one. For the device you mentioned, it’s planned.

[michael.jacobs]

Thanks for this crystal clear explanation. This threshold rule confirms my assumptions.
Any date when this change will be applied to THR320D ?
Will the nodes from the “node-red-contrib-ewelink 2.0.0” like the “Edit Temperature Node” also benefit from this “eWeLink WEB” mechanism improvement ?

[ward]

@michael.jacobs

Any date when this change will be applied to THR320D ?

It will be a change made on eWeLink platforms - WEB and CAST to cater to the device’s mechanism. For firmware side, you can consult SONOFF team.

[michael.jacobs]

OK, yet another example of a big discrepancy of 0,4° Celsius between the Android app screen and the web screen.

[michael.jacobs]

Finally, the eWeLink Web got synchronized with the device at around 14:08. This more than one hour later !

And the same for the WEB API, making my Node Red application unreliable, as you can see in below sudden drop of 0,5° Celsius :

[ward]

Hey, thanks for the follow-ups.

I think the main concern here is how 0.2 degrees [tolerance] affects your automations.

And also a friendly remender, most temperture sensors don’t have high accurancy of ± 0.1C. For humidity sensors, ±2% RH is a common.

If we increase the threshold, jumpy readings may cause you more trouble.

[michael.jacobs]

Maybe you’re right with the 0.2 degrees tolerance.
However, after further experimenting, the biggest is issue I still don’t understand the synchronization rule frequency between the device and the web. It seems to be pretty random, sometimes it takes maybe one hour or so. Starting the Android app seem to force this synchronization, but one can not expect to open and close the app all day long. So all together, not very reliable system until now. Looking forward to a few updates from Sonoff side to make this all more reliable.