Possible to get BalenaSense to display temp in Fahrenheit?

Hey @chrisism so I have been looking into that device and it seems like the container engine is in a pretty corrupted state and looks as though some unclean shutdown got the container store in a weird state. I think I will try reproduce this on my side on a rpi0 as this seems particularly nasty and I would like the engine guys to have a reproducible scenario to look into.

Does it always correct itself after a reboot?

Oh additionally what kind of SD card are you using with the pi zero, often times these types of issues manifest on old or cheap SD cards and are a nightmare to root cause.

Thanks @shaunmulligan, very much appreciated. It never corrects after a reboot. Only way to get it to work again is to reflash the card.

I’m using a 16Gb SanDisk Ultra Extreme.

Okay that should be very good and its the same one I am running on my balena-sense. Thanks for the additional info, I will try reproduce this and figure if we can get a fix for this.

Much appreciated, @shaunmulligan. In the interim, I’d like to reflash the card so I can collect some data

yup no problem, I am fairly certain I should be able to reproduce this locally, so no problemo

1 Like

just an update from my side, i managed to reproduce this on my rpi0, looks like there is a problem with the engine that this project seems to trigger on the rpi0. On monday I will get the engine engineers to take a look at my device and hopefully we can root cause it.

That worked perfectly, @phil-d-wilson. Many thanks for the assist!

–Chris

Thank you, @shaunmulligan!

Here’s a little more from the last crash after moving device to another locale in home:

=============================================================
Welcome to balenaOS

root@56ca97f:~# journalctl -b -a -f -u resin-supervisor
– Logs begin at Fri 2020-01-31 15:19:42 UTC. –
May 23 19:01:18 56ca97f resin-supervisor[18754]: activating
May 23 19:01:18 56ca97f systemd[1]: resin-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
May 23 19:01:18 56ca97f systemd[1]: resin-supervisor.service: Failed with result ‘timeout’.
May 23 19:01:18 56ca97f systemd[1]: Failed to start Balena supervisor.
May 23 19:03:28 56ca97f systemd[1]: resin-supervisor.service: Start-pre operation timed out. Terminating.
May 23 19:03:28 56ca97f systemd[1]: resin-supervisor.service: Control process exited, code=killed, status=15/TERM
May 23 19:03:29 56ca97f resin-supervisor[19743]: deactivating
May 23 19:03:29 56ca97f systemd[1]: resin-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
May 23 19:03:29 56ca97f systemd[1]: resin-supervisor.service: Failed with result ‘timeout’.
May 23 19:03:29 56ca97f systemd[1]: Failed to start Balena supervisor.

I have this exact same issue with my balena sense installation. It just stops working and the supervisor is stuck in a failed to start state, even without a pi reboot or shutdown. The only way I have found to fix this is to re-image the SD Card and redeploy the application

1 Like

It’s crazy. I’ve stopped rebuilding and left my instance in a failed state. As indicated above, the good folks at balena should be looking into this after the weekend. I’m reading that others, too, are experiencing same.

Hi, we’ll be looking at this issue during this week and let you know the results.

1 Like

@karaxuna Thank you… Very much appreciated.

Hi @shaunmulligan -

Any traction on this issue?

–Thanks / Chris

copy: @karaxuna

Hi,

Our engineers are still looking into this issue. Thanks for your patience.

John

Thanks @jtonello. Much appreciated.

Has their been a resolution to this issue as I had the same problem as @chrisism, or are the engineers still looking into it?
See: Air Quality Monitor Problem #RPizero #BME280
Cheers.

Hi @roj, our engineers are still working on that.
Thanks for bearing with us.

1 Like