Object settings
Every communication object has a settings dialog — expand the device and click the gear at the end of the object row (Edit Object). What you see depends on the protocol, but the common parts are:
General
| Field | Description |
|---|---|
| Object Name | The object's name. |
| Datatype | The object's data type. Picking a data type that differs from the object's native type shows a warning: a transformation is required to convert between them (see “Value Transformations & Health”). |
| Address | The object's binding: the group address, entity or protocol address it is connected to. |
The dialog has no direction setting: whether an object receives values, sends commands or both comes from the widget type (see “The Devices Workspace”).
Value settings
| Field | Description |
|---|---|
| Range - Min / Max | The value range. |
| Label - Min / Max | Labels for the range ends (e.g. Closed / Open). |
| Decimal digits | Display precision. |
| Units | The displayed unit (e.g. °C, kWh). |
Per-protocol settings
- KNX: the group address (Address) and the datapoint type (Datatype). There is no "Read on Start" option: each time the KNX connection is established, the server reads every object that receives a value and has an address, so the app shows values straight away.
- Home Assistant: Entity ID and optionally the Attribute to read.
- Modbus: see “Modbus TCP Integration”.
- HTTP: see “HTTP Integration”.
- MQTT: topic, payload format, publishing and subscribing options — see “MQTT Integration”.
- BACnet/IP: object type and instance, value type, change-of-value subscription and write priority — see “BACnet/IP Integration”.
- TCP/UDP: key, command and query templates, match pattern — see “TCP/UDP Integration”.
- Virtual: the range (Range - Min / Range - Max) and Persist State (keep the value across restarts); there is no default-value setting — see “Virtual Devices & Node-RED”.
- Camera: the Camera Stream URL (see “Cameras & Videophone Setup”).
- Videophone: the videophone address and credentials (see “Cameras & Videophone Setup”).
Notifications
An object can raise a push notification when a received value matches a rule. Switch on Notifications, then set:
| Field | Description |
|---|---|
| Type | Equal, Greater than or Lower than. |
| Value | The threshold or match value. |
| Interval (s) | The minimum time between two notifications. It is a minimum gap, not a repeat timer. |
A rule fires when the value crosses the threshold, not for as long as it stays beyond it. A Greater than rule sends one notification when the value reaches the threshold; the next one is possible only after the value has dropped back below it, and never sooner than Interval (s) after the previous one. An object holds one notification rule.
Notifications are delivered to the app as push messages (see “Push Notifications”).
Settings
- Log historical values — writes every value change to the time-series history (InfluxDB). This is what feeds trends in the app, meter charts, Grafana dashboards and CSV export (see “History & Data Logging”). The object's row then shows the database icon and the Grafana button (the LOGGED and GRAFANA legend, see “The Devices Workspace”).
- Persist State — saves the value on change and restores it after a server restart. It is separate from logging.
Click Save object to save the dialog, then Apply changes in the sidebar and confirm (see “Admin Panel Tour”). Logging starts with the next received value.
The Grafana panel builder
Logged objects offer a Grafana panel action that builds a Grafana panel or Flux query for the object:
- Pick the panel type, the aggregation function and aggregation period, the time range, and a title.
- Then either copy the Panel JSON or the query only (Flux) to paste into Grafana yourself, or pick a target dashboard and click Add panel — the panel is appended to that dashboard. You can also create a new dashboard by name.
If something is missing, the dialog says exactly what: Grafana is disabled (enable it in Services), no API token is set (see “Services & Protocols”), Grafana is unreachable, or the token lacks Editor permission. Details on Grafana and dashboards are in “History & Data Logging”.
