[PROBLEM] Timeout before AP mode

[robmck]

Is there a way to increase the timeout before a moOde audio device switches into AP mode?

Here's my problem: We sometimes get power outages, and the whole house reboots. The RasPIs reboot very quickly, much faster than the router does, so they can't connect to the router and flip into AP mode. I'd like them to wait a bit more before doing so.

(yes, I know, I could put a UPS on the router and cable modem, but I'd like to find a solution that doesn't require buying something). 

Thanks!

[Tim Curtis]

Menu, Configure, System

Address timeout. Set this to 120 (seconds) and if this is not long enough then increase it to >120 using the command below.

Code:

# Update to > 120
moodeutl -q "update cfg_system set value='180' where param='ipaddr_timeout'"

# Reset to default of 90
moodeutl -q "update cfg_system set value='90' where param='ipaddr_timeout'"

# Print current value
moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"

[robmck]

Thanks, Tim!

[heman22]

Menu, Configure, System

Address timeout. Set this to 120 (seconds) and if this is not long enough then increase it to >120 using the command below.

Code:

# Update to > 120
moodeutl -q "update cfg_system set value='180' where param='ipaddr_timeout'"

# Reset to default of 90
moodeutl -q "update cfg_system set value='90' where param='ipaddr_timeout'"

# Print current value
moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"

Hi @Tim Curtis, thanks for the response. I have used the info you have provided. I'm needing to make it closer to 5 minutes. It takes a while for the firewall, POE switches, and APs to fully boot and assign out IP addresses.

I used the commands above to set to 300, and verified it and it shows 300 using moodeutl, however the webui shows 180 seconds. See output below. How will moOde behave? 

Code:

pi@moode-felicity:~ $ moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"
300

[DRONE7]

Menu, Configure, System

Address timeout. Set this to 120 (seconds) and if this is not long enough then increase it to >120 using the command below.

Code:

# Update to > 120
moodeutl -q "update cfg_system set value='180' where param='ipaddr_timeout'"

# Reset to default of 90
moodeutl -q "update cfg_system set value='90' where param='ipaddr_timeout'"

# Print current value
moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"

Hi @Tim Curtis, thanks for the response. I have used the info you have provided. I'm needing to make it closer to 5 minutes. It takes a while for the firewall, POE switches, and APs to fully boot and assign out IP addresses.

I used the commands above to set to 300, and verified it and it shows 300 using moodeutl, however the webui shows 180 seconds. See output below. How will moOde behave? 

Code:

pi@moode-felicity:~ $ moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"
300

Have you cleared your browser cache and refreshed ? does it still report 180 after ?

[Tim Curtis]

Menu, Configure, System

Address timeout. Set this to 120 (seconds) and if this is not long enough then increase it to >120 using the command below.

Code:

# Update to > 120
moodeutl -q "update cfg_system set value='180' where param='ipaddr_timeout'"

# Reset to default of 90
moodeutl -q "update cfg_system set value='90' where param='ipaddr_timeout'"

# Print current value
moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"

Hi @Tim Curtis, thanks for the response. I have used the info you have provided. I'm needing to make it closer to 5 minutes. It takes a while for the firewall, POE switches, and APs to fully boot and assign out IP addresses.

I used the commands above to set to 300, and verified it and it shows 300 using moodeutl, however the webui shows 180 seconds. See output below. How will moOde behave? 

Code:

pi@moode-felicity:~ $ moodeutl -q "select value from cfg_system where param='ipaddr_timeout'"
300

Its the internal value "ipaddr_timeout" that will be used. The WebUI is displaying a bogus value because there is no coding for a value of 300 in the code behind the dropdown control.

I'll update that control for upcoming ~pre6