paulbates

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

The 2440M is a wireless hand held remote. I don't think its been sold for years. The 2842-222 is commonly referred to here as an MS-1. Also no longer sold and replaced by the MS-2 ... I forget the product number, its the only one you can buy

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 did this at my last house. Hydreon is still around. I connected it to an iolinc, but you should be able to substitute YoLink's i/o contact, which I have been considering to add to this house

I know for mine, that if the batteries ran down to dead (or close to it), it sometimes made them flaky. I started factory resetting and doing a restore device, after each battery change. Mine were 6 years old and still working when I sold my last house

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

So the original post here cast a wide net asking what could it be. I have experience with Insteon (an other things electronic) getting flaky and/or dying based on significant power events. If you can trace the difficulties you're experiencing back to starting around that time, it's possible that the power event did more than just black out and some devices were damaged. That would give you a path to focus on. I lost Insteon (and other) devices in the past after black outs/brown outs. Some Insteon device were recoverable with a restore device. Some had to be factory reset and restored. Some had to be replaced. Afterwards, I added a whole house power conditioner to my panel. I'm also confused in that the original other post was about scenes not working correctly?

Not necessarily but it can. One way to approach it is to turn breakers off one at a time to see if the problem is solved. Do it in order of suspects first... things with motors, big transformers, big electronics. You can even start by unplugging those things, where possible. Takes time, note taking and discipline. For the devices not responding to scene test... that's the scene test doing its job. Have you had a major powerline incident (blackout, brown out, nearby lightening strike?) Are they on the same circuit? How old are they? Are they powerline only (might have to replace if Yes) Try restore device Try factory reset and restore device Not always. I automated my 12 volt yard lights. The transformer I bought for them, only 60watts, almost completely blinded the i3 outlet I plugged it into. I was able to move the switching function to a switch that powered the circuits and was 30 yards away from the outlet. I should note that the transformer noise ultimately killed the i3 outlet. It's been a couple of seasons since moving automation to the switch and it never misses. These problems are not always easily discoverable or visible. It's one part thinking through "what have I changed or added", one part diagnostics: same circuit, older devices, etc. and one part discipline... come up with an order to test and move through it. I don't remember your other post on this but an aging or damaged PLM could be responsible by writing bad data its created to the devices over and over again.

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