Welcome to Smart Home Forum by FIBARO
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!
Smart Home Forum by FIBARO Team
Search the Community
Showing results for tags 'delay'.
Found 11 results
Double switch delay at turn on at wall switch
Guest posted a question in Double Switch 2Hello, i had installed a double switch 2 in a two-way curcuit. The function over the Fibaro app and scenes are Ok. But if turn on or off the lights manually with the wall switch there is a delay of reaction/of turning of the lamps of 1 second. Without the double switch there is no delay. Is this a "normal" reaction/restriction with which i have to live or could i change this in parameters of the double switch? Just for info: the double switch is just 2 meters away from the HC2 installed so i think it is not an range promblem. Thank you and best regards
Closed status of Fibaro Door/Window sensor delayed
Twannie posted a question in Door/Window SensorHi I have strange behavior of door windows sensors from Fibaro, with both old and V2 versions When opening a door and then closing it within about upto 30 seconds or so the "closed" status is received with a 10 seconds delay by the HC2 So the door sensor shows "closed" in the HC2 interface exactly 10 seconds after closing and scenes triggered run accordingly. Open status is always, always received without delay!!!! I have a HC2 with 95 physical sensors, zwave traffic is on average each 6.5 seconds (zwave monitor) Can some one help me with this? I am stuck
Delays in blockscenes
Spindel posted a question in Scenes and Interface
Alarm triggering with delay on doors
Azkikr posted a question in Scenes and InterfaceI 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?
Hi all. I have mount a portable Showroom (in a portable case) with a HCL (4.17) that execute scenes in a small tv, led lamps, touchlight switches, and the i-east. The HCL, global cache and i-east devices has been connected in D-Link router too instaled in the case (model DIR610) and work fine since have internet connection, when I disconect the internet cable, devices that have directly conection with router: (Global-Cache, I-east..) have a delay to start the comands from HCL (10s..or more)... I did make tests sending directly commands through the router to global-cache and i-east (with the manufacturer software) with and without internet cable, and both cases work fine.. without problems.... Seems to me that HCL first try reach something in internet... and after execute the commands... does anyone know the reason? and how to fix?
No longer relevant
Skating_vince posted a question in RGBW ControllerNo longer relevant...
[SCENE] triggers unwanted
kunoch posted a question in Scenes and InterfaceI do have a scene to start the TV and another one to automatically shut it down hen all the devices have been set to standby. Now I am facing the following problem that the auto-off scene constantly starts, even the power consumption is at around 100W. What do I do wrong or what do I misunderstand? Auto-OFF should trigger if the TV is ON with a delay of 60s and the power consumption is below 16W with another delay of 60s
Hue light delay
Bodyart posted a question in Other Devices / Third-party devicesHi all, often i see, that some HUE bulbs are not reacting, to commands throu Fibaro, of that Fibaro says, that the bulbs are unreachable. Anyone simmilar experience with it?
philio's delay on HC2
[email protected] posted a question in Other Devices / Third-party devicesHi guys I have problem. Actually Fibaro Double relay switch is weak in case of halogen because of inrush current and arcing at the startup. 1-Which brand do you offer to use instead ? then, I decide to use philio pan04, but it has 1sec delay at the mechanical switches. I mean after you change the momentory switch on the wall, after 1sec lamp turnes on and you see that statuse on the application. 2-How can I solve this problem ? 3-Furthermore, I've heared that no more than 12 pcs of philio relays work with HC2 together. Is it right ? Thanks in advance for answering
Sound siren 30 secs after alarm breached
hetbeest posted a question in Scenes and InterfaceHi all, I just bought a HC and I'm trying to use it (amongst others) as an alarm. I've got a couple of Fibaro motion sensors and some door sensors. I created a magic scene that will sound my siren, an Aeon Labs DSD31 ZW080-C15, when the alarm gets tripped. The problem is that it will react immediately and I would like it to wait for 30 seconds before sounding. I can set it to 2 minutes in a magic scene, but that's way to long. So now for my question... How can I create a (LUA) scene that will sound the siren 30 seconds after the alarm gets tripped? And in such a way that I can stop it from (going to) sound(ing) by disarming the alarm. Thanks for helping me out. Evert
Set value to a doorsensor, lua
Apax posted a question in Scenes and InterfaceHow hard can it be to set a value to 30 from 60 ? delay = fibaro:getValue(28, "alarmDelay"); -- Get time fibaro:debug ("exit delay =" ..delay); fibaro:call(28, "alarmDelay", "30"); --set new time delay = fibaro:getValue(28, "alarmDelay"); -- Get new time fibaro:debug ("new exit delay =" ..delay); But i cant change it, It is still 60