I wanted to ask if you could change the Temp readings from the Enviro+ with a raspi Zero W to remove the rapsi temp spreading to the Enviro Temp sensor ?
i love your project and using it to track the weather outside only the temps that are read from the Enviro are not accurate as the rapsi is producing a bit of heat that is given to the sensor of the enviro.
if there is a fix already in place could you point me to that ?
Thank you for this project (as this is the only one that is also fancy on a screen :))
as a small addition pimorino itself works with this:
Tuning factor for compensation. Decrease this number to adjust the
temperature down, and increase to adjust up
factor = 2.25
thats from there examples coming with the enviro+ installation under raspbian
Hi @sirbondness and welcome to our forums! Are you running the balenaSense project?
Hi there, thanks for using the project, weâre glad that you like it!
The project supports offsetting of the measured values before they are recorded in the database. To offset temperature, add a balenaCloud environment variable called BALENASENSE_TEMP_OFFSET , and add an offset in degrees C. Hopefully this will allow you to tune your setup to take the Pi temperature into account.
Let us know if this would be of help, thanks.
Heya 
yeah i did that, i just thought this could get into consideration as mostly the enviro+ is used as a PHAT so i was wondering if this could be implemented in the python from the start, as you anyway have a own python script for the enviro+
Thanks for this great project anyway
me againâŚi just facing a bigger concerning problem right now. If i should open a new thread, please let me knowâŚ
when i first deploy the balena-sense repo as descripted in your blog post here:
it works perfectly and flawless until i reboot, after a reboot the containers not coming up anymore and the supervisor is not able to start anymore.
Apr 23 09:12:27 90cb70b avahi-daemon[820]: Registering new address record for fe80::e844:bff:fe32:2c7f on veth2800dbc..
Apr 23 09:12:27 90cb70b NetworkManager[829]: [1587633147.9688] device (veth0f15937): carrier: link connected
Apr 23 09:12:29 90cb70b avahi-daemon[820]: Joining mDNS multicast group on interface veth0f15937.IPv6 with address fe80::3409:e9ff:fe99:f6d1.
Apr 23 09:12:29 90cb70b avahi-daemon[820]: New relevant interface veth0f15937.IPv6 for mDNS.
Apr 23 09:12:29 90cb70b avahi-daemon[820]: Registering new address record for fe80::3409:e9ff:fe99:f6d1 on veth0f15937..
Apr 23 09:12:32 90cb70b systemd[1]: resin-supervisor.service: Start-pre operation timed out. Terminating.
Apr 23 09:12:32 90cb70b systemd[1]: resin-supervisor.service: Control process exited, code=killed, status=15/TERM
Apr 23 09:12:32 90cb70b resin-supervisor[8361]: activating
Apr 23 09:12:32 90cb70b systemd[1]: resin-supervisor.service: Control process exited, code=exited, status=3/NOTIMPLEMENTED
Apr 23 09:12:32 90cb70b systemd[1]: resin-supervisor.service: Failed with result âtimeoutâ.
Apr 23 09:12:32 90cb70b systemd[1]: Failed to start Balena supervisor.
Apr 23 09:12:32 90cb70b systemd[1]: balena.service: Start operation timed out. Terminating.
Apr 23 09:12:32 90cb70b balenad[7625]: time=â2020-04-23T09:12:32.944253882Zâ level=info msg=âProcessing signal âterminatedââ
Apr 23 09:12:34 90cb70b kernel: eth0: renamed from veth34366cc
Apr 23 09:12:35 90cb70b kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth66b01c3: link becomes ready
Apr 23 09:12:35 90cb70b kernel: br-3812f8442a5a: port 7(veth66b01c3) entered blocking state
Apr 23 09:12:35 90cb70b kernel: br-3812f8442a5a: port 7(veth66b01c3) entered forwarding state
Apr 23 09:12:35 90cb70b NetworkManager[829]: [1587633155.1265] device (veth66b01c3): carrier: link connected
Apr 23 09:12:36 90cb70b avahi-daemon[820]: Joining mDNS multicast group on interface veth66b01c3.IPv6 with address fe80::e8ee:31ff:fe49:7fe4.
Apr 23 09:12:36 90cb70b avahi-daemon[820]: New relevant interface veth66b01c3.IPv6 for mDNS.
Apr 23 09:12:36 90cb70b avahi-daemon[820]: Registering new address record for fe80::e8ee:31ff:fe49:7fe4 on veth66b01c3.*.
it goes in a loop were it tries to restart the services over and over again. I also tried to first stop the services and reboot afterwards, still the same problem.
iam running this on a raspi Zero W with a Enviro+
any idea what could cause this ?
Hello again, has anything at all changed in your setup before the reboot?
Have you tried power cycling the device? If it is still unstable let us know and we can investigate further, thanks.
nothing changed, fresh deploy first restart, the problem appears.
power cycling doesnt help, after fresh deployment , stopping services and reboot same issue.
only on first deployment all is working as expectedâŚmhhh only thing i changed is the password for the grafana login on the webinterfaceâŚi will try without changing it and restart and let you know.
ok so even on a fresh install, no changes done before a reboot and it doesnt come back on anymore, the pi itself is reachable, only the services doesnt start anymore
root@d953477:~# journalctl -xe
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3269 (balena-engine-c) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3277 (balena-engine-c) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3298 (balena-engine-c) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3343 (balena-engine-c) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3698 (balena-engine-r) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3701 (balena-engine-r) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3704 (balena-engine-r) in control group while starting unit. Ignorin>
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3743 (balena-engine) in control group while starting unit. Ignoring.
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3744 (balena-engine) in control group while starting unit. Ignoring.
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 23 12:41:02 d953477 systemd[1]: balena.service: Found left-over process 3745 (balena-engine) in control group while starting unit. Ignoring.
Apr 23 12:41:02 d953477 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Hi there, can you please try running diagnostics on the device? From the device page, you can go to the âDiagnosticsâ side menu, and run the checks from there. Also, can you please share the OS and supervisor version? Thanks!
Heya
sure !
SuperVisor Version is 10.8.0
OS Version is: balenaOS 2.48.0+rev1
I think weâll need to do further investigation, can you please enable support access and share the device UUID with us? You can send it to me in a private message, and Iâll check it out.
Hi,
I think I managed to fix up your device. I canât say for sure but it looks like some bad interaction with the container runtime⌠what worries me is that it reads like you managed to reproduce this multiple times with a cleanly flashed device.
I am continuing to monitor the device until all services are running again.
It all looks good now. If you could power-cycle the device again to see whatâs going to happen that would be much appreciated.
will do ! will let you know
a powercycle brings the same problem back :-/
To reiterate you get this every time after a clean flash > power cycle ?
correct and it doesnt matter what kind of reboot (power cycle, stop services, use the reboot button or the shutdown) evrytime the system comes back up it cant start the services anymore.
