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.

Hey @johnnyruz ,
I've had kegtab up and running for a couple of months now and all seems to be going well.
The one issue I have is that the interface doesn't emphasize claiming the pour.
So I'm getting lots of pours registering as 'guest' because people forget or miss it or click 'done pouring' before claiming it by mistake.
I've even done it a few times myself!

The current interface:

My 2 minute mspaint sugestion -

Any thoughts?

Currently when running the app in local storage mode you're only able to assign 2 flow meters (kegboard.flow0 - pin 2, and kegboard.flow1 - pin 3) to taps.
Flow meters attached to pin 20/21 (kegboard.flow2 and flow3) are detected by kegtab app but cannot be assigned to a tap - the drop down menu does not display them as an option to select.
Arduino Mega with CH340 chip.

When configured with more than one tap, the other tap always start as hidden on the Kegbot App. Whenever the tablet is restarted or kegbot-android crashes (rarely), the additional taps have to manually be made visible again.

Kegbot#99

Had a quick look through the code, it appears that the 'ON/OFF' toggle for each tap is not saved into preferences currently. Is this something you'd be willing to add to the KegBot android app in your fork?