[BUG] strange behavior with S4H module when lost power on the device and re power

[Cippo2019]

• ShellyForHASS release with the issue: 1.0.1 (and also early version)
• Last working ShellyForHASS release (if known): ...
• Home Assistant 2022.8.7 Supervisor 2022.08.5 Operating System 8.5 Frontend 20220802.0 - latest

Hello, first of all sorry for my bad English and thanks a lot for your incredible work ! I appreciate it. I noticed that, unlike what a reboot is commanded from the web interface, if the current fails or you detach/attach the device shelly EM or shelly1 with the temperature probes, very high absorption values is read or very high temperatures. You can reproduct also if you detach and retach the device from power. This is not happen when you reboot via web interface or android app. And, on android app the value reported are normal , whitout any big value. Normal state.

Obviously this creates confusion on the HA statistic. I think that is we can set/correct into the S4H ?

here a picture to better understand

Thanks in advance :-) Tz

[auanasgheps]

I think this issue is similar to mine #724 When something weird happens and the sensor resets, instead of providing a "unavailable value" the sensor provides a wrong value.

[Cippo2019]

Hi all

any news on that ?

i try to explaine again (sorry for my bad English)

I noticed that, unlike what a reboot is commanded from the web interface, if the current fails or you detach/attach the device shelly EM or shelly1 with the temperature probes, very high absorption values is read or very high temperatures. You can reproduct also if you detach and retach the device from power. This is not happen when you reboot via web interface or android app. And, on android app the value reported are normal , whitout any big value. Normal state. Obviously this creates confusion on the HA statistic. I think this is coming from s4h. Have any of you noticed the same thing ? Or do you know how we can exclude that value to be collected by HA ? Thanks in advance