MrBill

@satwar I think P7 may be the mode that you desire. As I recall the relay will pull in when triggered but the T1 delay doesn't start until it's released. If that's the case you would set T1 short say 1 minute (which extends the on the time by that amount, thus creating a minimum on time) then set T2 longer (say 5 or 10 minutes) preventing retrigger. and then 1 cycle. If I'm correct it won't re-trigger until T2 expires. I don't want to push buttons on my working relay because it's been untouched for 4.5 years. I thought I had a backup in my parts box that I could perhaps use to experiment but I'm not finding it where it should be (amazon orders does show I ordered a backup 2 weeks after the first). See if this helps if not maybe I'll look harder. The above description is in the product description on amazon, the actual button press instructions are in the 4th photo (also pasted below), the time unit you likely want minutes or -2

Since no one else said it directly, an insteon battery sensor will NOT work, since it can't be woken remotely with a query. I don't speak z-wave, so unsure there. personally I think @KeviNH has the best idea...

@kevincol Don't assume it's the switches. Noise can come from anywhere, even things you don't think about like LED lightbulbs. There does seem to be a communication problem however. When i start troubleshooting things like this, I usually start by unplugging or turning off everything on the same circuit. If there are other insteon switches I pull the air-gap lever. If there's still noise I turn off big batches of breakers. Leavings on the modem and router, the PLM, the circuit in question. if those are on opposite phases then i usually turn on a nearby circuit on the opposite phase of the circuit in question. If it works under those conditions then start turning on more circuits until it doesn't. It's a little maddening to find noise or signal suckers, but with a good method it doesn't take long usually. I've gotten so anything new gets plugged in (or now even new light bulbs) I automatically test if its a problem with Insteon.

Since you're using status, try this for troubleshooting: Check the status of the switches from the Main tab of the admin console, then go change one of them, and come back to the admin console and check the status again. Now repeat with the other switch. Is the status of the switch changing in the ISY? There's too many options depending on the results of that test to keep typing what I'd try next. Possible problems could be a one way communication problem or bad switch. it's possible that surges etc broke something. It may more may not be an Insteon device actually causing the problem something else may have gotten damaged and is now emitting noise blocking insteon signal, but it does seem to be working at least in one direction which makes me wonder if it's not an Insteon device itself. (I once had an Insteon on/off switch for my attic fan get taken out by a surge, it impaired the entire system until the switch was disconnected then everything else was fine.)

I don't think it is.... that version is "Already subscribed", which appears to mean subscriptions are confused and the ISY thinks the admin console already has a subscription but the admin console is just starting so it doesn't have info on it. In OP's case the 10 available subscriptions are already full, and the newly opened admin console can't start a new on because all 10 slots are full. I didn't ask OP to paste the screenshot I suggested he take before he destroyed the evidence, and to be honest I don't know how to identify what started each subscription by slot with the exception of the portal. I suspect OPs problem is a one off weird situation where whatever process inside the ISY expires stale subscriptions just stopped working. On the problem that we've been discussing for a year (a.k.a. "Already Subscribed' bug), recent evidence seems to point that its not actually a mobilinc problem but something in the ISY that confuses subscriptions. Possibly related to Queue Full or some other socket related error that shows up in the ISY error log. Unfortunately the ISY error log is hard to understand and read, I just opened mine and it's full of crap following an ISY restart yesterday. I've discovered by trial and error it's best to shut Polisy down when restarting ISY, after ISY comes up and stabilizes then restart Polisy. I didn't follow that yesterday because I didn't think of it, I just clicked Reboot in the admin console now I have an error log packed full of error mostly from nodeservers, mostly a specific nodeserver, and when the query program ran overnight a bunch of "queue full" errors. To solve this I'll bet all I need to do is shut down Polisy, reboot ISY again and wait until ISY is up and running to restart Polisy. If I do that and check again tomorrow I'll have few error log entries and no queue full error during the overnight query, if I ignore the condition it will continue.

Pushover.net The app is a (free trial then) one time charge. You do need either Network Resources on the ISY (comes free with a portal subscription) or the use of a node server. If you have Polisy there are two nodeservers to choose from or without a polisy (but with a portal subscription) you can use Push as a cloud nodesever. lots of ways to use Pushover. If using the original Network Resources method then see this Wiki page for setup. One pushover account for many ISY's or separate, doesn't matter much unless your generating LOTS of traffic then you may want to split it up to keep away from monthly fees. (also if your a business, I believe they can private label, but that wouldn't be free. The notifications arrive nearly instantly. For example, If I pull open my mailbox the notification taps my wrist before my hand has a chance to let go of the mail box door. another option available to all is email, either with UDI's default mail server or your own. With that you can send text messages via the indvidual carriers email gateways.... your mileage may vary here, there are repeated complaints about slow delivery (mostly from those with AT&T). (special note with AT&T there are 2 email to text gateway 10digitnumber@txt.att.net and 10digitnumber@mms.att.net... of the two @mms.att.net works better for this for two reason 1) the message arrive FROM the email address that sent it, and 2) it's usually faster (althought today it's got 30 minutes delays).

