Automations used to watch one sensor and notify, send a command or call a webhook. Now they react to any data point, run by the clock, set values and write to Discord, and outbound webhooks send every reading to Grafana, InfluxDB or your own server.
Rules on data points
A condition can now be any data point you can read, also of another sensor or through a link. Numbers rise above or fall below a value, an on or off value turns on or off, a choice is a given option, or any value changes. Up to three conditions per rule.
By the clock
The trigger On a schedule runs up to twelve times a day on the days you pick, in your time zone. No conditions: the fan on at 7, off at 19. If the server was away at that time, a run more than ten minutes late is skipped, not caught up.
Set values and Discord
A rule may not set a value it watches itself, and fires at most six times a minute. Two rules that switch each other stop there. Last 30 days shows how often the rule would have fired before you save it.
Alerts in Discord
Create a webhook for the channel in Discord, then pick +Notification channel in HydroNode and paste the URL. A channel hears all sensors, chosen projects or chosen sensors, for Delayed, Offline, Back online and Low battery standby. Test sends a message right away.
Every reading to your server
An outbound webhook under ProfileIntegrationsWebhooks sends readings in bundles, after 10 seconds or 500 values, as JSON or Influx line protocol. Every request is signed with HMAC-SHA256, and access is checked again on every delivery.
hydronode,sensor_id=6d1f…,sensor=Greenhouse,point_id=a4f2…,point=Temperature,type=TEMPERATURE value=21.4 1762846201000000000Where to go next
- Automations, Notifications and Integrations in the docs.
- When a sensor counts as quiet: Know when a sensor goes quiet.

