Just wanted to post a thread specifically realted to this feature and issues/suggestions around it.
In general the Co2 pressure features on the F1 need usability improvements in how it is implemented and currently can be used. Right now the F1 pressure control is almost completely missing and is implemented at the most simple level. When working directly on the unit without the APP there is only a single location that pressure can be increased. Once you have unlocked the unit with a master mode card, you go into the Craft section, then Pressuring, then Co2. On this screen it will list a pressure level but NOT the actual pressure level, as the values shown here are currently broken. It will either show 0 or show pressure in the mid to high 20s, regardless of the actual pressure level. In cooling mode, the correct pressure level is shown. On this screen the user can inject mode Co2 by holding down the Long Press button. When Long press is held down this can cause it to update and show the correct pressure level, but it can also just as likely show an incorrect pressure level each time it is pressed. See the below video to see the bug I am talking about:
Besides this being the only location on the unit that pressure can be injected, a completely separate problem is that you have to 100% cancel anything else the unit is actively doing to be able to inject the pressure. So if you are brewing and want more pressure you have to completely stop the brew, navigate to the craft pressure menu, inject more pressure, then go start your brew up brand new. Same if you are Chilling or DIY kombucha. You have to cancel it completely. There needs to be a way to inject pressure regardless of what else the F1 is doing.
That brings us to the APP. In the app is a Toolkits section, that actually has what LOOKS like a more robust pressure control. If you go to the Co2 toolkit it will list the current pressure as bar and it will have a dial you can set to a higher pressure level, so if you are at 1 bar you can raise the dial to 1.5 bar and press the Pumping button to have the unit raise the pressure to that level. The problem is this also is completely broken if the iGulu is doing anything at all. The app will spin and act like it is going to raise the pressure, but the unit will do nothing at all, and the app will just remain in the pumping mode with the button changing to "Stop". The only way to use the toolkit is to go to the F1 unit, STOP whatever it is doing completely, and then go back to the app, and start the pressure change again. If the F1 is doing nothing at all then the feature will work. If it is in the process of anything the app feature just appears to be broken. The app also should list PSI, not bar if you have your F1 set to show PSI.
Sugguestions and bugs:
- The F1 should allow a way to raise pressure no matter what else the unit is doing. Brewing Ale, Chilling, Making Kombucha.
- The F1 pressure under craft should always show the correct pressure level.
- Recipies for master mode should have a pressure option, not just temperature and days. I understand that the F1 as designed cannot lower pressure and only raise it unfortunately due to hardware limitations, but we should still be able to set a minimum pressure level in recipies.
- The App should show F/C, and bar/PSI options as they are configured on the unit.
- Sparkling water option should allow the user to choose the PSI level, as the default that the unit maintains is far too low for sparkling water.
- Any menus that show PSI on the unit should have the ability to increase pressure by holding it down, and not require canceling out of whatever is going on and requiring someone to go into the craft menu.
- The max PSI that the Android app allows should be increased from 2.0 bar/29 PSI to 2.5 Bar/36 PSI.
Overall the biggest two issues are the injecting pressure menu showing bad values, and the unit not letting you increase pressure unless you cancel everything else going on.
For reference purposes I updated my unit with the newest firmware from 8/23/2024. My unit was running 2.5, and after updating to todays build it looks like the new version is also 2.5, but it did go through fine.
