hart2hart

@Goose66 Thank you for developing this NS. I installed the nodesever and then discovered two Encode Plus locks! I locked and unlocked them both and see the Battery %. This is already more than I expected with these locks after conversations with Schlage staff so if you can implement the user name or number that locked or unlocked, I'll be 100% in business. Based on NS info, do you think 10 is a good value for short poll? Does the NS get status updates in real-time from Schlage Cloud or does NS poll for updates at each short poll? Probably should know this but what is Force Update? @MrBill

Upgraded yesterday afternoon and all running good. Thanks for upgrade steps.

I’ll be checking it out soon too! Very interested to know if the library supports the Encode Plus.

Smooth update to 3.1.36.

Thanks for the information. I’ll be updating tonight. Are the correct steps and sequence? Upgrade packages Power cycle eISY to get full reboot Reinstall all node servers Restart node servers

It may not be relevant but just more information… you might use a state variable if you Disable the program as first step Set the state variable Enable the program

I’m with you. Maintaining codes from native app is fine and I’d likely never do it from eISY.

The support of UD and this community is world class. It may not be your favorite pick up the phone for every little thing. You get direct support of product creators as requested and the community is very responsive at providing a “simple answer” very fast.

Thanks @Goose66 for looking further. It appears we could meet a lot of needs with this api. I see lock, unlock, manage access codes, and event notification like when it’s unlocked and by whom.

Maybe I’m missing something but there is a replace device option. I replaced a failed Insteon dimmer last week. Just remove the failed device from folders first.

There was a Ring nodeserver that ran in cloud on UD servers that would have done as you described. That was discontinued a year or two ago. Today you need an eISY to run nodes servers and replace the ISY994.

Something went wrong with your original plm restore. That’s been fixed now but it sounds like the devices do not have links to the plm. By doing update device on each device now you will likely be good. I’d do a device at a time and confirm eISY and plm are seeing star changes.

Is 70.1A.92 the address on the back of your new PLM? It appears that when you transitioned between ISY994 and eisy that something lost track of PLM addresses and doesn’t know you’ve swapped PLMs. If PLM replace works it will write all device addresses to the new PLM and then move through each device and write the new PLM’s address to them.

Thanks for the deep dive. I’ve been loving the locks and wife appreciates the smaller inside footprint. I’d likely be happy using either method if the api goose 66 located will work for more integration. I actually added my two 300 series Schlage be469 locks back into service by putting them an inch from the zmatter zwave antenna and then once interviewed by iox moving them to basement and garage. Hi

Found answer in NS Document. Thanks

@DennisC it was the remote access you mentioned. I had turned it on and it showed enabled but had never connected. Michel coached me to go back and look again.

I'm ashamed to admin it but I had the lat and long reversed in the params so if you see these error messages...

I had the same issue and resolved it by loading from the LAN.

Thank you. I’ll always help test.

@Goose66 Great NS. I’d like to see a feature so i can disarm using multiple codes instead of just the one code that is in params. This feature would support sending the being forced to disarm code. Thanks.

Does NS support the Caseta ceiling fan switch?

Installed last week and working flawlessly!

Thanks and that is an interesting solution. At this point, I'm using these two programs to catch and isolate Armed status into a State variable. If the programs have issues, I'll try your solution. Security:Set Armed If ( 'Security System / Security System:Partition' Partition State is Armed Away Or 'Security System / Security System:Partition' Partition State is Armed Away Zero-Entry Or 'Security System / Security System:Partition' Partition State is Armed Stay Or 'Security System / Security System:Partition' Partition State is Armed Stay Zero-Entry ) And $Security_Armed is not 1 Then $Security_Armed = 1 Else - No Actions - (To add one, press 'Action') Security:Set Disarmed If ( 'Security System / Security System:Partition' Partition State is Ready Or 'Security System / Security System:Partition' Partition State is Not Ready ) And $Security_Armed is not 0 Then $Security_Armed = 0 Else - No Actions - (To add one, press 'Action') I have equivalent programs for Armed Away and Armed Stay.

Again, Thanks for the insights, Goose66.

Thanks for the insights.