New 0.9.5 test version fixes this.
If you choose to use the new version you will need to change the OPER to something else and back for it to take effect.
I installed the experimental app, and it solved the issue with wrong sensor value being shown on the device! Thanks! 
Are there any experiences with this device? It’s one I’m thinking about getting.
Thanks
This version still revert to room sensor when homey /heatit app restarts.
Can anyone Verify this happening ? Trm6…
Yepp, it does…
Still some bugs that need to be resolved.
you will need to change the OPER to something else, save, and back for to floor temp then dave agsin. That worked for me
Yes we know that . And every time homey restarts also , that is the problem !
@HeatitControlsAB The new version, 3.9.7 was automatically installed yesterday.
This version also revert to room sensor after update/restart.
Please fix this as soon as possible, thanks!
Working on a fix for it, should be able to release quite soon.
1 Like
@HeatitControlsAB, version 3.9.7 seems to fix the current temperature value, thank you for that!
What Olex mentionted, after reboot from homey the current temperature value default back to the internal temperature sensor. If you then change the OPER to something else, save, and back for to external or floor temp then save again it shows the correct value. But every time you reboot homey it need to be done.
Should be fixed in version 3.9.8, can be tested using the beta available here
1 Like
TRM6 doesn’t work anymore !
Agree with the two before. The last updated killed TRM6. Think I tried everything but reinstalling the app (I have a lot of Heatit that will be a real pain to re-create)
There is an issue with this beta version of the app, i recommend going back to the release version for now.
How do you revert to version before 3.9.8?
It was automatically updated to 3.9.8 7 days ago, even if it is now tagged as a beta.
I suppose it should not update automatically to a beta version?
I guess I have to switch off auto update!
Hallo, first of all a great compliment for programming the app for the Homey, and thank you for your time and effort. I am fond of the Heatit Controls app and have been using it whit Heat-it Z-TRM6 Z-wave 21units throughout multiple Homeys that I own.
Bud now i have a weird bug that i encountered multiple times. I will first describe the setup so that u will get a good impression needed for debugging. Please let me know if there is some info that i left out that i need the add.
- Homey Pro 2023 on auto update, so latest version.
- Heatit Controles App on auto update, also latest version.
- In this paricular set up add 8x Heat-it Z-TRM6 Z-wave temperature sensor/controller.
- In tools.developer.homey.app we can see it had a Z-wave connection. Under devices “measure_temperature” we can see is has been update and the correct value.
Now the bug:
Under tools.developer.homey.app/devices we can also see the “target_temperature” has been set from the GUI (app or desktop) of the Homey. No “time out” or “error” returned. Now Homey thinks it has been SET. But if we look on the device, the temperature had not been changed. If we than adjust the temp on the device it also sends no update to Honey. But it is still connected via Z-wave and has communication because we can see data coming in on attribute “measure_temperature” See print screen.
Excluding and repairing will help, but after some days or even weeks it wil come back on the same of other device. Almost every device has been affected at one time. Even returned RMA devices in the first week of purchasing after realizing it is the “Homey/App” that is causing the troubles.
If you need more info let me know, please help us because now we cannot rely on correct switching of the temperature.
@HeatitControlsAB
Yesterday, I came home from a trip and found that all my TRM6 did not respond.
A quick check in the forum reveals that there was a bug with the 3.9.8 version.
How could the automatically update perform an update to a version that is considered as a beta/test version?
Lesson learned, auto update will be switched off.
How do we downgrade?
This is not clear when looking at the version log.
Why did it take one week to inform the customers about the bug?
And why isn’t a working/temporary solution released?
Sorry, this is not acceptable.
Thanks!
@Olex Se om linken virker
Thanks.
Tried that, still on 3.9.8.
Will also try to restart Homey pro later today.
