larryllix

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.

Metal, likely being more reflective would stay cooler than solar absorbent plastic. Metal only feels hotter to the human touch due to a smoother surface making more contact and having a higher specific heat, so it doesn't cool as quickly when a cooler skin touches it.

I have no Insteon outlets but that sounds like a messed up link. Factory reset the device and then use the ISY admin console to Restore it, writing proper links back into it. If you didn't factory reset it before connecting to your ISY, this is quite common to find problems with any Insteon device.

From your local electrical utility. They can install it if they support that type of billing. If not you could likely buy your own from a supplier but the meter may cost you a few hundred bucks for quantity one. Then installing a meter base and wiring it in may cost another $500...rough guess. You would need the ISY zigbee card to talk to the meter, provided that ZigBee protocol is supported. Zigbee has had no standards until a short time ago so UDI would have to verify the standard their card supports. There are much cheaper and easier methods to get metering data if you don't need the ~ +/-1.0% energy accuracy.

The wall control has 60Hz synced time clock, an open/close button, light on/off, GDO RF control lockout, power, and a few other functions over two wires making it retro wiring compatible. That is the only reason I can think of why a simple contact input would not have been used.

I have many GH devices but if they do not get an IP address properly, they create their own WiFi that clobbers my routers on the same channels.

No Change here in Ontario, Canada. Brighten stills responds with "OK"

The ISY Portal is partially bi-directional. I do not have any active GH devices anymore, but many Alexa devices. Here is how it works with Alexa. Create a State variable for control. In ISY Portal use that State variable to create a pseudo MS In ISY Portal define what variable value will be shown as ON and Off In Alexa mobile app define a Routine using the pseudo MS as a trigger and the resultant as whatever you want it to do, voice output, device on/off etc.. I believe GH also has Routines. I hope this helps.