Thanks for the help.
I have checked and both user and root crontab have the line - (since it was suggested)
* * * * * ping -c2 192.168.1.1
but I have now (today) changed it to full path of ping just to be certain as in
* * * * * /usr/bin/ping -c2 192.168.1.1
======
but am I missing something - surely the WiFi power saving should NOT kick in in the middle of TWO active ssh sessions, regardless of what is or is not in crontab?
Question - does the two Arduinos regularly requesting access via WiFi act as the same keep alive requests?
Question - the two Arduinos only request access to record any change in any of three sensors = equals a gap in access times. Should they request access after every reading and the Pi just throw away repeating values, just to keep the WiFi alive?
Question - Should I get my 4B to ping the CM4 every minute as well, just to keep its WiFi from power saving?
Question - Should any of this be necessary?
Many thanks in Advance
Steve
I have checked and both user and root crontab have the line - (since it was suggested)
* * * * * ping -c2 192.168.1.1
but I have now (today) changed it to full path of ping just to be certain as in
* * * * * /usr/bin/ping -c2 192.168.1.1
======
but am I missing something - surely the WiFi power saving should NOT kick in in the middle of TWO active ssh sessions, regardless of what is or is not in crontab?
Question - does the two Arduinos regularly requesting access via WiFi act as the same keep alive requests?
Question - the two Arduinos only request access to record any change in any of three sensors = equals a gap in access times. Should they request access after every reading and the Pi just throw away repeating values, just to keep the WiFi alive?
Question - Should I get my 4B to ping the CM4 every minute as well, just to keep its WiFi from power saving?
Question - Should any of this be necessary?
Many thanks in Advance
Steve
Statistics: Posted by sgreensides — Tue May 07, 2024 6:44 am