Search results

1575.25 + 5 gal "Brown Bess" dunkelweizen = 1580.25 gallons.

The target system is an installation of Raspberry Pints on Debian 11 with the option chosen to enable MQTT. What that does behind the scenes I don't know. Based on the log output of Alpha 6, I'm inclined to agree with you. To test, I spun up a Debian 11 VM and followed the instructions you...

Lately by monitoring the serial console--with versions through Alpha 5, there's been no mention of any MQTT activity connected with a pour. Haven't watched it yet under Alpha 6. But the target is pointing to a RaspberryPints installation on Debian 11.

Got it, that works. And yes, it definitely looks more polished than the former /edit/ page. Since I don't recognize the acronym, I'm going to say no. But it sounds like it has something to do with Home Assistant--and while I do use HA, I'm not as yet trying to integrate KegCop with it.

OK, I re-flashed Alpha 6, a few times. First time, I re-joined it to the same SSID/AP I'd been using with it for Alpha 5 and prior. Same result, network was unusable, 75+% packet loss on pings. Re-flashed and joined to a different SSID, one with a closer AP (but with more than one AP on that...

I'll re-flash Alpha 6 and see what happens.

1. It's in the "Home Brewing Beer" section of the forum; there's a separate section for wine, mead, cider, and sake. 2. You don't "brew" any of those things.

I didn't even get to the point of being able to configure one--the only thing that's configured on this unit right now is the WiFi; literally everything else is at defaults.

Network connection on Alpha 6 is unusable--it won't even reliably respond to pings (75+% packet loss). Same SSID/password/AP/locations/everything as had been the case previously--literally nothing has changed except moving from Alpha 5 to Alpha 6. And /edit/, /file/, and /files/ are all 404...

Yes, WAF was another factor favoring the kegerator. I've seen some very nice-looking keezers--but those aren't "buy a freezer, build a collar, profit!" jobs. The Komos isn't visually stunning, but it's still neat and clean. No objections from SWMBO about having it in the dining room.

...which is one year. If my kegerator dies after more than a year, I'm SOL. If your keezer dies after more than a year, you're equally SOL. Nobody's repairing residential chest freezers, any more than they're repairing residential mini-fridges. Will morebeer.com (who effectively are Komos)...

What is "a good chance"? What is "prematurely"? You have no idea, and no data on which to base an idea; you're just fearmongering. Yes, I've read the horror stories--some of them, anyway. I'm aware that (like most consumer products) if it dies next year, it likely won't be repairable unless...

Somewhere over the course of the last day or two, the tap/flowmeter config disappeared on my unit. I have a saved copy of flowconfig.json, so easy enough to upload that, but it's (again) going to be missing a few pours. I'll try Alpha 6.

I'd take (and did take, a few months ago) a contrary position, having built my own several years ago. Once I added up the costs of buying all the relevant parts (including a freezer, because a mini-fridge that will readily handle four Corny kegs is very hard to come by), I decided on the...

I may have missed it in this thread, but I didn't see much discussion of what seems (to me, at least) to be the biggest drawback of most all-in-one systems: all the parts are one-off, single-source custom jobs that you may not be able to replace or upgrade if/when needed. Leaving aside the...

That's looking on the bright side, I guess. Hope it heals quickly and there's no persistent loss of use.

Correct, as far as I could tell. Hope you're feeling better soon.

...and after a couple of hours' uptime, the controller appears to reboot itself, and at that time the appconfig settings are lost--the rPints target, the theme, brewery name, and other settings are lost. uptime.csv doesn't indicate a panic: Date/Time, Start Reason, Restart Description, Uptime...

I'd also note that, although it certainly isn't a critical issue, there's something weird with the serial log when a pour is registered, in that it spits out that line immediately, even if it's in the middle of printing another log entry--or vice versa, as shown above, it starts printing the...