Don’t really know what “this” means in this context. Probably should open a new thread.
On quick review, the device (Z-TRM3) uses a V3 version report of the Thermostat_Setpoint CC, but the binding only supports V1 & V2. I do not see that changing in the near future. However, by Silabs specifications the device should be backward compatible with V1 and V2, so I’m guessing the HEATIT firmware update mentioned above fixes that. Also I couldn’t see (on my quick look) how adding a decimal works, but hey, don’t argue with success .
Anyway, assuming the first post is correct in that parameter 9 works (parameter 22 in the case of the Z-TRM6), another workaround is to create an endpoint (i.e. channel) for that parameter in the Configuration CC in the ZW device DB. You would have to deal with a Number item 10x larger and not a Number:Temperature, but it should work.
As an alternative to waiting, if anyone wants to test using the parameter (9 or 22) as a channel for an item to set the heating setpoint (ECO could be added later), I marked up a couple of XMLs with that functionality that can be added to your ZWave jar.
Z-TRM3 ztrm3_0_0.xml (20.0 KB)
Z-TRM-6 trm6_0_0.xml (28.3 KB)
The procedure is here. The files are located in /OH-INF/thing/thermofloor/
Hi guys. I have some openHAB 4.0.2 with the Z-Wave binding and an Aeotec Z-Stick 5 USB on a Raspberry PI 4 with 4GB RAM, which works fine with all the devices… except several Z-TRM3.
I am not sure here if the issue should have been solved in openHAB 4.0.2 or not.
I noticed som decimal story, but I am not able to see this anywhere.
Hi,
In my world the decimal story goes like this:
TRM3 setpoint values must be decimal and the decimal value must range from 1-9 NOT 0. Nor can it be 00 (integer).
So, your Setpoint value should read 24.1.
Yes strange, but works for me.
Bjorn
Thank you, @satman, for sharing the hint to add decimal digits higher than 1. That works in that way, that openhab now sets the new value for the setpoint (and not jumps back, like it does when sending without that addition) …
… but my problem is, that my thermostat (Z-TRM6) does not receive the new value or at least does not switch to the new value.
Did you also notice such a behaviour and have a further hint for me to get this working?
I remember that TRM3 Setpoint Items were defined default as Number:temperature, which I understood to be a character string. I therefore defined my Setpoint Items as Number only.
Clarification: TRM3 Setpoints accept all decimal values x.1 to x.9 but not x.0. My experience.
From the Debug everything looks good and timely. There is a “SET” and a subsequent “GET” (actually 2) that confirms the SET.Is this a new device that has never worked or one that worked before and stopped? Is the MODE on HEAT? Have you checked all the parameters to make sure the setpoint is looking at the right temperature sensor (floor or internal) and any offsets, etc.?