paulbates

My floodlight set up is like yours, and there are 3 keypad keys in different areas can also turn them on or off. I detect 'double tap' on or 'double tap' off on the floodlight keys with an ISY program to suspend the motion activation program (or turn it back on). The double tap program has a Wait timer in it too, after so many hours, turn motion activation back on. Paul

The other factor with a 2412 of that age is compatibility. I believe that it would not support the newer i2, i2cs protocols that the switches probably require. i2, i2cs are relatively newer insteon protocol features Paul

I get what lilyoyo means. I have some large, similarly functioning device groupings. Rather than dupe Everything, I have a large core scene, and then a smaller "accessory" scene with the additional items. A program sends the core scene at some points, and at other points, both scenes back to back. Not really noticeable when thought through and cuts down on link count and often reduces update time. Paul Sent from my iPhone using Tapatalk

Unless you have hundreds of insteon devices and big scenes already and are out of links, insteon scenes are designed for this purpose and are the best way to accomplish group activities. Other things to know: All On / Off is not limited to light switches. Io_lincs, for example, will trigger from an All On / Off Due to "false" triggering, Smartlabs has been removing the All On/Off features from newer switches in the past few years, so newer devices will not respond. Paul

Before doing that, pick one MS, put it in linking mode and then use Restore Device for it from the console. Retry it a motion test. Paul

The first thing to do is address the 1011 next to the switch. Right click on the device in the Admin Console and pick Write Updates to Device

The best manual linking software I've seen is Mark Sandler's Insteon plugin for homeseer. Very granular management of the insteon network. It also uses a serial IP like interface to utilize the hub (local api) as the PLM. If you're savvy with .net development, that's a possibility. I don't know if HS tackled MQTT, that would have to be explored on HS forum. I found the ISY an easier path to fast, stable automation of functions, so its about tradeoffs. Paul

Look at the nodelink subforum. Nodelink (on a pi and isy v5) will syslog out for its supported devices, and its isylogger node will send isy variables and program statutes to syslog.. having said that it is not a general syslog facility where you dice and slice what you want to log. But, it's worth investigating. Another angle: A few years ago Xathros documented writing from network resources directly to a syslog file. Very clever. Look at post 4 http://forum.universal-devices.com/topic/16861-isy-log-on-ios-or-web/?p=149308 Paul Sent from my iPhone using Tapatalk

Do the 2 steps in the bullets, then do some tests to see what's working Sometimes with restore PLM there are a couple that need to be manually restored... but determine by testing showing the ones that didn't come back properly Paul

NO - do not use delete PLM. It will remove all links from your insteon network in addition to your plm. If you don't have a backup to restore to your ISY , and then restore PLM from that..... you can rebuild your scenes by removing and adding the devices back in. You can "Click and select" groups of individual devices at a time... drag them out of the scene.. and then click and drag them back into the scene Paul

Do you have a recent backup from before the problem started? Sometimes the ISY can receive bad, incomplete information from a dying PLM, and the restore PLM puts that incomplete info back. Restore a recent backup, and retry the restore PLM Paul

Did you get a new router / change internet service? Paul

LOL.

Correct... and that's different than "open mic". In other words only when Alex 1) was addressed or 2) mistakenly thought she was addressed. The 2)s are few and far between for us. Paul

The table saw was controlled by an outletlinc

And quite honestly mine was an "icing on the cake" thing. I got the Dot at ReInvent last year. Hooked it up for fun. Because I had the ISY, Venstars and Harmony already, hooking it up was a no brainer. Its handy to turn on far away things like the attic fan and room lights on in the morning. But if I didn't have it. I've pretty much stopped using flash briefing, etc. We play jeopardy every now and then. I played with Alexa smart home groups with the ISY and it comes across to linear / kludgy when mixing. Paul

Agreed. I've watched min with my router - with and without prompting. I've even tried the "yelling at it" method. Paul

You say auto-correct, I say fruedian-slip

I could be wrong, but it doesn't seem plausible that all 4 sensors send their heartbeat at exactly the same minute/time, (or miss it at the exact same time). So I would look at the other end of the chain, something may have happened with the notification program, could you post that please? Paul

It can happen, but its a rarity. If you are powering something with transmitter or motor that produces a lot of line noise, insteon devices can get overwhelmed. Out of ~50 devices, I can think of one case where this happened to me. It was a yard light transformer and making a lot of noise, I had planned to replace it anyway. Paul

For me its more about I have comm already worked out for a lot of older singleband devices and a few duals I haven't lost a lot of insteon devices in 10+ years, so I don't have a "business case" to swap out +50 things with no real payback.. a switch is a switch My family really likes and has adjusted to the keypad and its behaviors. Its given a lot 'virtual circuit' flexibility in our +60 year old home's very limited electrical system. There area few zwave keypad 'alikes' that remind me of the old Leviton 4 botton x10. Expensive, and not nearly as functional as the keypad. My answer to the motion sensor issue was to go to my local mendards and clean out there stock of gen 1 motion sensors. They do the job for me. I hear what you're saying though. Its less about UDI and more about SH heading down the hub path. The hub is the razor for which they can sell a lot blades, if you remember that phrase. The implication is that the focus is on hub integration and the PLM is getting left behind. Paul

Not really. An option is: If you have them all connected in a scene, and they all consistently switch off together, ideally you should only have to check the status of one of them.. e.g. they all go off if one goes off. However, I'd leave it as is. Paul

Hi Basic X10 is built into the /PLMISY, and will function not sure how you could disable it from the ISY. The optional X10 ISY Module let's you rename things from A1, etc to a meaningful name. Removing the module won't solve the problem. However, early X10 switches had the ability to respond and send X10 commands if programmed that way. That's what your symptoms sound like. You can do one of the following There's a tedious procedure to remove the X10 address found with the switch directions...or... its easier to Factory Reset the switch, and then perform a "Restore Device" from the Admin Console. This will remove X10 and Insteon settings, but restore the Insteon settings to the switch. Restore Device is found by right-clicking the device in the admin console If you still want the X10 module removed, send a message to UDI tech support with the UUID of your ISY and request that they remove the X10 module. Paul

You might try using "If Control" rather than "If Status" in your program. The issue is that that ISY is not able to query wireless insteon sensors, it has to patiently wait for them to trigger, either actual sensor reading or the heartbeat message which confirms daily that the sensor is still there and alive. When the ISY reboots, all status of the sensor is lost and that may explain it. I use "If control" with my motion sensors programs. When using IF Control with a wireless device, you'll want to put a "Wait 5 Seconds" as the first line of your program before any insteon commands. Wireless devices typically transmit their messages twice, and the second transmission may clash with your program statements. Using "If Control", the program will wait to get the real message from any of the sensors to act, not try to assess status Paul

To answer the other question, there is the SmartenIT line of of products that includes the EZIO that are Insteon and ISY compatible. I believe that they can be configured for dry contact and analogue input. I think there are some limitations for the full feature set on the ISY. Info and comparison chart here Paul