Search results

At the moment, there aren't variable setpoint beer profiles, but I was thinking of creating something like this as a "cold crash now" button for the end of fermentation. Is that what you're trying to do, or are you thinking of doing this at the start of fermentation? (If so, is your beer...

Google probably changed something with their payloads. I’m working on a new major release for TiltBridge at the moment ahead of Fermentrack.net integration — I’ll make sure to test this before I release that. Thank you!

Hey there - I apologize for the delayed response on this one -- we're in the process of moving, and due to a combination of poor timing and other life changes are having to effectively move four separate times over a month and a half. You happened to post this right as we were working through...

I could be mistaken, but back when I was building the iSpindel support I don't think that the message payload included a device-calibrated gravity. I'm working on rebuilding gravity support for Fermentrack 2 -- if it includes one now, I can definitely add that as an option.

Ahhh - understood. Those are (were?) maintained by @UncleD who unfortunately hasn’t been around as much as of late. For the web app, I’m currently developing TiltBridge/gravity support for Fermentrack.net which will be the new, “native” cloud data target. This requires both a rewrite of chunks...

Apologies - what site are you trying to log into?

Exactly. Sorry for any confusion!

For the TiltBridge device web portal? No - but it doesn’t support HTTPS. The TiltBridge configuration portal really shouldn’t be exposed to the open internet. The idea is that you set it up to point to an external service and then access that.

I can only speculate as to what caused the issue you experienced, but I can confirm that the latest release contains a massive rewrite of the data sending code which fixed a number of problems - potential or otherwise - under the hood. Upgrading is definitely recommended if you have any problems...

At the moment, the only way to retain your settings would be to manually flash only the firmware partition using esptool. Unless you are already familiar with esptool I would say it’s generally more trouble than it’s worth. With that in mind, unless you use MQTT or Grainfather you can probably...

New Release Announcement I just released v1.2.2 of the TiltBridge firmware for all existing devices. This firmware release incorporates a handful of new features primarily targeted at Home Assistant users, as well as new data sending code which enables a number of new features and bugfixes...

That’s weird on both counts. Without looking at the blame log, I don’t anticipate that @LBussy changed anything meaningful with the temperature calibration code, so I’m surprised that you’re having issues with the legacy firmware. Additionally, you should be able to flash any firmware you want...

Inside Fermentrack if you go to the device menu and click "Flash Device" it will take you to the device flashing workflow which will allow you to then select the firmware you want to flash. I was testing with a slightly modified version of @LBussy 's 0.2.13 firmware, which is what is available...

Don't worry about it. I got some time this evening, so I assembled a new Pi/Fermentrack/Uno/DS18b20 setup. Unfortunately, everything seems to work as expected on my end: I don't know why things don't work on your end, but don't see anything that I can do at this point to fix your issue...

@TheFlangerBeer - I've created a test firmware that will print some debugging info to the log that I can use to (hopefully!) figure out what is going on. If you have a moment, can you flash the correct one of the following two firmware to your Arduino: RevC...

I'm at a bit of a loss at the moment, unfortunately. I built a slimmed-down proof-of-concept based on Lee's code that can be run in a C++ shell, and best that I can tell it seems to be doing the conversion appropriately: my_strtol called with -0.7 - Converted to 0 stringToFixedPoint called...

I appreciate it. The logs are very helpful, as the hardware you’re using (Arduino) isn’t what have set up on my end, so I'm debugging through you, unfortunately. I’m not seeing anything obvious on the Fermentrack side of things that could cause this as everything appears to be getting properly...

Can you paste them here?

Just to make sure everything is doing what I expect, do you mind quoting the logs here again?

That's my fault. The command should be: ./install.sh -i docker-dev I forgot the "docker-" part.