First, take a screen shot of http://ISYipAddress/rest/subscriptions that might be interesting to UDI support if you need to open a ticket. To clear the problem tho you will need to reboot the ISY, either via the portal if you have it, or just pulling the plug since you can't open the admin console.

I believe writes links to both devices, if the old device is DOA I suppose that those will fail? meaning the writes will take longer.

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device there is the wiki article. Basically if the old device is in a folder move it to the root level first. add the new device to the isy. click the old device in the tree right click and choose replace device and pick the new device from that context menu. the caveat is that both devices should be powered up. I usually power the new device with a temp cord that plugs in, factory reset it, add to the ISY, do the replace. then go install the new switch in place of the old after the ISY is happy.

I was busy looking for @kclenden post linked below which is a slightly different version of what @larryllix dinged in with while i was looking: PS: your first program "Robot Charging - [ID 005A][Parent 0059][Run At Startup]" without an IF body shouldn't have [Run at Startup] enabled, and I believe most people disable that type of program but I've done it without disabling.

@BizywkJust double checking.... but does Help > About show the same exact versions for UI and Firmware? What happans if you try adding an If, something simple like: AAA TEST Copy - [ID 013B][Parent 0001] If From 8:51:00AM To 8:52:00AM (same day) Then $stemp_test += 1 Else $stemp_test += 1000 Adjust the times to a couple minutes later than your current time and save. In the example Then should run at 8:51, and Else at 8:52.

Help > About Is your firmware and UI version Identical?

While the exact answer to your question appears above I'll contribute another troubleshooting method for your arsenal. Switch the the "summary" sub-tab of programs. Many people don't realize this table is column sortable. Find the columns for "last run time" and "last finish time" and click the column header to resort by that column, clicking a second time reverses the sort.

I agree with @Geddy if you actually have an ISY-994... However your title indicates ISY-99i. if that's the case, don't try to use the linked launcher. But do make sure your using the correct admin console for your firmware version. I'm also afraid there's no support for the 99 anymore, so if you have one you should think about upgrading it.

Clear the Java cache, and then follow the instructions in the thread linked below to use The Launcher. The Launcher is the newer method of accessing the admin console that always gets the correct version to match your firmware.

your new panel should come with an installation manual. the manual should have pages with the programming worksheet. Watch out for errata sheets too, I haven't done a Vista in 20 years, and it was a different series so they may have gotten better, but they used to be famous for "this is the updated step 12 on page 30".....

The only deviation I would add to @Bumbershoot, is if the new ISY has a z-wave board you'll need to check the version. I don't know when UDI started shipping them with 500 series boards (and you mentioned it's been in the box for a year). If you find the new unit does still have a 300 series board and you're not using any z-wave you might need to either remove the board from the ISY before going to v5.3.1. (I'd check with support@universal-devices.com). if you are using Z-wave then the furthest you can upgrade the firmware is 5.0.16C. (then you can upgrade the z-wave board at your leisure and then finally move to 5.3.1 after).

1 is faster. It resets the device and clears all the links in the device. The ISY still knows the correct version of what needs to be there. Select the device and then right click it and choose restore device, the ISY sends all the links to the device. under #2 your doing the same basic thing in the end, but with alot more steps. removing the links and deleting from ISY, then factory reset the device which is the actual end game, then putting it all back in.

@agudenit sounds like communication is working in one direction but not both ways. The ISY's signal is reaching the switches and they hear it, but when they answer or acknowledge the transmission in the other direction the ISY can't hear that. I'm not certain what to suggest to resolve it tho.

They are easy to find type "2 pole 30 amp contactor 120 volt coil" into amazon search (be wary of amazon search, it tends to mix in others that don't exactly match, double check your choice for all values including coil voltage). Be aware that some are noisy, some are quieter than others. I prefer to stick with name brands like siemens, Eaton, Square D, etc. You'll also need a proper enclosure, if it's metal be certain to follow proper grounding protocols.

If you've resolved your problem be sure to close the loop in other threads where you have queries hanging, so that no on needs to spend time on a resolved issue. Here is one:

typically the red ! will hang around. when I see one I right click on the device and pick query. The ISY then asks the device for its status. if the ! goes away at that point communication was successful.

If you enabled Run on Start for every program that's typically unneeded. Depending on the program and what it does Run at Start may or may not create undesired behavior. Typically ISY programs run on an event queue basis, "Run at Startup" forces an extra run at startup. If the UI and Firmware versions don't match exactly then that's why programs look wonky. Follow the instructions in the following thread to use The Launcher. It will ensure that you are launching the correct version of the admin console for your firmware version.

Be certain to notice the LEVEL dropdown at the bottom of the window. Changing to Level 3 is what turns on Device Communications.

Have you recently deleted a scene? I believe the looks like those attached to scenes. DOF is the off action. I recently accidentally deleted an insteon device while repurposing it. I meant to remove it from the scene it was in but instead removed it from the ISY. Then I just deleted the scene it was in. Later I found programs with simmilar comments added IN PLACE of the previous scene commands. .