Brewzilla G4 wrong hotspot password. Or who needs a malt pipe anyway.

[peterpiper]

Since acquiring my own AIO, rather than borrowing, I've managed a fair number of mistakes, from puddle on floor, due to tap left open when filling, to finding a 1kg bag of grain got missed out.
In this brew, a blackcurrant sour, it was the malt pipe that was missing. Not being spotted, still on bench, till after last bit of grain was gently stirred in.

My only excuse, I was rushing for deadline of brewday visitors arriving, after forgetting the BZ would need wi-fi reconfig (having recently changed ISP).

Followed BZ prompts to connect to wi-fi, but kept getting "wrong password" when trying to connect phone or tablet to BZ hotspot. It was prompting the same old password "8mtqghqe" (which I also had saved in phone, so knew it want a typo error).
After numerous failed attempts, tried "forget wi-fi". Then was prompted to use password "kegland 1", which connected straight away. It appears this an issue with the May software update, so anyone changing wi-fi before fix issued, might find this problem.

Ended up doing mash without malt pipe; recirc started after 20min; sparge as draining, pumping wort into fermenter buckets; emptied and cleaned BZ ready for boil.
It was a bit more work, but method allows you to do a 'floating sparge', sparge water being gradually added to just keep the grain bed covered. A method used in breweries, to give a faster sparge, by avoiding grain bed compaction. It also shows that grain escaping the malt pipe shouldn't cause BZ blockages.

 

[peterpiper]

The GitHub RAPT developers thread, now lists the incorrect password (after update) issue as being in hand.

 

[Twostage]

The GitHub RAPT developers thread, now lists the incorrect password (after update) issue as being in hand.

Gitlab. I made that mistake too.

 

[MashBag]

Am I the only one who doesn't need a password to make beer.

 

[peterpiper]

Gitlab. I made that mistake too.

Quite correct.
Apparantly, one advantage of GitLab over GitHub, is that it offers a comprehensive set of DevOps tools, including integrated pipelines.
Difficult to brew if you've misplaced your pipes, so see BZ including integrated pipelines, as an advantage!

To avoid any software issues at the following brew, earlier this week, I left BZ switched on for an hour the evening before brewday. All looked good. But on brewday, when running in manual as didn't have protein rest profile ready, system repeatedly ran through downloading an update. Which obscured half the display for 5 minutes, then brief message "power off to update", then it starts downloading the update again!
Eventually I had to power off - part way through a brew.
Don't think, these software developers can live in a real world.

 

[Twostage]

Quite correct.
Apparantly, one advantage of GitLab over GitHub, is that it offers a comprehensive set of DevOps tools, including integrated pipelines.
Difficult to brew if you've misplaced your pipes, so see BZ including integrated pipelines, as an advantage!

To avoid any software issues at the following brew, earlier this week, I left BZ switched on for an hour the evening before brewday. All looked good. But on brewday, when running in manual as didn't have protein rest profile ready, system repeatedly ran through downloading an update. Which obscured half the display for 5 minutes, then brief message "power off to update", then it starts downloading the update again!
Eventually I had to power off - part way through a brew.
Don't think, these software developers can live in a real world.

Yes, I had the downloading, need to reboot endless cycle a couple of weeks ago. As I was running in manual mode I could happily just ignore it.

I think you're right about the developers not in the real world. Quite a common thing to throw at developers who never actually use the software they create. Its exasperating sometimes. There should be a QA process, though, that tests these things.