slimypizza

I just updated my system remotely from 5.7.1 to 5.8.0. Went without a hitch. I only had to clear java cache and reinstall IoX after the update and reboot. Not sure what the update afforded me but I like to stay current.

I think Insteon runs very easily with Home Assistant (Pi4). But I guess YAML and the cards do present a learning hurdle. HA is a great front end with the heavy lifting handled by EISY.

Thanks. I'm Version: 5.7.1_7. Good to know!

How do I know which version of 5.7.1 I am on? When I launch my admin console and got to Help->About, all I see is that I am running 5.7.1. There is no 5.7.1_7 or _5 or anything else. Is there another place to look?

Same here. It seems to want an update for: pkg tpm2-tools must be upgraded to 5.5_1

Was (sort of) happy with MyQ for a year or so but the recent persistent login/connection issues were too much for me to want to deal with. Installed the Insteon I/O Linc Garage Door Control over the weekend and all is well. Disconnected the MyQ unit which had come with the house we purchased last year and I won't consider using it again. The Insteon unit integrates well with my EISY and HomeAssistant system and is much speedier triggering events such as turning on outside floodlights when opening the garage door in the evening, and the integration with Alexa is smooth and instantaneous.

I’d been putting this project off for a while but yesterday decided to proceed with the migration from ISY994i to EISY as well as installing a USB PLM. While not trivial, I did complete the migration in an hour or so. All in all it went….okay. There were a couple of confusing moments (causing me to initiate perhaps needless multiple reboots of EISY and my router) and the migration guide could probably use some editing but it got me through. I don’t use Z Wave but I do use Home Assistant as a front end which required deleting then reinstalling the ISY/IoX integration and for some reason I had to rename a few devices in HA and one Insteon lamp module had to be reset. The portal transfer was straight forward. I’m glad I remembered the free trial step. All seems to be running well and I have my old ISY994i and PLM as a back up should I ever need it. I don’t see any performance improvements but my ISY994i was working just fine anyway and while I do have a lot of programs it’s not a huge number. Alexa seemed unruffled and there was no need to rediscover devices. The EISY seems to run hot but I think I read that is normal. Thanks to all who posted their prior stories and solutions to problems. That was a big help to me to read before attempting this.

Just a thought but how are you assigning the static IP address to your new ISY994? Are you making the assignment in the router based on the MAC address – of the old ISY994? The new ISY994 will have a different MAC address so the old assignment will not work. Assuming this is what is happening, you will need to enter a new static IP assignment based on the new MAC address.

I inquired a few days ago (4/19) about EISY availability. Here's the prompt reply I got: Hi John, we should have them in 2 weeks. With Kind regards,

I have a couple of Kasa plugs and use Home Assistant to integrate them into my system. I have HA running on a Rpi4 and is a fairly simple solution to integrate Kasa and other protocols (Nest, Blink, SmartHQ, MyQ, etc) into a single interface.

You say this has happened a few times before. You really should consider a UPS for your Polisy and avoid disruptions due to quick power off/power on occurrences.

I subscribe to the ISY portal but that’s not how I access it remotely. I have a reverse proxy set up on my router and access the ISY remotely via a URL on port 443 (which is open anyway).

I use geofencing and haven’t had too many issues with it over the years. I formerly used (ios) Locative to send REST commands but when I started using Home Assistant (HA) as my front end UI a couple of months ago, I took advantage of the trackers it has that tie into our cell phones. Setting up a geofence through HA was easy and we deleted Locative in favor of this approach. I use this for our system to determine if we’re home or not. If everyone is away, that triggers a set of (ISY) programs to turn lights on/off and set thermostats. When someone comes home, the garage door opens and a subset of lights come on depending on the time of day, and the thermostats reset. I realize there may be perceived security issues opening the garage door but I consider those to be low.

Shouldn't this be Sunset to Sunrise?

Agreed. The single From-To program should work. I tend not to use scenes myself and I have From-To programs that control multiple devices without any problems.

I would try writing two programs: Prog1 If 3:30pm Then Set 'Nook Center Recepticle.1 On-O' On Set 'Nook Center Recepticle.2 On-O' On Prog2 If 9pm Then Set 'Nook Center Recepticle.1 On-O' Off Set 'Nook Center Recepticle.2 On-O' Off

Factory resetting the den switch, the switch that mysteriously was turning on 6 other lights, did the trick. Operation is back to normal. Thanks all.

This is really strange. After restoring all affected switches and confirming that the mystery scene/crosslink behavior was gone, it returned the next day. Same thing. Manually turning on the den light switch turns on 6 other lights. I did not factory reset the switches previously, just restore from the ISY admin console. Will try factory reset next.

Update: Issue seems to be resolved after Restoring all affected switches. At first I'd only restored then deleted/added the switch that was causing the strange results. Restoring all switches was necessary. I've no idea how this phantom situation came to be but glad to know that it is resolved. Thanks to all who read/posted.

I should mention I know for a fact this behavior was not the case all along. We seldom manually turn on the den light switch but I know that until some unknown point in time (today?) it did work as expected. We've had the switches for a couple of years. It is a good suggestion but this could not be due to leftover X10 or insteon links. This is really strange. OK so next I'm going to delete every affected light and then re-add. I'll report back if that made any difference.

Here’s a strange one. I just noticed that an insteon 2477D dimmer switch which we seldom use manually (so I don’t know how long this may have been happening), now controls 6 other insteon lights. WTH. I did not program this. Ever. The switch in question controls the light in the den fan. Pressing it on now turns on that light, the living room light, the dining room light, the front porch, the front flood, the back porch and the back flood. Pressing off turns all those lights off. This only happens when using the switch manually. Everything functions normally going through the admin console. Also, the other lights that come on do not show up in the ISY console as ON. I can turn them off via the console but they don’t register as being on even though they are. All I’ve done so far to troubleshoot is to delete the den light switch and re-add. That didn’t have any effect. Any ideas?

I fixed it. Strange. I had to go in to Alexa.amazon, Smart Home, Groups, Kitchen Group and then scroll down to "Scenes in this Group" and check "kitchen light". For some reason it was unchecked. Doing so and Saving, allowed me to once again turn the light on and off via verbal command. I've no idea why/how this was changed.

Looking for a little help. A simple scene to turn on/off the kitchen light no longer works when speaking to Alexa. It’s a scene consisting of a 3-way switch arrangement. Worked fine for a couple of years but now Alexa says “Kitchen doesn’t support that” when we say “Alexa turn on the kitchen light”. Same thing if trying to verbally turn it off. I can control the light just fine from the ISY admin console page or manually. I have removed and the added the scene/device from alexa.amazon.com. This happened out of the blue. No updates or additions to the network. Any ideas or advice on how to restore this functionality – the ability to control the kitchen light via spoken command? Thanks.

This (flashing red light and error mode) has happened to me every time I've ventured to try out ver 5.x and then gone back to v4.x. My solution each time was to pull the memory card from my IYS994i, reformat it, and then reinsert and reinstall v4.x. It's a pain.

Can you VPN into your home network from your office? If so you can access your ISY that way and your employer doesn’t have to support Java.