Hello,
Thank you for this great Plugin, I love Shelly and HASS, so this is realy an incredible added value for me.
It seems that the temperature offset is ignored when you retrieve the temprature of a H&T sensor.
For example, on Shelly web interface I read 17,6掳C, with a Temperature Offset of -3.
In HASS the reported temperature is 20,6掳C.
The temperature Offset is well applied in the Shelly Wbe interface, but it's ignored when parsed to HASS.
Some times I can see the right value showing up a fraction of second, very weird ...
(I tried with the last beta release 0.1.3)
Maybe Shelly report different in REST and CoAP. I saw something about that in an internal group. I will check that but I think it should be fixed in firmware not the plugin.
Maybe Shelly report different in REST and CoAP. I saw something about that in an internal group. I will check that but I think it should be fixed in firmware not the plugin.
I think you are right, I tested a REST call and the temperature value was right.
Any way to disable the CoAP calls until Shelly get it fixed?
Yes but then you will get slow response instead...
The question is if this will be adjusted ever in the FW as it's shown correctly in the app. I have the same issue with the humidity.
What do you mean with slow response?
@drash1, @Baumtreter can you retest with 0.1.6b7 and update to latest firmware 1.5.8 as well ?
Thank you,
Simone
Hi Simone! Thanks for your support. I would try it but it seems that the new firmware isn't rolled out yet here in Germany 馃
Hi Simone! Thanks for your support. I would try it but it seems that the new firmware isn't rolled out yet here in Germany 馃
Are you on current latest and still facing the issue ?
Simone
Yes. 1.5.7 is the latest available Update for the Shelly HT. The issue is from day one.
Hi Simone! Thanks for your support. I would try it but it seems that the new firmware isn't rolled out yet here in Germany 馃
Are you on current latest and still facing the issue ?
Simone
Hello Simone, the last available FW for H&T is 1.5.7. I tried with 0.1.6b9, but the problem still persist.
It should be 20,8掳C

Also I'm not sure what the Device temperature is? I'm not sure it was there before.
It seems that the temperature offset is ignored when you retrieve the temprature of a H&T sensor.
For example, on Shelly web interface I read 17,6掳C, with a Temperature Offset of -3.
In HASS the reported temperature is 20,6掳C.
If avaiable, what says http://x.x.x.x/status ?
Simone
Also here: Thabks for your support.
It says:
{"wifi_sta":{"connected":true,"ssid":"MQTT","ip":"xxxxxxxx","rssi":-53},"cloud":{"enabled":true,"connected":false},"mqtt":{"connected":false},"time":"","serial":1,"has_update":false,"mac":"xxxxxxxxxxx","is_valid":true,"tmp":{"value":21.75,"units":"C","tC":21.75,"tF":71.15, "is_valid":true},"hum":{"value":53.5, "is_valid":true},"bat":{"value":80,"voltage":2.81},"act_reasons":["button"],"connect_retries":0,"update":{"status":"unknown","has_update":false,"new_version":"","old_version":"20191216-090428/v1.5.7@c30657ba"},"ram_total":50600,"ram_free":41212,"fs_size":233681,"fs_free":160640,"uptime":19}
As you can see Humidity is correct at 53.5%
Here is a screenshot from HA which shows that the offset is not transmitted.

@Baumtreter , please post details on Facebook English Group and tag "Dimitar Dimitrov"; this is the only way to get a fix in the firmware.
Thank you,
Simone
Would be appreciate if anyone with the same Issue AND a Facebook Account could do that as I don't have one :)
Would be appreciate if anyone with the same Issue AND a Facebook Account could do that as I don't have one :)
Posted on your behalf.
Simone
You're the best! Thanks a million!
Shelly recognized the issue and

Awesome! Thanks a lot Simone! Will keep you posted as soon the update pops up.
My Shelly app is set to read H&T temperature values in F, but the HA integration seems to assume it's in C, and does the calculation again.
For example:
Please update to firmware 1.6.0 and recheck,
Simone
Hi all, just to inform that after 3 weeks of inactivities on old thread, I'll proceed to close them.
If later one someone verify that the issue is still there, a new issue need to be opened.
Thank you,
Simone
No update for 21 days, closing
Simone
Most helpful comment
Posted on your behalf.
Simone