No announcement yet.

At least keeps defaulting to exactly on second condition

  • Filter
  • Time
  • Show
Clear All
new posts

    At least keeps defaulting to exactly on second condition

    Every time I set the condition "At least" it keeps defaulting to exactly despite the IF being the second condition. It used to be fine, even in HS4 but has now started misfiring the events. If anyone has any solutions that would be great.

    Click image for larger version

Name:	Screenshot 2022-01-25 230219.jpg
Views:	88
Size:	27.4 KB
ID:	1523264

    Both the trigger and condition would need to happen exactly at the same time; won't happen.
    try to use " less than" or "more than" in your trigger/condition combo.

    Edit: just re-read your post. Try starting from scratch in a new event. Events can get corrupted.


      I’m able to create this event and it shows the “for at Least”. I agree with 123qweasd, try deleting the event and recreating it.

      Sent from my iPad using Tapatalk
      HS4 &HSTouch Designer 3.0.80
      BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee, Nest, AK Bond
      EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
      weatherXML, Jon00 Alexa Helper, Network Monitor, MyQ, Z-Wave


        I ended up re-creating the event again from scratch. The original was a copy from another event as a template. The strage thing is that if I expand the IF statement it shows "at least" but when it isn't expanded it shows as "exactly" for both the IF statements. Anyway it now works as expected despite it showing "exactly" under both IFs. Weird.