paulbates

You also have to move the existing motion sensor up to the root level folder of the first iox tab. You can move the new back to it's location after the replace finishes. Trice can be quicker/easier, especially if scenes are involved

I didn't go back and check the thread, but another cause can be Insteon wireless devices, specifically the motion sensor. When batteries get low they can do random things... but... ... they would still occur with the PLM unplugged. Here is the the evidence you have: PLM "choked" when doing a Restore modem (not normal) Problem goes away when PLM unplugged Insteon can work perfectly forever and then slide into problems like this and there are not always easily resolved in a straight line diagnosis. At this point, barring any other recommendations, I would be replacing the PLM on my system EDIT: Follow the PLM replacement procedure, its not just swapping out the cables.

Another possibility is, if possible, plug non-Insteon electronics in the closet into a single power strip, and plug that power strip into an Insteon filter module. (Don't plug anything Insteon into the power strip). This will isolate the line noise from your powerline. If everything won't fit in one power strip, chances are it's only one or two of the electronics in the closet, and rotating through plugging things in and testing will prove it out EDIT: Chances are, whatever the most recent non Insteon addition to the closet is the culprit

That's my thought 2) Electronics are notoriously noisy on the powerline, and the iolinc has no rf, powerline only. ezfloras are powerline only also, I had 2 of them If you have a spare lamp or on.off module, try plugging the iolinc back in the closet and the module directly into the back of the iolinc. Lamp/io modules act as rf repeaters. It might also help the ezflora, some testing needed. If you don't have a spare, temporarily borrow one to test. If it works, you can order one for this purpose

2 thoughts Since it's being reused, factory reset it: Unplug it from the wall, hold the set switch while plugging it back and and keep holding the set switch till it beeps. Try adding it again Io lincs use single band communications, not rf. Plug it in the same outlet as the PLM, try re-adding it and move it back to the install location and test its operation

Thanks guys!

I'm preparing to upgrade my eisy to 6.0 / eisy-ui in the near future. I've been following others progress from afar. I think the disk space issue and using the df command were related to policy. I sifted through some of the threads but not 100% sure and want to be sure before proceeding. My command line days are getting more behind me and have no time logged on FreeBSD. I was able to ssh in and run df. Here are the results. I should not run into space issues?

It's looking to me like the PLM is in the initial stages of failing. Do you have a recent backup?

Brian would know that answer for sure. It looks like the plm as a problem is a dead end, unless you find no other solution.

Gotcha. In the same boat as I use an ipad a lot

or, the PLM is having difficulties and the restore prompted it. Hard to say. Have there been any power surges that you know of, or brown outs blackouts recently? Another test of the PLM, which will affect programs, is to unplug it and wait for the problem to reappear... but if anything critical is handled by your iox programs then DON'T do this test.

One thing I've noticed following the v 6 upgrade threads is that sometimes switching from Safari to a different browser helped some people.

The next step is suggest is a restore modem / plm from the file menu in iox. If that works, it's likely a bad plm on the the way to failure. Let's see if it does help. Again, if it does help, it is not all set, this is a symptom of a dying plm If it doesn't work, now much lost including time.

Ok. That means it was manufactured in the 28th week of 2017 and making it 8 years old. There's a time around then when Insteon remedied a problem with capacitors that caused the early demise of PLMs, I don't know exactly when so it's candidly tough to call it as the root cause to me. I would still say it's likely Here's some more steps In iox. Go to tools / diagnostics / PLM info. What does it say? Report that back There's another step but it comes after hearing what the first step reports

How old is your PLM? An older PLM nearing end-of-life is a possible explanation. If you don't know, there's a white sticker on the back with 4 numbers on it. What are those numbers?

Sounds like the thing to do is SSH in and check that prior to proceeding with the upgrade

There's a google holidays plugin. I don't use it so can't say exactly what the current state is, but you can find it in the forums, look at comments, etc

I'd try a "restore device" to both devices (separately). If that doesn't get it, try factory resetting the lamplinc and restoring. If that doesn't work, the next step is getting a ladder for the fan linc

I would leave it alone for longer. Do you have any of your devices set to "Blink on traffic"? If yes the devices led will blink regularly / repeatedly as the eisy does its work..you can look at that. You can also look at the PLM led, it should be blinking regularly/repeatedly if it's still updating You'll have green 1011 nodes for wireless devices. If you're down to just wireless devices with that icon, You'll want to gather them together if possible. One at a time, put them in "set" mode and right click and pick "restore device"... wait for it to finish and continue on. If you can't bring the wireless devices to the computer running the AC/Iox, it can take a while.

The soft release of 6 may have done it unintentionally. I'd open a ticket.

I'd recommend submitting a ticket before taking more direct actions. This problem is not on the "usual suspect" problem list https://universal-devices.com/my-tickets

Here is the link for the specs. Scroll down or search for Variables https://wiki.universal-devices.com/ISY_Developers:API:REST_Interface

That's also a reasonable assertion, except I ran it in the distant past and moved to v3, "un-configured" the old skill... and did not get that email I think if we have v3 running, ignore the message

Is is possible you haven't gotten rid of older version(s)? If you have the older version of Amazon Alexa skill loaded for your Alexa, that would explain it

See this thread There is a newer skill that we all should be using