MrBill

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.

No it's tomorrow, Friday June 9th at 9AM PDT. (being very specific because the time attached to it has been confused and misstated by Insteon.)

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 have all the same items in the circuit as you. I do have an Insteon noise filter plugged in between the wall and the UPS.... the PLM however piggybacks the noise filter (plugging into the front passthru plug). When I need to find a new noise source I tend to turn off half the breakers in the panel see if it works, turn those back on then do the other half... then keep halving the halves until i get it down to on circuit, then hunt the circuit.

try unplugging it or turning the breaker off if you can. Why? Oddly I had a deep fryer in the kitchen in the past that if plugged in a turned off, or turned on and not heating created insteon noise. if it was actually turned on and currently heating insteon worked fine. moral: you can't assume "not running" means not creating noise or sucking signal (which is a related topic).

After doing this you would need to "restore PLM"... unfortunately that will restore the entire network. I honestly don't know what would happen if you tried to delete stuff in ISY B then "restore PLM". The problem is Insteon writes links in every device that include the PLM's address... you need all those links rewritten which includes the links stored in the PLM and in all devices--- this is what "Restore PLM" does, if it discovers that the PLMs hardware address has changed it needs to update and re-write the links in all devices.

I agree with @kzboray that it's likely noise. One question to ask yourself is have you gotten anything new lately? TV, kitchen appliance, any appliance for that matter... etc Don't rule out bad MicroSD card. After you install a new MicroSD (up to 32gb, look for A1 rating) the first thing you need to do is reinstall the firmware (the boot loader copy that allows you to log in is not complete) I'd re-install 5.0.16C assuming since you have a 300 series z-wave board... 5.0.16C is far more stable than .16A was..... After loading firmware then restore your backup. that's a 300 series board.

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 can confirm this to be correct. I have two separate Insteon networks in my house. One system only has a couple of devices and and is used for text. However I note that singles are echo'd (blink on traffic) by all devices in the main Insteon network.