Wait until network is up before assuming a board is new

[zylantha]

Kegbot starts very early in the Android boot process, well before wifi is up and running.

This results in kegbot thinking that its existing keyboards are ‘new’ and unrecognised every boot - because there is no network up to connect to the database to check this.

If kegbot is configured with a remote server, and wifi is not yet up and running, kegbot should enter a short loop to wait to see if wifi comes up (say 10s) before proceeding.

[johnnyruz]

Hi @zylantha ,
I've just started experimenting with Kegbot and making some small changes so apologies for not fuly understanding the issue. Can you maybe share a little more info about this issue or steps to reproduce it?

I see what you're saying about Kegbot starting up before wifi has a chance to initialize, but I'm not seeing my tablet recognize my Kegboard as 'new', or at least I'm not looking at the right place?

A few details about my setup:

• Acer A210 Tablet
• Arduino Uno "Kegboard" with 2 Adafruit flow meters (I also have a knock-off Arduino Nano which led me to try to get the CH340 driver working)
• Kegberry Server running on Raspberry Pi 3

My Arduino kegboard just has the name of "kegboard" with no serial number, so on my tablet I see flow meters kegboard.flow0 and kegboard.flow1. In the server I just see a single controller named "kegboard" and this hasn't changed over multiple reboots of the tablet.

[zylantha]

Hi mate It could well be (probably is) just the way that my Android device boots up - it's an AOC all-in-one 24-inch touch screen monitor, which has a built-in Android mode that I use. I have two genuine kegboards, which have unique serial numbers (if that matters). I also have Kegbot configured to automatically start whenever these kegboard devices are connected over USB (Android complains bitterly if I don't). However every time I boot the screen, I get the message saying "new board detected" and it asks me how many flow meters are attached - even though these are already configured in the system. If I leave them unplugged when the screen boots, and plug them in after everything is up and running properly (including wifi), then plug them in - everything works fine... hence I realised that it's probably caused by the connection to the backend server not working, because the USB devices are detected - and the app loaded - before Wifi is initialised ... but this may only be reproducible on my system (because of the peculiarities of my setup). I can take a video of the startup if it would help? Unfortunately I know nothing about Android programming - so was hoping this might be something you could easily fix in your fork - maybe to detect if there is no local IP assigned, before attempting to connect to the server, and then just entering a sleep state and waiting - checking regularly for an IP address and only then proceeding? Or maybe bypassing the "do I know about this kegboard already?" check if there is no live connection to the backend? (there must be some form of flag for this in the routines) Thanks for bringing Kegbot back to life :)

…

On 21 December 2017 at 00:36, johnnyruz ***@***.***> wrote: Hi @zylantha <https://github.com/zylantha> , I've just started experimenting with Kegbot and making some small changes so apologies for not fuly understanding the issue. Can you maybe share a little more info about this issue or steps to reproduce it? I see what you're saying about Kegbot starting up before wifi has a chance to initialize, but I'm not seeing my tablet recognize my Kegboard as 'new', or at least I'm not looking at the right place? A few details about my setup: - Acer A210 Tablet - Arduino Uno "Kegboard" with 2 Adafruit flow meters (I also have a knock-off Arduino Nano which led me to try to get the CH340 driver working) - Kegberry Server running on Raspberry Pi 3 My Arduino kegboard just has the name of "kegboard" with no serial number, so on my tablet I see flow meters kegboard.flow0 and kegboard.flow1. In the server I just see a single controller named "kegboard" and this hasn't changed over multiple reboots of the tablet. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHT5Ilo_pMMRLowScw15FcGO33Uc1Gx4ks5tCQ1UgaJpZM4RIUNU> .

[johnnyruz]

Hey, I've just been helping another user and got around to setting up an actual Kegbot Server rather than the Kegberry Server that I've been using (and will probably continue to use as my server for Kegtab). With the standard kegbot server I'm seeing exactly what you're talking about. I can't promise a timeline but I'll take a look at this.

[zylantha]

Great to hear that it's not just me! Thanks for your efforts in bringing Kegbot back to life :)

…

On 5 January 2018 at 06:43, johnnyruz ***@***.***> wrote: Hey, I've just been helping another user and got around to setting up an actual Kegbot Server rather than the Kegberry Server that I've been using (and will probably continue to use as my server for Kegtab). With the standard kegbot server I'm seeing exactly what you're talking about. I can't promise a timeline but I'll take a look at this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHT5It_T_RVz7D3US9iGV1zxntasLoPVks5tHSicgaJpZM4RIUNU> .