Indi-AllSky System 'up time'?

[ldb20151]

Does the pi OS or Indi-Allsky track system 'up time'? Is there a way to extract that information?

Im trying to track down the source of my system lock up issue, which so far involves many hours of running the system at temperature -- mostly unattended. I'm looking for a way to monitor how long the system is up before it is recycled by me and/or stops responding. I do have the watch dog timer working but for some reason, the system becomes inaccessible -- if its still running I can't tell because SSH, the camera web interface and hardwired console will not respond. So, knowing the system operation time would give me insight into what's happening when I can't get in.

v/r,
-Larry

[aaronwmorris]

The uptime is available on the System page, on the System entry (line 2) in the center.

[ldb20151]

Thank you—looked right past it!Is this parameter stored anywhere I could retrieve it? I appears to reset each time I boot. When the system locks up I can’t use any interface until I reboot.  Was hoping it was stored and could be retrieved. LarrySent from Larry's iPhoneOn Nov 7, 2025, at 17:14, Aaron W Morris ***@***.***> wrote: The uptime is available on the System page, on the System entry (line 2) in the center. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[aaronwmorris]

You should check the auto-connect retries on your wireless connection.

nmcli con show "Connection Name" | grep connection.autoconnect.retries

-1 means auto connect up to 4 times, 0 should mean reconnect forever. You can alter it with

nmcli con mod "Connection Name" connection.autoconnect.retries 0

[aaronwmorris]

You should also probably ensure powersave is disabled on the wifi connection.

nmcli con show "Connection Name" | grep 802-11-wireless.powersave

# 2 means disabled
nmcli con mod "Connection Name" 802-11-wireless.powersave 2

[ldb20151]

I get #0 vs a #2. I thought I had disabled power save -- chatgpt says 0=full performance; no power saving features enabled.
Am I missing something? I'm using a pi 5; perhaps a pi 4 is different?

nmcli con show "my connection's name" | grep 802-11-wireless.powersave
802-11-wireless.powersave: 0 (default)

[jimmauck]

I believe 802-11-wireless.powersave = 0 means default (inherit) global setting, which could inherit power save as enabled.

Setting 802-11-wireless.powersave 2 explicitly disables power save on this interface.

[ldb20151]

That makes sense. ChatGPT is often wrong.🫤I finally figured out that I failed to setup the script to configure power conditions on reboot. I had power saving disabled but it reset on reboot, which I didn’t notice. I believe I have it corrected so it’ll boot to power save =2. I’ll monitor it for a while and if all looks good I’ll reinstall outside. Thx!LarrySent from Larry's iPhoneOn Nov 9, 2025, at 16:09, JimMauck ***@***.***> wrote: I believe 802-11-wireless.powersave = 0 means default (inherit) global setting, which could inherit power save as enabled. Setting 802-11-wireless.powersave 2 explicitly disables power save on this interface. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[jimmauck]

Good plan. Like I said, I had a similar issue, I.E., Wi-Fi dropping out. I diagnosed it by checking system logs after rebooting to gain access. I could see the system was running fine during the "outage" but apparently the Wi-Fi was out. Next, I connected keyboard/monitor and diagnosed when the condition occurred that wlan on the Pi indicated it was connected to the AP, but nothing was returned from the network, no ping or arping returns.

[ldb20151]

After your note I checked my Ubiquity AP logs—All my APs are Ubiquity nanos.  They all showed very frequent pi disconnects— hundreds yesterday.  Ubiquity APs apparently have a well known (to all be me) issue connecting, or staying connected with raspberry pi’s —they don’t like frequent disconnects caused by power management system.  I’m baffled at this since the symptoms (lock outs) became a big issue fairly recently. Though as I look back I do see occasional lockups last year. It didn’t occur to me then to be a WiFi issue. I never checked the Ubiquity logs. I don’t understand the details behind the problem but so far, the solution to disable all power saving features is a ready fix. The real energy reqmt differences looks small to me. If not, I could run a network line to my camera to bypass the WiFi disconnects. Right now, if WiFi works I’ll stick with it. Larry Sent from Larry's iPhoneOn Nov 9, 2025, at 17:26, JimMauck ***@***.***> wrote: Good plan. Like I said, I had a similar issue, I.E., Wi-Fi dropping out. I diagnosed it by checking system logs after rebooting to gain access. I could see the system was running fine during the "outage" but apparently the Wi-Fi was out. Next, I connected keyboard/monitor and diagnosed when the condition occurred that wlan on the Pi indicated it was connected to the AP, but nothing was returned from the network, no ping or arping returns. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[bvalente22]

>>Ubiquity APs apparently have a well known (to all be me) issue

connecting, or staying connected with raspberry pi’s That wasn't known to me either as I have a ubiquity setup with all nano APs. I checked my unifi logs and I don't really see that, I have three rpis running, two of them indi-allsky. I'll have to keep an eye out for this

…

On Sun, Nov 9, 2025 at 2:53 PM ldb20151 ***@***.***> wrote: After your note I checked my Ubiquity AP logs—All my APs are Ubiquity nanos. They all showed very frequent pi disconnects— hundreds yesterday. Ubiquity APs apparently have a well known (to all be me) issue connecting, or staying connected with raspberry pi’s —they don’t like frequent disconnects caused by power management system. I’m baffled at this since the symptoms (lock outs) became a big issue fairly recently. Though as I look back I do see occasional lockups last year. It didn’t occur to me then to be a WiFi issue. I never checked the Ubiquity logs. I don’t understand the details behind the problem but so far, the solution to disable all power saving features is a ready fix. The real energy reqmt differences looks small to me. If not, I could run a network line to my camera to bypass the WiFi disconnects. Right now, if WiFi works I’ll stick with it. Larry Sent from Larry's iPhoneOn Nov 9, 2025, at 17:26, JimMauck ***@***.***> wrote: Good plan. Like I said, I had a similar issue, I.E., Wi-Fi dropping out. I diagnosed it by checking system logs after rebooting to gain access. I could see the system was running fine during the "outage" but apparently the Wi-Fi was out. Next, I connected keyboard/monitor and diagnosed when the condition occurred that wlan on the Pi indicated it was connected to the AP, but nothing was returned from the network, no ping or arping returns. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#2501 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD66374YSLZLDVK7WHIRTYT337AVRAVCNFSM6AAAAACLOOC6NCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJRHAZDQNI> . You are receiving this because you are subscribed to this thread.Message ID: <aaronwmorris/indi-allsky/repo-discussions/2501/comments/14918285@ github.com>

-- Brian Brian Valente astronomy portfolio https://www.astrobin.com/users/bvalente/

[ldb20151]

I’m a newby when it comes to the pi. Only been working with them for a little over a year, so I should say there are issues based on my research—mostly online. So maybe take with a grain of salt. It might be caused by my failure to set things up correctly. I have definitely seen disconnects and occasions where the AP won’t recognize the pi client as being connected at all. Also have seen the pi connect but only at a low 5.5mb rate, which is not good. Copilot and ChatGPT show lots of similar issues being discussed by other users. I’m sure user mileage will vary. :)LarryOn Nov 9, 2025, at 21:07, bvalente22 ***@***.***> wrote:

>>Ubiquity APs apparently have a well known (to all be me) issue

connecting, or staying connected with raspberry pi’s That wasn't known to me either as I have a ubiquity setup with all nano APs. I checked my unifi logs and I don't really see that, I have three rpis running, two of them indi-allsky. I'll have to keep an eye out for this

…

On Sun, Nov 9, 2025 at 2:53 PM ldb20151 ***@***.***> wrote: After your note I checked my Ubiquity AP logs—All my APs are Ubiquity nanos. They all showed very frequent pi disconnects— hundreds yesterday. Ubiquity APs apparently have a well known (to all be me) issue connecting, or staying connected with raspberry pi’s —they don’t like frequent disconnects caused by power management system. I’m baffled at this since the symptoms (lock outs) became a big issue fairly recently. Though as I look back I do see occasional lockups last year. It didn’t occur to me then to be a WiFi issue. I never checked the Ubiquity logs. I don’t understand the details behind the problem but so far, the solution to disable all power saving features is a ready fix. The real energy reqmt differences looks small to me. If not, I could run a network line to my camera to bypass the WiFi disconnects. Right now, if WiFi works I’ll stick with it. Larry Sent from Larry's iPhoneOn Nov 9, 2025, at 17:26, JimMauck ***@***.***> wrote: Good plan. Like I said, I had a similar issue, I.E., Wi-Fi dropping out. I diagnosed it by checking system logs after rebooting to gain access. I could see the system was running fine during the "outage" but apparently the Wi-Fi was out. Next, I connected keyboard/monitor and diagnosed when the condition occurred that wlan on the Pi indicated it was connected to the AP, but nothing was returned from the network, no ping or arping returns. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#2501 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD66374YSLZLDVK7WHIRTYT337AVRAVCNFSM6AAAAACLOOC6NCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJRHAZDQNI> . You are receiving this because you are subscribed to this thread.Message ID: <aaronwmorris/indi-allsky/repo-discussions/2501/comments/14918285@ github.com>

-- Brian Brian Valente astronomy portfolio https://www.astrobin.com/users/bvalente/ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[aaronwmorris]

I have merged #2507 which allows you to change the powersave setting of wifi connections directly in the indi-allsky web interface.

[ldb20151]

Thank you. I’ll do an upgrade. Larry Sent from Larry's iPhoneOn Nov 10, 2025, at 15:29, Aaron W Morris ***@***.***> wrote: I have merged #2507 which allows you to change the powersave setting of wifi connections directly in the indi-allsky web interface. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>