hart2hart

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')