MrBill

Did Finder find the eisy or did you need to manually add it in the Finder window? If you needed to add it did you include a port number? 8080 for http, or 8443 for https. http://192.168.1.222:8080/desc https:/192.168.1.222:8443/desc of course your IP address will be different. ISY994 didn't need a port number, eisy does.

I figured we were reading it differently but thought i should contrast in case the PLM is indigo based.. because he may loose his links if he restores PLM in this case. May be recoverable from indigo, but i know nothing about Indigo other than it's Mac OS only..

a PLM connected to Indigo, correct? In that case the ISY wouldn't have the links table, and i don't know that it can be read from a PLM to a new controller. I think Restore Modem in that case would clear the PLM because that's writing new links to the PLM, and there are none in the ISY. @DennisC read your comments differently than I did, I'm not sure what his thought was...

The Schlage Encode Plus (BE499) has now been installed. To answer the specific question "can Homekit/Home app and Schlage Home app co-exist?" the answer is Yes. However there are some serious shortcomings, that frankly I blame more on Apple than I do Schlage. Basically, Users can be created either in (Apple) Home or Schlage Home. Users must be managed from whichever app created them, not interchangeable. Once the User/home key/guest code is created in (Apple) Home the lock can be unlocked very quickly and awesomely in using an iPhone or Apple Watch. The home app can be configured to send notifications that will show locked/unlocked status, and if by another user the notification will include that users name. Other than the notification, there appears to be no other way in (Apple) Home to see the history of the lock. (specifically for example: there is no way to see who unlocked the door or when UNLESS the push notification from the Home app is still around in iOS Notifications.) A lot of the (Apple) Home app notifications are pretty generic too, for example "Front Door was locked" "Front Door was unlocked" with no information about the source (By Contrast, the Schlage Home app notifications include words like "Locked by Thumbturn" vs "Locked by 1-touch Locking" which tells you if the person locking was inside (staying) or outside (leaving) when they locked the door. In the Schlage Home App Users can be created with code only access (no HomeKey). The Schlage users can be scheduled (Apple users and guests can not be scheduled), and there is a slide switch to turn notifications for these users on/off by user. Viewing History in the Schlage Home app shows every lock and unlock, but if an Apple device was used it simply shows "Unlocked by Apple Home Key" but not whose home key. I take this to mean that Apple won't let that detailed information be known. I've experimented with one of the Home Assistant integrations installed via HACS, the information supplied is basic, locked/unlocked state (with user name if it's a code Created via Schlage Home) and Battery state. Haven't had time to look at a few others i find at github, I'll report back if any of them turn out to be better. I had more expectation based on what's been built into the pyschlage library linked at the top of the thread. @Goose66 @hart2hart @lilyoyo1

The tempest is horrible at measuring very light rain. Tempest reported like .19... an old fashioned glass rain gauge, that wasn't even out at the beginning of the day collected over half inch. This is one large reason, of several, that I'm not impressed with Tempest. Another is that it's twice failed (disconnected) during rain events. For one, Weatherflow said the sensor had failed and replaced it immediately. They second time they told me I needed to power cycle it, and since the sensor is hard to reach I hadn't done that yet, then it suddenly came online by itself after about 4 or 5 days.

I'd try moving the lamplinc temporarily for testing to the same circuit at the PLM. That's just generic Insteon troubleshooting tho, not sure how Zmatter could interfere... the radio's are different frequencies.

did you restart the admin console after adding the nodeserver? The admin console only finds nodes on startup.

might be related to:

@JPStokes Try deleting that slot in the admin console. Note: your slot number is very likely different than mine. if that doesn't work, or if it comes back, then open a ticket. they will likely need to manually remove the old on the backend.

I see no information about java 20 on https://www.java.com are you certain you're on the correct site? this link has the manual installs which include the linux version (scroll down) https://www.java.com/en/download/manual.jsp As @kzboray point out you need to remove your existing java first. the prerequisite here is knowing enough about whatever flavor of linux you're running to uninstall the incorrect version of java and install the correct version.

@CPrince you'll probably need to open a ticket to find out what the first line means and what could cause it. Tue 2023/06/06 12:48:20 AM 0 -101 portal the successive entries we both assume to be reconnect attempts.

Tools > Error log in the admin console. When you say nothing do you mean the error log is empty (which doesn't sound correct) or no entries match the time of disconnections and reconnections?

That doesn't look like Java 8 to me. might be a way to make it work, but you need a java magician.

Does the ISY Error log give any clues as to why it's disconnecting? This morning @bmercier had a scheduled maintenance that caused interruption, but it sounds like your speaking of much more frequency.

I've never had that model. First step is always to try removing, factory reset, re-add. If that's not helpful hopefully someone else with have another suggestion.

What specific insteon 4 digit number outlet are you speaking of, there's more than one choice over time for outletlinc ? did you try deleting it from IoX, factory resetting it, then re-adding it?

Make multiple concentric geofences, such as a larger "neighborhood" and smaller "home". Then construct your program(s) such that the larger "neighborhood" boundary must be crossed first.

I just re-read from the top of the thread and wonder what java you are using? The admin console is written/optimized for use with Java 8 from https://www.java.com there is a linux version available. You don't need anything fancy like the SDK or other specialized versions. Other flavors of Java will likely work, however you will likely have to mess with the environment etc to get things to work perfectly.... unless you're an elite java junkie or have other reasons I'd stick with Java 8.

With the IoX launcher downloads the correct version of the admin console each times its run. Choosing LAN should download it from the ISY itself, however security/firewall/etc may get in your way. Choosing Cloud gets it from a UD server (hosted at aws), generally choosing cloud is faster, especially when using a 994 because the 994 must encrypt to file before it's sent to the browser and the 994 doesn't have a fast processor. admin.jnlp can be downloaded directly from the ISY at http://IP.OF.THE.ISY/admin.jnlp Keep in mind there is no version control with this method. In other words anytime the firmware version is changed, you must remember to delete the old admin.jnlp and download a new admin.jnlp Use Help > About to determine if you have matched versions or not.

Re-writes the links stored in the device. When a scene is turned on, the Controller might be the ISY or it might be Switch or Button programmed as a scene controller. Controller and/or Responder links are written to each device so that the device knows if it's a member of a scene etc. This makes it possible for a scene to work faster and without the need for the ISY to even be functional. A controller sends "Scene On" and Responders listen for the command. If a link somehow becomes corrupt in a device it won't respond correctly. Restoring the device causes the links to be re-written or restored to what the ISY thinks should be there. If restore device corrects the problem then a link had become corrupt. There's a complicated method to view the links and manually compare them but only a few people in the forum can read them and give advice whether they are correct or not, so I just suggest blindly re-writing them when it could be an issue.

@Jay M One at a time, right click each device in the scene then pick "Restore Device" from the context menu.

I've been deep into the differences and the Schlage documentation today and ended up swapping up from Encode to Encode Plus. I feel that the API will work the same with both models. and two, I doubt Schlage will change too much of the API because they have shared it with Amazon and Google.

I believe encode plus is the HomeKit version.

I found this thread: And don't see newer information in the forum. @hart2hart 's quote Things may have changed. I was researching this Schlage Encode recently because it's an option that's only a small increase in the options on a custom front entry I was ordering. It appears Home Assistant has a custom integration installable from HACS, it also appears there is a separate python library available. Given that a Node Server should be doable now. those that participated in the original thread are: @RandyT @hart2hart @lilyoyo1 I placed my order with the Encode Wifi lock... I'll update after it's installed. It's unclear to me if Lock/Unlock is supported, but Status (locked/unlocked/jammed is reported, and last code used to unlock Id# and Name#. Edit to add: I just looked at the documentation for the python library, apparently it's reverse engineered but includes all or most abilities, including code changes, lock/unlock... etc

Why should Doc's be repetitive? If anything perhaps a migration Troubleshooting section could be added, "if you're seeing this then see step __ of the migration instructions."