Search the Community

Like several other users, I struggle to customize the Fibaro (iPad) mobile app to suit my needs. The graphical looks is superb, but we are in great need of better configuration and shortcut functionalities. Too many clicks are needed to access the most frequently used devices, scenes or rooms. Too much fancy graphics that will impress my friends, but confuse and annoy my wife. The widgets are however a start and bring scenes to the immediately accessible surface, but it's only a start. Here are a few improvement proposals (or questions, if I have missed some already available obvious solutions). (1) Why limit the number of available widget slots to 6 ? My iPad has a huge fancy empty dark blue screen. I would gladly sacrifice the energy graph or some other elements of graphically pleasing looks but dubious information value. (2) I need to get some of my VDs to the surface. Widgets are limited to Scenes. Any chance I have missed something? (3) I need the icons of the widgets to reflect status. I have found no way to dynamically change this. LUA fibaro: getSelfId() can only pick up VD IDs as far as I been able to confirm. Any solutions out there? Just one simple example: I have a great VD which changes the heating scheme from "Scheduled" to "Holiday" to "Home" status. VDs change icons dynamically. No way to bring this to the dashboard. A bit irritating.

Hi I have problem making scenes for my light outside and hope someone can help me I have one dimmer, one motion detection and light sensor. When it gets dark the light should turn on 30% with the dimmer. If there are some motion the light should go to 90% on the dimmer. After 3 min after last motion it should go again to 30% on the dimmer. When it gets bright again the light should turn off. Gunnar H.

Hey.... Im having problems setting up scenes?? Any support available for this? Thanks

I suddenly have a small problem with my HC2. I have approx 50-60 devices. All kinds of devices like, dimmers, wallplugs. relays, thermostats, rollershutters, sirens, garagedoor controllers etc. Suddenly out of nowhere allmost all my devices change state when some scenes are running. I have made no changes. The scenes are simple block scenes that turns on or off some light in the morning/evening triggered by a timer and a variable. They have been running like this for months. Suddenly when this scenes are triggered all my devices change state. Blinds closes, garagedoors opens, light are turned on. What can cause this? Have tried to restore and older backup. Did not help. Are running ver. 4.130. Anyone have an idea?

L.S. I'd like to request the functionality to open device or a scene by clicking on the device/scene icon, instead or next to the small wrench. This will make working with the devices and scenes much easier. Best regards, Bodyart

Hi , I am using both HC2 and HCL in master slave mode. and i tried to activate alarm panel to take actions in arm mode. first, i selected emergency lights , close blinds and send notification and tested it and it worked good. this situation was before adding any other scenes to the system. i activated the alarm panel in the HC2 (master controller) only . After adding several scenes ( Ex: scenes to open and close lights according to motion detection and LUX in several areas ) , i tried to re test the alarm panel by arming the motion sensors in my system and try to breach any of them. when i did so in the 1st trail only the blinds closed but no notifications sent and the emergency lights did not work as well. i tried to reset the alarm panel and deactivate all actions and re enable it again. when i did so nothing of actions took place. Hint : i have several scenes take place several rimes and always there is notification to alarm that that scenes run sequently more than the number of runs i set in each scene ( 10 times ) my question : is this delay due to these scenes which run a lot or this is a bug in system ? i am using the latest update in both controlled ( not the beta one )

This is feature request with low priority. So i will post it only on forum Better function of clipboarding from debug windows from VD debug window and LUA scene debug window. How it is now works: Succesfull clipboard: Hold left mouse button to select some debug lines and then ctrl+C for copy, while left mouse button is held down. Unsuccesfull clipboard: Hold left mouse button to select some debug lines, release mouse button and then ctrl+C for copy, while left mouse button is holded. What is requested: Hold left mouse button to select some debug lines, release mouse button and then ctrl+C for copy, while left mouse button is holded.

Hi UPDATED 1.1 UPDATED THIS VD FROM A SCENE WATCHDOG TO A SCENE & VIRTUAL DEVICE WATCHDOG Hopefully this will be a useful little VD to some users It was inspired by a comment made by @tinman (I think) This VD Enables a user to scan all scene and virtual device DEBUG MESSAGES and trigger on predefined key words in the debug messages. This may be useful to see if a scene develops an error or perhaps you are just looking for a keyword for a different reason All scenes and virtual devices are included by default Specific scenes and virtual device id's can be flagged to exclusion Separate watch lists for scenes and virtual devices A watchdog report is sent for all matches identified. Can be sent via email or smart message hub You get one email or message per id flagged ( not per watch word) It will send message if no match in either vd or scene is found (added in v 1.1) Suggested icon included below Note: If you use the Smart Message Hub please add that scene ID into the exclusion list as that scene will be flagged by the watchdog after the first use. This can be run on demand or on a schedule using Main Scene by @Sankotronic or similar. I run it on a schedule once per day Installation Import the VD Configure the following as required -- user configurable local jT = json.decode(fibaro:getGlobalValue("HomeTable")) -- comment out if HomeTable is not used watchListSC = {"syntax", "error", "line334", "concatinate"} -- words that you want to watch in scenes watchListVD = {"expected", "unfinished"} -- words that you want to watch in virtual devices excludeList = {"23", "32"} -- scene and virtual device id's that you would like to exclude from watching SMsgH = true -- set to false if you don't use smart message hub SMsgHtarget = "pushover" -- set to preferred medium if you use smart message hub deBug = false -- enable for greater debug verbosity Place on a scheduler if required The VD has a status label and when it was last run and this is what the report looks like on pushover VD attached scvd_Watchdog_1.1.vfib

Hi All, Probably a really stupid question and i think i know how to resolve this, But with my scenes i get notifications telling me "Too many Instances" - I know on the scene you can type in the max number of instances - however what does this actually mean ?, I can run it more than "2" times or whatever the prescibed max number is. I'm assuming this is one of those things you want to set a parameter up that zeros it on a daily basis ? however have no idea how to do this, anyone able to walk me through an example please. Thanks in advance

