larryllix

I think you need to open a ticket with UDI. They know things about the inside of your ISY that we don't. I would hate to see you rebuild all this only to find out there is another problem with your ISY OS. Maybe your old PLM is overloaded with too many links? Of course that would be right after factory resetting my ISY, reloading the OS image and restoring my programs.

Think you might have blown your UDI assist when you saved all those messed up programs. Now you need to edit every program looking for commented out lines that ISY could not convert correctly. Some will be correct already and some may have comment lines substituted. When they were not absolutely sure, they left it for the user to examine and correct as needed. They may still have yellow icons in the admin console program tree yet.

If I would have gone with GH rooms idea it may have worked better but it would have required renaming all my device vocals, once I figure out what was likely to be happening. Eleven years now and we are thinking of taking off the switchplate labels for lights but I don;t know how to label the vocal commands now. Alexa....give me a list of the closest light control commands

That was my problem. I started out with only devices in my Gathering Room and didn't use any prefixes. I have most of my devices with no room prefix like blue lights, red lights, TV, etc,. When I started adding things like bedroom TV, blue bedroom lights etc... Google got confused a lot, and with it's additional attempt at grouping devices, it didn't work well at all. With Alexa, these combinations of prefixes and no prefixes, are not a problem, and I still have use them all except for All lights, which I changed for GH when I used it. When I would use All lights before bed, GH would shut my whole house off, including the heat, making it's AI attempt assumptions. ISY Portal doesn't send your ISY names for devices to GH/Alexa.

I drink and eat different things each day. I might have to change the vocals each day then.

You are missing the fact that the ISY Portal is a conversion table from ISY elements (programs,scenes, variables, devices, etc..) to vocal device names. It doesn't matter what your elements in ISY are named, you must supply independent name, or up to five different vocal names for each element you want to control. eg. My Ceiling pot lights over my kitchen eating bar are named. Kitchen Lights, Kitchen bar lights, bar lights, counter lights, and kitchen counter lights. You have to remember one of them. With Google I found you have to watch the multiple usage of any device name. IOW: If you have red bedroom lights, and bedroom lights it will often confuse the two names. If you have 8 different colours for a light strip eg. Red Bedroom lights, Blue Bedroom Lights, Orange Bedroom lights, etc... when you say Hey Google...turn off the bedroom lights. It would respond with OK...turning off eight devices, and send every one of the codes out flooding the comm channels. After Google constantly changing their security systems and having to restart or create a new account, about three times now, I stopped using my four GH devices. Now I found out when my router would get a power blink, and they couldn't connect right away (competing with about 70 other devices), my GH devices would all start sending out their own SSID WiFi beacons on the last known WiFi channel and flooding my router's WiFi system, causing comm problems on my LAN. Now my sit in my junk box doing nothing and I rely on my 10 Alexa devices only.

But with Zwave sensors you don't have the problem of the Insteon direct link scene turning the lights off again. All control logic goes through the ISY programs right?

First...you can right click on your programs, copy to clipboard, paste into forum post. I would try something like this. If elk is armed Then Wait 30 seconds Enable program2 <--------------- or set $variable = 1, also init to 1 Else Wait 5 seconds Disable program 2 <------------- set $variable = 0, also init to 0 Program2 If MS is switched On Then do whatever Else ---- Of course, you could use a state variable also and make a folder conditional upon that variable being 1 and not 0 Put all your related programs into that folder. Be aware that turning the folder off will stop your programs dead and anything that requires finishing will need to be handled separately. OR... Use an Integer variable (not State) and Include that variable in all your program conditions If MS is switched On AND $Variable is 1 Then MS actions Else ------

Ohhh..not sure what MSes you are using. If you cannot turn off the Off signal from the MSes, it will not work very well. I have some Insteon MS IIs that have this problem and they are a PITA having to flounder in the middle of the night in the dark. I have found that a cure should be to set the On duration to a long time inside the MS but these POSs will not send another On signal until the On duration x2. (The internal circuitry needs to be off as long as it was on).

Have a look at this I believe the top two programs do what you want. Yours look very similar.

Add ISY to the java permissions table under the "security" tab.

Oh Yeah. You may need to go to the java console and enable access to your ISY in the permissions table....about third tab IIRC. ooops fourth Tab in the picture above. "Security"

hmmmm.. I am not good with java but I would attempt to update your java version, Then clear all java cache items from your java console and reload the ISY launcher software fresh.

One more try before you get too crazy. You may have a bad load in your admin console. Close it and load it again.

No. Mine are all Insteon. This seems to warrant opening a Ticket with UDI. I would be sure @Michel Kohanim can fix you up, diagnose further, and want to see this.

Here is what the pulldown menu should look like. You may have to "remove from folder" before deletion. This option has changed over the years.

I think you may have misread the queries. "What do you see when you right click on the other devices in that folder? "

Click/select on the device in the admin console device tree. Press the delete key. ISY will look a after all the links. If you don't have a keyboard use whatever you do, equivalent to a mouse right click, and select delete from the dropdown menu. Sorry. I don't use touchpads.

To each his own but I don't know why people make things so complicated with complex and obscure Insteon scenes (from Hub experiences) when they have a smart box like ISY994. Just create a single scene for each button LED and a program that turns on that scene on and off from the button signals. Each LED is individually controllable, and no complex cross switching logic is needed. If these LEDs were enabled to receive external signals properly, as other Insteon devices are, no scene creation would be required at all.

I would get a new one and swap it in to prove it or not. If the problem doesn't improve, I would swap the original back in and then you have a spare for an older PLM. This is what I did and I now have a tested spare for my 6.5 year old PLM. I have never needed a replacement for my ISY994, PLM or other electronic device in my home due to PSU failure. Now I should get back to watching my round tube TV in black and white, again.

Perhaps ISY Portal is over busy with handing out signals to connected cloud services. Is there any time of day pattern you can determine?

I get that very occasionally on my Alexa units. I think it meant "I'm sorry, all our agents are busy filling online orders right now. Please try again later". Do you get it on GH also?

If amazon will give out the API for the device, then you or somebody else could write a NS for ISY or even use NRs to control it.

He already indicated it was exposed to weather.

All makes sense but it is outside exposed to some weather. Hole won;t work in this case. Inside a protective case to dissipate heat into the outside atmosphere may make more sense for this but IIRC this is an established installation. Breaking the cable in the basement and installing a control point inside on the basement ceiling may be an option.