Hey! I formatted my rPi and attempted a clean install with the script but It looks like since Python 2.7 went EOL certain packages aren’t installing as the latest versions require the newer python version (mainly the mock package).
I’ve tried installing an older version of mock manually, but it looks like somewhere in the script it calls out to attempt to install the newest, which gives an error and the installer will not continue. Any advice on how to edit the script to install an older mock version?
I deleted /home/kegbot and the previous mypkgs in /home/pi before re-running the script, and got some errors. (So if I need to do something else like reimaging my pi, just let me know)
It looks like there was an error cloning the git, and also locating pycore-flags.txt.
I did notice that, I re-ran the script and it did not give the same error, although I noticed it doesn’t seem to be creating the /home/kegbot folder for some reason.
Did you by any chance delete the whole /home/kegbot folder instead of just everything underneath the folder? I’ve definitely made that mistake before as well!!
That folder is created when the script creates the kegbot user, so what’s likely happening is that the folder doesn’t exist, but the user does, so it skips the creation of the user and that folder.
Two options (option 1 is untested!):
Manually Re-create the /home/kegbot directory (sudo mkdir /home/kegbot). Then set the kegbot user as the owner of that directory (sudo chown kegbot:kegbot /home/kegbot)
Re-flash the Pi with the latest version of Buster and run the install script from scratch
Looks like I’m still having issues, but I think I’m going to try to use a clean image, just to be sure it’s nothing due to my setup.
(Also wondering if it’s something with my network, I may try hard wired first before reimaging_
Yeah looks like a network stability issue. I was able to test my “option 1” solution and it did work, but I think your best bet is to just try to re-flash and do a clean install.
Hard-wire is definitely the way to go if you have access to it!
I redid it with it wired directly to ethernet and the script seemed to have worked fine!
I recently put everything into an enclosure, so I’m assuming the wifi signal must be weak.
Tried that and it is still not working. I don’t know if it is due to most of the programs have been updated and the script has not been updated to match them.
Example: python 2.7 is no longer used it is version 3.8.3.
I’ve tried it using an Jessie but still got the same thing when typing the IP address.
I’ve use stretch and it did the same thing.
I’m lost but have two Pi’s that I can wipe and start fresh. Just wish it would work. Ready to start inviting people over but done want to be that place that runs out of beer when the kegs gets low or just have a boring chalkboard for tap list.
Thanks for all the support. I’m trying to keep the dream alive.
Ps anyone have any Kegbot boards they are willing to sell? I need 4
I’ll have to run through the installer again to see if I can replicate. I’ve seen that page before, usually when I try to connect after a reboot but before the kegbot application has completed its startup.
Definitely a lot of out-of-date stuff in the version installed with my scripts. The devs have been working to move to a more modern solution. It’s fully functional and should work well but I have not integrated some of the features like the Live Pour tracking and RFID in the web browser. Not sure when I’ll be able to work on porting that over.
Check https://github.com/Kegbot/kegberry for the updated scripts that will install the latest version based on Docker and Docker-Compose.
FYI I just ran through a clean install and everything went smooth (3b+ with latest Raspbian Buster OS installed via the new Raspberry Pi Image writer app). I realized the first post in this thread had an outdated link to an install script and the newest one was buried in the responses (OOPS!). I’ve updated the first post with the updated install link and additional info about the real-time node server.
I still think the new Docker-Compose route is the best way to go long-term if I can find some time to actually get back to active coding on this!!
Thanks for all your help. Have 5 taps up and running with rfid working well…
Had some foaming issues Im busy sorting out… Is it possible and where can increase the pour timeout using ur live pour monitoring.
Know it can be done on app,is it possible on kegberry?
Hi, did you by any change manage to find a way around this… Also have node server issues when selecting members only… Changing it back works , but would like to have the Members only ticket.
