Welcome to Smart Home Forum by FIBARO
Search the Community
Showing results for tags 'z-trm2'.
I am writing a scene which needs to set the setpoint temperature of my Z-TRM2 thermostats using a LUA command in HC2. I plan to address each thermostat individually, not through heating panels. The current value is succesfully retrieved by this command: fibaro:getValue(id, "value") where id is the id for the setpoint sub-device of the thermostat. This works as expected. However, when I try to change the setpoint through this command: fibaro:call(id, "setValue", "18") nothing happens, as shown by a subsequent getValue call. There is no error message, but the setpoint remains unchanged. I have tried to use the numeral 18 in stead of a string, and I have also tried with a variable name.What am I doing wrong in my fibaro:call command? The syntax is taken from the LUA API documentation, where this example is given: -- 'setValue' action call with one additional parameter fibaro:call(12, 'setValue', '23'); Is the required command for the Z-TRM2 module different?
This comment could also have been placed in the "Third party devices" forum, as it relates to alarms from a HeatIt Z-TRM2 thermostat for floor heating. But the supplier insists that the problem is with the Fibaro HC2, making this the right forum. I have 13 of these thermostats. Occasionally and randomly, I receive a message by e-mail from the HC2: "<Device id> Important! <Device ID> detected high temperature. It may mean potential fire". There is no actual high temperature. What happens, the supplier tells me, is that a single bit (from where?) makes the HC2 think the temperature is 255 C, if only for a split second. This fake measurement is even reported from slave units that have no sensor attached (e.g. a room sensor input not used). Has anyone experienced similar behavior from other devices? False alarms are really annoying! What I plan to do is a) to disable all slave units that are not used, like the room sensors where I use only a floor sensor. I know how to do that - does anyone see a reason not do disable in this case? These units are already hidden. b) to look for ways to disable the entire "high temperature" alarm feature for these units (I have smoke sensors to do that job). How do I disable the alarm feature? c) wait for confirmation from HeatIt/ThermoFloor that their reports to Fibaro have led to a solution, at either end