hart2hart

@Goose66 , thanks for your insights. I believe I have success again. The issues were: I was completely overthinking LOL I, for some reason, was thinking of fields coming over from plug-in as multiple fields like an atomic database transaction when they are clearly coming over serially and can't fully tell order they will be posted to eISY. Solution was to remove all the other fields as trigger part of IF. The fields last message and last unlock user are all that are needed. They function as a IF Status so they only trigger when that field changes. I'll test more but looking great now. Once I'm a little surer of solution as a way to use the cloud polling with associated timing issues, I'll create another thread with the core programs and description for others to provide feedback and potentially use and refine. Again, thank you, @Goose66 . EDIT: AS I recall, all programs are effectively disabled in early part of restart/reboot to prevent a fire storm of program activations. Is this right and does it include during plug in initialization? Paul

Thanks. I upgraded on a reboot too. Good to know what happened.

I followed your thought and short poll is set at 10. Is that still reasonable?

Thanks @Goose66 The queueing information is very helpful and confirms what I came to understand but I wasn’t thinking that way in original post. I’ve got test programs in the multi step method like you mentioned and some kinda like ones I posted above. I’ll keep at it and will post final results including limitations. Others may find it useful to automate other things based on the locks The encode plus locks are great and I really like using iPhone and Apple Watch to contactless unlock them especially after a run. I am now going to create programs to lock any door that is showing as unlocked when security is armed Thanks again for the node server and advice Paul

Thanks, @Goose66 I'm completely down with your thoughts and that's why I'm trying to engineer the timing to get this done. Clearly, it's a first world problem to automate unlocking deadbolt as signal to disarm security a few seconds later. However, I'm not sure where to see log updates from the plugin other than the one place and I can't find mention of any of the fields being updated in that log like say the weatherflow NS that generates a ton of them. Okay a little more thought on it and I think I'm closer... I'm using lock status, last message, last message time, and last access code used. When the short poll or force update is executed, what order (or is it an atomic transaction and all the fields are being updated and then committed at once like database multi record update atomic transactions) are the fields updated from node server to the eISY environment? Theory is that last update time is being "sent" to eISY first and it triggers program. It then is seeing older data from other fields as those fields have not yet been "sent" from node server. For this to be a credible theory, it would mean there is a bit of a time gap between fields being sent to eISY if the change is not atomic as I suspect. Make any sense?

Did you try to add via simple start linking and then putting ms in setup mode. It’s the only method I use to add devices but admittedly haven’t added a ms in many years. Got rid of all them once I added Ring cameras with motion via Ring plug in. Edit. Thinking a bit more maybe you can’t link ms using that method.

deleted.

Thanks. Unless something went wrong, I updated packages last week or so.

Thanks. I will submit ticket. I’ve seen it on Schlage and envisalink-DSc and think I may have seen it couple other places dive the pg3x update a week ago.

Is this recent update?

It appears you didn’t do a replace device and just added the new device. Therefore the removed device is still reference in those programs. You need to update programs to do whatever is needed using the new device.

@Goose66 Without Plugin writing to log, I've done about as much as I can. I had iPad with UDM running so I could watch Schalge last fields. When I increased the short poll, the issue of immediately disarming went away so short poll was causing the trigger. With short poll being longer, I closed and locked deadbolt and last message did not change so I press Force update on iPad UDM. This seemed to keep it from "false" triggering based on old data. Program that would have disarmed security did not trigger but this was mangled around the issue with the DSC plugin not working properly after power failure reboot. It's hard to be certain but it appeared there was a time when Force Update from program only updated the last message time but not the message, so program triggered based on message time change. However, it still had message from the last time i unlocked the deadbolt vs message where i just locked the door to do the test. Sorry for all the typing and conjecture on my part, how can I/we debug? Thanks

@Goose66 I noticed once before and thought it might be a fluke, but I had a power failure today and a couple hours later was testing on the Schlage issues. It didn't make sense results I was getting until I realized the DSC plugin was not updating fields. Restarted it and status started showing. With a little more work, it appears same happens to Schlage after a reboot. It did not do this in past so I'm guessing the latest PG3X update may have conflict with plugin. Can anyone else confirm issues after a reboot that has latest update installed.

I’ve been using one on a bird bath heater and fountain for several years.

I've confirmed as much as I can that it is triggering programs based on "old" message data that I cannot see in AC and UD Mobile because the last message data I see should not be triggering the programs. I'm going to test by increasing short and long polling as I think that is when the program is triggering with what appears to be stale data to me.

Any possibility that recent Polyglot upgrade could have contributed to this?

