hart2hart

Good! If I recall correctly (@MrBill or @Geddy can you confirm) the ISY will show devices in Safe Mode. Given that no devices are showing, could this be the ISY that was never used? Maybe you could power it off and pull SD card from the other ISY and then restart to see what you get by following same steps.

Ethernet to USB is not the right adapter. As @MrBill points out it would require a serial to usb adapter and if memory serves me correctly the ISY does not support its use. I believe the goal with the ISY994 is get it running enough to run the proper upgrade and migration steps to obtain a proper backup that can be used to migrate to the eISY. The next step is to move further into the AC. With IoX, when you click on the ISY link do you get launch from cloud?

Are you plugging the ISY994 into same Ethernet cable that the eISY (or is eISY on wireless wifi) was plugged into from your original posting? Is the PLM plugged into the ISY994 and the PLM plugged into an outlet? So we are on same page., can you snap a photo of the ISY994 showing all the wires it is connected to when all plugged in?

Good. Sounds like you may have at least one working ISY994. Can you locate the other ISY994 to see if it powers up? If the other one does not power up, it may be the one you’ve been using most recently and hence, it’s SD card would have the most recent data. Keep in mind if it does not power up that we need to try the power supply from the ISY that did appear to get power. Let me know how that goes.

Thanks for your service to us and our country. With other here, I’d love to assist you sorting migration to the great eISY if possible. If it is ok with you I’d like to take one step at a time in the process? As others said, it would be so much easier if we could get the ISY 994 back or at least the data on SD card. You said your ISY994 is dead. So to determine if it might be the power supply, does dead include as a symptom that none of the ISY994’s blue LED lights come on?

Thanks. Based on description, it felt like it was pure polling. I do have a Ring camera (mapped to the Ring NS) in the garage that I could use to detect motion and then Force Update just before lock entry so I’ll keep that in mind as future unfolds.

Thanks for the explanation. Is there anything we as users of the NS could do to make it easier? Pure spitballing here but could we “see” the GUID Name string in the NS log and then create a custom parameter to map it to an integer “user number”?

Thanks again, @Goose66 . I would like to see the user name or number available when the lock is unlocked and/or locked. I would use it to disarm the security system.

@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...