Search results

I'm not sure what the bug is that's supposed to have been fixed. But after updating to Alpha5, uploading appconfig.json and flowconfig.json, and hard-resetting the device, the new settings took, the theme and brewery name were right, the tap information was there, etc. The Raspberry Pints...

Ah, got it. I'll try it again tomorrow.

Nope. I'm not sure if resetting the controller (Settings -> Advanced -> Reset Controller) is wiping out appconfig.json, or if it isn't being picked up in the first place, but one way or the other, following the reset, the app config settings are back to defaults.

But if I can upload appconfig.json, presumably I can edit it before I do so. So what happens if I change the configuration to this, and then upload it? "rpintstarget": { "host": "192.168.1.165", "port": 1883, "username": "RaspberryPints", "password"...

The same thing is true of the URL target--entering a URL still leaves "update" set to "false." But strangely, "update" is set to true for taplist.io, for which I don't have any configuration entered. I don't know if I should be seeing enable/disable buttons for the different targets, but I'm not.

...and I think I see the problem: "rpintstarget": { "host": "192.168.1.165", "port": 1883, "username": "RaspberryPints", "password": "password", "topic": "kegcop", "update": false },

Unplugging the USB cable used to flash the new firmware and check the logs, and plugging in the USB charger.

2023-04-17T22:04:08Z V: Keg Cop Save: Saving configuration. 2023-04-17T22:04:08Z V: Keg Cop Save: Configuration saved. 2023-04-17T22:04:12Z V: KegScreen reporting not enabled, skipping (Temp Report). 2023-04-17T22:04:34Z V: Processing put to /api/v1/config/settings/. 2023-04-17T22:04:34Z N...

OK, now running: Theme, brewery name, kegerator name, temp sensors, and at least the Raspberry Pints target reset on power cycle. Tap information doesn't. There's still zero action on MQTT on a pour; log in the next post.

Interesting. First, somehow the controller lost the theme, brewery name, temp probe settings, and target settings between last night and tonight. The tap information was preserved. uptime.csv doesn't show anything unexpected: Date/Time, Start Reason, Restart Description, Uptime (Secs)...

It isn't that hard to note the relevant settings--there aren't that many of them--but wasn't sure if I needed to. Sounds like I do. Edit: Alpha4 is now installed. The uptime.csv file is available, which will give me a way of keeping track of it. I also put it on a SSID that's only served by...

Can I update to it without it wiping all my settings?

So now that I have what seems to be a stable KegCop installation, how do I go about figuring out why pours aren't showing up in Raspberry Pints?

Maybe I wasn't very clear with my question. I'm not asking how to calculate IBUs; I have software (Brewfather) for that--if I give it weight, AA%, and the other relevant factors, it'll give me IBUs (which are right in line what what the calculator you linked gives). But the recipe linked...

It's there on 1.2.1-alpha3.

Logging in that way works, but there's no uptime.csv file there.

Should that work on Alpha2 as well? Because it doesn't for me; it 404s.

For HBU? Because utilization isn't stated as a factor for calculating HBU in the sources I'm finding on Google, e.g.: https://beerandbrewing.com/dictionary/CfPWSONzyd/ https://homebrewing.org/pages/what-is-an-hbu-pack...

As far as I can tell, mine is still working on 1.2.1-Alpha2. It's keeping its settings and seems to be tracking pours. And I'm in a Unifi network environment with three APs in likely range of the ESP, so if that's what's causing all the trouble, I should be pretty near a worst-case scenario...