n_sievers

Thank you! I will try this approach 1st.

Thank you for your response. I have been considering this as I have something similar to this set up with a notification upon condition that only want to execute once and not continually trigger. With regard to the "status" that I mentioned, the deabolt access alarm condition is only available as "status" that can be referenced and stays static at that until the state changes and not "control" type of notification/command that can be referenced once when that condition/state charges. Thank you for the response, I will try this approach out.

I have a program that is set to trigger a lighting scene when the deadbolt is unlocked via the keypad between Sunset - to Sunrise +. I am using the deadbolt access alarm status "keypad unlock" and the parameters to initiate this and trigger the "then" path of a separate program to set the lighting scene. This generally works as intended but the issue comes about when the deadbolt status hasn't changed from "keypad unlock" and the trigger time of day comes around again, thus triggering the program to run since status is still "keypad unlock". I am looking for a solution that only triggers the program once when the deadbolt is unlocked and not again if the deadbolt remains unlocked and the trigger time comes around again. Unfortunately the access alarm parameters are only "status" and not "control" for the "keypad unlock" condition. For clarification there is another deactivation program for the trigger lighting based on time of day or by manual deactivation. Any thought/insight on resolving this is greatly appreciated.

Thanks to all that responded. Since I deleted the program, the issue has not resurfaced.

So following my deletion of the program it was included in, it hasn't occurred again; fingers crossed!

Thank you for your response. It, along with one other device, is associated with 1 program so will just completely delete that program, reset the local ON level to 100% and see if it occurs again...

I have the most bizarre issue occurring with a single device in my system and am looking for any possible insight. I have a single SwitchLinc 2477D that has continued to have random OFF events occurring and in conjunction with that, the local ON level setting chages from 100% to 40%. This is an entirely new system in a 2nd residence that I have set up up from scratch on a new eisy that is currently running 5.9.1. I have another very extensive system that is currently running on a Polisy, upgraded through several iterations starting with ISY 99i many years ago so am very versed in this and have never encountered anything like this previously. The initially installed switch that this was occurring with was a brand new device and after a couple months of this issue randomly occurring and me completely factory resetting the device and restoring with the issue continuin to return, I replaced with a completely different switch and the issue still was randomly occurring. I have completely deleted the device, added as a new device instsead of restoring and this issue still returns! I have checked all of my programs and associations and there is nothing I am seeing that could be the possible cause of this issue. I have reviewed the logs and all is see is a status change to "off" when this occurs and no other events happening in the immediate timeframe leading up to it. Any insight as to what I could look at would be greatly appreciated.

Just tried logging into portal and get "HTTP error 429" message and remote access to UD Mobile is not functioning either.

Down here as well.

Just did this and resolved my issue as well, thank you for posting!

Just checked and mine just reconnected a few minutes ago too.

Unfortunately mine still remains disconnected.

Thank you, I appreciate the quick response and will continue to wait.

I have received the notice that the portal maintenance was completed but unfortunately my system's connectivity has not resumed. When logging into the portal, it is still showing as disconnected with no remote access to UD Mobile and Alexa connectivity. I am running a Polisy Pro on v5.8.4.

I just got home from a trip and found my routines that announce sensor change of state are no longer working. I can’t be sure when they stopped for sure but was sometime between last Wednesday and today. I have tried disabling and rebuilding with no success. I am running Polisy Pro on v 5.8.4