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 'scene'.

  • 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
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

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

  1. Czy ktoś może podpowiedzieć jak stworzyć scenę w której z określonym interwałem czasowym centrala wyśle powiadomienie push z informacją o aktualnej wartości czujnika? Chciałbym aby klient raz na dzień dostawał info jaka jest wilgotność powietrza, ponieważ jest to ważne dla odpowiedniego utrzymania jego drewnianej podłogi. ____________ Can anyone suggest how to create a scene in which, with a specific time interval, HC3 will send a push notification with information about the current sensor value? I would like to receive information about the air humidity once a day, because it is important for the proper maintenance of client wooden floor.
  2. Hello, iam implementing automated heating which would consider weather temperature forecast for heating. Unfortunatelly although everything works fine iam not able to get forecast from ope weather. Everything works when i send same request using browser but as soon as i send it through Lua. API returns 401 Invalid API key. See yourself: local openWeatherAPIKey = "xyxyxy" -- You need to fill this out function process_heating() -- inside here i have implementation of heating itself, not interesting... end local location = api.get("/settings/location") local lat = location.latitude or 0 local lon = location.longitude or 0 local locStr = "lat="..lat.."&lon="..lon local opts = "&units=metric&cnt=1&appid="..openWeatherAPIKey local fullRequestUrl = "http://api.openweathermap.org/data/2.5/forecast?"..locStr..opts fibaro.debug("topeni", fullRequestUrl) local http = net.HTTPClient() http:request(fullRequestUrl, { options = { checkCertificate = false, method = "GET", timeout = 5000 }, success = function(res) local openWeatherData = res.status == 200 and json.decode(res.data) local max_temp = 0 if openWeatherData then max_temp = openWeatherData.list[0].main.temp_max fibaro.debug("topeni", "Today max temp: "..temp_max.."C") elseif res.status == 401 then local resp = json.decode(res.data) fibaro.debug("topeni", "Unable to load weather data 401: "..resp.message) fibaro.debug("topeni", fullRequestUrl) else fibaro.debug("topeni", "Unable to load weather data "..res.status) end process_heating(max_temp) end, error = function(res) fibaro.debug("topeni", "Unable to load weather data: "..res) process_heating(0) end }) Script outputs final request URL in case of failure to console. When i run this it fails, when i copy that final URL to web browser i get data as expected. Any idea what could be wrong?
  3. How to run an existing block scene from the android device using the "Welcome Home" mobile app?
  4. Hi There, I'm not getting my scene to work properly so I need some help. I want my lights to turn on if the variable is now equal to night, if the lux of one sensor is lower then 13 and is on of the two motion sensors is tripped. Then the lights can turn of when both motion sensors are save for 5 minutes. See the scene I created but is only working if I set the two sensors in a device group but then they work as an "and" state so both sensors need to be triggert before the lights turn on. Hopefully someone can help me.
  5. On my roller shutter 3 I don't have a wired switch. Therefore I bought an Aeotec WallMote Quad. Scenes for opening and closing is not a problem and moving to certain positions as well. I have a Zipatile 1. I need a scene that stops the roller shutter 3 from running or even better: on button pressed check if the roller shutter is running and then stops the shutters. I've tried the example in the attachment, but it doesn't work. Any suggestion? Thanks!
  6. Well i am running HC3 and i have a Aeon Gen5 Siren in my backyard for when i am working in my shed. Neighbours told me that my Siren ( that i am using over there for iff someone rings my frontdoor bell ) sometimes keeps going. So i wonder if i can use a scene or something that turns that Siren off every XX time so neighbours can't complain any more.
  7. I have HC2 and the door/window sensor was located next to HC2 5 meters away. For a while, my device didn't send the door status to HC2 and the scene didn't start. Maybe I need to re-bind this sensor, but it problem comes back every 2-3 months How to solve this problem?
  8. Sorry as I know this i s a newbie question (most likely) Setting up my HC I have a "Double switch 2" configured and I would like to make the wall switch turn of all lights with a double tap. I have actived Parameter 28 for double click. (correct?) Now I have tried multiple venues to achieve this without any success. In the Block programming the Switch (named "Bel Knapp 1") only displays options on/off like it was the output? There is no option as example to choose scene ID 28 (double click). I feel there is a configuration issue here but am not sure... A nudge in the right direction would be very appreciated thanks /Nick
  9. Well i have a HC3 and i want to create a scene that when a MC is open then light goes on and if MC is closed the light goes off after 5 minutes. Scene that i have is: When door opens then camera takes a snapshot, sends a push notification to mobile. What i want is: When door opens the camera takes a snapshot, sent a notification to my mobile and turn a flood light on, then when door is closed the flood light will stay on for 5 minutes and then automatically turns off.
  10. Version 1.1.0

    822 downloads

    A set of scene icons based on those supplied by Fibaro.
  11. Hi - I would like to modify a device parameter configuration using a scene. In this example I have a set of security lights which have a timer to switch on for 60 seconds. sometimes we want to use them as normal lights and i'd like to be able to set the timer to 20 minutes so they dont keep turning on and off. Parameter number 1 desired value would change using lua code to 1200. thanks.
  12. Hello I'm new to making scenes in HC3, -just bear with me. Thought to start with some simple things like Trigger and Conditioning. Have a source I want to get a message if the temperature is above 9 degrees But the scene is running even though the temperature is below 9 degrees (see picture) Have tried to read on how to do. Feels like it's a simple thing I am missing I have also the same problem with freezer (not unexpected but i guess ) But i would like to have that on -18 in stead
  13. Version 1.0.0

    1,712 downloads

    More then 300 scene icons
  14. Is it possible to write a (one) trigger for the HC3 scene that responds to all devices, whose interfaces are light. I don't want to write for every light device a trigger.. What I've tried, and it doesn't work is: { operator = “all”, conditions = { { type = “device”, property = “value”, operator = “anyValue”, isTrigger = true } } } OR id= Or id = {45, 46}, --omit altogether and hard to maintain OR id= fibaro.getDevicesID Or id = fibaro.getDevicesID({ Interfaces = {“light”,}, Properties = { dead = false,}, Enabled = true, Visible = true }), And changing 'device' to 'interfaces' or 'interFaces' doesn't work either. { operator = “all”, conditions = { { type = “interfaces”, property = “value”, operator = “==”, value = “light”, isTrigger = true } } } The only code that's working is: But, this trigger is only for 2 devices, and I have a lot more.... And I don't like it because it's hard to maintain.. { operator = "any", conditions = { { type = "device", id = 45, property = "value", operator = "anyValue", isTrigger = true }, { type = "device", id = 46, property = "value", operator = "anyValue", isTrigger = true } } } Can someone help me with this? please!
  15. Hello, I created following scene that turn off all the lights in my apartment: This scene should be automaticly launched while button 2 is pressed 2 times on Dimmer in Lobby. But it's not launching. It is properly running by mobile app. Does anyone knows what I am doing wrong ? What to check ? Regards.
  16. Hi all, I would like to display a debug message with the time of sunset + an x amount of minutes. So there needs to be a calculation. I have a few scenes whose start is dependent of the month, turning lights on earlier or later. My debug message should be something like "today lights will be on at 21:15". That 21:15 is the calculated time. I have these declarations at the start of scenes: local sunsettime = fibaro:getGlobalValue("SunsetTime"); local sunsetHour = fibaro:getValue(1,'sunsetHour') But I can't figure out how to do this. Shouldn't be very complicated, but i'm not good in LUA programming with time. Hope someone can help me out.
  17. Version 13.1

    2,234 downloads

    AOQ can control any other Fibaro system HC3, HC2, HCL (master/slave concept) Before migrating your devices to HC3, AOQ could be the solution to make it smooth and simple. If you've found yourself with too many Lua and Block scenes and need more automation, this QA is the right solution for you. The QA is designated to control and monitor your home system. QA automatically identifies the type of elements in the system. (Z-wave device, Nice, QA device, scene, automatic scene (Block and Lua). Any valid Z-wave,Nice and QA devices property and their values could be monitored, controlled and execute commands accordingly AOQ supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly. The first time you use All-in-One QA, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields. jM={ { 15, "137|630", {timeSlot={“12:00~18:00”},state="value=true", trueAct={“|230|”, “turnOn”,””}}} } Time span IDs list Criteria & Rules Action tables Time span a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined: time span = 0 defines the line as activity only. time span = ‘negative number’ line is suspended (remarked) IDs list given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”). global variable – add an ampersand sign & to System, QA and Local variable names: &varName keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character. Criteria & Rules (optional) property, state, time slot, active rules… Action tables (optional) tables of commands to be executed. To avoid using device IDs jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only. for example: jS2n= {boiler=137, dryer=630, light=230} device name must be included within back apostrophe sign in jM{} hash table. Now jM{} hash table above will look like that: jM={ { 15, "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true", trueAct={“`light`”, “turnOn”,””}}} } 1. Monitor option Some time the scenes or QA devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong. The monitor option will send an alert in case of defined states are timed out. Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords jM={ {8, "_17|_545",{timeSlot=”10:00~22:00”}}, -- within every 8 min. between 10am to 10pm, scenes 17, 545 must be active. If not alert sent. {3,"134|618|_556|_588"}, -- within every 3 min. devices 134,618 and scenes 556,588 must be active. If not auto-alert sent. {10,”132|145”,{property=”power”}}, -- within every 10 min. devices in list must to report new power value. If not auto-alert sent. {30,”470”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent. {20,”&HomeStatus|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent. 2. Control option Execute actions based on device state, status or value changes. QA supports option like on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one QA (which even doesn’t trigger by the system). Following action tables are available: trueAct{} - executed when state status is true. falseAct{} - executed when state status is false. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately. InitAct{} - Set of specific actions to be executed on startup only. errAct{} - Set of specific actions to be executed if verification failed. okAct{} - Set of specific actions to be executed if verification succeded. Here is an example of most common scenario, to turn on light when motion sensor breached and turn off light when sensor back to safe after few minutes (3 min. in this example) jM={0,”`mSensor`”,{state=”value=true”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} Since no need to turn on light during the day, timeslot could be defined jM={0,”`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}} But now could be an issue to turn off the light, if sensor breached few seconds before end of timeslot and back to safe is out of defined time slot, falseAct{} won’t be executed. In this case, turning light off action should be part of trueAct{} table jM={0,"`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={{“`lightSw`”,”turnOn”,””},{“`lightSw`”,”turnOff”,”180”}}} Z-wave devices, global variables and keywords could be defined at several lines (no limit). Scene could be defined one time only. For more details please download AOQ Advanced User’s Guide - complete instructions and information AOQ Quick Guide – syntax format reference and examples AOQ HC-WebEye Viewer – AOQ browser viewer guide QA Advantages: Debug window view: On the first run follow information will be displayed at debugger During normal operation every executed command showed at debugger. following data shown for every command: jM line number: device name: state value and status by color (green - true | pink - false); command executed. The debug information has special tag "AOQ<QA-ID>" and "TRACE" / "WARNING" / "ERROR" type for filtering. AOQ table preview: Table's header includes: startup time stamp, script current version, scene Name, LED as displayed at HC3 front panel, sunrise/set hours. Current home mode (@home or @vacation) System's current profile mode. Elapsed time Total Z-wave events Min, average and max Z-traffic Table columns are: Type – device type (Z.Device, G. Variable, Keyword, QA, luaScene, blockScene). ID: Description – room name: device ID: device name. Z-wave devices sorted by rooms, then by device ID. Battery capable device have green background according to current battery level. If device included in alarm circle icon appears before name. green circle - armed, red circle - breached Value – items current value. Criteria – state of evaluation to determine true or false status. If formula included, the state displayed on green background. in State– elapsed time since last status change. Alert – by default this column isn’t shown. If any devices have been alerted the column will be shown. Please notice that in some cases the device could be alerted, but after while it could back to normal activity. For example, if motion sensor is breached over specified time-span, alert notification will be sent. But after a while the sensor back to safe and alert is canceled, “back to normal” notification will be sent. At header of alert column shown current number of alerts Time Span – time span to monitor state of items. If time span set to 0, then this line acts as activity, no timeout alerts reported. If time span set to negative number, this line is suspended and no actions executed. Time Slot – Time slot range to execute related actions. Timestamp to execute specific action at specific time. Active (in range) time slot shown in green fonts. trueAct – list of actions to execute when the state is true. falseAct – list of actions to execute when the state is true. trigAct – list of actions when the value changes timeoutAct – list of actions to execute when time-span reached. Timer will be restarted when device state changed again to true. timeLoopAct – list of actions to execute when time-span reached. Timer restarted immediately after actions table executions. initAct – list of actions to execute on QA startup. Active Rules – non default defined rules (initOnStartup, Vacation, timeSpanOn, onClock, lineState, trigAll) jM{#} - line number in jM{} hash table jM{ hash table line} – shows device location in jM{} hash table. At the bottom of the table two execution lines show: list of up to 60 last executed actions (in order of execution) are displayed. (like CNN news line). list of delayed commands to be executed (and time left to execute) All global variables, their values and last modification time shows below the table.
  18. Hi, I have some scenes that; for debugging reasons, contain also an action to send an e-mail. Normally I should be able, judging from the date/time this mail was sent to check if my scene is working correctly. If necessary I can compare the mail with the log. If the log says that sensor A saw movement at 3:30 in the night and then the lights went on, then there probably is no problem. The mail then has the content , for example "Scene 13 just triggered", and was sent at 3:30 in the night. But... I DO get these correct mails that prove that the scene is working correctly, from the type in the example mentioned, but at an other hour, completely at random, I get AGAIN the same mail and now without any trace in the log of a triggering event for the scene. So the scene was NOT triggered but the mail was sent anyway. Anybody else having this problem or a reason for this behaviour ?
  19. Hello, I want to make a scene that when mij motionsensor is armed and breached the light and siren are going to work. I made it but when my motionsensor is armed the light instantly goes on and the sirene goes loud. It does not work. Who can help me?
  20. Hei, Quick App - Sonos Zone Controller works great inside the controller bur how can i use it with scenes ? In scenes is is not possible to choose the quick app Thanks for your answer.
  21. Function Request: Within block scene, it would be good to have the option within Simple Message Block to select: Log Output as a drop down within Simple Massage Output type: Debug, Error, Warning, Trace Message This will allow people to send a message into the Log during the flow of the Block Scene.
  22. I can't get a scene to work if I add a time interval. It looks ok but is not working and I don't know what I do wrong. It works if I remove the Time Range block... Please help!
  23. response, status = api.get("/scenes") fibaro:sleep(1000) if (status == 200) then fibaro:debug("Get Scenes Successful") created = true else fibaro:debug("Failed to get Scenes " ) end for _,s1 in ipairs(response) do local s2 = api.get("/scenes/"..s1.id) if s1.name == gSceneName then fibaro:debug("SceneName: " .. s1.name .. " Scene ID: " ..s1.id) print (s1.isLua) -- ** gets correctly print (s1.lua) -- <=== RETURNS a null --- HOW do I get this print (s1.roomID) -- ** gets correctly print (s1.iconID) -- ** gets correctly print (s1.sortOrder) -- ** gets correctly SceneID= s1.id fibaro:sleep(1000) Essentially I'm trying to get the Lua code from a scene so I jason encode it so I can then populate another scene with the same lua code. I'm trying to automatically update/create Lua scenes without having to go in and edit each one individually. I can populate the "lua " field with an API PUT ... But I can't read it back. The code above returns all the other fields but not the s1.lua Any help would be greatly appreciated - thanks.
  24. Hello. I don't know how to set up a scene for Fibaro HC lite to sort a picture when the door opens on the sepecified mail. For Fibaro HC2 I did this scene and it works perfectly. Unfortunately at Fibaro HC lite I have no opportunity to choose any room in the system, as I cannot appear to choose.
  25. Version 1.0.0

    422 downloads

    File: ikony_sceny.zip Modified icons for most common HC3 scenes - blinds, lights, blinds + lights. Size 128x128px, PNG, transparent background. ikony_sceny.zip
×
×
  • Create New...