HC3 trigger scenes at 0:00

[moltos 4]

Hi,

 

I have observed that the HC3 triggers my scenes within the day-change at 0:00 by hand.

The system ignores in this case all declaration and switch to a "run actions" within the scenes.

The declaration should prevent this cause my trigger intervall is starting at 7:30 and only up to 17:30:

 

{
conditions = {
    { type = "date",
      property = "cron",
      operator = "matchInterval",
      value = {
         date = { "30", "7", "*", "*", "*", "*" },
         interval = 900
              },
    isTrigger = true
    },
    { type = "date",
      property = "cron",
      operator = "match<=",
      value = {"30", "17", "*", "*", "*","*"}
    }, 
    { type = "global-variable",
      property = "sRollEastSun",
      operator = "==",
      value = "off"
    } },
  operator = "all"
}

 

Eventlog:

[07.07.2020] [00:00:00] [DEBUG] [SCENE:R.OFFICE]: checkState | CLux: 1.0 | dLux: -9999.0

[07.07.2020] [00:00:00] [DEBUG] [SCENE:R.OFFICE]: Rolladen offen

[07.07.2020] [00:00:00] [DEBUG] [SCENE:R.OFFICE]: Rolladen offen

 

In my case the blind will open, which should be the case when the sun is not shining on to the windows or after 17:30.

A trigger should start at 7:30 in my case, end at 17:30 and 0:00 by far smaller than 7:30, correct?

 

Has anyone here made similar observations?

[SmartHomeEddy 818]

@moltos
You need an extra condition. The matchInterval only starts at 7:30 and than goes on and on at the defined interval. This is my declaration for every hour from 6:00 and the last time is at 23:00. 
 

 

Please login or register to see this attachment.

Edited July 8, 2020 by SmartHomeEddy

[moltos 4]

Thanks, 

in my observation i think we must exclude more and let less space for interpretation.

The current documentation will have much space for improvement (+ some case sensitive wrong documented parameters).

 

I have changed my interval triggers as well. Hopefully this will stop this strange behavior at night.