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


Figlio

Member
  • Posts

    21
  • Joined

  • Last visited

About Figlio

  • Birthday 01/04/1984

Profile information

  • Gender
    Male
  • Country
    Netherlands
  • Gateway/s
    Home Center 2

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Figlio's Achievements

Newbie

Newbie (1/8)

1

Reputation

  1. Hi @Sankotronic, thanks for looking into it. I ran some test over the past two weekends to see I could find the issue but I dont seem to be able to find it. Last thing I tried was to clean the scene that is responsible for turning the lights on. Now it is just a call TurnOn. Unfortunately it is still not working. Please find a screenshot of the events panel attached. It is the Tuinlamp that I want to turn off at sunrise (except for the weekends y shoud not turn on at all). any other ideas?
  2. Hi @Sankotronic I am experiencing some behaviour of the Main Scene I cannot explain. I try to turn on the garden lights every morning, except the weekends, at 6 and turn them off at sunrise. Whilst this runs very smooth every day during weekends the lights are turn on at sunrise. Could you please point me in the right director for debugging the setup below? Million thanks! -- TIME BASED SCENES AND VD SETUP -- REPEATING SCENES SETUP -- here you can setup scenes that will be executed at predefined interval -- in minutes. Lowest value is every 1 minute and longest interval is up to -- you. 24h = 1440m, 1week = 10080m, 30d = 43200m etc. -- enter scene names that will run repeatedly every X minutes separated -- by comma. This is needed for debugging and can be used to send push -- notification local runSceneRepeatName = {} -- enter scene IDs that will run repeatedly every X minutes separated -- by comma. local runSceneRepeatID = {} -- enter at which interval time in minutes will scenes run separated -- by comma. local runSceneRepeatTime = {} -- enter here flag for sending push message when scene is executed -- 1 for sending message, 0 no messages local runSceneRepeatPushFlag = {} -- enter here message content that will be sent to you when scene is -- executed. If above flag is 0 for any of the scenes then just put -- empty "" for it. local runSceneRepeatPushMessage = {} -- for each scene enter variable with name "count" (must be all same name) -- separated by comma. This is used to count interval at which scene will -- be started and is neccessary for proper execution! local runSceneRepeatCount = {} -- enter here "Yes" for each scene if you want them to run immediatelly when -- this scene starts running after reboot or saving or enter "No" if you -- want scene to run after defined interval after scene is restarted local runSceneAtStart = {} -- SCHEDULED SCENES SETUP -- here you can setup scenes that will be executed at predefined time of -- day in format "00:00". You can set up more than one time during day. -- Also you can enter flag for each day of the week when scene will be -- executed or not. See more details bellow. local runSceneSchedName = {"Tuinlamp_On","Tuinlamp_Off","Battery Check","Buitenlamp_On","Buitenlamp_Off","Tuinlamp_On","Tuinlamp_Off"} -- enter scene IDs that will run at scheduled time separated by comma. local runSceneSchedID = {47,46,33,43,44,47,46} -- enter at what time of day will scenes run separated by comma. -- You can define more than one time in format "00:00" for one scene -- or even use local or global variables like sunsettime or sunrisetime -- Example: {{"13:30", "19:20"}, {sunrisetime, "13:00", sunsettime}} -- in above example first scene will run at 13:30 and 19:20 while -- second scene will run at sunrisetime, 13:00 and at sunsettime -- IMPORTANT NOTE - if you use variable to set time then make sure that -- you add refreshing of value in function extraUserCodeFirst() like -- this for above example: -- runSceneSchedHour[2][1] = sunrisetime -- runSceneSchedHour[2][3] = sunsettime where first square brackets -- [2] with number inside refers to second scene and second square -- brackets [1] with number inside refers to time in order which means -- sunrisetime is 1st time [1] for 2nd [2] scene and sunsettime is -- 3rd [3] time for 2nd [2] scene in a row added to the variable. local runSceneSchedHour = {{"06:00"},{sunrise},{"10:00"},{sunset},{"23:59"},{sunset},{"23:59"}} -- enter here flag for each day of the week for scene to run at above -- scheduled time. if flag 1 the scene will run and if flag 0 then -- will not be run for that day. Remeber, Sunday is first day of the -- week on HC2! Example for two scenes: -- {{1, 0, 0, 0, 0, 0, 0}, {0, 1, 1, 1, 1, 1, 0}} - in this example -- first scene will run only on Sunday, and second scene will run on -- weekdays byt not on weekends (Saturday and Sunday). local runSceneSchedWeek = {{0, 1, 1, 1, 1, 1, 0},{0, 1, 1, 1, 1, 1, 0},{1, 0, 0, 0, 0, 0, 0},{1,1,1,1,1,1,1},{1,1,1,1,1,1,1},{1,1,1,1,1,1,1},{1,1,1,1,1,1,1}} -- enter here flag for sending push message when scene is executed -- 1 for sending message, 0 no messages local runSceneSchedPushFlag = {0,0,0,0,0,0,0} -- enter here message content that will be sent to you when scene is -- executed. If above flag is 0 for any of the scenes then just put -- empty "" for it. local runSceneSchedPushMessage = {"","","","","","",""} -- REPEATING VIRTUAL DEVICE SETUP -- here you can setup VD that will be executed at predefined interval -- in minutes. Lowest value is every 1 minute and longest interval is up to -- you. 24h = 1440m, 1week = 10080m, 30d = 43200m etc. -- enter VD IDs that will run repeatedly every X minutes separated -- by comma. local runVDRepeatID = {} -- enter here which button to press to execute command local runVDRepeatButton = {} -- enter at which interval time in minutes will VD run separated by comma. local runVDRepeatTime = {} -- enter here flag for sending push message when VD is executed 1 for -- sending message, 0 no messages local runVDRepeatPushFlag = {} -- enter here message content that will be sent to you when VD is -- executed. If above flag is 0 for any of the VD then just put -- empty "" for it. local runVDRepeatPushMessage = {} -- for each VD enter variable with name "count" (can be all same name) -- separated by comma. This is used to count interval at which VD will -- be executed and is neccessary for proper execution! local runVDRepeatCount = {} -- enter here "Yes" for each VD if you want them to run immediatelly when -- this scene starts running after reboot or saving or enter no if you -- want VD to run after defined interval local runVDAtStart = {} -- SCHEDULED VD SETUP -- here you can setup VDs that will be executed at predefined time of -- day in format "00:00". You can set up more than one time during day. -- Also you can enter flag for each day of the week when VD will be -- executed or not. See more details bellow. -- enter VD IDs that will run at scheduled time separated by comma. local runVDSchedID = {} -- enter here which button to press to execute command for each time that -- you enter bellow. Example for Sonos remote VD from Krikroff. If you set -- runVDSchedButton = {{"7", "9"}} and -- runVDSchedHour = {{"07:00", "11:00}} -- Then button "2" (Play) will be pressed at 07:00 to start music and -- button "9" (Stop) will be pressed at 11:00 to stop music. local runVDSchedButton = {{}} -- enter at what time of day will VD button be pressed separated by comma. -- You can define more than one time in format "00:00" for one VD -- or even use local or global variables like sunsettime or sunrisetime -- Example: {{"13:30", "19:20"}, {sunrisetime, "13:00", sunsettime}} -- in above example first VD button will be pressed at 13:30 and 19:20 -- while second VDs button will be pressed at sunrisetime, 13:00 and -- at sunsettime local runVDSchedHour = {{}} -- enter here flag for each day of the week for VD to press button -- at above scheduled time. if flag 1 the VD button will be pressed and -- if flag 0 then will not be pressed for that day. Remeber, Sunday is -- first day of the week on HC2! Example for two VDs: -- {{1, 0, 0, 0, 0, 0, 0}, {0, 1, 1, 1, 1, 1, 0}} - in this example -- first VDs button will be pressed only on Sunday, and second VDs -- button will be pressed on weekdays but not on weekends (Saturday -- and Sunday). local runVDSchedWeek = {{1, 1, 1, 1, 1, 1, 1}} -- enter here flag for sending push message when VD buttons is pressed -- 1 for sending message, 0 no messages local runVDSchedPushFlag = {} -- enter here message content that will be sent to you when VD is -- executed. If above flag is 0 for any of the VDs then just put -- empty "" for it. local runVDSchedPushMessage = {} -- SCHEDULED GLOBAL VARIABLE CHANGE SETUP -- here you can setup global variable which value will be changed at -- predefined time of day in format "00:00". You can set up more than one -- time during day. Also you can enter flag for each day of the week when -- global variable value will change or not. See more details bellow. -- enter global variable name which value you want to change at scheduled -- time separated by comma. local chgGlobalSchedName = {} -- enter here what value will be set to global variable for each time that -- is entered bellow local chgGlobalValue = {{}} -- enter at what time of day will global value change separated by comma. -- You can define more than one time in format "00:00" for one VD -- or even use local or global variables like sunsettime or sunrisetime -- Example: {{"13:30", "19:20"}, {sunrisetime, "13:00", sunsettime}} -- in above example first global variable value will be changed at 13:30 -- and another value at 19:20 while second global variable value will be -- changed at sunrisetime, 13:00 and at sunsettime local chgGlobalHour = {{}} -- enter here flag for each day of the week for VD to press button -- at above scheduled time. if flag 1 the VD button will be pressed and -- if flag 0 then will not be pressed for that day. Remeber, Sunday is -- first day of the week on HC2! Example for two VDs: -- {{1, 0, 0, 0, 0, 0, 0}, {0, 1, 1, 1, 1, 1, 0}} - in this example -- first VDs button will be pressed only on Sunday, and second VDs -- button will be pressed on weekdays but not on weekends (Saturday -- and Sunday). local chgGlobalWeek = {{1, 1, 1, 1, 1, 1, 1}} -- enter here flag for sending push message when VD buttons is pressed -- 1 for sending message, 0 no messages local chgGlobalPushFlag = {} -- enter here message content that will be sent to you when VD is -- executed. If above flag is 0 for any of the VDs then just put -- empty "" for it. local chgGlobalPushMessage = {} -- DEBUGGING VARIABLES -- setup debugging, true is turned on, false turned off. local deBug = true -- for showing events as they happen local exDebug = false -- for checking repeating and scheduled scene -- & VD variable values if correct local gpsDebug = false -- GPS user location check and calculation local sumDebug = true -- it shows summation of global var changes -- EXTRA FUNCTION WHERE YOU CAN ADD YOUR CODE -- use this function to add code that will be executed before all other -- code in the loop function extraUserCodeFirst() -- if you use variable for scheduled execution of scene or VD then you -- need to add here equanation to get last value calcualted -- your code goes here runSceneSchedHour[2][1] = sunrisetime runSceneSchedHour[4][1] = sunsettime runSceneSchedHour[6][1] = sunsettime end -- use this function to add code that will be executed after all other -- code in the loop function extraUserCodeLast() -- your code goes here end
  3. Hi forum, Now the weather is getting colder our heating system is up and running again. This morning I came downstairs noticing the heating didn't turn on... Apparently, the scene managing the boiler had crashed. Would there be a way to get informed about scenes crashing? That way I can fix a problem more quickly preventing having a cold house. Thanks for your help! Ciao Figlio
  4. Hi all, Is there a way to simulate pressing a button on a VD by a scene? Help is much appreciated! Ciao Figlio
  5. I do not have any parameters te set. The dimmers are not fibaro, I use three qubino dimmers and three domitec wave dimmable led lamps. I am not aware of being able to set parameters for them, hence i use a scene to do so.
  6. Issue is solved... Thanks for your help @10der. This worked for me <code> --[[ %% properties %% events %% globals --]] local DimSchuifpui local DimKeuken local DimBank1 local DimBank2 local DimBank3 local DimEntree fibaro:setGlobal('SceneStart', 1); fibaro:call(22, "turnOff"); --Schakelaar Schuifpui --fibaro:call(26, "setValue", "0") --Zet Schuifpui op 0% fibaro:call(21, "turnOn"); --Schakelaar Keuken fibaro:call(28, "setValue", "25") --Zet Keuken op 25% fibaro:call(24, "turnOn"); --Schakelaar Bank fibaro:call(100, "setValue", "0") --Zet Bank1 uit fibaro:call(102, "setValue", "0") --Zet Bank2 uit fibaro:call(106, "setValue", "10") --Zet Bank3 op 10% fibaro:call(94, "turnOff"); --Schakelaar Entree --fibaro:call(64, "setValue", "0") --Zet Entree op % fibaro:sleep(500) DimSchuifpui = fibaro:getValue (26, "value") DimKeuken = fibaro:getValue (28, "value") DimBank1 = fibaro:getValue (100, "value") DimBank2 = fibaro:getValue (102, "value") DimBank3 = fibaro:getValue (106, "value") DimEntree = fibaro:getValue (64, "value") fibaro:debug( 'Schuifpui staat nu op = ' .. DimSchuifpui) fibaro:debug( 'Keuken staat nu op = ' .. DimKeuken) fibaro:debug( 'Bank1 staat nu op = ' .. DimBank1) fibaro:debug( 'Bank2 staat nu op = ' .. DimBank2) fibaro:debug( 'Bank3 staat nu op = ' .. DimBank3) fibaro:debug( 'Entree staat nu op = ' .. DimEntree) fibaro:setGlobal('SceneStart', 2) </code>
  7. Thanks for helping out guys.. With your suggestions I made it work! J two things seem to indeed have been wrong. First the local "schuifpui" suggested by @jimicr Second the calling value On on the Dimmer as suggested by @petergebruers @petergebruers The global variable is used for another scene which is used when the lights are switched on manually. The scene sets them to 75%. I use the global variable to determine whether the scene was started by another scene (1) or manually (2). The following code works for me: --[[ %% properties %% events %% globals --]] local DimSchuifpui local DimKeuken local DimBank1 local DimBank2 local DimBank3 local DimEntree fibaro:setGlobal('SceneStart', 1); fibaro:call(22, "turnOff"); --Schakelaar Schuifpui --fibaro:call(26, "setValue", "0") --Zet Schuifpui op 0% fibaro:call(21, "turnOn"); --Schakelaar Keuken fibaro:call(28, "setValue", "25") --Zet Keuken op 25% fibaro:call(24, "turnOn"); --Schakelaar Bank fibaro:call(100, "setValue", "0") --Zet Bank1 uit fibaro:call(102, "setValue", "0") --Zet Bank2 uit fibaro:call(106, "setValue", "10") --Zet Bank3 op 10% fibaro:call(94, "turnOff"); --Schakelaar Entree --fibaro:call(64, "setValue", "0") --Zet Entree op 0% fibaro:sleep(500) DimSchuifpui = fibaro:getValue (26, "value") DimKeuken = fibaro:getValue (28, "value") DimBank1 = fibaro:getValue (100, "value") DimBank2 = fibaro:getValue (102, "value") DimBank3 = fibaro:getValue (106, "value") DimEntree = fibaro:getValue (64, "value") fibaro:debug( 'Schuifpui staat nu op = ' .. DimSchuifpui) fibaro:debug( 'Keuken staat nu op = ' .. DimKeuken) fibaro:debug( 'Bank1 staat nu op = ' .. DimBank1) fibaro:debug( 'Bank2 staat nu op = ' .. DimBank2) fibaro:debug( 'Bank3 staat nu op = ' .. DimBank3) fibaro:debug( 'Entree staat nu op = ' .. DimEntree) fibaro:setGlobal('SceneStart', 2)
  8. Then after 2 times the correct dim values are set...
  9. Hi all, I run into a problem with a scene behind a button in a VD I m using to set my living room lights at a certain dim level. I have many buttons each with a different setting of the lights. The problem is i need to run the scene three times to get the lights set at the correct dim level. In the screenshot below the debug of the thee times i ran the scene are shown. To start, I manually set the lights at 100% and then turned them all off. How can i solve this? Note: I use a MCO Home control pad to manually turn on the light. There is a scene that sets the dim level at 75% when the light is switched on manually. I use the Global SceneStart to determine whether the mco home button is switched on manually or by this scene. Please find my scene here: --[[ %% properties %% events %% globals --]] local DimSchuipui local DimKeuken local DimBank1 local DimBank2 local DimBank3 local DimEntree fibaro:setGlobal('SceneStart', 1); fibaro:call(22, "turnOff"); --Schakelaar Schuifpui --fibaro:call(26, "setValue", "10") --Zet Schuifpui op 10% fibaro:call(21, "turnOn"); --Schakelaar Keuken fibaro:call(28, "setValue", "25") --Zet Keuken op 25% fibaro:call(100, "turnOff"); --fibaro:call(100, "setValue", "10") --Zet Bank1 op 10% fibaro:call(102, "turnOff"); --fibaro:call(102, "setValue", "10") --Zet Bank2 op 10% fibaro:call(106, "turnOn"); fibaro:call(106, "setValue", "10") --Zet Bank3 op 10% fibaro:call(24, "turnOn"); --Schakelaar Bank fibaro:call(94, "turnOff"); --Schakelaar Entree --fibaro:call(64, "setValue", "25") --Zet Entree op 25% DimSchuifpui = fibaro:getValue (26, "value") DimKeuken = fibaro:getValue (28, "value") DimBank1 = fibaro:getValue (100, "value") DimBank2 = fibaro:getValue (102, "value") DimBank3 = fibaro:getValue (106, "value") DimEntree = fibaro:getValue (64, "value") fibaro:debug( 'Schuifpui staat nu op = ' .. DimSchuifpui) fibaro:debug( 'Keuken staat nu op = ' .. DimKeuken) fibaro:debug( 'Bank1 staat nu op = ' .. DimBank1) fibaro:debug( 'Bank2 staat nu op = ' .. DimBank2) fibaro:debug( 'Bank3 staat nu op = ' .. DimBank3) fibaro:debug( 'Entree staat nu op = ' .. DimEntree) fibaro:setGlobal('SceneStart', 2)
  10. Thanks 10der for your reply. I am not sure i understand what you mean with your post, though... The problem is not in the two scene's anymore. It is just the first one, which as it seems not all actions are performed when I run it. When I ran my scene 3 times after I manually set the lights at 100% and then turned them all off. Please find the debug in the screenshot. As you can see it actually took three times to actually set the right values. How can i solve this? Please find my scene here: --[[ %% properties %% events %% globals --]] local DimSchuipui local DimKeuken local DimBank1 local DimBank2 local DimBank3 local DimEntree fibaro:setGlobal('SceneStart', 1); fibaro:call(22, "turnOff"); --Schakelaar Schuifpui --fibaro:call(26, "setValue", "10") --Zet Schuifpui op 10% fibaro:call(21, "turnOn"); --Schakelaar Keuken fibaro:call(28, "setValue", "25") --Zet Keuken op 25% fibaro:call(100, "turnOff"); --fibaro:call(100, "setValue", "10") --Zet Bank1 op 10% fibaro:call(102, "turnOff"); --fibaro:call(102, "setValue", "10") --Zet Bank2 op 10% fibaro:call(106, "turnOn"); fibaro:call(106, "setValue", "10") --Zet Bank3 op 10% fibaro:call(24, "turnOn"); --Schakelaar Bank fibaro:call(94, "turnOff"); --Schakelaar Entree --fibaro:call(64, "setValue", "25") --Zet Entree op 25% DimSchuifpui = fibaro:getValue (26, "value") DimKeuken = fibaro:getValue (28, "value") DimBank1 = fibaro:getValue (100, "value") DimBank2 = fibaro:getValue (102, "value") DimBank3 = fibaro:getValue (106, "value") DimEntree = fibaro:getValue (64, "value") fibaro:debug( 'Schuifpui staat nu op = ' .. DimSchuifpui) fibaro:debug( 'Keuken staat nu op = ' .. DimKeuken) fibaro:debug( 'Bank1 staat nu op = ' .. DimBank1) fibaro:debug( 'Bank2 staat nu op = ' .. DimBank2) fibaro:debug( 'Bank3 staat nu op = ' .. DimBank3) fibaro:debug( 'Entree staat nu op = ' .. DimEntree) fibaro:setGlobal('SceneStart', 2) [coe
  11. I guess I could but than i might have to change the 75% in two scenes when i wish to change that value. I think I solved it though by creating a global variable being set in the second scene to 1 in the beginning and back to 2 at the end. I experience something strange though which I am not sure i caused by this or something else. It seems that I have to run the scene twice to have the correct dim values set. The first time the scene runs it restores the dim value of the last setting of the light. Any idea what can cause this?
  12. HI all, Is there a way to disable a scene (which is triggered by a change in value) from another scene. Situation: I have a simple scene that sets the light at 75% when i change the value of another device (mco home touch pad). Now I want to create another scene that sets the light at say 25%. However, i do need to change de value of the mco home because otherwise the light has no power (the mco home is also a non z-wave device). How could I prefend the first scene from putting the light at 75% and running only the second scene? Hope you could help. Ciao Figlio
  13. Hi all, How do I get te currently set temperature from a heating panel of a certain room to use in a scene? I'm trying to do the following. I have a scene looping to switch the boiler on and off depending on the current temperature in a room. For each room I have a heating panel and a danfoss value on each radiator. I use this value to readout the currently set temperature (which is done through the heating panel). This works very fine. However, in my living room i have floor heating without a danfoss value. I like to also program different temperatures using the heating panel but for that i need to get the set temperature from the panel instead of from the danfoss valve. How? Hope someone can help me out... Any help is much appreciated!
  14. Hi @Sankotronic, Yes I did manage. It took me some time but figured it out. I was reading your instructions and kept on being stuck after pasting the scene and debugging. It would give me the debug as you present in the first post. However, i figured that not all variables were being created by the VD. Since I'm a newbie both on the forum as in programming fibaro i didn't notice this before. Anyway, its working now as expected. Now its time to start using these variables in scenes. Great work! and easy to set up as well once you understand the basics. My search did learn me lots though.... I will also give your other scenes and VDs a go. Thanks again!
×
×
  • Create New...