Forward readings to Brewfather#
Self Hosted Cloud Hosted
BrewGraph can send every accepted reading on to Brewfather as it arrives. This page shows how to set up the two Brewfather targets, which addresses are accepted, what the Forwarding page tells you, and what to do when a target fails. It is separate from importing a batch from Brewfather, which pulls data in and uses its own key. See Integrations.
Note
Forwarding on Cloud Hosted is not open yet. Until then the Forwarding page is not offered on a hosted account.
Choose a target type#
Target type |
Measurement |
Address path |
|---|---|---|
iSpindel forward |
Gravity |
|
Brewfather custom stream |
Gravity, pressure, temperature |
|
Both send a fixed payload that BrewGraph builds, so there is no template to write. Every device on the account forwards to the target; you do not set a URL per device.
Add a target#
Open Settings > Forwarding (Self Hosted: Other > Integrations) and choose Add target.
Enter a name and choose the measurement. The measurement cannot be changed later. To forward something else, delete the target and create a new one.
Choose iSpindel forward or Brewfather custom stream as the type.
Paste the address from Brewfather, for example
http://log.brewfather.net/ispindel?id=<id>for the iSpindel forward orhttp://log.brewfather.net/stream?id=<id>for the stream.Use Preview payload to check what will be sent. The preview runs in your browser and sends nothing.
Save.
Address rules#
An address is checked when you save it, and a faulty address cannot be saved. The message next to the field says what is wrong.
The address has a scheme and a host. Only
httpandhttpsare accepted.It has no spaces or control characters, and no credentials in the form
user:pass@.For
log.brewfather.netthe path must be exactly/ispindelfor an iSpindel forward or/streamfor a Brewfather stream, and the query must have anidthat is not empty. A different path, such as the stream path on an iSpindel forward, is refused.The host must not resolve to a loopback or link-local address.
A Custom target is not path-checked.
What the Forwarding page shows#
Each target is a card with its name, measurement, type and an on/off switch. The card also shows:
the time of the last successful delivery,
Last failure, when the most recent delivery failed, with the cause,
the number of consecutive failures,
Paused: auto-paused after repeated delivery failures, when BrewGraph has switched the target off.
Use Send test payload to send fixed sample data to the destination after a confirmation. Authorization headers are never shown.
If a delivery fails#
The Last failure line names the cause. BrewGraph retries a failed delivery and does not store the response from the destination.
Shown as |
What to do |
|---|---|
|
The address points to a host BrewGraph does not call, such as a loopback or link-local address. Use the public address from Brewfather. |
|
The address is wrong. Copy it again from Brewfather and check the path
and the |
|
Brewfather or the destination refused the delivery. Check the |
|
The destination is slow or down. Try again later. |
|
Check the host name and that the destination is reachable from the internet. |
|
Send a test payload and check the address. If it keeps failing, contact support with the time of the failure. |
Auto-pause and resume#
After 3 failed deliveries in a row, BrewGraph switches the target off so that it stops calling a destination that does not work. A successful delivery resets the count. You get a notification, and opening it takes you to the Forwarding page.
To start again, correct the address if needed and either switch the target on or choose Resume. The count of failures starts from zero.
See also: Ingest error codes for readings that BrewGraph itself refuses.