paulbates

Wow. I've had mine for 2 years. It came charged and I charged it once this spring. I had an X10 key chain remote I replaced it with, I didn't change its battery that frequently either. Paul

That's an interesting idea! However 5000 seems like a lot. If you averaged 4 presses a day, that would be 1250 days or 3.5 years. Mine doesn't make it over a year. The manual says 9 - 12 months per charge. Maybe start with 1000 and then see how long the charge takes. The manual says the charge should take an hour.. so use that as a factor to increase or decrease the count. e.g.. if it takes the full hour, lower the count and give it some room. If it takes half an hour, up it to 2500. I would leave extra room so you're definitely charging before it runs out. Maybe its pressed a lot more than 4 times a day.. measure that and adjust the program accordingly. Also, remember to use the "init to" function in your program after incrementing the variable you're counting with. Otherwise, the ISY will lose its memory of the count if you reboot or have a power outage Paul

Hi- Unfortunately that product does not provide battery alerts. You have to keep track on a calendar and keep it charged regularly. I have one in our bed room for my wife to use for the attic fan, its the same thing. I charge it in the spring and it lasts the year. I know its "old school", but I have a spreadsheet for battery powered HA items and charge/change them on a schedule and not wait for an indicator to come on, Charging the remote is on that list. I've had fewer problems with Insteon battery powered devices approaching it that way. Paul

In Insteon, when 2 or more devices are controlling each other, a scene has been created. You are actually creating and using scenes when you use the instructions that come in the box with the devices to link them. That manual process creates references between of participants you linked to use as part of the scene. This is how insteon knows how to coordinate activity between multiple devices. However, the ISY was not part of that manual link creation process using the out of the box instructions, and does not know to respond / acknowledge the new scene you created via manual linking. To say it another way, its working as designed. Your choices are: Continue to manually create scenes with the individual devices using the out of the box instructions that came with the devices and have the ISY continue to not know about it and manually query to discover state. ...or.. Remove the manually created scenes and create them with the ISY. The switches will respond to the remote just like they do now. The only difference is that the ISY will be a participant in the scene and aware of the changes, which is what you want. It takes just moments to create the scene with the ISY. I find it easier to use the ISY than manually link.

Small world! Next week, it will be 25 years for me.

Hi Tom Each EZflora has 8 zones maximum, so yes 2 ezfloras are needed for your application. I wired mine into the existing rainbird controller with a length of sprinkler wire from a sprinkler supply store. That made it a little easier, no wiring changes to the existing system. So I don't have detailed instructions per se... but I wired zone 1 on the old controller to zone 1 on the ezflora with the new length of sprinkler wire, zone 2 to zone 2, etc. Then write programs. Basic programs to run the system are fairly easy: turn a zone on... and wait xx minutes... It gets a little more complicated if your system has a pump or master valve, do you know if that's the case? If you have either one of these, its a little more complicated... I'll wait to see if you report back that you have either one of those to explain how to deal with that further. Paul

As Lee pointed out, it could be line noise closer to the outletlinc, or something wrong with the outletlinc iteslf You could try a factory reset, followed by a restore device. If that doesn't fix it, try the event trace. Paul

My Menard's has the keypads in stock... its a check their stock, driveby and fix in a day if you have one nearby. If you include the cost of shipping from SH, its usually a little cheaper that way too. If they have 6 vs 8, its any easy swap of the keys and reprogramming of the keypad.

Are there electronics like a TV or phone chargers plugged into the outletlinc? If you are using the outletlinc to control electronics, you'll most likely need a filterlinc plugged in between the outlet and devices. I've found outletlincs to be more sensitive to noise from loads than other insteon devices. A way to validate this theory is to unplug the load from the outletlinc and then retry the program / ISY control. Paul

You should not have to. Your current PLM's address is programmed into those devices. If the power blip just caused the PLM to lose its memory, this will put it back. The process will go look and see if PLM's address is on the devices, as well as put the devices's addresses back in to the PLM Here are the possibilities The modem lost its memory, and the factory reset and 'restore modem' will put it back and you'll be working as beforeHowever some devices may not come back, you'll see with a red !. Those might recover with a factory reset and 'restore device' (or they may be damaged beyond restore and have to be replaced) The modem may not respond to the restore modem, because its was damaged beyond repair and need to be replaced The factory reset, restore modem / restore device procedures are how you discover the extent of the damage. The fact that some of your keypads were recovered via this procedure is encouraging. More might also recover. Paul

