I tried this. It worked for a bit (a few seconds?) and then it started showing the external temperature again. You can a couple of attempts in the attached screenshot, where the vertical lines are the quick period between incorrect and correct value.
1 Like
@HeatitControlsAB I think I found another bug:
When using the picker, the following happens:
Move from Power Regulator to Off:
Sensor mode (OPER) changes from PWER to A (I would expect it to still be PWER?)
Operation mode (MODE) changes from Heating to OFF (as expected)
Move from Off to Power Regulator:
Sensor mode (OPER) changes from A to PWER (as expected)
Operation mode (MODE) is still OFF (I would expect it to move to Heating - as the thermostat is now not heating despite being set to Power Regulator)
@AxelS thank you for notifying us, both issues are fixed in an internal version.
When the update is fully tested it will be released to the Beta channel.
Thank you and keep up the good work 
Hi @HeatitControlsAB, thanks for the update.
I observe the following after updating to 4.0.8 (two different Homeys on different locations with a few TRM6s - some in power regulator mode and some in floor sensor mode):
Power regulator issue: The behavior for switching back and forth between Off and Power Regulator is the same as in 4.0.7.
Main sensor issue: The correct sensor is used, but the value is not updated. It is stuck on the value from last restart of the The Heatit app or when changing sensor mode. Similar to an issue in an earlier release that was discussed here some time ago.
How does one do this now? There is no Homey app, only heat it.
Do you mean that it doesnât show PWER when in off?
If that is the case, this is on purpose. If you would switch to a different mode, say Heat, it wouldnât know which sensor to use since PWER is a sensor mode, therefor, it changed back to your previous sensor mode, the one used before it was set to PWER.
But this wasnât an issue on 4.0.7? There has been no change to this from that version, and on our Homey install it seemed to be working well during our tests.
Hi @HeatitControlsAB and thanks again for following up. Appreciate all your work on the Homey app 
Do you mean that it doesnât show PWER when in off?
If that is the case, this is on purpose. If you would switch to a different mode, say Heat, it wouldnât know which sensor to use since PWER is a sensor mode, therefor, it changed back to your previous sensor mode, the one used before it was set to PWER.
I am only changing back and forth between Power Regulator and Off. When changing from Power Regulator to Off, the sensor mode parameter changes to A and operation mode parameter changes to off. When switching to Off from Power Regulator, sensor mode stays on A while operation mode stays off. The unit display stays off and the device does not heat.
I understand that sensor mode would need to change to the last ânon-PWERâ setting when changing the selector to Heat, but would prefer sensor mode to stay on PWER (and only change operation mode) when switching between Off and Power Regulator.
Hope this makes sense.
But this wasnât an issue on 4.0.7? There has been no change to this from that version, and on our Homey install it seemed to be working well during our tests.
This was not an issue on 4.0.7. See screenshot below - Heatit app was upgraded from 4.0.7 to 4.0.8 at the red marking, and Heatit app was restarted on the yellow markings.
Maybe the behavior was introduced by the changes made in 4.0.8 to use the correct sensor for device measured temp?
I am not sure why it does not work for me when it worked in testing, here is some background in case it helps: I have rebooted Homey and have tried to switch between sensor modes, that did not solve the issue. This issue occurs on all my TRM6 devices on two different Homeys at two different locations. Happens regardless of what sensor mode they are in. The oldest device was paired to Homey in january 2024 and the youngest device was paired in april 2025, using the newest Heatit app version at the time.
No problem, happy to help.
Iâll check this and let you know, I think we can change it like you want it to.
Think the issue might be how the variable which decides the measured temperature below the setpoint wheel was saved, think a fix has been found.
Thanks!
Then it will be secure automatically, and I add the nodes in group 2?
So if the alarms are node 1-4, in the settings of no1 I put â2,3,4â, and in the settings of no2 I put â1,3,4â? Then the alarm test (one press on button) should make all 4 beep?
It will ask you to use the pin code, if you enter this it should include securely.
You can confirm by checking the advanced settings and seeing it doesnât show âXâ at âSecureâ.
Yep, although node 1 is reserved for the Homey itself 
Not 100% certain a test function also triggers the other detectors, but you can find this out easily enough.
Thanks again - I set the pin myself, or is it printed on the unit?
If the button test does not trigger the rest, I guess the only way to test would be with actual hest/smoke then. Iâll try and report back 
Printed on the unit, you should see a QR code sticker with some numbers below it.
Somehow the app uninstalled from my homey.
Somewhere within the last 2 weeks I think.
And now I canât get it to install again.
Anyone having the same issues?
Homey is on version 12.3.3
Hi, I recommend you check with Homey.
Weâve received feedback from them that it might be due to insufficient space/ram.
i have the same problem here.. today my heatit app are uninstalled. 
Saw in the release notes of the latest update (homey firmware) that something was fixed regarding this.
But im not home for a few days so I wonât risk the remote update now. Will report later.
Hi there. I have two Heatit Z-TRM3 and one of them gives me ZWaveSendCommandTimeout after 30000ms. They both worked fine with the Futurehome hub.
1)I have tried to reinclude the device several times, with no luck.
2) Restarted the heatit app in homey, no luck. But with each app restart it is possible to change some values. So there is communication there.
Is there anything else to try?
Please let me know if this works for you.