Hello guys, Am I wrong or JSON body (in REST API) changed its structure in 4.122? I just came to it by testing Zipato RFID keypad in block scenes and wondered why it's not working . I believe, that Triggers and Action werent there on 4.120? Can anybody chcek it? I have 4.122 everywhere and i don't want to downgrade. Also i do not thing, that using capitals in in property values in an API is good idea. See property "runConfig". { "id": 114, "name": "test", "type": "com.fibaro.blockScene", "roomID": 0, "iconID": 5, "runConfig": "DISABLED", "alexaProhibited": true, "autostart": false, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": true, "isLua": false, "properties": "", "triggers": { "properties": [ { "id": 549, "name": "value" } ], "globals": [], "events": [], "weather": [] }, "actions": { "devices": [ 549 ], "scenes": [], "groups": [] }, "liliStartCommand": "\"\"", "liliStopCommand": "\"\"", "sortOrder": 135, "lua": "--[[\n%% properties\n549 value\n%% weather\n%% events\n%% globals\n--]]\n\nlocal startSource = fibaro:getSourceTrigger();\nif (\n ( tonumber(fibaro:getValue(549, \"value\")) == 255 )\nor\nstartSource[\"type\"] == \"other\"\n)\nthen\n\tfibaro:call(549, \"secure\");\nend\n\n", "html": "<span id=\"hiddenFields\">\n<input name=\"lastAddedGroup\" id=\"lastAddedGroup\" type=\"hidden\" value=\"5\">\n<input name=\"lastAddedElementGroup_1\" id=\"lastAddedElementGroup_1\" type=\"hidden\" value=\"3\">\n<input name=\"thenBlockPosition\" id=\"thenBlockPosition\" type=\"hidden\" value=\"2\">\n<input name=\"lastAddedElementGroup_2\" id=\"lastAddedElementGroup_2\" type=\"hidden\" value=\"1\"><input name=\"lastAddedElementGroup_3\" id=\"lastAddedElementGroup_3\" type=\"hidden\" value=\"3\"><input name=\"lastAddedElementGroup_4\" id=\"lastAddedElementGroup_4\" type=\"hidden\" value=\"1\"><input name=\"lastAddedElementGroup_5\" id=\"lastAddedElementGroup_5\" type=\"hidden\" value=\"0\"></span>\n<div class=\"SceneAreaSection\" id=\"sceneGroup_1\">\n<span id=\"sceneGroupList_1\"><img class=\"scene_bracket_left\" id=\"group_1_element_0\" src=\"../img/bracket_left.png\"><div class=\"scene_device\" id=\"group_1_element_1\" name=\"group_1_element_1\"><input name=\"elementtype_group_1_element_1\" id=\"elementtype_group_1_element_1\" type=\"hidden\" value=\"device\"><input name=\"elementid_group_1_element_1\" id=\"elementid_group_1_element_1\" type=\"hidden\" value=\"549\"><div class=\"scene_device_head\"></div><div class=\"scene_device_centrum\"><div class=\"scene_device_dropdown\"><a onclick=\"xreopenAddDevicesWindow(1, 1, 'editScene'); return false;\" href=\"#\"><span class=\"txt\" id=\"deviceName_group_1_element_1\">Klávesnice</span><img style=\"margin: 8px 0px 0px 10px; float: left;\" src=\"../img/dziubek.png\"></a></div></div><div class=\"scene_device_tail\"></div></div><div class=\"scene_order\" id=\"group_1_element_2\"><input name=\"elementtype_group_1_element_2\" id=\"elementtype_group_1_element_2\" type=\"hidden\" value=\"operator\"><input name=\"elementid_group_1_element_2\" id=\"elementid_group_1_element_2\" type=\"hidden\" value=\"549\"><div class=\"scene_order_head\"></div><div class=\"scene_order_centrum\"><select name=\"select_group_1_element_2\" class=\"scene_order_dropdown\" id=\"select_group_1_element_2\" onchange=\"onSelectChange(this); onOperatorChange(this);\"><option value=\"4\">==</option><option value=\"29\">Není rovno</option></select></div><div class=\"scene_order_tail\"></div></div><div class=\"scene_action\" id=\"group_1_element_3\"><input name=\"elementtype_group_1_element_3\" id=\"elementtype_group_1_element_3\" type=\"hidden\" value=\"deviceValue\"><input name=\"elementid_group_1_element_3\" id=\"elementid_group_1_element_3\" type=\"hidden\" value=\"13\"><div class=\"scene_action_head\"></div><div class=\"scene_action_centrum\"><select name=\"select_group_1_element_3\" title=\"Zavřeno\" class=\"scene_action_dropdown\" id=\"select_group_1_element_3\" style=\"float: left; \" onchange=\"onSelectChange(this);\" data-device-type=\"com.fibaro.doorLock\" data-device-id=\"549\"><option value=\"12\">Otevřeno</option><option selected=\"selected\" value=\"13\">Zavřeno</option></select><select name=\"doorLockUser_group_1_element_3\" class=\"scene_dropdown\" id=\"doorLockUser_group_1_element_3\" style=\"margin-left: 8px; display: none;\" onclick=\"reGenerateDoorLockUsersOptions(this, 549)\" onchange=\"onSelectChange(this);\"><option selected=\"selected\" value=\"0\">Jakýkoliv uživatel</option></select><span id=\"handValue_group_1_element_3_RGBW\" style=\"display:none;\"><span class=\"Txt scene_RGB_label\">R:</span><input name=\"handValue_group_1_element_3_R\" class=\"scene_input rgbw_input\" id=\"handValue_group_1_element_3_R\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">G:</span><input name=\"handValue_group_1_element_3_G\" class=\"scene_input rgbw_input\" id=\"handValue_group_1_element_3_G\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">B:</span><input name=\"handValue_group_1_element_3_B\" class=\"scene_input rgbw_input\" id=\"handValue_group_1_element_3_B\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">W:</span><input name=\"handValue_group_1_element_3_W\" class=\"scene_input rgbw_input\" id=\"handValue_group_1_element_3_W\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"></span><select class=\"scene_order_dropdown hidden \" id=\"handValue_group_1_element_3_property_value\" style=\"margin-left: 10px;\"></select></div><div class=\"scene_action_tail\"></div><div class=\"scene_time_centrum\"><div class=\"scene_time_dropdown\" style=\"float: left; padding: 2px 10px 2px 8px;\"><input name=\"valueTime_group_1_element_3\" class=\"scene_input\" id=\"valueTime_group_1_element_3\" style=\"width: 40px;\" onkeyup=\"positiveNumbersOnly(this); onInputChange(this);\" type=\"text\" value=\"0\"><span class=\"txt\" style=\"margin: 2px 0px 0px 4px;\">s</span></div><div class=\"scene_time_tail\"></div></div></div></span>\n<div class=\"scene_add_remove\">\n<a title=\"Odebrat poslední prvek\" id=\"deleteButtonGroup_1\" onclick=\"xremoveElementFromScene(1, document.getElementById('lastAddedElementGroup_1').value, 'editScene'); return false;\" href=\"#\"><img style=\"float: left; margin-right: 10px;\" src=\"/fibaro/img/remove.png\"></a>\n<a title=\"Přidat další prvek\" id=\"addButtonGroup_1\" onclick=\"setNoLua(); setLua(0); setClickedPosition(this); xgenerateFullMenu(1, 'editScene'); return false;\" href=\"#\"><img class=\"addButtonGroup\" style=\"float: left;\" src=\"/fibaro/img/add.png\"></a>\n</div><img class=\"scene_bracket_right\" id=\"group_1_element_bracket_right\" src=\"../img/bracket_right.png?v=1494339732339\">\n<div class=\"hr0\"></div>\n</div>\n<div class=\"SceneAreaSection\" id=\"sceneGroup_2\"><span id=\"sceneGroupList_2\"> </span><div class=\"scene_order\" id=\"group_2_element_1\"><input name=\"elementtype_group_2_element_1\" id=\"elementtype_group_2_element_1\" type=\"hidden\" value=\"operator\"><input name=\"elementid_group_2_element_1\" id=\"elementid_group_2_element_1\" type=\"hidden\" value=\"3\"><div class=\"scene_order_head\"> </div><div class=\"scene_order_centrum\"><select name=\"select_group_2_element_1\" title=\"A\" class=\"scene_order_dropdown scene_order_dropdown_operators\" id=\"select_group_2_element_1\" onchange=\"checkSceneOperatorChange(2); onSelectChange(this);\"><option value=\"1\">A</option><option value=\"2\">Nebo</option><option selected=\"selected\" value=\"3\">Pak</option></select></div><div class=\"scene_order_tail\"> </div></div><input name=\"selectOldValue_group_2_element_1\" id=\"selectOldValue_group_2_element_1\" type=\"hidden\" value=\"3\"></div><div class=\"SceneAreaSection\" id=\"sceneGroup_3\"><span id=\"sceneGroupList_3\"> <img class=\"scene_bracket_left\" id=\"group_3_element_0\" src=\"../img/bracket_left.png\"><div class=\"scene_device\" id=\"group_3_element_1\" name=\"group_3_element_1\"><input name=\"elementtype_group_3_element_1\" id=\"elementtype_group_3_element_1\" type=\"hidden\" value=\"device\"><input name=\"elementid_group_3_element_1\" id=\"elementid_group_3_element_1\" type=\"hidden\" value=\"549\"><div class=\"scene_device_head\"></div><div class=\"scene_device_centrum\"><div class=\"scene_device_dropdown\"><a onclick=\"xreopenAddDevicesWindow(3, 1, 'editScene'); return false;\" href=\"#\"><span class=\"txt\" id=\"deviceName_group_3_element_1\">Klávesnice</span><img style=\"margin: 8px 0px 0px 10px; float: left;\" src=\"../img/dziubek.png\"></a></div></div><div class=\"scene_device_tail\"></div></div><div class=\"scene_order\" id=\"group_3_element_2\"><input name=\"elementtype_group_3_element_2\" id=\"elementtype_group_3_element_2\" type=\"hidden\" value=\"operator\"><input name=\"elementid_group_3_element_2\" id=\"elementid_group_3_element_2\" type=\"hidden\" value=\"549\"><div class=\"scene_order_head\"></div><div class=\"scene_order_centrum\"><select name=\"select_group_3_element_2\" class=\"scene_order_dropdown\" id=\"select_group_3_element_2\" onchange=\"onSelectChange(this); onOperatorChange(this);\"><option value=\"7\">=</option></select></div><div class=\"scene_order_tail\"></div></div><div class=\"scene_action\" id=\"group_3_element_3\"><input name=\"elementtype_group_3_element_3\" id=\"elementtype_group_3_element_3\" type=\"hidden\" value=\"deviceValue\"><input name=\"elementid_group_3_element_3\" id=\"elementid_group_3_element_3\" type=\"hidden\" value=\"4\"><div class=\"scene_action_head\"></div><div class=\"scene_action_centrum\"><select name=\"select_group_3_element_3\" title=\"Otevřít\" class=\"scene_action_dropdown\" id=\"select_group_3_element_3\" style=\"float: left; \" onchange=\"onSelectChange(this);\" data-device-type=\"com.fibaro.doorLock\" data-device-id=\"549\"><option value=\"3\">Otevřít</option><option selected=\"selected\" value=\"4\">Zavřít</option></select><select name=\"doorLockUser_group_3_element_3\" class=\"scene_dropdown\" id=\"doorLockUser_group_3_element_3\" style=\"margin-left: 8px; display: none;\" onclick=\"reGenerateDoorLockUsersOptions(this, 549)\" onchange=\"onSelectChange(this);\"><option selected=\"selected\" value=\"0\">Jakýkoliv uživatel</option></select><span id=\"handValue_group_3_element_3_RGBW\" style=\"display:none;\"><span class=\"Txt scene_RGB_label\">R:</span><input name=\"handValue_group_3_element_3_R\" class=\"scene_input rgbw_input\" id=\"handValue_group_3_element_3_R\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">G:</span><input name=\"handValue_group_3_element_3_G\" class=\"scene_input rgbw_input\" id=\"handValue_group_3_element_3_G\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">B:</span><input name=\"handValue_group_3_element_3_B\" class=\"scene_input rgbw_input\" id=\"handValue_group_3_element_3_B\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"><span class=\"Txt scene_RGB_label\">W:</span><input name=\"handValue_group_3_element_3_W\" class=\"scene_input rgbw_input\" id=\"handValue_group_3_element_3_W\" onkeyup=\"onInputChangeDevice(this,549);\" type=\"text\" value=\"0\"></span><select class=\"scene_order_dropdown hidden \" id=\"handValue_group_3_element_3_property_value\" style=\"margin-left: 10px;\"></select></div><div class=\"scene_action_tail\"></div><div class=\"scene_time_centrum\"><div class=\"scene_time_dropdown\" style=\"float: left; padding: 2px 10px 2px 8px;\"><input name=\"valueTime_group_3_element_3\" class=\"scene_input\" id=\"valueTime_group_3_element_3\" style=\"width: 40px;\" onkeyup=\"positiveNumbersOnly(this); onInputChange(this);\" type=\"text\" value=\"0\"><span class=\"txt\" style=\"margin: 2px 0px 0px 4px;\">s</span></div><div class=\"scene_time_tail\"></div></div></div></span><div class=\"scene_add_remove\"><a title=\"Odebrat poslední prvek\" id=\"deleteButtonGroup_3\" onclick=\"xremoveElementFromScene(3, document.getElementById('lastAddedElementGroup_3').value, 'editScene'); return false;\" href=\"#\"><img style=\"float: left; margin-right: 10px;\" src=\"../img/remove.png\"></a><a title=\"Přidat další prvek\" id=\"addButtonGroup_3\" onclick=\"setClickedPosition(this); xgenerateFullMenu(3, 'editScene'); return false;\" href=\"#\"><img class=\"addButtonGroup\" style=\"float: left;\" src=\"../img/add.png\"></a></div><img class=\"scene_bracket_right\" id=\"group_3_element_bracket_right\" src=\"../img/bracket_right.png?v=1494339732339\"></div><div class=\"SceneAreaSection\" id=\"sceneGroup_4\" style=\"display: none;\"><span id=\"sceneGroupList_4\"> </span><div class=\"scene_order\" id=\"group_4_element_1\"><input name=\"elementtype_group_4_element_1\" id=\"elementtype_group_4_element_1\" type=\"hidden\" value=\"operator\"><input name=\"elementid_group_4_element_1\" id=\"elementid_group_4_element_1\" type=\"hidden\" value=\"549\"><div class=\"scene_order_head\"> </div><div class=\"scene_order_centrum\"><select name=\"select_group_4_element_1\" class=\"scene_order_dropdown scene_order_dropdown_operators\" id=\"select_group_4_element_1\" onchange=\"checkSceneOperatorChange(4); onSelectChange(this);\"><option value=\"1\">A</option><option value=\"2\">Nebo</option><option value=\"3\">Pak</option></select></div><div class=\"scene_order_tail\"> </div></div><input name=\"selectOldValue_group_4_element_1\" id=\"selectOldValue_group_4_element_1\" type=\"hidden\" value=\"1\"></div><div class=\"SceneAreaSection\" id=\"sceneGroup_5\" style=\"display: none;\"><span id=\"sceneGroupList_5\"> </span><div class=\"scene_add_remove\"><a title=\"Odebrat poslední prvek\" id=\"deleteButtonGroup_5\" style=\"display:none;\" onclick=\"xremoveElementFromScene(5, document.getElementById('lastAddedElementGroup_5').value, 'editScene'); return false;\" href=\"#\"><img style=\"float: left; margin-right: 10px;\" src=\"../img/remove.png\"></a><a title=\"Přidat další prvek\" id=\"addButtonGroup_5\" onclick=\"setClickedPosition(this); xgenerateFullMenu(5, 'editScene'); return false;\" href=\"#\"><img class=\"addButtonGroup\" style=\"float: left;\" src=\"../img/add.png\"></a></div></div>" }

