Jump to content

paulbates

Members
  • Posts

    5776
  • Joined

  • Last visited

Everything posted by paulbates

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. Did you get a new router / change internet service? Paul
  8. LOL.
  9. 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
  10. The table saw was controlled by an outletlinc
  11. 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
  12. Agreed. I've watched min with my router - with and without prompting. I've even tried the "yelling at it" method. Paul
  13. You say auto-correct, I say fruedian-slip
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. To answer your first question, I've found that some things don't trigger it reliably. Things that are hard relay contacts work fine for me, other things, not so much. On X10 with Powerflash (PSC01) I could read if my furnace was on with a simple current sensing doughnut around the hot. The sensing part worked perfectly, but the X10 signal part sometimes was lost. I connected the doughnut to an iolinc, i got a faint green glow from its led, but it would never trip it. I got advice on changing the doughnut, putting in optically isolated sensor,, could not get it to work. I now have a thermostat that reports the on time and reassigned the iolinc. Point is, what type of contact source it is can make a difference.. and having said that, when they're connected to something that is a clean contact, they work fine last for years. I've had one in my attic and garage for 6+ years, they continue to function great. So its not been reliability as much as the sensing mechanism as you point out. Also, as they are single band, you do have to make sure that you have a range extender if you don't have another dual band device in the area. Everything in my garage is single band so I had to add put an access point (old version of the range extender) there. Paul
  22. I agree with oberkc. Another route, if you have issues with them, is to put filters on them near the transformers. See if you get unpredictable behavior.. one being that they can be turned on remotely, but not back off Paul
  23. A separate question. Are the pendant lights low voltage? Low voltage transformers can create a lot of line noise that disrupts insteon switches Paul
  24. paulbates

    Replaced PLM

    This has happened to me. Factory reset one of them and then restore device to it. If that works, continue to the rest. Let's get through this part and then move on to the mystery device offs if its still an issue. Paul
  25. Correct, it's as oberkc described. Disabled only means the if logic won't run on its own. The if logic will work on a disabled program if you 'run if' from another program. I have a number of programs that I use as subroutines... disabled but work when called from other programs Paul Sent from my iPhone using Tapatalk
×
×
  • Create New...