Kegberry not recognizing authentication through android tablet

This is probably not be because of it running on a raspberry pi, but wanted to include the info just in case.

I currently have kegbot installed and running on a Rasberry Pi. I also have the kegbot android app running, with it set to connect to a server. I used the link provided during setup of the app, and it is able to communicate with the kegbot server (images, kegs, volumes, etc show on the tablet). When I select a tap, and authenticate on the tablet, the pour always stays at 0, and the kegbot web interface shows as a guest pour.

Where would be a good place (which logs/etc) to start to troubleshoot this issue?

Server - App version: 2.1.1
Android - App 1.0.0 beta 84
Worker Name Status
[email protected] ok
[email protected] ok

kegbot 3131 0.0 0.6 4608 2916 ? Ss 18:46 0:00 -su -c sleep 10; /home/kegbot/kegbot-server.venv/bin/kegbot run_workers
kegbot 3134 0.0 0.6 4608 2880 ? Ss 18:46 0:00 -su -c sleep 20; /home/kegbot/kegbot-pycore.venv/bin/kegboard_daemon.py
kegbot 3136 0.3 2.5 14432 11372 ? Ss 18:46 0:03 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/gunicorn pykeg.web.wsgi:application --timeout=120 -w 2
kegbot 3150 8.5 7.7 49480 34416 ? S 18:46 1:11 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/gunicorn pykeg.web.wsgi:application --timeout=120 -w 2
kegbot 3152 2.2 6.1 33800 27488 ? S 18:46 0:18 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/kegbot run_workers
kegbot 3166 18.0 2.5 14368 11312 ? S 18:46 2:27 /home/kegbot/kegbot-pycore.venv/bin/python /home/kegbot/kegbot-pycore.venv/bin/kegboard_daemon.py
kegbot 3197 0.0 0.2 1760 1048 ? Ss 18:47 0:00 /bin/sh -c celery -A pykeg worker -l info -Q stats --concurrency=1 --hostname="[email protected]%h"
kegbot 3198 4.9 7.1 39392 32076 ? S 18:47 0:38 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q stats --concurrency=1 [email protected]%h
kegbot 3199 0.0 0.2 1760 1148 ? Ss 18:47 0:00 /bin/sh -c celery -A pykeg beat --pidfile= -l info
kegbot 3200 2.6 6.7 36812 29912 ? S 18:47 0:20 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg beat --pidfile= -l info
kegbot 3201 0.0 0.2 1760 1144 ? Ss 18:47 0:00 /bin/sh -c celery -A pykeg worker -l info -Q default --hostname="[email protected]%h"
kegbot 3202 5.1 7.1 40416 32092 ? R 18:47 0:40 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q default [email protected]%h
kegbot 3277 8.0 7.5 48568 33512 ? S 18:49 0:53 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/gunicorn pykeg.web.wsgi:application --timeout=120 -w 2
kegbot 3278 0.0 6.2 39700 27648 ? S 18:49 0:00 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q default [email protected]%h
kegbot 3279 0.0 6.2 39700 27652 ? S 18:49 0:00 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q default [email protected]%h
kegbot 3280 0.0 6.2 39700 27652 ? S 18:49 0:00 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q default [email protected]%h
kegbot 3281 0.0 6.1 38548 27564 ? S 18:49 0:00 /home/kegbot/kegbot-server.venv/bin/python /home/kegbot/kegbot-server.venv/bin/celery -A pykeg worker -l info -Q stats --concurrency=1 [email protected]%h
root 3335 0.0 0.4 2908 1920 ? S 18:50 0:00 su -l kegbot -c sleep 15; /home/kegbot/kegbot-pycore.venv/bin/kegbot_core.py --flagfile=/home/kegbot/.kegbot/pycore-flags.txt
kegbot 3336 0.0 0.6 4608 2916 ? Ss 18:50 0:00 -su -c sleep 15; /home/kegbot/kegbot-pycore.venv/bin/kegbot_core.py --flagfile=/home/kegbot/.kegbot/pycore-flags.txt
kegbot 3341 3.3 3.2 58268 14480 ? Sl 18:50 0:20 /home/kegbot/kegbot-pycore.venv/bin/python /home/kegbot/kegbot-pycore.venv/bin/kegbot_core.py --flagfile=/home/kegbot/.kegbot/pycore-flags.txt

I have found this to be the best solution to pours not working.

  1. Turn off tablet
  2. Delete taps and meters from the server
  3. Reboot server
  4. Start tablet without keg board(s) connected
  5. Connect kegboard(s)
  6. Kegbot will detect the controller and ask how many meters are controlled.
  7. Select how many it controls
  8. Do a test pour and the tablet should say "kegbot detected activity on @&$&@%#-.flow0 (or flow 2,3,4 depending on the number of meters per board)
  9. Add that tap on the server side and attach the appropriate flow meter to it.
  10. Repeat 8&9 for each tap.

I have to do this whenever I attach my meters from my kegerator to my jockey box.

MyInsanity - I know this is an old thread, but I was wondering if you ever found a resolution to this issue. I’m facing the exact same thing. I’ve tried a rPi B and a rPi 2, the pre-built image, and building from scratch on Raspbian. I’ve also tried 2 different Android devices. Pours do register on the server, but they show 0.0 while pouring and always register as guest. I did try to go through and remove taps and recreate per the instructions in this thread but nothing seems to make a difference.

I wanted to report back that I did figure this out. The issue was setup-related. I had the Arduino connected to the Raspberry Pi via USB and not to the Android tablet directly. As soon as I connected the controller directly to my Nexus with an OTG cable the pours and login information began working successfully and reporting back to my kegberry server!