Scenes triggered by time don’t work

[Igy 23]

I created several scenes where the timer functions to start the scene is being used. But none of them works. Any idea where should be the problem? See the pictures attached.

Thanx for any adwise.

HC2, FW 4.056,

Please login or register to see this attachment.

Please login or register to see this attachment.

[Cafun 13]

Did you changed icon on this scene ? I have noticed that scenes based on time stops to work when icon changed from default one.

 

I changed some icons of time based scene's. Some are working others not. So I don't know if it has anything to do with the icon change.

[morpheus75 75]

my hc2 has been on 4.055 beta since sept.  everything working so havent bothered to update as i believe in the saying 'if it aint broke, dont fix it'

my time based scenes are all LUA (all my scenes are tbh),

i created a timeSetter scene and a global variable called 'time' - this just updates the global variable every minute

 i then added the 'time' in the global triggers in the header of each scene that was time based.

so every minute the the different scenes would run and if the time matched an action would occur.

eg below

 

the timeSetter scene

 

Please login or register to see this code.

 

please note the %% autostart in the header - this is to make sure that this scene starts whenever hc2 restarts itself

 

every minute the time is written is HH:MM format in the global variable

 

eg scene for lights

 

Please login or register to see this code.

 

this works for me and hasnt failed me (yet!)

[Cafun 13]

Nice morpheus75! That's also a way to do it. I'll keep that in my mind.

 

Edit:

So, you only have one scene which runs on time.. Other scenes are running because of the variable changes?

How many scenes do you have? Do you "bundle" the most of the timerelated scenes in one scene which will be triggered by the variable, or did you created a scene per subject?

[Henrik 24]

When your scenes stop working, do the actual scene stop running or is it still running but not triggered? If you go to the "Dashboard", is there a blue "Stop" button next to the scene?

 

An active timer-based scene should always run. It would be interesting to know if the scene stops running or if just stops triggering.

[Cafun 13]

Hmm, good question. Don't know it yet. When I have a scene stopped running/triggered, I take a look!

[morpheus75 75]

Nice morpheus75! That's also a way to do it. I'll keep that in my mind.

 

Edit:

So, you only have one scene which runs on time.. Other scenes are running because of the variable changes?

How many scenes do you have? Do you "bundle" the most of the timerelated scenes in one scene which will be triggered by the variable, or did you created a scene per subject?

 

I have the 1 timeSetter scene which alters the variable and all other scenes are triggered by the 1 minute interval for the change in time.  I found this more reliable. As long as this scene works properly the rest are triggered and if the time is correct the action is performed.

In the above example i still used the os.date function as this scene i wanted to use the sunrise/sunset offsets but in another scene i just use the value of the 'time' variable directly eg

 

Please login or register to see this code.

[Cafun 13]

Thanks for explaining! Those scenes triggered by the variable are triggered on the same time. Isn't that a problem for cpu load of the HC2? If I look at my scenes.. I have a total of 50 active. I guess 10 of them involves time based. Nah, I guess it shouldn't be a problem..

But I'm going to look if I can consolidate scenes.

 

Tip: use [ code ] and  [ /code ] (without space) to put your scripts in. It more readable that way.

[morpheus75 75]

Thanks for explaining! Those scenes triggered by the variable are triggered on the same time. Isn't that a problem for cpu load of the HC2? If I look at my scenes.. I have a total of 50 active. I guess 10 of them involves time based. Nah, I guess it shouldn't be a problem..

But I'm going to look if I can consolidate scenes.

 

Tip: use [ code ] and  [ /code ] (without space) to put your scripts in. It more readable that way.

 

yes the 4 big scenes are triggered at the same time. it then reads the code in all of them and only 'actions' it if time matches. to be honest CPU usage is fine and have had no issues. i think maybe because i have grouped them into a 'big' scene - who knows....  but it works for me.

i have a total of 177 devices, 29 scenes and 18 rooms (according to the backup & recovery screen)

 

PS. Thanks for the tip - didnt know that

[Quikdav 15]

Same for me. I changed the default icon and the scene never restarted even after rebooting the HC2 !!!

 

So there is something wrong with that !!!

[JEAU 2]

I also have this problem after changing some Icons, but now no time based scenes work for me even I changed the icons, made it newly or  restarted 

 

Why this HC2 is full of problems,  Fibaro please do something 

[JEAU 2]

My HC2 Problem solved by removing uploaded Icons and totally resetting HC2 to factory setting  then updated the firmware then restored the backup 

 

that is shame just a small changes like changing to custom Icon brings that much harm to Fibaro Home center, I personally think my slow Vera is more reliable than Home Center 2, 

[maximosm 4]

I have the same problems with some time scenes. The solution is only to have all of scenes without custom icons?? 

[maximosm 4]

The problem ist continoued after the last update.I have delete every icon i made a reset and after that restore but after 3 days stoping the time scenes working.Please anyone help.

[hanhoo 3]

I use time tiggered scenes only to set variables and then use these variables as triggers in many other scenes (Sunrise/Sunset variable for instance). I have not had a problem ever in this way. 

 

I read another tip (credits to the thinker) to not set the variable directly, but create a virtual device to control the variables. So at SUNRISE the scene pushes in the 'DAYLIGHT' button on the Virtual Device which sets the variable to the day status. Then you can see and influence the status of the daylight variable in the virtual device. Handy to check if it's working, and invluence it for testing purposes.

[maximosm 4]

The problem still is there.after so much time.