Rudolph

Sorted, just needed a bit of patience and a screen refresh, but LUA worked as planned!

I could not find a reference to this issue on the forum, so I have to ask: Changing a VD setting by fibaro:call(4, "pressButton" , 6) in which ID = 4 for a HomeStatus VD and VD button number = 6 works fine from a scene , but if I change it in: fibaro:call( jT.VD.HomeStatus, "pressButton" , 6) in the LUA of a HeatingOverride VD it does not work. Should it work or am I trying to get a round peg in a square hole ? The goal is to change the HomeStatus automatically to Holiday whenever I program one of the heating zones in the Heating Override VD to Vacation. . And yes, the VD LUA has local jT = json.decode(fibaro:getGlobalValue("HomeTable")); in the header and HomeTable is created correctly.. Your help will be much appreciated! Rudolph

Just to say a thank you to @Sankotronic , @Dave Harrison , , @AutoFrank and all other forum contributors for the sharing done on this forum. After 4 years I was about to ditch my Vera and give up on home automation. Too much time wasted on getting it to work reliably, to much irritation on working with a poor interface. After some research I decided to give it one more try with a HC2 box. Over Xmas I managed to get it to do everything I wanted, and thanks to the much better interface and all available LUA code. tutorials and advice on the forum it took me a lot less time than anticipated (and even less if I would be able to slowly read instruction and type correctly ). HomeTable, Heating Override, BatteryCheck, HomeState, Multiple calls for heating, Timer, all working really nice with some own scenes and VD adaptions. I did not want to spend a lot of time learning LUA ( my first and last programming skills date back from 40 years ago, in ALGOL....) but with examples in hand the odd adaption & modification was doable. I am full aware that no HA solution is perfect, but this does the job for me. Keep the good work going!

Hi Dave, Thanks for the reply and your code, seems spot on to replace the thermostat function of the HR4 ZW in LUA. Will try ASAP and let you know. And I will use your above code for Fibaro thermostatic valves the moment I will add them to the system I am still curious WHY it does is not possible to link the HR4 ZW direct in the HC2 with a regular Fibaro relay actuator ???. And I always assumed as it was a thermostat the logic to compare set point and actual temperature would be in the HRT4 and it would send a simple 1 or 0 signal to the SR302 if it did or did not need the boiler on. How to get this signal read in the HC2 ??? Anyway, I am still very happy to find how much easier things are with the HC2 compared with the VERA!! Ruud

Hi guys, I just upgraded (after 4 long years) from a Vera to a HC2 (4.150 ), and am migrating existing actuators, sensors & logic. I am trying to use existing Horstmann HRT4-ZW thermostat, originally paired with HRT4 ASR-ZW receivers.But as the latter keep breaking and on the Vera were unreliable showing their state I thought of linking them with Fibaro relay switches. Well, I tried several times, also tried the association route, but while I can control the HRT4's fine from the HC2 (set point can be ste and actual temps show up correct ) the relay switch does nada. Now I read somewhere that 4.150 has an issue in this area, but could not find if it was solved. In another thread I found a potential issue with templates, but the device shows: Device kind:com.fibaro.thermostatHorstmann Producer:Horstmann Controls Limited Version:5.0 Configuration:Device configured If a link is a problem I can go the LUA route, but I struggle to get more out of the thermostat than setpoint and actual temperature. How do I extract the value (I assume 0 or 1) that is send to the boiler receiver to start/stop the boiler????? I played with below scene to see if I could find the answer, but I have to admit I am not fluent in LUA, I tend to copy and modify the nice examples I find on forums:) Anybody any suggestions ? --[[ %% properties %% events %% globals --]] fibaro:call(17,"setTargetLevel", "24") local val=(fibaro:getValue(17, "value")) -- curr temp local setp=(fibaro:getValue(17, "targetLevel")) -- target temp local interval=(fibaro:getValue(17, "interval")) local mode=(fibaro:getValue(17, "operatingMode")) local log=(fibaro:getValue(17, "log")) fibaro:debug(val) fibaro:debug(setp) fibaro:debug(interval) fibaro:debug(mode) fibaro:debug(log) response: [DEBUG] 17:51:33: 24 [DEBUG] 17:51:33: 24 [DEBUG] 17:51:33: nil [DEBUG] 17:51:33: nil [DEBUG] 17:51:33: WAITING_FOR_WAKEUP_TO_CONFIGURE