Closed jamjamjakjak closed 1 year ago
Do you mean the Pi Zero? The Pico is a microcontroller.
I'm terribly sorry, yes. I'm currently overwhelmed with sickness
Raspberry Pi Zero, please update title or I'll try when I wake up. Zz
Thanks and sorry for the inconvenience
On Thu, 16 Jun 2022, 14:25 Kyle Gabriel, @.***> wrote:
Do you mean the Pi Zero? The Pico is a microcontroller.
— Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/1202#issuecomment-1157161547, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYJ2AVZMJBKHJW5E55HESE3VPKGC5ANCNFSM5Y5HRBNQ . You are receiving this because you authored the thread.Message ID: @.***>
Sorry about the delay.
I finally got into the Zero unit and it seems I hackily modified: nano /usr/lib/influxdb/scripts/influxd-systemd-start.sh
and changed
echo "InfluxDB API unavailable after $attempts attempts..."
sleep 1
to
echo "InfluxDB API unavailable after $attempts attempts..."
sleep 3
Ultimately extending the timeout period to allow its tiny processor to boot the influxdb.
Only other issues is that when processing Function > Conditional Controller you must wait a few minutes for the process to complete, it may seem as if it has hanged, but it is processing and needs its time. Otherwise is very functional.
Hope this helps other users looking to use this unit.
Hello, thanks for fixing the time lapse issue, I forgot to submit my fix. Your notification did remind me of another.
The raspberry pico after a few influxdb entries hangs on boot, you need to increase the timeout within the influxdb startup script. The pico can run this project but needs more time for it's tiny processing power to boot. The frontend comes up, just a DB timing out and restarting loop.
All my units are in production away from me, next time I'll check for the timeout adjustments. It required two edits of variables.
Hope this helps. I use many picos these days as pi is bit expensive with shortages.
Cheers