Kev1000000

Sent, thank you, Michel!

Paul, thanks for the help! No, the local web server is also not responsive when it gets in this state. I am trying to access the REST API. I'll try and pull the logs when it gets in this state. Since I can get to the admin console via the portal, should be easy to pull the logs. Good idea.

Very recently, the local API on ISY994i appears to go down/unresponsive for long periods of time. It does eventually return (downtime is around 4-12 hours usually), but the instability is causing my integration into my custom interfaces to be very unreliable, and now the wife is getting upset ? I can still access the ISY through the portal, and all of the local INSTEON communication + programs operate just fine. It's simply the local access of the API that is seemingly going down. Any ideas or areas I should look into to help resolve this? I am FW version 4.7.3.

I have, they were beyond useless

Haha, that's the question I am trying to figure out!

Q1: Nothing happened to the physical devices. They are easily controllable via ISY, the API, etc. Q3: I am using the Optimized for Smart Home skill, not the custom "ask izzy.." I know everything on the ISY-side is fine. ISY didn't lose communication to the devices, the ISY API works great with these devices, and if I add spoken word names to these devices in my wife's account, the Alexa app can discover them. It is JUST my Alexa account that cannot discover any of the devices/programs I've added spoken words for. I have a bunch of them added on my account, Alexa just never finds them. I assumed I just lost the auth token or something, so I already disabled/re-enabled the skill dozens of times and re-linked my Amazon account via the ISY Portal. Nothing ever solves it though. My Alexa account never finds the devices.

They do not exist within the Alexa app, but they exist within ISY and the Portal. Alexa "not pulling any of them" means Alexa doesn't find those devices during the "Discover Devices" process (only on my account).

All of the devices, programs, and scenes exist. Alexa just doesn't pull any of them that are associated with my account. Any devices, programs, and scenes that are associated with my wife's account work just fine and are discoverable via Alexa. This started happening out of the blue. No changes from my end.

About 30 for my account, 15 for my wife's.

No devices are discovered at all on my account.

For over a year, I have been running two Amazon Echos in my home, both on separate accounts (as described by the Wiki), with near 100% reliability. The two accounts are mine + my wife's, and we're in an "Amazon Household." This is has been perfect up until two weeks ago. On my account, no devices can be discovered at all. My wife's account discovers devices and works just fine. I've already tried... Disabling/Re-enabling the skill on my account. Unlinking/Re-linking my amazon account through the ISY portal. Disabling the skill on my wife's account and enabling the skill on my account. Factory resetting the Echo De-registering the Echo from my account and re-registering. If I use the "switch accounts" voice command, the Echo that normally doesn't work will work when logged into my wife's account, so clearly this isn't a hardware problem. For whatever reason, my account can not communicate to this skill correctly, even after doing all of the above troubleshooting steps. Anyone have any ideas? I am at a loss.

Lee, I will try out the TriggerLinc idea. I'll report back the results. Great idea! Klundy, the reason I didn't want to go that route is, anyone could brute force the garage door open. If that happens, my scenes would fire, which includes unlocking my door to the house. If I go the wireless device route, then only that button press would fire my scenes, making it similar to a key. Bulletproof? No. But I do feel it's a little more safe than relying simply the status of the Garage door. Although, I do assume the Garage door I/OLinc works based off of the door sensor. Does the I/OLinc receive an event from the garage door opener, which would only fire if I pressed the garage door opener button? If so, that option may be the best. I just assumed it all worked based off of the door sensor. Thanks for the help, guys.

I am trying to find some sort of device combo that will allow me to send wireless commands to the ISY via a small remote/button of some sort. The idea is, I want to place a small button in my car to set my house to either "HOME" or "AWAY" mode. Yes, I could use my phone, but that requires me to take it out of my pocket, load the app, and then find the right buttons, etc. I want a very simple remote I an mount in my car that can talk to the ISY. I would like the range to be ~200ft ish. So, ideally, this is how it would work. I leave for work and press a button to set my house in away mode. The following will happen: [*:b0qrvd53]Garage door will close. [*:b0qrvd53]All lights off. [*:b0qrvd53]Security Cameras on. [*:b0qrvd53]Door will auto-lock (via MorningLinc) When I arrive home while just pulling into my driveway, I'll set the house into "HOME" mode. The following will happen: [*:b0qrvd53]Garage door will open. [*:b0qrvd53]Entry light on. [*:b0qrvd53]Security Cameras off. [*:b0qrvd53]Door will auto-unlock (via MorningLinc) The only missing link is the button I can mount in my car that will talk to ISY natively without having to run a separate dedicated PC. Ideas?

Well, I deleted the device and re-added it, and it seems to have fixed the problem. The timer is now getting reset, and things seem to be working as they should. Haven't had too much time to test all scenarios yet though. Thanks again, Lee.

Ahh, very nice way of debugging! Alas, I have see no X10 events in the event viewer. It seems the ISY is getting the events from the MS, but for whatever reason, ISY thinks the MS in question is not the same one I named and using in my program. I only have 1 MS.