I'm getting odd results but when trying to debug I realized the fields like last message, access code, and last time are not flowing into the general eISY logging system. The following programs trigger based on the last way the deadbolt was unlocked without the code from above that does a Force Update even running. I could see that last message is "Locked by Schlage Button" so I'm lost. Garage:Deadbolt Unlocked By Apple Key - [ID 01F6][Parent 0124] If $Security_Allow_Schlage_To_Disarm_I is 1 And 'Garage / Garage Door' Last Message is Unlocked by Apple key And 'Garage / Garage Door' Last Message Time is not '$Security_Armed_Garage_Deadbolt_Last_Message_Time_I Unix Timestamp' And 'Garage / Garage Door' Last Message Time > 0.0 Unix Timestamp Then Set 'Security System / Security System:Partition' Disarm Send Notification to 'JPaulText' content 'Security Disarmed Via Schlage Message' Else - No Actions - (To add one, press 'Action') Garage:Deadbolt Unlocked By Paul - [ID 0125][Parent 0124] If $Security_Allow_Schlage_To_Disarm_I is 1 And 'Garage / Garage Door' Last Message is Unlocked by keypad And 'Garage / Garage Door' Last Access Code Used is '$Security_Code_Paul_I User Number' And 'Garage / Garage Door' Last Message Time is not '$Security_Armed_Garage_Deadbolt_Last_Message_Time_I Unix Timestamp' And 'Garage / Garage Door' Last Message Time > 0.0 Unix Timestamp Then Set 'Security System / Security System:Partition' Disarm Send Notification to 'JPaulText' content 'Security Disarmed Via Schlage Message' Else - No Actions - (To add one, press 'Action')

What is expectation for the data to update after the Force Update command is issued?

Still researching and testing. There are three messages in last message list without a description. They are: o Unknown o Unknown (both unknowns show at the top of the drop-down list) o 31 Also, there is a message type called "History Cleared" in the drop-down list. Does that imply the node server could have a command that would clear all history. If so, I could run that command when security is armed to make it simpler as I suggested in option 2 of original post.

...a bit more, the fields for the deadbolt from node server appear to only support Status and not Control so this means if field happens to have same value as last time, it will not trigger -- correct? If that is the case, should I put in an additional If like IF the epoch date is > 0 to ensure it always triggers program when it changes? Can the field be defined so it triggers with Control or Status? It feels like the IF section for comparing Old stored and current event epoch times may always force a trigger as the new date changed.

What version does Finder or AC report you are running? 6,0.3? 6.0.0? When you go to Polyglot, does it report and update to 3.4.5?

@Goose66 , this node server is great. I've been using open action of Schlage lock to disarm my security system for a few months and with Force Update, its great! There is a "flaw" in my programming that I recognized with my scheme, so I always make sure the last message is locked by handle on the door. Without describing it completely, with scheme I'm using if last message was a disarm with code. and I forgot to actually lock the door then just opening the door would result in a security disarm. Now that Apple Key is working, I want to expand auto disarm to four other locks but not with the flaw that requires me to confirm contents of last message each time security is armed at all locks Methods I've considered: 1) Get last message time and confirm it was in the last say 10-15 seconds. Issue is I can't locate how to manipulate current time into epoch time with eISY program (also couldn't find a node server that does it) to do the math. On one of Jimbo Automates node servers, he added seconds since last update element so someone could monitor the device had not changed. Would that we possible with this node server? It feels this would be the best option. to control and feel good about not hosing security. EDIT - I just located how to set variable to current epoch time so evaluating how that might help. 2) Another possibility would be if there was a way for me to request node server to clear the last message and user code fields at the time security is armed. Flaw here would appear to be would the fields get set again at time I did Force Update. 3) Finally, at the time the security system is armed, store and persist the current value of Last Update epoch time in a variable and then when using mostly my current scheme add to the If to say current last update time is not same as the value stored in the variables. Easy enough it appears, does it sound reasonable to prevent what I described as the flaw. What do you think? Example programs using this method: Security:Store Last Update Times for Locks at Armed If $Security_Armed is 1 Then $Security_Armed_Garage_Deadbolt_Last_Message_Time_I = 'Garage / Garage Door' Last Message Time Unix Timestamp $Security_Armed_Garage_Deadbolt_Last_Message_Time_I Init To 'Garage / Garage Door' Last Message Time Unix Timestamp Garage:Deadbolt Entry Delay Disarm With Schlage Code 'Security System / Security System:Partition' Partition State is Entry Delay And 'Security System / Zone:Garage Door' Zone State is Open Then Wait 1 second Set 'Garage / Garage Door' Force Update Action of Short poll (10 seconds) or the Force Update from above triggers following programs Garage:Deadbolt Unlocked By Paul If 'Garage / Garage Door' Last Access Code Used is '$Security_Code_Paul_I User Number' And 'Garage / Garage Door' Last Message Time is not '$Security_Armed_Garage_Deadbolt_Last_Message_Time_I Unix Timestamp' Then Set 'Security System / Security System:Partition' Disarm (it uses the user code to disarm but that doesn't show in the program copy to clipboard) Garage:Deadbolt Unlocked By Wife If 'Garage / Garage Door' Last Access Code Used is '$Security_Code_Wife_I User Number' And 'Garage / Garage Door' Last Message Time is not '$Security_Armed_Garage_Deadbolt_Last_Message_Time_I Unix Timestamp' Then Set 'Security System / Security System:Partition' Disarm (it uses the user code to disarm but that doesn't show in the program copy to clipboard)

@Goose66 , I contacted Schlage support and received updated instructions compared to when I first purchased the locks. The locks now work all three ways: 1. Schlage App 2. HomeKit app 3. Nodeserver The new instructions is to add to Schlage App first and then in the Schlage App to take option "Works With Home?" to add them to the Apple Home app. I can now unlock with just touch of iPhone and Apple Watch.

Click Start Linking and then Press and hold set button till it dings always works best for me for adding devices. Is that method you used or did you key in the insteon id?

Try the login credentials you used before 6.0.0 was installed.