Device state history
Review and analyze device state changes over time (15-minute detail).
Quick checks (if the timeline looks wrong)
If the device is offline, you will see gaps. Without prices, parts of the view cannot be built.
Is the device online?
If the device is offline, you will see gaps.
Is price data available?
Without prices, parts of the view cannot be built.
Quick checks (if the timeline looks wrong)
- Is the device online? If the device is offline, you will see gaps.
- Is price data available? Without prices, parts of the view cannot be built.
- Are there multiple rules? Priority/conflicts can explain differences.
- Was manual control used? It can temporarily override automation.
Decision tree: what explains the timeline?
- No updates at all: MQTT/network issue or device offline.
- Gaps during the day: data outage (offline) or missing measurements/status updates.
- State differs from the rule: another rule may override, or manual control was used.
- Heating looks ?unstable?: MPC/learning settling or sensor limits causing frequent changes.
Concrete examples
- Price rule: device runs mostly in cheaper price zones and stays off in expensive ones.
- Time window: device never starts outside the allowed time window even if price is cheap.
- MPC: timeline may show an MPC highlight (MPC overlay) and control can start early predictively.
- Offline backup: if connection drops, the device can continue on the last synced schedule (supported devices).
What is Device state history?
Device state history shows device state changes during the day with 15-minute detail. It helps you understand when a device was on/off and which automation influenced the decision.
- In the app the view is called "Device state history"
- App route: /devices/timeline
- Each row represents a device (or an output channel on multi-channel devices)
- The timeline combines states, prices and rule impacts (price/schedule/temperature)
- It is primarily an analysis and explanation tool: it helps you understand what happened and why
Day selection and updates
Choose the day and understand when data updates.
- Change day with the day navigator (previous / next / today)
- The view uses 15-minute price data for the selected day
- If price data is missing, the timeline cannot be fully constructed
- If a device was just added or offline, parts of the day may be missing state data
How to interpret the 15-minute timeline
Each segment represents the inferred state for a 15-minute slot. If data is missing, you may see gaps or delayed updates.
- 15-minute slots help align prices and device behavior on the same timescale
- If the device does not report continuously, state is inferred from the latest known value
- If you see no updates, check MQTT connectivity and that the device is online
- If you see gaps, it is almost always missing data (offline, interruptions, no measurements)
Price zones and price grid
Price zones help interpret whether device usage is aligned to cheap or expensive hours.
- Price zones: very cheap / cheap / mid / expensive / very expensive
- The view may include a price overlay (price shown in the background)
- A device-specific 15-minute price grid can be opened from a row (expand)
Rule impact (timeline indicators)
The timeline shows how different automations affect the device.
- Schedule rules can force ON/OFF segments within certain time windows
- Temperature rules show their own indicators (heating/cooling)
- Price rules control on/off based on price and the timeline shows the result
- The legend text in the app: "Timeline indicators"
- If multiple rules exist, a higher-priority rule can override others
MPC on the timeline (if enabled)
If MPC is enabled for a device, the timeline may show MPC control periods.
- MPC control is shown as a highlight (overlay) on the timeline
- MPC aims to optimize heating predictively (price + target)
- If MPC has no active plan, the highlight may not be visible
Manual control vs automation (why it may look ?weird?)
A key benefit is separating manual actions from automation. If you switched a device manually, it can appear as an anomaly compared to rules or price.
- If you manually switch the device, it may remain in that state until the next automation event changes it
- If the device does not react, verify it is online and the correct output/channel is selected
- To ensure behavior during outages, offline scheduling can sync schedules to supported devices
Troubleshooting & FAQ (timeline)
Timeline is empty or rows are missing
- confirm devices are added and visible in the Devices view
- confirm the selected day is correct
- confirm devices are online and reporting works
Price zones are not visible
- the day's price data is missing or not yet updated
- confirm the system is online and try again later
State does not match reality
- the device may have changed state but the event did not arrive (MQTT interruption)
- for multi-output devices, make sure you are looking at the correct row/channel
- check MQTT/TLS settings in the device guide if interruptions occur