This Post is for Version TRM2fx with has got Firmware 3.4. But with TRM2fx I had same issue. I allready wrote thermofloor and made a list of failures and missing things in firmware. Answer: We will look for it, that had been all.
What I did to solve this (Thanxs for all made the parameters working):
I write a rule to made my own setpoints for temperature which work:
rule "TRM2fx OG-Flur"
when
Item OG_Flur_Thermo_Soll_Temp changed
then
var int help
var int newTemp
newTemp = (((OG_Flur_Thermo_Soll_Temp.state as Number).doubleValue + 2) * 10).intValue
logInfo("Recalculate OG_Flur", "Comfort: " + newTemp.toString)
OG_Flur_Thermo_Soll_Temp_Comf.sendCommand(newTemp)
help = ((OG_Flur_Thermo_Soll_Temp.state as Number).doubleValue * 10).intValue
logInfo("Recalculate OG_Flur", "Eco-Parameter: " + help.toString)
OG_Flur_Thermo_Soll_Temp_Eco.sendCommand(help)
end
The items for it:
//Help Item
Number:Temperature OG_Flur_Thermo_Soll_Temp "OG-Flur FB Heizung Soll [%.1f °C]"
Number OG_Flur_Thermo_Soll_Temp_Eco "OG-Flur FB Heizung Soll Eco" { channel="zwave:device:smartholhome:node6:config_decimal_param10" }
Number OG_Flur_Thermo_Soll_Temp_Comf "OG-Flur FB Heizung Soll Comfort" { channel="zwave:device:smartholhome:node6:config_decimal_param9" }
In the rule above I allways set Eco-Temperature by parameter with calculating parameter with my Help Item and set Comfort 2 Degrees higher. This way I can trigger my own item via Groups and the rest works.
If you ask why dont use the original Setpoint: The Setpoint don’t gets Update if Temperature is changed an Device itself. Parameter receiving Updates sometimes.
Thanks for info.
My problem is that there is no channel for" setpoint eco" for TF016 with fw 1.92.
From what I can see from other threads it should be possible to create it in the database, using parameter 11, but it is a bit beyond me…
BTW, it sounds like Z-TRM2fx still does not work correctly in OH?
(I wanted to buy a couple, but now I am not so sure anymore.)
With openhab they work, because with openhab you can write some rules to correct most things, which are broken in firmware.
Chris and the others did a good job made channels to the parameters.
I wrote a list of 10 to 12 bugs and 5 useful wishes to thermofloor. They only answered the will look for it and deleted the list from support board where I could read it and see the status.
Back to the original thread: could someone activate the switch of the device as a channel again? Found an option to activate a switch in device option. I’ll try out if I m able to activate something useful there.
Hi, I too would like to have the switch channel activated again. At first I wanted to associate the switch output to an Fibaro relay connected to som other heaters, but the association never worked.
Then I made a rule to control the relay from the switch status. This worked ( polled the state every minute).
But when the channel is removed none of this is working.
Hi, not to bump an old thread but I’m having some issues adding my “Z-TRM2fx” to my system. I’m fairly new to Z-wave, openHAB and probably other parts of my issues. From what I understand from this topic the 2fx will add as a previous product, where the channels are somewhat wrong. I’ve delved in the lands of javascript, C, C++ and some other programminglanguages so I’m not completely out of it, but I can’t seem to find any useful file on my openHAB which let’s me add your work.
What version of the binding are you using? If you’re using the 2.5 binding, then it should be supported unless I’m missing something (since this was updated 7 months ago).
Important: for this device there are ota firmware updates published.
Next version will have change in options because at the moment you can only set differences of +/- 5 degrees in temperature: next version will have a two byte value for higher offsets.
