Alarm Engine Support Forum Before sunrise rule broken

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #8222
    Keith Belt

      (note:  all firmware had been updated to latest)

      Have a Zwave light set to go on\off at sunset\sunrise.  Its been working fine but wanted to adjust on\off time since still light outside.  Can adjust sunset rule OK by +30 to go ON a half hour *after* sunset.  But sunrise rule will not accept any negative numbers for turning OFF *before* sunrise.  The rule creator will allow me to enter -30 (using up\down arrows), but after saving, the rule still says just “sunrise”.  It won’t seem to “take” (-) numbers.

      K.

      #8223
      Keith Belt

        Just found a second broken rule:  Programming the formC relay to activate a strobe when any area alarm sensor is tripped.  The rule programmer allows selection of “any” as a choice in the zone dropdown box, but when I save, the rule in the listing doesn’t say “any”, it says “Garage Door Entry”, which in my case is the first sensor.  I can select individual zones OK, but I can’t select “any”.  If I select “any”, it defaults to zone 1.

        #8224
        Michael Burrell

          Keith,

          This is a bug in the rule editor that was unintentionally implemented by our web development team during a recent update . It was noted by our QA tester that the editor allowed negitive values for termostat settings etc. Which if entered would create an issue in the Zwave controller. So they removed the ability to allow negitive values, which inadvertly broke this rule input since it was allowed for this.

          Additionally, we are updating this rule input to be two different options in the drop down. How it is currently configured it is a cumbersome to understand. We plan to add two seperate options that are “Mins before Sunset” and “Mins after Sunset” this way it is always a postitive number. This will be the same for sunrise.

          I apologize for the inconvience of this, we just recently discovered it. I will push on them for an quick resolution.

          Thanks,

          Mike

          #8225
          Michael Burrell

            On the second rule issue. Are you wanting the strobe to activate during an alarm?

            I just tested this rule out below and I am able to do this. Can you please provide the rule structure that your having issues with, I would like to test it and provide the bug report.

            #8227
            Keith Belt

              I think its more to do with the “Edit” feature being wonky.  I tried from another computer and was able to program “any” zone as long as I did it the first time through.  But afterwards, could not change that.  No matter what zone I change to, after saving and returning to the rule list, it still shows “ANY”, not the changed zone.

              The verbiage of this rule was also a little confusing to parse.  The Prefix for the rule is “WHENEVER ANY…”, so once the area is selected, I kind of expected that to be it.  Selecting “any” again seemed redundant and selecting a specific zone seemed contradictory, after establishing “whenever any area-1 alarm…” as the condition.  It would make more sense if it just said “Whenever….”.

              The M1 had a “whenever a burglar alarm” rule, that was more intuitive and is the one you think of when programming this kind of event.  The E27 rule may be more technically accurate, but its less intuitive what is being defined.  For example, does “ANY alarm” also include things like low battery faults or failed communications for wireless sensors, or is it just sensor violations (i.e., intruders).

              K.

               

              #8228
              Michael Burrell

                The intention of the format was to provide a more accurate representation of the rules.

                The ANY AREA and ANY ZONE drop-downs have a couple of functions: they work as parameters for the rules and as filters to help you find the parameter you want to use. If you are looking for a specific zone to activate the rule from, you can utilize ANY AREA, which will show you all zones in the system to pick from. If you do not want a specific zone, then the ANY AREA and ANY ZONE options are your choices. Reviewing this I did locate a bug in the filtering.

                The WHENEVER ANY prefix is only related to the specific ANY ALARM rule. I believe the devs struggled with how to phrase this. They were attempting to have it read WHENEVER ANY area 1 ALARM, but what happens is when you combine WHENEVER ANY and Any Area, you get WHENEVER ANY Any Area ALARM. Removing the ANY is less descriptive if a single area is selected but redundant if the Any Area option is selected.

                The WHENEVER ANY ALARM IS ACTIVATED rule includes all ALARMS, such as FIRE ALARM, CO ALARM, BURGLAR ALARM, MEDICAL ALARM, PANIC ALARM, WATER ALARM, and TEMPERATURE ALARM. This does not include TROUBLE conditions, for which there is a separate rule if needed. The WHENEVER ALARM rules are based on alarms shown as such in the system and, if enabled, would report to the central station as dispatched alarms.

                The Alarm Engine also has the WHENEVER ANY BURGLAR ALARM rule. You can also utilize ANY or specific FIRE ALARM, CO ALARM, MEDICAL ALARM, WATER ALARM, and TEMPERATURE ALARM activations. These can be filtered by Area or Sensor.

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.
              Scroll to Top