Pi 4 Model B / Wifi Works, but can't access Server

[rompstar]

so I was reading the other post on the Pi4 Model B (4BG model) not working and I have downloaded the: 2023-08-20-picobrew-pico-lite.img that you posted on your Google drive. It boots and it creates the PICOBREW Wifi and my Z sees it and connects to it.

But I can't seem to connect to the local server to make my edits and upload recipes.

http://192.168.72.1

when I type: sudo network -I

that is the IP address that I see, any recommendations ?

I feel like I am super close :)

Thanks!

[tmack8001]

Try either http://raspberrypi OR connect the device to PICOBREW and try http://192.168.72.1

[chiefwigms]

Also if you can, try to use Ethernet instead of WiFi

[rompstar]

it seems to work now / what do you mean Eithernet over Wifi ? /// connect the Z machine using eithernet to my regular router or directly to the Pi4 ?

what format is supported for Recipe Import ? I have one in .xml format, but its is not able to import it..

thanks!

[tmack8001]

Importing is a proprietary json format.

You can also sync the beerxml file you have via crafter.pilotbatchbrewing.com

Or just create the machine steps as the Pi solution doesn't care about any of the ingredients and was primarily built to support controlling time at temperature of the Picobrew devices, use whatever crafter you want for nailing your ingredients.

[rompstar]

I logged into crafter.pilotbatchbrewing.com // i press sync and nothing happen ? posting screenshots, what am i doing wrong ?

[tmack8001]

You need to add your RaspberryPi ip address to your brew crafter user profile as the red error text says.

On Sat, Jun 15, 2024, 10:59 PM Ray Miecznik @.***> wrote:

I logged into crafter.pilotbacthbrewing.com // i press sync and nothing happen ? posting screenshots, what am i doing wrong ? [image: Uploading Screenshot 2024-06-15 at 7.58.08 PM.png…]

— Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/387#issuecomment-2171024425, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQPAI47CMOGDJXY2ZQLJZLZHT5SRAVCNFSM6AAAAABJMERRNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGAZDINBSGU . You are receiving this because you commented.Message ID: @.***>

[rompstar]

I tried that, now getting a sync error..

just to be clear.. my Z machine is connected over Ethernet to the Pi and that works fine / the Pi is setup for the WiFi too - I am connecting to the PICOBREW using my laptop for the 192.168.72.1 access

i can ping 192.168.72.1 from my laptop fine...

thanks!

[BuckoWA]

Try this - on the same browser you are accessing BrewCrafter2, navigate to the https://raspberrypi (or https://192.168.72.1). Your browser may give you a certificate error. You need to accept the certificate (it is unsigned). Then try syncing the recipe again from BrewCrafter2. This has worked for me in the past.

[rompstar]

that works, it synced them and I see in the Library, thanks!

but I don't see it on the Z machine, does it take a while to sync between the Pi server and the machine ?

[tmack8001]

You may need to toggle the sync setting from within the RaspberryPi hosted website. There is an edge case around syncing from BrewCrafter and having it actively available as "synced" in the cache for the machines to pull down.

[rompstar]

cool, i toggled the synced on the Pi off and ON and now it is synced, thanks for all the help!!!!

[rompstar]

what plans you guys have for this software ? do you know the install base for active users given the company is out ?

for my self, I pickup the Zymantic (had a leak, designed a 3d part and gave back to community https://www.thingiverse.com/thing:6661173), and the Z (new) and the PicoStill (new) for $200 / I used to brew big batches, but am actually looking forward to more variety and smaller batches that are more automated, this way I can brew on weekdays too without putting away a full day to brew beer.

Kind of sad they screwed this up!

Just brewed an English Brown Ale yesterday on the Zymantic and it worked, no leaks, haha!

The Zymantic still works with the mothership, but the Z not anymore, NET errors / so this picobrew git (what name you guys gave this) works perfecto!

[rompstar]

ok so this morning tried to connect using my Z and i get a no internet error.. nothing changed, connected over ethernet to the Pi, all network works...

https://youtube.com/shorts/Hlu9JMDaFDk?si=i5cFu51_bHt2XgJ4

[rompstar]

i disconnected the ethernet between the pi and the Z and connected the Pi to the internet using another ethernet cable, now it connects over Wifi fine, weird behavior ...

[tmack8001]

What you are seeing is the fact that the RaspberryPi supports both 2.4 and 5.0ghz frequencies. Most consumer grade and commercial grade access points (commonly confused as routers, since they are often both a router and an access point in one device) will push clients over to the higher frequency range for speed and reliability 5.0ghz. when this happens the Pi access point (broadcasted as ssid PICOBREW) will become invisible to the Picobrew hardware and no longer be seen since these machines only support 2.4ghz. In Ubuntu (underlying OS of our solution) there isn't a way to announce that 5.0ghz shouldn't be used though the interface we try to prioritize this network by attaching to the explicit essid vs the ssid only.

Anyways long story to try and say "band steering" which is used to optimize your network for speed/reliability causes issues if the client being steered is yet itself hosting an access point unknowingly supporting other single channel devices.

[tmack8001]

what plans you guys have for this software ?

I brew exclusively on Picobrew hardware so as long as I do that... This project will be functioning just fine. As far as "new features" there aren't much that are needed TBH with what has been done already. There is a want I have to opt-in connecting to live data streaming to BrewCrafter which is an always on online product I host again for the community.

do you know the install base for active users given the company is out ?

100-1000s of people are still active using Picobrew devices around the world even in markets Picobrew wasn't operating in.

[rompstar]

cool, thanks for taking time to explain it all, so when is the next Beta coming out ? ;)

[rompstar]

also, the image that i got was from your Google drive, so unless someone reads the prior forums, they won't find it on the .git official links - you planning to make it available for other people so it works on the Pi 4/5 ?

thanks!!

[tmack8001]

Plans to? Yes. Have I tested things on a more recent Pi myself? No. Do I get paid to do this? No.

Thanks for testing and confirming things work.

[rompstar]

well maybe you should get paid ;) thanks for all your help!

[rompstar]

I noticed something with the network problems... First I split out my 2.4 and 5Ghz on my Comcast modem for WiFi, (I don't see how to do this on my NightHawk) and then I made sure the Pi only connected to the 2.4 only over WiFi (updated settings), but that still resulted in the network errors..

the Pi was connected using an ethernet cable to a Hub, and the Hub was connected to my Netgear Nighthawk Wifi router, which was connected to the Comcast modem using ethernet, all cable connections so far.

so: Pi --> HUB --> Nighthawk --> Comcast

so I connected the Pi directly to the Comcast modem using ethernet and the errors went away. Now things work..

so: Pi --> Comcast / Pi Wifi is connected to the 2.4 on the Comcast Modem

Now I get a COLD Sensor error, lol - so I need to figure this out, but at least the Z sees my recipes.

The original Zymantic also works over Wifi, that machine has no errors...

:)

[tmack8001]

Now I get a COLD Sensor error,

This is known to happen when your Picobrew had a power disruption for some reason. Long story short is that there are 2 boilers: BIG and SMALL and when this binary configuration is lost in the firmware it asks the cloud for what it is - the Pi solution doesn't always know, but there is a user accessible "check boiler type" utility buried in the Service Mode (hold down the click wheel when restarting your Z to access this).

[rompstar]

yep, thanks / I joined the FB Group and everyone said the same thing, after that I had a Hot Error 8 followed by 6, I solved that fairly easily and brewed a test batch just using water, all went great!