"To reset the Power Line Modem to its original factory settings, unplug it from the wall outlet and wait 10 seconds. Press and hold its SET button, plug it back in, continue holding the SET button for 3 seconds and release. After several seconds, the Status LED will turn on, indicating a reset is complete." Then, you'll need to use the the "Restore Modem" option from the File menu of the admin console. Do no use the Delete modem function. Paul

You can try a factory reset of one of the keypads. It may not work, but easy to try and similar in technique to the procedure Stu had you try: Pull out the set button, wait for 10 seconds This time, push it all the way in and hold it After you hear a 'beep' let it go. Go the the admin console, right click on the switch and select 'restore device' Let the restore run, usually < 1 minute Retry the switch Given your description, this most likely won't work, but will only take a few minutes to try and will obviously be better the buying replacement keypads if it works. Give it a try on one and see what happens/ Paul

Stu, the outletlincs are very sensitive to line noise. While It probably defeats the aesthetics purpose, a filterlinc between the AC and OL should solve the problem.

That would be via airplay which requires a session token. It requires an external program on a server to manage it, Here is an example from rehills: http://forum.universal-devices.com/topic/18417-do-i-really-need-to-build-all-these-resources/?p=175065

I had a sears GDO that was similar. It's a multifunction wall mounted remote with light , that still recognized a short contact between the two leads. Its very easy to test.

Cool! glad its working for you . Paul

Np, we'll figure it out. For the moment, put the time parameters back in. And one program should work A few more questions since we've touched on the easier stuff. The first two are probably 'yes' but want to make sure You're hitting save on the left each time to save program changes? I forget sometimes The time on your ISY is correct to your timezone, within a few minutes? For the notifications: How did you configure mail eg... Default, or did you set up gmail? If you are sending to gmail (and some others) there needs to be a few words of text in the subject line and body of the messages ... Some email systems ignore messages without a subject line or body content Paul

sorry, I meant make your program look like this If Status 'Garage / I/O Linc - Garage-Sensor' is On Then Send Notification to 'James iPhone' content 'Garage Door OPENED' Else Send Notification to 'James iPhone' content 'Garage Door CLOSED'

Hmmm. Could you temporarily remove the time part of the 'If' and retry? And From 9:00:00AM To 9:30:00PM (same day) Paul

It may not be the program. Are you sure that the ISY sees the change in state? If you put the door down, does the IO linc show off? Paul

Agreed. It sounds like the PLM is going bad. You can try Tools/diagnostic/PLM Info status... though it may show ok if the ISY can talk to the PLM Tools/diagnostic/Show PLM Links Table. If that shows a few or no links, its bad Paul

Yes. I've had one for 15 years. I used to have problems with electronics in general prior to installing it. We have overhead wires and get a lot of lightening from this time of year through fall. My insteon problems of the last 10 years are traced to known culprits like PLMs and the ~2011 series keypadlincs. Outside of that I have Insteon devices that are approaching their 10th birthday. Here is the closest example of the surge protector I had installed in my panel. The link discusses the protection warranty for $10,000 for the first 5 years. You could still have problems, but I think this is a good "insurance investment" Paul

When you are in the admin console, 'right click' on the program name on the left side.. then pick the last item on the drop down list, 'copy to clipboard' Paul

Actually no. Insteon does not support a traditional 3 (or more) way set up. You can either get rid of the other switch (remove and cap), or replace it with a switchlnc and add them to a scene. The switches will turn each other on and off via the scene. One of the switches will have its load connected to the light. It sounds like remove and cap is best. It may matter what box the actual load to the light comes to. You may have to experiment to be sure. Paul

Here is my program for this functionality if that helps Garage Pushover Status - [ID 004D][Parent 004C] If Status 'Garage / Door Sensor' is On Then Resource 'Pushover Garage Door Opened' Else Resource 'Pushover Garage Door Closed' You can replace the 'Resource' statements with your sms notification statements. If this doesn't help, post your programs Paul