Hi guys, I seem to be missing something very basic... And wonder if anybody could give me a pointer. I want to do something as simple as this. 1) When movement is detected: Turn on the light 2) When there has been no movement for x seconds: Turn off the light (where x will be different for the different areas, e.g. from 15 seconds to 5 minutes) So I create two scenes (using the graphic blocks) 1) Turn on lights, (IF motion == Breached 0s) THEN (Turn on Lights) 2) Turn off lights. (IF Motion == Safe 60s) THEN (Turn off lights) But very frequently in my log, I see "Too many instances of the turn-off scenes". Which got me thinking. If I understand correctly, a new instance of 2) will be started every the sensor triggers that motion stops. So If I'm in the scene, and then move again within 60 seconds, scene 1) will be triggered again (but doing nothing, as the light is already on). When I stop moving again, yet another instance of 2) will be started. And then eventually, the max number of triggers are reached, which causes the error. The longer the timeout is, the more possible instances of 2) may be running. So I guess I could increase the number of instances, but is this really a good idea? Or am I going about this the wrong way? Should I instead create a LUA (which I haven't tried yet, but have a lot of programming experience), with the following two scenes: 1) Scene motion (motion == breached) Set global variable motion = yes if (number of instances > 1) exit Turn on lights while (variable motion == yes) wait 10 seconds while end turn off lights 2) No-motion (motion == safe 60s) set global variable motion = no Thanks for any advice on this. John Erik

