This update is about a failure that was hard to see: a heater that looks fine but no longer listens.
Warning for a silent heater. A TRV can stay reachable on Zigbee while it has stopped reporting anything, and while the app’s setpoints have stopped reaching it. The thermostat tile kept showing normal regulation, and the boiler kept running for a cold radiator. I ran into this myself, with a head that had been frozen for six weeks. When a heater has not reported a single reading for more than two days, the thermostat now shows a warning. Re-pairing the heater, then using Repair on the thermostat, fixes the link.
The boiler is no longer started for it. Until that heater reports again, its room no longer counts as asking for heat. In a group of several heads, this only happens when all of them are silent: one dead head does not leave the other radiators without hot water.
Valve opening tile removed without Zigbee2MQTT. Without a configured Zigbee2MQTT connection, the app regulates by setpoint. It neither sets nor reads the valve opening, so the tile showed an old, frozen value. The tile is now removed in that case, together with its history. It comes back as soon as a Zigbee2MQTT connection is configured.
You don’t need the boiler part. The central device is only for a boiler relay. With electric radiators, each NodOn module is the heater of its room: you pick it when you create a thermostat, at the “heater” step.
Why the NodOn doesn’t show up there either. The app lists heaters that expose either a settable target temperature or a settable on/off switch. As far as I can tell, the NodOn app drives the SIN-4-FP-21 through a pilot-wire mode (Comfort / Eco / Frost protection / Off), which the app doesn’t recognise yet.
Workaround that works today:
Create a virtual device with an on/off switch (a virtual socket).
Add two Flows: when the virtual device turns on, set the NodOn pilot-wire mode to Comfort; when it turns off, set it to Frost protection (or Eco).
Pick the virtual device as the heater of your thermostat. The app then runs it as an on/off heater, and the radiator follows.
To add native support, could you send me the device’s capabilities? Open Homey Developer Tools, find the NodOn module and paste its class and capabilities here, ideally with the list of values for the pilot-wire mode. With that, I can make the app drive the module directly.
These two releases fix the problems I found while getting my own TRVs back in shape: heaters that look fine but don’t respond, and valves that don’t close.
Heaters that stop responding (1.1.6)
Warning for a silent heater. A TRV can stay reachable on Zigbee while it has stopped reporting anything, and while the app’s setpoints have stopped reaching it. When a heater has not reported a single reading for more than two days, the thermostat now shows a warning. Re-pairing the heater, then using Repair on the thermostat, fixes the link.
The boiler is no longer started for it. Until that heater reports again, its room no longer counts as asking for heat. In a group of several heads, this only happens when all of them are silent.
Valve opening tile removed without Zigbee2MQTT. Without Zigbee2MQTT, the app neither sets nor reads the opening, so the tile showed an old, frozen value. It is now removed in that case, together with its history.
Sensors and valves (1.1.7)
A sensor that only reports its temperature no longer looks dead. Homey only timestamps a reading when it changes. A sensor with nothing else to report, such as a smoke detector, sat at the same temperature for an hour in a stable room, and the app suspended that room. As long as Homey keeps seeing the device, an unchanged temperature now stays valid for up to six hours.
A valve set to something else is put back. If a valve’s setpoint is changed by hand, or by something other than the app, the app now writes its own setpoint again, at most every five minutes. Before, the valve kept its own value indefinitely.
Valves handed back from Zigbee2MQTT can close again. When the Zigbee2MQTT connection dropped or was removed, the app left the valve with a closing limit of 0 %. On a Sonoff TRVZB, that means it never closes, whatever the setpoint. The app now restores the factory limits. If a TRVZB keeps heating with a low setpoint since you stopped using Zigbee2MQTT, a factory reset and re-pairing of the valve fixed it for me.
Repair can now remove a deleted heater. A heater deleted from Homey stayed in its thermostat, invisible in Repair. It now shows up as “Device not found” so you can untick it.
Hi, I was struggling with a large and complex number of advanced flow settings for my heating system, but I came across your app.
I’m just starting to set it up. I’ve created three thermostats that I’ve connected to Eurotronic Spiryt Zwave thermostats. Additionally, there’s a Frient temperature sensor and a Netatmo weather station in each room. My gas boiler is controlled by Shelly, and it all integrates very well.
But I have a question: if I want to create a heating scheme, and let’s say I want 22 degrees Celsius in the bathroom from 7:00 a.m., should I set the thermostat to comfort mode at 7:00 a.m. or, say, 6:30 a.m.? Does your app somehow analyze the indoor and outdoor temperatures and be able to start heating earlier so that the desired room temperature is reached at the set time?
Hi Damian, welcome, and glad the app is helping you get rid of the flow spaghetti! Your setup sounds great: Spirit valves, a Frient sensor per room and a Shelly on the boiler is exactly what the app is built for.
To answer your question honestly: no, the app doesn’t do “optimum start” yet. It doesn’t learn how long a room takes to heat up, so it can’t work out on its own when to start heating to reach 22 °C at exactly 7:00. The preset change happens when you trigger it.
What the outdoor sensor does do is feed the proportional algorithm. The “outdoor coefficient” makes the heating stronger when it’s cold outside, so the room recovers faster and holds its setpoint better. That’s anticipating heat loss, not shifting the start time.
So for now, trigger Comfort ahead of time. How early depends on the room and the weather. A bathroom with a radiator often needs 20–45 minutes for a 2–3 °C rise. Two easy ways to do it:
Simple: a flow at 6:30 → Set the preset → Comfort. Check the room temperature at 7:00 for a few mornings and adjust the time.
Weather-aware: two flows, e.g. at 6:15 if the outdoor temperature from your Netatmo is below 5 °C, and at 6:40 otherwise, each running Set the preset → Comfort.
If you’d rather fall back to Eco automatically afterwards, Set the preset for a while lets you set Comfort for a fixed duration.
Hope that helps, and let me know how the setup goes!
v1.4.0 — Preheating, and Homey’s weather as outdoor temperature
Preheating: be warm on time
Until now, a Flow that switched to Comfort at 7:00 only started heating at 7:00. Now use the action Reach [preset] at [time], e.g. Reach Comfort at 07:00: the thermostat switches early enough for the room to be at temperature at 7:00. Up to 4 targets per thermostat; you can run the card the evening before.
How it knows when to start
Each thermostat learns from its own warm-ups how long the heating takes to get going and how fast the room warms.
Until three warm-ups are measured, it starts at most 90 minutes early; after that, up to 3 hours (adjustable).
With an outdoor temperature, it also learns that the room heats more slowly when it’s cold outside, and starts earlier on cold mornings (after a few weeks of measurements).
New: no outdoor sensor? Use Homey’s weather
When adding a thermostat, or later under Repair, choose Homey weather (internet) as the outdoor temperature source. It uses the temperature Homey gives for your location, refreshed every 10 minutes, for both outdoor compensation and preheating. If the weather can’t be fetched, the thermostat simply works as without an outdoor sensor.
Good to know
Only targets that raise the temperature start early; Reach Eco at 22:00 switches at 22:00.
Changing the preset or temperature yourself shortly before a target cancels it.
Nothing starts early with a window open, the boiler in frost/stop mode, or the thermostat off.
Settings → Preheating shows the maximum lead and what has been learned.
New Flow cards:Preheating starts (trigger), A preheat is scheduled (condition), Cancel scheduled preheats (action).
@Damian_Surma, this answers your bathroom question: Reach Comfort at 07:00 will get it to 22 °C by 7:00.
Motion sensor as presence: no more false “away”
If you picked a motion sensor or camera as the presence source, the home went to away as soon as nobody moved. Now the home only counts as empty after a delay without detection: 1 hour by default, set in Settings → Presence and motion → Delay before away.
New source: Homey presence (geolocation)
Under Repair → Presence, choose Homey presence (geolocation). The home is occupied while at least one Homey user is at home.
When everyone has left, it still waits until no motion or presence sensor of any thermostat has seen anyone for the delay. A nanny or children staying home keep the heating on.
Presence forced by a Flow still applies immediately.
Sure! The key point: Reach [preset] at [time] is an action card (THEN), not a trigger. You don’t run it at 7:00: you run it beforehand to schedule the target, and the thermostat then decides by itself when to switch.
Example 1: one evening flow for the whole bathroom routine
WHEN Date & Time → The time is 22:30
THEN Bathroom → Set the preset to Eco
THEN Bathroom → Reach Comfort at 07:00
THEN Bathroom → Reach Eco at 09:00
At 22:30 the bathroom goes to Eco and the morning is scheduled. Overnight, the thermostat looks at the room temperature and switches to Comfort early enough to be at 22 °C at 7:00 (e.g. at 6:20 on a cold morning, 6:45 on a mild one). At 9:00 it goes back to Eco (lowering the temperature never starts early).
Example 2: weekdays only
WHEN Date & Time → The time is 00:30
AND Date & Time → Today is Monday, Tuesday, Wednesday, Thursday or Friday
THEN Bathroom → Reach Comfort at 07:00
The card always targets the next 7:00, so running it just after midnight lets you filter on the day. Add a second flow with Saturday/Sunday and Reach Comfort at 08:30 for lie-ins.
Example 3 (optional): get notified when it starts
This is where the trigger comes in. Preheating starts fires at the moment the thermostat switches early:
WHEN Bathroom → Preheating starts
THEN Push notification → Bathroom preheating: [Preset] at [Target time], [Lead (minutes)] min early
Handy for the first few days, to see what it decided.
A few tips
Run the scheduling flow at least 3 hours before the target time (the maximum lead), so the evening before or just after midnight is perfect.
Don’t let another flow change the bathroom preset or temperature in the 3 hours before 7:00: a manual change in that window cancels the target (that’s on purpose, you overruled it).
The first mornings it starts at most 90 minutes early, using default values. After three warm-ups it uses what it measured. Settings → Preheating shows what it has learned.
Adaptive Thermostat 1.5.1: Window contact changes are delayed or missed entirely
Hi Vincent,
Several of my thermostats sometimes take minutes to pick up changes from their assigned window contacts. Initially, detection worked without noticeable delays.
The contacts correctly report opening and closing in Homey, but Adaptive Thermostat continues to show the previous window state.
Examples on 3 November 2026, all times CET:
Event
Window contact
Adaptive Thermostat
Opened
11:26:36
11:31:18 — approximately 282 seconds later
Closed
11:45:00
11:46:35 — approximately 95 seconds later
Opened and closed again
11:58:40–12:00:33
No window state change recorded
During the last test, the window remained open for approximately 112 seconds. While it was open, the virtual thermostat still showed the window as closed, status “heating”, 13% heating power and a regulated setpoint of 23°C. The radiator’s target temperature also remained at 23°C.
Settings and troubleshooting so far:
Detection: “Contact sensor”; action: “Turn off”. The correct contact is assigned.
Both opening and restoring delays were initially set to 0 seconds.
Tested both delays at 5 seconds in the office: no improvement.
Restarted the app: no improvement.
During the last test, the regular trigger for my custom heating schedule script was disabled. The problem still occurred.
The old flows that controlled the radiators directly through eWeLink are disabled.
My heating schedule script sets Eco/Comfort/Boost on the virtual thermostat. It does not write the window state or control the radiators directly.
Could this involve the handling of real-time events or the refreshing of sensor states? The exact cause has not yet been established.
What runtime diagnostics would you need to determine whether the contact events reach the app and why the window protection does not respond promptly?
Existing physical Futurehome termostat controlling floor heating i in my entrance (heater). Since the termostat is quite close to the door it sometimes is affected by draft from the door so i want an external sensor to control it. For this i use a Sonoff SNZB-02D termometer (room temperature sensor) located on the wall 1.5 meter away.
The virtual termometer i created seems to follow the external sensor and my flows, but the physical one is shooting at 23 degrees and continues to heat even if the temperature according to the virtual one is OK. Any idea why this happens? I have reset the termostat a couple of times and also the old Futurehub controller is disconnected.
Hi Jens, thanks for the screenshot, it shows what’s going on. The virtual thermostat is doing its job, but the physical one still decides by itself when to heat, using its own sensor.
The app controls this kind of heater by sending it a target temperature. In cold weather it adds up to 2 °C to make up for heat loss, so your 21° becomes 23°: that’s the regulated setpoint on the virtual thermostat’s tile. Your physical thermostat reads 19° near the door, so it sees 23° as far away and keeps heating. Turning self-regulation off wouldn’t be enough, because it would receive 21° and still see 19°.
What works today is to make the app drive it as a simple on/off heater:
Create a virtual device with an on/off switch (a virtual socket).
Add two Flows: when it turns on, set the Futurehome thermostat to a high temperature (e.g. 30°); when it turns off, set it to a low one (e.g. 5°).
In the virtual thermostat, use Repair to pick the virtual socket as the heater.
For floor heating, set the Recalculation period to 15–30 minutes in the settings.
The heating then follows your Sonoff sensor. Any floor temperature limit set on the Futurehome itself still applies.
Hi Chris, thanks for the very precise timings, they led straight to the cause, and it’s a bug in the app.
When the app reconnects to Homey, a sensor could stop sending it live updates, with no error anywhere. Your contact kept working in Homey, but the thermostat only noticed a change at its next recalculation, which is every 5 minutes by default. That explains the delays of 95 and 282 seconds, and why a window open for under 2 minutes could go completely unnoticed. It also explains why it worked at first. Your schedule script, your eWeLink flows and your delay settings had nothing to do with it, so you can set the delays back to what you prefer.
I reproduced the fault in a test and fixed it. The fix will be in version 1.5.2, and I’ll post here once it’s in the App Store. There’s nothing to change on your side. A slow heater could also postpone a window change, and that is fixed too.
No diagnostics needed for now. I could only reproduce this on my side, not on your Homey, so if a window is still late after updating, please post the same kind of timings here.
Adaptive Thermostat 1.5.2 is out. Window contacts react at once again: after the app reconnected to Homey, a sensor could stop sending live updates, so a window was only seen at the next recalculation, up to 5 minutes later by default, or not at all if it was open only briefly. Motion and temperature sensors were affected the same way. Update the app, there’s nothing to change. Thanks @Chris_M for the precise timings. If a window is still late, please post the timings here.
Hello @byackee1 ,
Would you be willing to add support for Fahrenheit? Some temperature sensors in my home don’t even have a Celsius setting, and the adaptive thermostat doesn’t normalize to C. So it’ll read the average room’s F value as C and report back to homey that my rooms temp is 160+ F.
Hi aesubs, thanks, the screenshot explains it: 163 °F is 72.8 °C, so a sensor at 72.8 °F is being read as 72.8 °C. That’s a bug in the app, and while it happens the thermostat won’t heat, because it thinks the room is far too warm.
You shouldn’t need a Fahrenheit mode as such. The app works in °C internally and Homey shows its thermostats in °F based on your location. What was missing is converting devices that report in °F. Preset temperatures in the thermostat’s settings stay in °C for now.
The fix is in version 1.5.3, now in the App Store. Just update the app.
Could you tell me:
Which app provides these sensors?
On the sensor’s own tile, do you see the right temperature (about 73°), or 160+ there too?
After updating, does the thermostat show the right room temperature?
If the sensor’s own tile also shows 160+, its app sends °F while telling Homey they are °C. My fix can’t detect that, so let me know and we’ll look at it.
Thanks for the quick patch! It did resolve the normalization problem. The current temp is showing up as the correct value in Fahrenheit now.
If youre referring to the sensors that only report in F. I have some generic matter sensors in some places that are old. However most of the other matter temp sensors in my house expose a setting to switch which unit the readings are sent to the controller as.
One more thing: Would consider adding a units setting that allows specifying F values for the various thermostat settings? This isn’t a bug report like the last message, as it’s totally feasible for me to just do the conversions manually and input the values as C. But it would be convenient to avoid the need while I try to get values dialed in over time.
I’m using a Shelly 1 Mini Gen4 (Wi-Fi, outbound websocket connected) as the heater for a room, switching a thermal valve actuator. After two days without heat demand, the thermostat shows a warning that the heater hasn’t reported any measurement, and it stops controlling the boiler for that room. The relay has no power metering and only reports on state changes, so it stays silent when idle. Could the check be adjusted or disabled for plain on/off relays?
@byackee1 have you considered multiple device and sensor selections for a thermostat? For instance, in almost every room I have multiple window sensors because there are multiple windows. In some of my rooms I have 2 heating sources with independent switches. In some cases an aggregate/average for multiple temp sensors would also be useful.
Multiple selections, in combination with SUM, AND, OR, logic here and there, would offer the flexibility to accommodate many more home scenarios.