MrBill

I don't have any Z-wave locks. One of my doors has a magnetic lock, that I set up long before the current lock offerings became available. The reason I replied above is that I'm very aware of the fact that lock cylinders can be re-keyed. You can also often order locks keyed to a specific key code. or have a locksmith or even sometimes a hardware store re-key. Also many times the lock cylinder can be swapped out to a different brand. I'm not a locksmith but I do have rental properties and re-key all the locks between tenants myself. I purchased my Schlage pin kit originally to solve a problem, over the years it's saved me thousands. I don't know enough about Z-wave locks to advise you, but I read most threads on this forum and could clearly see that you were being short sited with your sweeping statements above.

Your logic is faulty. Have the replacement locks keyed to whatever manual key you desire.

I don't know that I'm going to be helpful. The need is to debounce or slow down the state changes being sent the EZIO. Normally the controller of the device should handle that, I don't know why I didn't think of that fact before, the secondary method would be a time delay relay. The problem is the one that I use for a different application doesn't actually work the way I thought it did... it's more of a "timer" than "time delay". Yes, C (cycle) = 0 with cycle forever, you may be confusing what cycle means tho. Once 'triggered' the cycle has started, meaning that infinite will never stop the on/off cycle that's been set. When I used your values including C=0 the "work" light flashed too rapidly for a mechanical relay to be be able to work. When the relay turns on (which is indicated by the work light) the coil in the relay is energized, it takes just a moment for it to build up enough magnetic power to "pull" the relay in. (a mechanical relay, the blue box just above the red LED 'work' light is not a good choice for very rapid on/off cycles). With the values you are using: Time unit = 0 and T1 and T2 = 3 you are setting 3/10 of 1 second on and 3/10 of 1 second off. This is a very fast cycle that is too fast to energize the relay coil, and because c=0 it's never ending. If you want to test your relay, use my values turn it to P7, time unit -2 t1= 1 time unit -2 t2 = 1 and c= 1. That is 1 minute cycles. Now 'trigger', the relay will turn on for 1 minute then off for 1 minute. After that cycle is complete 'retrigger' is possible, Unfortunately what is NOT possible is to re-trigger during that cycle, which would in theory start the cycle over. That would be exactly what we want: if the snow sensor turns on the relay it stays on for a minimum amount of time and if the snow sensor turns off and on (re-trigger) during the process the timing starts over again. (You could also perhaps use 5 or 10 seconds to test, i.e. time unit -1 and T1 and T2 = to 5). Now if you use the above values with c=0, once you trigger the on/off cycle the on/off timing will start, once it starts that's all that happens it cycles indefinitely on and off for the set amounts of time. Re-trigger does nothing.

My apologies, I've afraid I've wasted your time (and maybe a few dollars on amazon). I set the relay up first with the values that you gave in your post. I noted right away that caused the red LED "work" light to cycle rapidly. That light comes on when the relay turns on and goes off when the relay turns off. The values entered cause it just to loop forever, at a rate that is too fast to energize and de-energize the relay. I then set the mode to P7 (based on my prior guess) and with -2 (minutes) for the "accuracy" and a value of 1 for both T1 and T2. This behaved almost as expected. I triggered the relay and the relay came on for 1 minute, then went off for one minute. What did NOT work is re-triggering during either time period. In fact T1 begins at the leading edge of the trigger, and once triggered both time periods must expire before a re-trigger occurs. My thinking was this relay could be used to debounce because timing began on the trailing edge of the trigger and that re-triggering would restart the timer... that's clearly not happening. I then went through each mode using 1 minute timers looking for one that would work as a debounce. P1 is close, but still turns off at the end of the cycle and requires a re-trigger. Is your snow sensor a commercial product? do you have a link so that I can read how it works? Maybe it has a setting that would help. I use an EZIO but differently than this application. I certainly understand that you don't want the input cycling on and off which would generate too much Insteon traffic.

That does sound like a bad relay, or some other component. I just went and looked again and found my spare relay, I was looking for a box and it was in a small white envelope wrapped in bubble wrap. I'll find a transformer and see if i can or can't duplicate your results. I'll post back later.

Insteon devices are dual band and can help each other with transmission via a mesh. When I had just a few Insteon devices I sometimes had communication issues. Now that every switch in the house, except for two garbage disposals and the attic light switch, is Insteon I really never have issues.

you're not generally short on words ?

I agree with @Teken ...sort of.... Delete and add in the portal and the alexa app. not the device from the ISY

The basic steps to follow are: backup power down, insert new card, power up telnet to isy and format SD card it (may not be required for a new card) use the admin console for your version to login, and re-install the firmware (Note: you can't use The Launcher in this case). (see the wiki page for more info.) restore backup Note your backup does not contain the firmware, thus the reason for step 4 and 5 both. the wiki page is here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card (the ISY will support a 16GB card so long as you're not using ancient firmware 4.2.18 or before.) My ISY has an address reservation on the network set via the router so the IP address won't change. If you have a static IP configured from the configure tab of the admin console be ready to find the ISY's new IP address. Also note that the wiki is contradictory on the point of whether you should format via telnet session. at one point it says that it's NOT required for a new card, but later there's a note: "Please note: the ISY works with both FAT 16/32, but FS function formats it specifically for use with ISY with some performance improvements so its preferred you use this method." that suggests formatting via this method should be done.

I agree, also on 5.3.0, and don't have this issue. I was going to type the same thing earlier but got sidetracked.

I've actually been impressed that HA doesn't cause any problems in my setup. It seems to maintain the same subscription for very long periods of time (many days).

@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.