Replies: 1 comment 1 reply
-
|
You can use both, from 2.3 the corr-gravtity and gravity will contain the same value. I have used corr-gravity for testing out new features like the filtering in the past. So both temperature correction and low pass filter will be applied to all options. Brewfather uses plato by default if the name does not contain [SG] (See the services integration chapter) so you can stick with the standard gravity or gravity-sg. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am using GM 2.3.0 on iSpindel hardware. I send JSON data to Brewfather on HTTP Post 1, BrewPiLess on HTTP Post 2 and to FermWatch32 via MQTT. I have set adjust gravity to 20C for temperature compensation and am using SG. There are several options for gravity:
Gravity, ${gravity}
Gravity (SG), ${gravity-sg}
Gravity (Plato), ${gravity-plato}
Gravity unit, ${gravity-unit}
Corrected gravity, ${corr-gravity}
Corrected Gravity (SG), ${corr-gravity-sg}
Corrected Gravity (Plato), ${corr-gravity-plato}.
I think that I will need to set "gravity":${corr-gravity} in the JSONs to various destinations but I would like some confirmation that this is the right choice. Cheers Peter
Beta Was this translation helpful? Give feedback.
All reactions