Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Search the Community

Showing results for tags 'scenes'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

Found 75 results

  1. Hi All, Please guide me to right way to get args in scene on HC3 HC2 code to get scene args was: local args = fibaro:args() on HC3 it not working now Tried: local args = fibaro.args() -> got error: attempt to call a nil value (field 'args') local args = fibaro:args(). -> got error: attempt to call a nil value (method 'args') LUA editor don't show any functions containing "args".... Help, please... Thanks
  2. As has been re-iterated many many times on this forum, there are two methods of updating a slider in a virtual device from a scene or another VD: Using fibaro:call(device, "setProperty", "ui.sliderX,value", value) causes the numerical value of the slider to be updated, but not the length of the slider bar. Neither does it execute the code behind the slider. Using fibaro:call(device, "setSlider", X, value) causes the numerical value and the length of the slider to be updated,, and executes the code behind the slider. In both cases, "device" is the ID number of the VD, "X" is the slider reverence number and "value" is the new slider value (0-100). Generall, option 2 is preferred because everything is updated. However, there seems to be an issue if the VD has more that nine sliders. Executing a few lines of test code for each of the methods illustrates this. First, method 1. Executing this code: local device = fibaro:getSelfId() local sliderString1 local sliderString2 local numSliders = 13 fibaro:debug('-----------------------------------------------------------') fibaro:debug('--Set Sliders----------------------------------------------') for i = 1, numSliders do sliderString1 = ('ui.Slider' .. tostring(i) .. '.value') fibaro:call(device, "setProperty", sliderString1, tostring(i)) fibaro:debug('Slider ' .. tostring(i) .. ' = ' .. tostring(i)) end fibaro:debug('--Read Sliders---------------------------------------------') for i = 1, numSliders do sliderString1 = ('ui.Slider' .. tostring(i) .. '.value') sliderString2 = fibaro:getValue(device, sliderString1) fibaro:debug(device .. ', ' .. sliderString1 .. ' = ' .. sliderString2) end Gives: [DEBUG] 16:21:04: --Set Sliders---------------------------------------------- [DEBUG] 16:21:04: Slider 1 = 1 [DEBUG] 16:21:05: Slider 2 = 2 [DEBUG] 16:21:05: Slider 3 = 3 [DEBUG] 16:21:05: Slider 4 = 4 [DEBUG] 16:21:05: Slider 5 = 5 [DEBUG] 16:21:05: Slider 6 = 6 [DEBUG] 16:21:05: Slider 7 = 7 [DEBUG] 16:21:05: Slider 8 = 8 [DEBUG] 16:21:05: Slider 9 = 9 [DEBUG] 16:21:05: Slider 10 = 10 [DEBUG] 16:21:05: Slider 11 = 11 [DEBUG] 16:21:05: Slider 12 = 12 [DEBUG] 16:21:05: Slider 13 = 13 [DEBUG] 16:21:05: --Read Sliders--------------------------------------------- [DEBUG] 16:21:05: 1044, ui.Slider1.value = 1 [DEBUG] 16:21:05: 1044, ui.Slider2.value = 2 [DEBUG] 16:21:05: 1044, ui.Slider3.value = 3 [DEBUG] 16:21:05: 1044, ui.Slider4.value = 4 [DEBUG] 16:21:05: 1044, ui.Slider5.value = 5 [DEBUG] 16:21:05: 1044, ui.Slider6.value = 6 [DEBUG] 16:21:05: 1044, ui.Slider7.value = 7 [DEBUG] 16:21:05: 1044, ui.Slider8.value = 8 [DEBUG] 16:21:05: 1044, ui.Slider9.value = 9 [DEBUG] 16:21:05: 1044, ui.Slider10.value = 10 [DEBUG] 16:21:05: 1044, ui.Slider11.value = 11 [DEBUG] 16:21:05: 1044, ui.Slider12.value = 12 [DEBUG] 16:21:05: 1044, ui.Slider13.value = 13 As would be expected. However executing a code snippet using method 2, like this: local device = fibaro:getSelfId() local sliderString1 local sliderString2 local numSliders = 13 fibaro:debug('-----------------------------------------------------------') fibaro:debug('--Set Sliders----------------------------------------------') for i = 1, numSliders do fibaro:call(device, "setSlider", tostring(i), tostring(i)) fibaro:debug('Slider ' .. tostring(i) .. ' = ' .. tostring(i)) end fibaro:debug('--Read Sliders---------------------------------------------') for i = 1, numSliders do sliderString1 = ('ui.Slider' .. tostring(i) .. '.value') sliderString2 = fibaro:getValue(device, sliderString1) fibaro:debug(device .. ', ' .. sliderString1 .. ' = ' .. sliderString2) end Give this: [DEBUG] 16:43:02: --Set Sliders---------------------------------------------- [DEBUG] 16:43:02: Slider 1 = 1 [DEBUG] 16:43:02: Slider 2 = 2 [DEBUG] 16:43:02: Slider 3 = 3 [DEBUG] 16:43:02: Slider 4 = 4 [DEBUG] 16:43:02: Slider 5 = 5 [DEBUG] 16:43:02: Slider 6 = 6 [DEBUG] 16:43:02: Slider 7 = 7 [DEBUG] 16:43:02: Slider 8 = 8 [DEBUG] 16:43:02: Slider 9 = 9 [DEBUG] 16:43:03: Slider 10 = 10 [DEBUG] 16:43:03: Slider 11 = 11 [DEBUG] 16:43:04: Slider 12 = 12 [DEBUG] 16:43:04: Slider 13 = 13 [DEBUG] 16:43:04: --Read Sliders--------------------------------------------- [DEBUG] 16:43:04: 1044, ui.Slider1.value = 10 [DEBUG] 16:43:04: 1044, ui.Slider2.value = 11 [DEBUG] 16:43:04: 1044, ui.Slider3.value = 12 [DEBUG] 16:43:04: 1044, ui.Slider4.value = 13 [DEBUG] 16:43:04: 1044, ui.Slider5.value = 5 [DEBUG] 16:43:04: 1044, ui.Slider6.value = 6 [DEBUG] 16:43:04: 1044, ui.Slider7.value = 7 [DEBUG] 16:43:04: 1044, ui.Slider8.value = 8 [DEBUG] 16:43:04: 1044, ui.Slider9.value = 9 [DEBUG] 16:43:04: 1044, ui.Slider10.value = 10 [DEBUG] 16:43:04: 1044, ui.Slider11.value = 11 [DEBUG] 16:43:04: 1044, ui.Slider12.value = 12 [DEBUG] 16:43:04: 1044, ui.Slider13.value = 13 Which is clearly wrong. Is this a bug, or have I done something really dumb (if so please enlighten me). If it is a bug, does a workaround exist? TIA.
  3. Hi all Is there a fibaro killscene and startscene command similar to hc2? Thanks
  4. Hello, I need a help. I can see more ways od forum and marketplace for override heating zone, but they are to complicated for me. I need simple scene (or virtual device??) which will set all heating zones to specific temperature for specific time and after that back to schedule. Why I need this? I have central heating system with wood and water acumulation puffer. Sometimes temperature in system increase to high and for security reasons I need to cool down system. I made scene which control temperature in system and send me notification when temperature is too high. Notification ask me if I want to run some scene. Here I want to open all radiators. Or, if somebody have another idea, maybe I don't need override heating zone. I have Fibaro heat controller on all radiators, but I don't know how to open it to max with scene. Thank you in advance.
  5. Hi, Pretty basic question but I have searched the forum (and web) and not been able to find any solution that can help me. I have created a variable, Home_Away with two values; Home and Away. I then built two simple block scenes that says says that if a wall plug is ON it should switch to HOME (and OFF gives AWAY). I have then a ZRC-90 remote controller that puts the wall plug in in on (button 1) and off (button 2) mode. So far so good. I have then tried multiple times and in different ways to build a simple scene that should run and turn on a window light at a certain time when I'm not home (when I'm home I want to control the light myself). I have then built an additional scene that should turn the light off automatically at a fixed time when I'm not home. This doesn't work the way I want it at all... For instance, if the light is off and I put the wall plug in off (Away) mode the light still turns on - I don't want it to turn on until both conditions are met (time and variable). Adding to this is that the scene to turn it off doesn't seem to work either so I guess I'm missing some fundamental part here? Scene to turn on light below: Scene to turn off light below I can also add that my intention is to continue building from this logic to have multiple lightning scenes that only runs when the house is in Away mode. Many thanks in advance for any type of guidance!
  6. 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
  7. cag014

    All about icons

    Version 3.1

    4,251 downloads

    Did some rework on Fibaro and Aeon sensors icons and few others The stand alone sensor icon actually has a little human figure stand still (white color) to use as part of inactive motion icon. Added linear icons
  8. Dear gentleman, I have a problem with making a scene for ARM/DISSAR the system using the smart implant. I want to mention that my alarm system it is not a smart one. I will describe what I have done till now. I installed 2 relay on the alarm PGM exits to know the status of the system and to have a feedback if the alarm is activated. I use the smart implant as follow: 1. The OUT1 is connected to the ON/OFF impulse in order to ON and OFF the system. Each impulse will ON or OFF the system 2. The IN1 is connected as switch on the ARM/DISARM status. Basically if the relay it is open the system is DISARM and if relay is closed the system is ARM. 3. The IN2 is connected as switch for the thief alarm. Basically if the system it is ARMED and someone enter in the house this relay will be CLOSED and get a feedback. Relay = ON - ALARM and relay = OFF - NO ALARM Till now it is ok and it is works. My question is the scene. I did not succeed to make a correct scene. What I want to make it is next: 1. ARM the SYSTEM scene 2. DISARM the system scene To ARM the SYSTEM i've made a scenario like: if IN1= breached then OUT1 = On ... and the fibaro arm the system. To DISARM the SYSTEM it is similar - if IN1= safe then OUT1 = On the problem is that the system goes in to a loop. To avoid that I put a one time trigger like - OnceEg. Run Scene on 23/4/2024 at 12:30 at beginning of each scene. So in this case the system will not go on the loop but it seems that there is a mistake in my logic scheme because the if I run DISARM scene even if the IN1 is safe (meaning that the system it is already disarmed) the OUT1 give the ON impulse and arm the alarm. Please guys, be so kind and give me a solution. Thank you.
  9. I have three rooms with a Dimmer 2 in each. The dimmers are activated from motion detectors in each room. While cleaning I'd like to have the lights at full output and I have set parameter 19 to 90%. When activating the toggle switch the lights will go to 90% but when the motion sensor see a motion it will activate the scene dimming the lights to 8%. Is it possible to make S1 override all scenes as long as it is on? At the moment I turn the motion sensors towards the wall so they aren't activated but that is no sophisticated solution!
  10. Hello seniors and comrades, i have a virtual device for iEast stream pro and i would like to Use the Playlist Function buttons to play Music in my Scenes but i have no idea how to do it. i don't know how to make and add music in the playlists. i can only play through USB Button function. i have tried searches but nothing, and this forum is my only hope i got. Lua Code in the Playlists: -- Play Preset #1 local command = "/httpapi.asp?command=MCUKeyShortClick:1"; local selfId = fibaro:getSelfId(); local ip = fibaro:get(selfId, 'IPAddress'); local port = fibaro:get(selfId, 'TCPPort'); local connection = Net.FHttp(ip, port); connection:GET(command) fibaro:call(selfId, "setProperty", "ui.labelState.value", "[preset 1]"); See the attached is my VD for iEast Stream Pro Looking forward for your kindness and help. Thank you all.
  11. 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
  12. Several posts on this forum recommend including a check in LUA scenes to ensure that only one instance of the scene is currently running. The recommended code is similar to this: if fibaro:countScenes() > 1 then scenes = fibaro:countScenes() fibaro:debug(os.date("%d %b").." Scenes active "..scenes) fibaro:abort(); end The main panel for each scene, however, includes a parameter controlling max. running instances: Why is it necessary to include the extra code, if this parameter already limits the scene to one active instance? Is it only to get the explicit warning from the fibaro:debug() command?
  13. Good Day All, I'm new to Fibaro and have purchased a HCL on the confirmation from Fibaro support that it would wllow me to Open and Close Fakro Windows and Blinds through Google Assistant. I've have limited success with this and queries to Fibaro support have been met with stonewalling after the sale was made. They pointed me to the help files, which are not the easiest to follow and are inconsistent but none the less, it seems as if all is set up as required by Help. I cannot get the Hey Google, talk to Fibaro command to work. The boomy Fibaro voice cannot find any devices. It can find the HCL, but noting attached. Support did say that this was due to the fact that they are "security devices" 🙄 A Window Blind? Stonewalling I think. Hopefully someone here may have encountered something similar and knows a solution? Attached is a screenshot of the 4 scenes I have setup in HCL Next are two screen shots showing the configuration of Blinds Evening which is similar to Blinds Morning – both of these scenes are visible in my Google Assistant and I can successfully activate them by saying “Hey Google, activate Blinds Evening” for example. Blinds Evening and Morning are created using Graphics Blocks while Blinds Open and Close are created using Magic Scenes. Next are screen shots of the Blinds Open scene (which is the same as Blinds Close except reated using Magic Scenes) – these do not show in Google Assistant - Can't figure out why. As you can see below, the Blinds Evening and Blinds Morning Scenes show up in for Google Assistant but not the Blinds Open or Close. Even if I copy the existing Blinds Morning or Blinds Evening Scenes (created using Graphics Blocks), giving the copied instances a new name, they still do not show up for Google Assistant. Lastly is a screen shot of all my devices: Here are examples of the configuration of 1 each of the blind and Skylight The scenes I have set up for morning and evening trigger all blinds from the HCL itself. My goal is to be able to activate Blind 1 – 4 (open & close) and Skylights 1 – 4 (open & close) - all individually from my Google Assistant through voice by saying “Hey Google, open Roof Light 1” for example. Has anyone cracked something like this before? Any tips are appreciated. Regards, Eamon.
  14. I have found using Hue lights through HC2 quite challenging. Although the Hue AIO VD helps a lot, it still is not as easy as i would hoped when i bought my HC2. I also have experience with Homey and home assistant. Both controllers have an option to call/start scenes that are defined in the philips hue app. For example; i have 5 Hue lights in my living room. I have a couple of scenes defined in the Hue app, 1 for warm white generic light, 1 for when we watch a movie, etc. With Home and HA i was able to start those scenes, so when i would want to change a scene, i do it in the Hue app (which is 10x more user-friendly then changing a Hue scene in HC2), and then homey or HA is able to call that (changed) scene. Can i somehow call those scene's in HC2?
  15. I found this image in the knowledge base but I can not "easily" add any activity the my harmony hub to the scene. The only way is via LUA?
  16. I have created different scenes in the block scene editor. These are all working except for the one that should do the following: 1. When I arm the alarm, the door sensor is armed. 2. When I open the door it should give me 10 seconds before the alarm goes off. 3. If I disarm the alarm, therefore disarm the door sensor within 10 seconds the alarm should not go off. This all works fine with a minor detail: if I shut the door within 10 seconds the alarm does not go off, while it should go off unless I have disarmed the alarm. I have tried the following block scene: First I tried stating at the device that if it's armed and breached it should trigger and I put a 10 second delay at the end. That did not work. Then I tried the above method checking if the door is device is triggered while armed and breached AND if after 10 seconds the device is NOT disarmed. By the way I also tried the statement if after 10 seconds it IS armed. Both with the same result: If I close the door quickly enough, I'm inside and the alarm is not triggered. Then I thought that maybe it just does not work that well within the block scenes. So I transfered it to LUA (automatic method by Fibaro). The LUA code I get, looks horrendous though. I'm not a developer, but this does not look as very well written code to me. --[[ %% properties 200 value 200 armed %% weather %% events %% globals --]] local startSource = fibaro:getSourceTrigger(); if(startSource["type"] == "other") then fibaro:call(49, "turnOn"); fibaro:call(104, "turnOn"); fibaro:startScene(12); fibaro:call(203, "sendDefinedPushNotification", "4"); fibaro:call(207, "sendDefinedPushNotification", "4"); setTimeout(function() fibaro:call(49, "turnOff"); fibaro:call(104, "turnOff"); end, 900000) else if (( (tonumber(fibaro:getValue(200, "value")) > 0 and tonumber(fibaro:getValue(200, "armed")) > 0) ) and ( tonumber(fibaro:getValue(200, "armed")) ~= 0 )) then local delayedCheck0 = false; if ( (tonumber(fibaro:getValue(200, "value")) > 0 and tonumber(fibaro:getValue(200, "armed")) > 0) ) then delayedCheck0 = true; end setTimeout(function() local delayedCheck1 = false; local tempDeviceState1, deviceLastModification1 = fibaro:get(200, "value"); if (( tonumber(fibaro:getValue(200, "armed")) ~= 0 ) and (os.time() - deviceLastModification1) >= 10) then delayedCheck1 = true; end local startSource = fibaro:getSourceTrigger(); if ( ( delayedCheck0 == true and delayedCheck1 == true ) or startSource["type"] == "other" ) then fibaro:call(49, "turnOn"); fibaro:call(104, "turnOn"); fibaro:startScene(12); fibaro:call(203, "sendDefinedPushNotification", "4"); fibaro:call(207, "sendDefinedPushNotification", "4"); setTimeout(function() fibaro:call(49, "turnOff"); fibaro:call(104, "turnOff"); end, 900000) end end, 10000) end end So here I am, with the big question to you out there: is there anyone who has this working and what code do you have?
  17. Hello friends, I would like to control my sonos devices via scenes. It seems not possible to do that with common ways. So maybe someone in this forum already did that via http methods, rest apis etc. Would be great help if someone has any idea about that. Thanks in advance.
  18. Jeg driver og setter opp scenes for ID-Lock 150, og med varsling for ulike brukere på døra. Det funker bra med f.eks. pushvarsel når brukeren taster inn PIN kode, men jeg får ikke til å sette opp varsel for bruk av RFID brikke. I scenen kan du velge "PIN entered by", og så i neste boks velge "RFID brikke XXXXX". Jeg laget en scene hvor første valget var PIN entered by, og så i neste blokk PIN Kode XXXX, satte opp et OR argument med samme opplegg, men da valgte jeg RFID brikke XXXX. Får varsel når PIN kode trykkes - men ikke når RFID brikken brukes.
  19. After having done a few scenes (LUA scripts) I am a little confused by some of the options offered by the HC2 interface. Here are three examples: 1. The overview Some of this is obvious, like the scene name and the number of instances currently running. But why do the last two scenes, both running, show different run/stop buttons? And what does the on/off slider signify? I have successfully started scene 3, even though it shows "off". I have also tried to set it to "on", but it goes back to "off". Question: How are these two buttons, on/off and run/stop to be interpreted and used? 2. The detailed view This view raises several questions: Category: Is this category ever used for anything? Max running instances: In my LUA scripts I normally include tests like this: if fibaro:countScenes() > 1 then ... to abort the script if more than one is running. Does that make this number insignificant? Run scene Manual/Automatic: The trigger in the LUA script (or a lack of trigger) dictates how the scene is started. For a standard manual script without trigger, what difference does the man/auto setting make? And for a script with %%autostart is it necessary to set the Run scene selector to Automatic as well? Do not allow alarm...: My interpretation is that all scenes that are alarm related should check this box, all other scenes should not. By alarm related, I mean scenes that are triggered by an alarm. Is this good practice?
  20. Hi team, I have been trying to work with a fibaro door contact and time of day being the criteria to turn on some devices. Unfortunately, it is taking the door contact and for some reason ignoring the criteria for the time of the day. Here are a couple of screenshots of the settings for your to look at.
  21. it's possible to integrate HC2 with an ip-camera by specifying URL:s for the video stream and controlling it with left/right/up/down URL:s etc. This is one-way communication from HC2 to the camera. Now, some cameras can be armed/disarmed, which means that it will start to record when it detects motion. The idea is that this should trigger an alarm in HC2. My idea is to have a scene which can arm/disarm the camera and then, when the camera detects motions it should trigger a scene in HC2. Has anyone figured out how to trigger a scene in HC2 when the camera detects motion? Is there any kind of support for this? Also, is it possible to arm/disarm your camera through HC2?
  22. I'm completely new to scene creator's, and i Wonder if someone could help me out With a start... I would be happy if someone could post me some examples of Block scenes for: A wall plug turning off after a period of time, and then send SMS/push Notification to a cell phone.... Door changes status from locked to open - turn one/several lights on and send SMS/push Notification to cell phone This would be a start for me
  23. Hello Fibaro team, Internet as we speak is transforming towards more and more use of HTTPS and TSL. My question is simply, is there a timeplan for HC2 to transfer from HTTP to HTTPS also on the local site access solution? I understand there can be difficulties with the certificates...... For example, I would prefer to send an HTTPS request to HC2 for starting scenes or altering status on a device, where username and password are protected with TSL transmission. Kindly, DrPepper
  24. Hi, I create a pop-up notification, which works well, except the button does not trigger my scene. I double and tripple checked the scene, add more or less buttons, tried different scenes, but nothing works. If I hit the button on the pop-up it only disappears, but no scene is triggered. Is there anyone can help on it? Do I need to set anything else in the HC2? or the pop-up scene? My scene is as follows: I also confirm that the scene for the button is working. --[[ %% properties %% events %% globals --]] local imgUrl = 'http://192.168.1.200/fibaro/icons/scena/User1043.png' local currentDate = os.date("*t"); --[[ if (fibaro:countScenes() > 1) then fibaro:abort() end --]] -- opening the pop-up window, HomeCenter.PopupService.publish({ -- title – required field, title = 'Laundry', -- subtitle – optional field, subtitle = string.format("%02d:%02d:%02d | April %02d, %04d", currentDate.hour, currentDate.min, currentDate.sec, currentDate.day, currentDate.year), -- Title of the pop-up content (optional), contentTitle = 'Laundry is ready', -- Content of the pop-up – required field, contentBody = 'Please confirm', -- Image of the notification (acceptable formats - .jpg, .png, .bmp), img = imgUrl, -- Notification type: ('Info' – blue color, 'Success' – green color, 'Warning' – yellow color, 'Critical' – red color) type = 'Info', -- defying buttons – ‘caption’ – text of the button, sceneId – Id of scene that will be started after clicking on button (0 – no scene will be started), you can defy up to 3 buttons, in default there will be a button with ‘Ok’ buttons = { { caption = 'OK', sceneId = 285 } } }) thanks for helping
  25. when creating a scene I get the message 403 ACCESS FORBIDDEN. None of mye scenes are working anymore, and I cannot create new ones. I have deleted the old scenes and restarted the Home center lite but does not help. Any solutions anyone??
×
×
  • Create New...