Hi All, I'm new to all of this, Have a HC2 , also have a Harmony Remote along with a few sono's speakers. I was looking to create my first scene using the Motion sensor to essentially play music on my sonos if it gets triggered during certain times of the day, however everytime i try creating a scene the Sonos device doesnt show up, nor does any of my Harmony remote options ? I'm assuming i'm doing something wrong or does this kind of stuff need to be done via LUA (i can't code btw- but might have to start learning)

Hi! Have you tried to run a scene with danalock V2 in HC2? I can lock and unlock the door with signle command button on HC2. But whene I try t do the same command in scene (Open/Close) I can't do it. When the scenes run nothing happen. thanks.

Updated Aug 2018 Now that my setup is reaching an amount of stability and it is getting to where I want it I decided I would update my setup post and also structure it a bit better. The core of my automation system if I exclude all the AV equipment is as follows HC2 runnnig 4.18. Approximately 102 z-wave devices and about 20 Sonoff wifi devices running Tasmota RPi running sonos http-api and HA Bridge, RPi running Unifgi Controller, RPI running octpprint fro 3d printer control, SPC Gateway for Siemens Alarm integration 4 IP cameras, 6 Echo Dots, 14 sonos zones, GC-100-12 for IR control over all media devices (TV, Media Sources, Projector,, etc), HDMI Matrix Automatic Dust collection system in garage (3d printed blast gates, limits switches with wemos D1 mini monitoring inputs and smart control switching of vacuum system) Room setup I have the usual rooms across ground floor, first floor, garage and outside I also have a section called System with the following rooms where i have all my scenes and VD's (more details on this below) Control – manual control of house stuff, Settings – Where I can tweak the automation, Status – display various system status stuff, Automation – only used by other scenes/VD, Alexa – only used by Alexa Development – stuff I’m working on Critical Scenes and VD’s Main Scene – master scheduler & Hometable – used to track id’s of scenesm, VD’s and devices and custom icons Timers + Sunset/Sunrise + weather courtesy of Sankotronic SCVD Watchdog scene - monitors for error or stopped VD and restarts them, monitors for specific debug messages and clears them if required Smart message Hub – used for main events that I want to know happen (alarm on/off, house modes, etc) Multiple Data Loggers – used for background tasks that I can check if I need to (keep clutter out of message Hub) Network device Monitors & State Table to track network devices status and system state information Lights in critical areas are automated as well as music and media, the rest is manual when needed. House modes can override automated settings (entertain mode changes behavior of garden, patios, bbq area lights) Some of what I have running is... Morning audio greeting in our bedroom and the kids bedroom, weather, temp in house, time, etc (our alarm clock!) 2. After greeting it groups players, selects a radio station, checks if it's available and if not selects another one Starting music in the kids bedrooms for night time. I also check periodically if the radio station available and restarts the radio station or selects another one if not available. Announcements for when fridges or freezers go over temp One button click for night, welcome back, leaving home (music, lights, TV, music adjustment + audible greeting ( time and temp of house on arrival) open zones on leaving, Zone Inihibit leaving and night options if windows are left open TV switch on in the playroom switches off the music, camera snapshops of front gates when they are opened/close Use of MP3 clips that systems uses instead of Polly TTS if internet is offline ... and the list goes on System Overview

Hi, After I put together the Virtual devices Introduction Tutorial I was asked would I do something similar for Scenes. I’ll preface this post (like the Virtual devices) that I am no expert but I am willing to document what I understand and it can be added to over time. It would be great if some of the experst could read through, fill in the coupelof gaps and let me know if I havesomething wrong or coudl do with better explanation I also start at a very basic level as some of the newer users people liked that with the virtual device tutorial I am also only going to Lua scenes as I have never worked with Magic Scenes or Graphics Blocks Scene Basics A scene is a mechanism to execute a lua code script for an on-demand basis. General Tab Name, Room - self explanatory ID – set when the scene is saved, doesn’t change for life of scene. This is the unique identifier for this scene and can be used as part of the startScene command fibaro:startScene (ID) Max number of instances – A scene can be called from a number of different sources. This dictates how many instance of the scene can be running concurrently. This can also be set within the scene using lua. I’m not sure if these two settings are in conflict which one takes priority. if (fibaro:countScenes()>2) then fibaro:abort() end -- or if (fibaro:countScenes()>1) then fibaro:debug("stop scene") fibaro:abort() end Lili commands – voice control for running/stopping scene using Lili who is the native HC2 personal assistant. Run Scene Automatic – it can be called from other scenes or run manually Manual – it can be called from other scenes or run manually (unsure what the difference is between manual and automatic) Disabled – scene cannot be run Scene Hidden: Not visible in the Web UI (unless you select HC2 hidden devices) Protect by Pin: Prompted for PIN CODE if scene is set to running Do Not Alarm to Stop: ??? Change Icon – select a new icon to display alongside the scene (128x128 png transparent) Advanced Tab Lua Window The code in the lua window is the defaulst header for any scene and needs to be kept. Debug window (debug output from scene code when it is run) START – Start the script running STOP – Stop the script running CLEAR – Clear the debug window Web UI View 1. Title of scene 2. Edit 3. Delete (confirmation req) 4. Icon 5. Disable/enable 6. Run/Stop scene 7. Status – populated by fibaro:log command Lua Scene Header The header of a scene always contains some of all of the following. These are used to trigger the scene in a number of different way. --[[ %% autostart %% properties %% events %% globals --]] %%autostart – including this means that the scene will run when it is saved or when the HC2 restarts. $$ properties – the user can add a device ID and parameter. Any change to this parameter will trigger/run the scene. The format is ID following by parameter. --[[ %% autostart %% properties 1429 value %% events %% globals --]] In the example above if 1429 was a door sensor and value was the status parameter that changed (0 <-> 1) when the door opened than any status change would cause the scene to run. This has to be the device ID and cannot be a variable that represents the ID %%events – ?? %%globals – the user can add the name of global variable (exactly and case sensitive). Any change to the value of the global variable will trigger/run the scene An example would be --[[ %% autostart %% properties %% events %% globals G_AREA__1 --]] A scene can be setup to trigger from properties, events or global variables The following code allows a different action depending on the trigger if this is what’s required. -- Trigger Management local currentDate = os.date("*t") local startSource = fibaro:getSourceTrigger() --Start of Scene Execution if (startSource["type"] == 'property') then fibaro:debug("Started through property") tempFunc1() -- this is calling the the function if something happens. elseif (startSource["type"] == 'global') then fibaro:debug("Started through variable") tempFunc2() -- this is calling the the function if something happens. elseif (startSource["type"] == "autostart") then fibaro:debug("Started through autostart") tempFunc3() -- this is calling the the function if something happens. elseif (startSource["type"] == "other") then fibaro:debug("Started through other ") tempFunc4() -- this is calling the the function if something happens. else fibaro:debug("Scene not started, this can only be started through other, property, global or autostart!"); end In the example above the following happens Scene triggered from property (1425 value) - it will execute function1() Scene triggered from global variable(sleepState) - it will execute function2() Scene triggered from an autostart - it will execute function3() Scene triggered from any other valid method - it will execute function4() or else the scene will no start Local Variable declaration These are variables tha you intend to use within the scene. You can also use global variable but these do not need to be declared prior to usage Many people put the local variable declaration at the start of the scene followed by the functions -- example of local variable declaration local HC2email = "true" -- Notification Alerts using Fibaro email service local HC2popUp = "true" -- Notification Alerts using Fibaro popup service notifications local pushOver = "false" -- Notification Alerts using Pushover Notification Service (Tutorial by AutoFrank) local ALLINONE = "false" -- Notification Alerts using 'All in one Notification' scene (created by jompa68) local updateData = "false" -- Set to true to update the data in the table. ** SET BACK TO FALSE ONCE COMPLETE ** Code Comments Comments /explanations in the code are very useful as the allow you to explain what the code is doing to either yourself or others You need to preface or encapsulated all comments to prevent them being executed at runtime. Example of single line and multi-line comments are shown below -- Example of a single line comment --[[ example of a multiline comment where the sentence spans one or more lines in the scene --]] In general all scenes will have the following structure but over time most people develop your own style … --[[ %% autostart %% properties %% events %% globals --]] if (fibaro:countScenes()>2) then fibaro:abort() end -- explanation of the code purpose or usage or installation -- local variable declarations -- functions -- Main Code sequence (calling the functions above) Lua command syntax is generally the same whether it is used in a scene or used in a virtual device (exceptions to this are http requests) Some useful lua command if fibaro:getGlobalValue("Occupancy_HOUSE") == "no" -- compare global value if fibaro:setGlobal("Alarm_TrigCount", "0") then -- setting global value if tonumber(fibaro:getValue(GardenSensor, "value")) == 1 -- get device status value fibaro:startScene(AlarmSet) -- Start a scene fibaro:call(1387, "pressButton", 10) -- press a button on a vd fibaro:debug("Notify Alert! "..jN[i].device.." is offline") -- print a mix of variable and text string fibaro:call(2, "sendEmail","Alert!", "Garden Sensor triggered") -- send email using HCC2 native email service -- HC2 native popup notirfication service HomeCenter.PopupService.publish({ title = 'Home Alarm Activated ', subtitle = os.date("%I:%M:%S %p | %B %d, %Y"), contentTitle = 'Zones Status', contentBody = fibaro:getGlobalValue("G_SPC_AREA_STATUS_1"), type = 'Success', }) Some useful lua functions ENCODING - replace a space in a string with another character, a + symbol in the example below This function takes one parameter - s so The Cat and the Mat will be changed to The+Cat+and+the+Mat -- function to replace a space in a text string with a + function urlencode(s) if (s) then s = string.gsub (s, "\n", "\r\n") s = string.gsub (s, "([^%w ])", function (c) return string.format ("%%%02X", string.byte(c)) end) s = string.gsub (s, " ", "+") end return s end test = urlencode(message) ROUNDIT Rounds a number to a defined number of decimal places This function takes one parameter - num (the number you want rounded) and idp (the number of decimal places) so roundit(2.12348, 3) would result in 2.123 function roundit(num, idp) local mult = 10^(idp or 0) return math.floor(num * mult + 0.5) / mult end If there are any other useful functions that you feel would be of benefit to new users please let me know and I'll include them Overall the best way to gain a greater understanding is to download the many scenes that are published to the forum and start to take them apart. I hope this will be of benefit to some users and suggestions and corrections are always welcome happy coding -f

Hi, I am considering HCL to replace my VeraLite, which suddenly went dead... Majority of tasks I expect are simple, so HCL would satisfy this. But I have a bit complex one with heating: I currently have 8 thermostats in different rooms. Those are working indepently based on their program using scenes. For instance: Living rooms temperature is during Weekend from 7:00 to 20:00 is 22 degrees and from 20:00 to 7:00 19 degrees and 22 degrees from 16:00 to 20:00 + 19 degrees from 20:00 to 16:00 during Working day. Similarly for bedroom, bathroom, etc. So far I understand HCL would support this. However, I am using something like multiple button for defining modes like Home, Holiday, Weekend off, etc. This is the first selection and based on this above described scenes are running. So the sample with the Living room applies for Home, but for Holidays the temperature is 15 degrees, for Weekend off 17 degrees till Sunday 15:00 and 22 degrees after. Is HCL relativelly easily able to manage this? I am not a programmer and I am using PLEG in Vera, but how it is this solveable in HCL? HC2 is 2x more expensive than HCL and HCL is 2x expensive than Vera, so it is my concern...

Hi, I have external lights. I use geolocation with ifttt. When I arrive near my house my lights turn on automatically. But it must light up when it is dark. At sunset. I created one variable : I created 3 scenes. First scene : --[[ %% autostart %% properties %% weather %% events %% globals --]] local sourceTrigger = fibaro:getSourceTrigger(); function tempFunc() local currentDate = os.date("*t"); local startSource = fibaro:getSourceTrigger(); if ( ( ((currentDate.wday == 1 or currentDate.wday == 2 or currentDate.wday == 3 or currentDate.wday == 4 or currentDate.wday == 5 or currentDate.wday == 6 or currentDate.wday == 7) and string.format("%02d", currentDate.hour) .. ":" .. string.format("%02d", currentDate.min) == fibaro:getValue(1, "sunsetHour")) ) ) then fibaro:setGlobal("ext", "1"); end setTimeout(tempFunc, 60*1000) end if (sourceTrigger["type"] == "autostart") then tempFunc() else local currentDate = os.date("*t"); local startSource = fibaro:getSourceTrigger(); if ( startSource["type"] == "other" ) then fibaro:setGlobal("ext", "1"); end end My first scene Sets my variable to 1 when the sun goes down My second scene sets my variable to 0 when the sun rises. --[[ %% autostart %% properties %% weather %% events %% globals --]] local sourceTrigger = fibaro:getSourceTrigger(); function tempFunc() local currentDate = os.date("*t"); local startSource = fibaro:getSourceTrigger(); if ( ( ((currentDate.wday == 1 or currentDate.wday == 2 or currentDate.wday == 3 or currentDate.wday == 4 or currentDate.wday == 5 or currentDate.wday == 6 or currentDate.wday == 7) and string.format("%02d", currentDate.hour) .. ":" .. string.format("%02d", currentDate.min) == fibaro:getValue(1, "sunriseHour")) ) ) then fibaro:setGlobal("ext", "0"); end setTimeout(tempFunc, 60*1000) end if (sourceTrigger["type"] == "autostart") then tempFunc() else local currentDate = os.date("*t"); local startSource = fibaro:getSourceTrigger(); if ( startSource["type"] == "other" ) then fibaro:setGlobal("ext", "0"); end end And My third scene that executes the lighting of my lights when ext = 1 and that the sun goes down. --[[ %% properties %% weather %% events %% globals ext --]] local startSource = fibaro:getSourceTrigger(); if ( ( tonumber(fibaro:getGlobalValue("ext")) == tonumber("1") ) or startSource["type"] == "other" ) then fibaro:call(32, "turnOn"); end I have a problem, It makes day or night my scene of lighting my lights work all the time. I don't understand. One idea ? if you can help me please. Thx.

hi, This tutorial is based on an idea that i believe originated to @cag014 some time back and has been adopted by many. So well deserved kudos to @cag014 and others that helped originate and develop the concept. I am merely a scribe that has benefited from this. I decided to write a quick tutorial for two reasons... I implemented this over christmas and and found it very useful and much easier than I thought It would appear that we have some new forum members that got HC2 devices from Santa The core of this approach is to store all the reference ID's to your devices, virtual devices, scenes, etc in a json encoded table. The references like jT.kitchen.light are used in the scene or vd and device ID can easily be changed in the table. One important benefit is that it you need to exclude/include a device the device ID will change. With this approach you simple change the reference in the Home table and your done. Without this approach you wll need to go through your code and change the device ID where appropriate. ** This doesn't get over the need to enter ID as triggers in the scene headers as fibaro doesn't allow variable in the header ** The solution has two parts to it. The home table itself where the data is stored. - this is held in a predefined variable (lower part of variables panel) The references in your scenes and virtual devices use this table HOME TABLE This can be created and maintained through either a scene or a virtual device. I chose a VD but there is no advantage I can thing of using one way or the other. Go to Panel, Variables Panel and create a new predefined variable (lower part of panel) called HomeTable. When you create a predefined variable it has two values. Name the variable and save. Edit the variable and simply delete the second value. Using either a scene or a vd create your table and store it. This is lua from my VD. I create one button and enter the code below. The top part shows the format of the table. I opted to place each element I am looking to store into rooms and/or other natural groupings but you can choose any way to structure. I'll attached a copy of my full table at the end of this to show what I use it for. The next part encodes and stores the data The last part is where I read back one entry to show the table stored okay. -- HOME TABLE FOR ALL DEVICES, SCENES ETC. jsonHome = { hall = { Lights=88,Lamp=1421,Temp=1,Motion=1,Humidity=1,Lux=1,ZRC90=1447,SmallBathLight=147,SmallBathMotion=1, SmallBathTemp=1,SmallBathLux=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, kitchen = { Pendant=176,Table=174,Spotlights=90,Temp=1549,Motion=1548,Humidity=1551,Lux=1550,UV=1552,XmasLight=1531, WineFridgeTemp=1,Dishwasher=1,rcTV=1490,rcSonos=1561,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, } jHomeTable = json.encode(jsonHome) -- ENCODES THE DATA IN JSON FORMAT BEFORE STORING fibaro:setGlobal("HomeTable", jHomeTable) -- THIS STORES THE DATA IN THE VARIABLE fibaro:debug("global jTable created") -- STANDARD DEBUG LINE TO DISPLAY A MESSAGE -- I then like to read back a entry from the table to show that the table didnt get corrupt in the process. local jT = json.decode(fibaro:getGlobalValue("HomeTable")) -- REFERENCE TO DECODE TABLE fibaro:debug(jT.kitchen.Motion) -- DISPLAY ONE VARIALE the output of this when I click the button (or run the scene is as follows) It is reading back the ID (1548) stored for Motion under the kitchen grouping I would recommend using an external editor like Notepad++ or Zerobrane to edit/manage the code in the vd and then copy back to the vd when ready to update as the HC2 lua editor is very small At this stage you now have your table REFERENCING THE TABLE CONTENTS IN YOUR SCENES AND VIRTUAL DEVICES For this you need to place the following line of code in each scene or vd local jT = json.decode(fibaro:getGlobalValue("HomeTable")) and then use references instead of device ID's in the scene code. The easiest way to explain this is with an example. This scene switches on a light in my kitchen if it is dark, motion is detected and no light is on already --[[ %% properties 1548 value %% events %% global --]] local jT = json.decode(fibaro:getGlobalValue("HomeTable")) -- KITCHEN AUTOLIGHTS if (tonumber(fibaro:getGlobalValue("Darkness")) == 1 ) and (tonumber(fibaro:getValue(jT.kitchen.Motion, "value")) > 0 ) and (tonumber(fibaro:getValue(jT.kitchen.Spotlights, "value")) == 0 ) and (tonumber(fibaro:getValue(jT.kitchen.Pendant, "value")) == 0 ) and (tonumber(fibaro:getValue(jT.kitchen.Table, "value")) == 0 ) and (tonumber(fibaro:getValue(jT.sunroom.Light, "value")) == 0 ) and (tonumber(fibaro:getValue(jT.sunroom.Lamp, "value")) == 0 ) then fibaro:call(jT.kitchen.Pendant, "setValue", "40") UpdateEventLog("kitchen lights auto on") end It's easy enough to see how the references are built up if you examine the scene v the table at the top of this post and that it !! Addition: If you need to adjust a single parameter in the table you can use the following. This can be useful if you don't want to adjust one value and then copy the whole table back into the vd and update or more useful if you want to adjust the value in the fly in a script. -- NEW PARAMETER VALUE jT.kitchen.Motion=2000 -- TO SAVE THE CHANGE jSonosTable = json.encode(jT) fibaro:setGlobal("SonosTable", jSonosTable) fibaro:debug("global jTable created") Hopefully this will help some users If you have any suggestions as to how to improve this please let me know and I'll edit -frank ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Copy of my table to show how flexible this approach can be jsonHome = { system = { Sunset_SunRise=1560,houseStatus=1507,alarmStatus=881,HouseTemps=1236,sonosSummary=1407,sonosTTS=1452, sonosSequences=1536,TVSequences=1545,lightingSequences=1534,powerConsump=1484,specialHouseMode=1538 }, hall = { Lights=88,Lamp=1421,Temp=1,Motion=1,Humidity=1,Lux=1,ZRC90=1447,SmallBathLight=147,SmallBathMotion=1, SmallBathTemp=1,SmallBathLux=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, playroom = { Light=84,TVLight=1438,XmasLight=1518,Motion=1595,Temp=1596,rcPlayroomTV=1487,rcSonos=1574,Lux=1597,Humidity=1598,UV=1598,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, living_room = { Light=231,libraryLight=164,libraryTopSocket=166,Temp=1584,Lamp=1423,Lux=1585,Motion=1583,Humidity=1,UV=1,TVLight=1499,XmasLight=1513,rcSonos=1,rcLivingRoomTV=1506,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, utility_room = { Light=141,Temp=1194,Motion=1270,Humidity=1,Lux=1,UV=1,FreezerTemp=1,Washer=1,Dryer=1 }, equipment_rack = { RackSummary=1453,Rack1Temp=1192,Rack2Temp=1193,fanUpper1=1432,fanLower2=1434,powerAmpLower=1269, powerAmpUpper=1267,heatingFlowTemp=1199,rcSatBox=1491,SatBoxPresets=1492,rcHdmiMatrix=1489,rcAppleTV=1539, rcAppleTvSystem=1540,rcBluRay=1544,rcDroidBox=1541,networkMonitor=1493,avDeviceMonitor=1494,haDeviceMonitor=1495,hc2Resources=1391 }, kitchen = { Pendant=176,Table=174,Spotlights=90,Temp=1549,Motion=1548,Humidity=1551,Lux=1550,UV=1552,XmasLight=1531, WineFridgeTemp=1,Dishwasher=1,rcTV=1490,rcSonos=1561,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, sunroom = { Light=172,Lamp=6,projectionScreenPower=1509,rcProjector=1542,rcProjectorScreen=1543 }, dining_room = { Light=25,Lamp=1,Motion=1,Temp=1202,Lux=1,Humidity=1,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, pizza_bbq_area = { CenterLights=253,Spotlight=710,Lanterns=712,HeaterSwitch=255,LEDLights=238,Motion=705,Heaters=250,Temp=1,Lux=1, Humidity=1,rcSonos=1,PizzaBbqCam=761,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, garage = { Light=895,BenchLight=1,DoorOpener=80,DoorStatus=778,Temp=1578,Humidity=1590,Lux=1589,Motion=1587,UV=1591, GarageControl=1559,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, driveway = { porchLight=68,pillarLights=145,Spotlight=893,Motion=1429,GateTemp=958,GateOpener=94,GateStatus=956,GateControl=1537,DrivewayCam=1556,FrontDoorCam=1557 }, back_garden = { patioLight=64,utilityLight=76,sidePatioLights=60,boundaryLights=62,Spotlight=58,Motion=1427,Humidity=218,Lux=217,Temp=958,XmasLight=1523,BackGardenCam=1558 }, hotpress = { Light=143,DoorStatus=888,Temp=890 }, bathroom = { Light=162,MirrorLight=1468,MirrorDemist=1470,Temp=1170,Humidity=1,Motion=1 }, guest_bedroom = { Light=31,Lamp=718,Temp=1588,Motion=1587,Lux=1589,Humidity=1590,UV=1591,BathLight=1,BathTemp=1,BathMotion=1,BathHumidity=1,BathFan=1,BathMirrorLight=1460,BathMirrorDemist=1462,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, master_bedroom = { Light=56,LampDad=29,LampMum=1,Temp=1,Motion=1247,Lux=1, Humidity=1,BathLight=1,BathTemp=871,BathMotion=870,BathHumidity=1,BathLux=872,BathFan=1,BathMirrorLight=1464,BathMirrorDemist=1466,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, lau_eth_bedroom = { Light=52,Temp=1185,Motion=1253,Lamp=1440,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, frank_bedroom = { Light=54,Temp=1200,Motion=1255,Lamp=1450,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, office = { Light=33,Temp=1186,Motion=1251,Lamp=720,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, Landing_Stairs = { stairsLight=92,landingLight=168,rcSonos=1,TTS_message="",TTS_volume=10,RadFav=3,IsPlaying=1,nowPlaying="",vol=1,clip="" }, scene = { MainScene=614,AlarmControl=598,rebootHC2=593,goodMorning=463,goodNight=331,LeavingHome=483,welcomeHome=488,quietMorning=499,kidsToBed=490,plaroomTvOn=580,firstFloorMusicOn=579,firstFloorAllOff=578, hallSceneControl=519,StairsLight30=556,GateOpen5=526,GateOpenHold=361,GateOpenClose=425,DumpEventLog=565,PlayroomOff=617 }, vd = { AlarmManagement=881,TVPresets=1545,SonosTTS=1452,LightPresets=1534,HouseModeExt=1538,SonosPresets=1536,RackTempMngt=1453,MediaSourcePresets=1567,JhomeTable=1566,GateControl=1537,GarageControl=1559 }, users = { admin=2,frank=1564,sylvia=1565 }, ios = { frankS6=993,sylviaS7=1526,frankipad=1532,sylviaipad=1533 }, IsOnline = { GlobalCache=1,SatBox=1,AppleTV=1,AndroidBox=1,TVPlayroom=1,TVKitchen=1,TVLiving=1,Projector=1,HC2=1,SynNAS=1,AlarmGateway=1,AlarmPanel=1,SonosAPI=1,DrivewayCam=1,GardenCam=1,FrontDoorCam=1,PizzaBBQCam=1,Internet=1,USG=1,HouseAP=1,GarageAP=1 }, }

Hope someone can help on it I have the problem that some lights doesn't switch off and some randomly switch on. In detail: I have an ON Scene and an OFF Scene for the lights. They are triggered by Motion Sensor. I can see after the Motion Sensor is save again, the OFF scene is running, after a while it's not running anymore and the light is still on. The thing is it happens only sometimes, but too often. Here is an OFF Scene: --[[ %% properties 262 value 97 value %% events %% globals CRLED --]] --CR_LED_OFF ID 156 local date = os.date( '*t' ) local time = tonumber( string.format( '%02d%02d', date.hour , date.min ) ) local startSource = fibaro:getSourceTrigger(); if(startSource["type"] == "other") then fibaro:call(28, "turnOff"); else if (( tonumber(fibaro:getValue(262, "value")) == 0 ) --Motion Dressroom and ( tonumber(fibaro:getValue(97, "value")) == 0 )) --Motion Bedroom then setTimeout(function() local delayedCheck0 = false; local tempDeviceState0, deviceLastModification0 = fibaro:get(262, "value"); if (( tonumber(fibaro:getValue(262, "value")) == 0 ) and (os.time() - deviceLastModification0) >= 120) then delayedCheck0 = true; end local delayedCheck1 = false; local tempDeviceState1, deviceLastModification1 = fibaro:get(97, "value"); if (( tonumber(fibaro:getValue(97, "value")) == 0 ) and (os.time() - deviceLastModification1) >= 120) then delayedCheck1 = true; end local startSource = fibaro:getSourceTrigger(); if ( ( delayedCheck0 == true and delayedCheck1 == true and fibaro:getGlobalValue("CRLED") == "Active" ) or startSource["type"] == "other" ) then fibaro:call(28, "turnOff"); --Light Changeroom end end, 2*60000) --delay 2min end end ******************************************************************************** BTW I'm sure and double confirm the variable CRLED is Active Here is an ON Scene: --[[ %% properties 262 value %% events %% globals CRLED Mode --]] --CRBF_LED_ON 150 local startSource = fibaro:getSourceTrigger(); if ( ( tonumber(fibaro:getValue(262, "value")) > 0 ) --Motion Dressroom and ( fibaro:getGlobalValue("CRLED") == "Active" and ( fibaro:getGlobalValue("Mode") == "Day" or fibaro:getGlobalValue("Mode") == "Evening" )) or startSource["type"] == "other" ) then fibaro:call(28, "turnOn"); --LED ON end

I am trying to create a day/night setup via lua. Where at 8 am-10pm the variable is set to day and at 10pm-8am the variable is set to night. I cannot successfully do this via a block scene so i have used LUA to do this. Could someone help me look over my code to see if this is correct as i am fairly new in LUA. Thanks! --[[ %% autostart %% properties %% globals --]] -- Only need to call getSourceTrigger once -- For better debugging, I moved it to the top, -- before countScenes local sourceTrigger = fibaro:getSourceTrigger() fibaro:debug("Script started because of: " .. sourceTrigger["type"]) if fibaro:countScenes()>1 then fibaro:debug("Scene already running, aborting this one") fibaro:abort() end if (sourceTrigger["type"] == "autostart") then while true do local currentDate = os.date("*t") -- Do the time-string manipulation thingy here, instead of in -- each and every if-then statement -- %02u means unsigned int, 2 wide, leading zero TimeAsString = string.format("%02u",currentDate.hour).. ":" .. string.format("%02u", currentDate.min) fibaro:debug("TimeAsString: ".. TimeAsString) Day_night = fibaro:getGlobalValue("Day_night") fibaro:debug("Day_night: " .. Day_night) if ( currentDate.wday == 1 or currentDate.wday == 2 or currentDate.wday == 3 or currentDate.wday == 4 or currentDate.wday == 5 or currentDate.wday == 6 or currentDate.wday == 7 ) and TimeAsString == "8:00" then fibaro:debug("Setting scenario number 1") fibaro:setGlobal("Day_night", "Day") elseif ( currentDate.wday == 1 or currentDate.wday == 2 or currentDate.wday == 3 or currentDate.wday == 4 or currentDate.wday == 5 or currentDate.wday == 6 or currentDate.wday == 7 ) and TimeAsString == "22:00" then fibaro:debug("Setting scenario number 2") fibaro:setGlobal("Day_night", "Night") else fibaro:debug("Current time doesn't match any scenario") end end fibaro:debug("Scene not started, this is autostart-only!") end -- end of sourceTrigger["type"] == "autostart"

Hi Forum, Owning a Fibaro HC2 with some dimmers, switches and door sensors for a few years, and since a few days also a Fibaro Swipe. Can someone help me on the way how I can program (via blocks?) with 1 swipe to control 3 dimmers? Not only switching on or off, or opposite state, but also controlling the dimming level. I guess a variable needs to be adressed first where you select 1 of the 3 dimmers (liek left is dimmer 1, up is dimmer 2 and right is dimmer 3). But then how can I, as a next step, control the dimmer level with the circuler gesture. (directly to 1 dimmer I can do it, but so far not for 3 dimmers). Thanks for all your help! Chris

I'd like to see an optional parameter added that will disable triggering scenes when setting a global variable in LUA. The HTTP API has this functionality albeit in reverse (default to false) Something along the lines of: fibaro:setGlobal( varName, value [, invokeScenes] ) Where: varName: The name of the global variable value: The new value of the global variable invokeScenes: Boolean, default true

I understand that the plugin in HC2 is only to enable manual control of lights from the HC2 and from the Fibaro App. Are there any other ways I could include one or more hue lights into scenes? Any coding? Anything else before I have to throw a large investment I made in hue lights or instead the Fibaro one? Many thanks for your support.

hi guys, yesterday I wanted to upgrad from 4.080 to 4.082. After the upgrade finished, I had only 5 devices left of my previous 43 devices. I tried to load the backup, that was automatically created. Same result 5 devices only. I then went back to 4.080 with recovery mode. Loaded the backup and again 5 devices only. If I go back further, where I had 31 devices only, everything is restored as expected. But ofcourse not all devices are there then. When the restore of the 43 devices Backup finishes, i can see breefly a message telling somithing like: finished removing dead devices ... Now my question, how can I get my devices back without having to: exclude them from the z-wave pull them out from wall-covers all over the house move them close to the main controller to include them again move them back to their places across the house correct all the IDs in my szenes find a solution to prevent this happening again I'm happy for any help/hints to get things up and running again. Thank you, kro

I just got some smart bulbs and created some scenes to trigger the lights to come on as soon as i enter the room (the motion sensor detects motion). But i notice by the time i walk in the room there is some lag (about 3-5 seconds) before the lights turn on. How can i get them to turn on faster? is it possible? I have a relatively small home and these devices are about 50 feet from the controller with multiple walls in between but i have an extender between the controller and these bulbs and motion sensors. Any help would be appreciated. thanks.