Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client Timeout not changing #201

Closed
Jchuchla opened this issue Jan 27, 2020 · 3 comments
Closed

Client Timeout not changing #201

Jchuchla opened this issue Jan 27, 2020 · 3 comments

Comments

@Jchuchla
Copy link

In 3.1, i'm trying to edit the client timeout value. It seems that no matter what I change it to, it immediately reverts to 15 when I click the save button.

I'm finding that I can't use the AP fallback feature because my AP takes longer than 15 seconds to boot and when a power failure occurs, it will always fallback to AP mode because it's not waiting long enough for the AP to come online.

@penfold42
Copy link
Contributor

Confirmed bug.

script.js is sending it as a string, not a number.

Can you build from source ?

@Jchuchla
Copy link
Author

I don't have the toolchain setup for it. If you want me to test it here, you can send me an efu. Otherwise I can wait for an update. It's not a show stopper for me at the moment. Just a feature I can't take advantage of.

@penfold42
Copy link
Contributor

Ok.

BTW, If you can set it in the config file and flash it, it should work.
It’s only a bug in the save from webUI.

forkineye added a commit that referenced this issue Feb 4, 2020
Fix #201 send ap_timeout as integer, not string
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants