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

new pi 4 and 2023 version #378

Open
Canook2000 opened this issue Jan 9, 2024 · 15 comments
Open

new pi 4 and 2023 version #378

Canook2000 opened this issue Jan 9, 2024 · 15 comments

Comments

@Canook2000
Copy link

I was not getting pi to connect to my network and did not see picobrew. I downloaded the 2023 lite version and now I see the picobrew network, but it is still not connecting to my home network even though I did change the ssid and password to my 2.4 network. Can I can the setup from the picobrew network....if so, how do i sign in ...I am attempting to use Putty

thanx, Peter Curtin [email protected]

@tmack8001
Copy link
Collaborator

Login for the device unless modified in either the initial boot file or post installation is the default username:password combination for raspbian OS.

@tmack8001
Copy link
Collaborator

Likely what is happening is we need to base the image off of the newer raspbian builds that have support for the newer silicon firmware.

I just received my RPi 5 dev device to do additional testing on related to firmware modifications.

@tmack8001
Copy link
Collaborator

Check one of these builds which were one of our together for another individual https://drive.google.com/drive/folders/1pxt0ivVPzOXRseO6Lk39lHK9z2dJJBu3?usp=drive_link

I haven't had time to test these fully myself.

There will be 4 different ones. 2 will be "lite" (latest and stable - relating to the wifi firmware to use) - these variants are headless meaning no desktop experience, just terminal output
2 will be "full" (same latest and stable) and these will have a more desktop experience included

@Canook2000
Copy link
Author

Canook2000 commented Jan 10, 2024 via email

@Canook2000
Copy link
Author

Canook2000 commented Jan 12, 2024 via email

@tmack8001
Copy link
Collaborator

The GUI is web based. The Pi hosts a python+flask webserver and uses nginx as a way to provide self signed certificates and run on both http and https depending on the interface used by the Pico device.

https://trevor-mack.com/picobrew-raspberrypi-setup/ has most of the setup instructions as well as the Release Notes on GitHub here.

Basically you connect the Pico device to the PICOBREW network and setup recipe instructions on the web interface defaulted exposed at http://raspberrypi/ (some networks you need to access the IP address of the Pi as some residential routers block local domain resolution by hostname as this can often times be insecure access patterns attempted by attackers.

@Canook2000
Copy link
Author

Canook2000 commented Jan 13, 2024 via email

@tmack8001
Copy link
Collaborator

There are some sample base style recipes to reference in the help section.

Though as far as the pi experience it was purely developed to be simple and purely to control the Pico device vs craft recipes directly.

I also have a free to use crafter hosted online that is specifically targeting Pico device efficiencies at crafter.pilotbatchbrewing.com that has one way syncing to our rPi solution you can use to populate the machine instructions into the 'recipe library', but for me I typically have 1-2 mash schedules and adhoc set up to the maybe 5-7 hopping schedules making for only 15-18 unique "recipes" that I've used to brew 100s of batches of beer over the years.

@Canook2000
Copy link
Author

Canook2000 commented Jan 13, 2024 via email

@tmack8001
Copy link
Collaborator

The RPi doesn't support importing xml, only the JSON format that the RPi server is built on which isn't a common beer recipe format.

However... My BrewCrafter website linked earlier will import and scale a beerxml for the Pico machines (or should, let me know if you have issues with that).

Then when your desired beerxml is uploaded to BrewCrafter you can sync it to the RPi (needs to be network local to your device browsing BrewCrafter since I use local JavaScript ajax queries to get it over - unless you put your RPi on a public IP address or a VPN tunnel or something of that sort... ).

Really the RPi recipe interface just controls time at temperature of the machine and doesn't care one bit about ingredients... So if you use BrewFather or just source kits, create a new recipe in the RPi interface and set up the "machine instructions" accordingly for the mash and hopping/boil schedule you desire for that session. It really doesn't have to be complicated.

Default new recipe is even good enough for a large number of styles (as long as you change the hop schedule appropriate to what you are brewing).

Screenshot_20240113-221643.png

@Canook2000
Copy link
Author

Canook2000 commented Feb 3, 2024 via email

@Canook2000
Copy link
Author

Canook2000 commented Feb 3, 2024 via email

@Canook2000
Copy link
Author

Canook2000 commented Feb 5, 2024 via email

@Canook2000
Copy link
Author

Canook2000 commented Feb 8, 2024 via email

@tmack8001
Copy link
Collaborator

Awesome, glad you have cracked the nut.

BrewCrafter2 syncing to RPi only works 1) with the client device (browser) on the same network as the RPi (or at least available to access the FQDN of where the webserver of the RPi is hosted) and 2) if using the out of the box installation as you are, you will need to explicitly accept the "unsecure / self-signed ssl certificates" as trusted to allow your browser to communicate to it form the BrewCrafter2 website.

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