Not getting temperature reading


#1

Last night my HestiaPi lost its WiFi connection, I’m not sure exactly why.
I found the following it the log file.

2020-03-17 23:10:38.883 [ome.event.ItemCommandEvent] - Item ‘Network_WLAN_IP_Topic’ received command 169.254.154.171

Why the IP address has changed from the usual 192.168.. I’m not sure?
Other devices on the network appear to have been unaffected.
Any way, according to the log HestiaPi continued to work just with no WiFi access.
Until this error is logged.

2020-03-18 08:55:24.470 [vent.ItemStateChangedEvent] - MyTemp changed from 19.2 to 19.3
/home/pi/scripts/getBMEtemp.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getBMEtemp.sh: fork: retry: No child processes
/home/pi/scripts/getBMEtemp.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getBMEtemp.sh: fork: retry: No child processes
2020-03-18 08:55:34.914 [vent.ItemStateChangedEvent] - MyTemp changed from 19.3
/home/pi/scripts/getBMEtemp.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getBMEtemp.sh: fork: retry: No child processes
/home/pi/scripts/getBMEtemp.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getBMEtemp.sh: fork: retry: No child processes to 19.3

The script does work a few mins later but over the next hour or so this error is shown more and more frequently until it fails all together and HestiaPi stops controlling the heating as it can’t get a current temperature reading.
The same was happening with all the other scripts as well.
My only access to the system was via the touch screen but as there is nothing on there to reboot the system all that I could do was turn the power off/on.
Its rebooted and is now running ok.
Any ideas what when wrong and how to prevent a re-occurrence?
Some way to reboot the system via the touch screen or automatically via a rule, when things go wrong may be an idea?

Thanks
Liam


#2

Please try this if possible and report back here. We expect all above issues to be related to that.
We are sorry about that.


#3

I was also getting the same errors for scripts that aren’t related to the sensor, would that cause issues with these scripts as well?

/home/pi/scripts/getuseddiskspace.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getcputemperature.sh: fork: retry: Resource temporarily unavailable
/home/pi/scripts/getwifiinfo.sh: fork: retry: Resource temporarily unavailable


#4

A bad solder point can cause unpredictable behaviour to the hardware I believe.