rhughes

You should be able to set them to Non-toggle OFF mode from the ISY console. No need to create scenes.

Nice. I've always enjoyed using state machine logic for complex programming. A few questions, though: 1) Why is the state variable initialized to -1 instead of 0, the steady state? 2) I don't understand what program Test2.C0 is intended to do. 3) Can you use a regular variable to hold the secret code so you only change it in a single place, not 3 places? Randy

Hi, Just to follow up, I received my new PLM, installed it, and used the ISY to update it as well as all the devices (I have around 70). This seemed to clear up all my program/reporting/linking problems I've been having over the past year or so. My guess is that I was at some limit on the old PLM that the new PLM got past; probably the >800 links limit. I've lived with it now for a couple of weeks with no problems. I'm sure this isn't a panacea and your mileage may vary.

Hi, I have an Insteon setup with about 80 devices so far, including switches, lamp lincs, 9 keypads and miscellaneous wireless devices. I've noticed that when I add additional devices, it seems to cause random problems that required me to fiddle around reprogramming, removing/adding devices, etc. I rely on a fair number of scenes as well as programs (which require status updates). This weekend I finally had the ISY refresh all the device link tables, including the PLM link table. That seems to have stabilized things considerably, except for one keypad linc that I had to reload again. That got me to thinking that maybe my system was getting too big for the PLM. I checked and the ISY shows the PLM has about 950 links. No problem, thought I, since the 2412S should support >2000 links. But then I started checking all the posts related to the new 2413S PLM which I am thinking about changing to since it is dual mesh. Here's what I found: 1) The old 2412S PLM has a link table capable of supporting >2000 links, but only the first 800 support reporting status changes(!!) 2) The new 2413S PLM has a link table capable of supporting 1026 links, but all links support reporting status changes 3) Also, the new 2413S PLM doesn't power the ISY, so a separate power supply is needed Given this, it seems some of my problems are that I'm outgrowing the capabilities of the 2412S PLM. It looks like I should move to the new 2413S PLM and ensure I don't grow beyond its capabilities. I should be able to simplify a bit to keep the link count under the magic 1023 limit, at least until Smarthome comes out with a new "PRO" version PLM Does anybody see any faults with this logic? Thanks.

Thanks for the advice, Lee.

Hi Brian, Right, my mistake. I have an Access Point plugged directly into the PLM. That's how I'm receiving the signals. I only use one since I installed a hardwired Insteon phase coupler. Since I have another Access Point, I'll try plugging it in at the other end of the house for better signal coverage. Thanks for the feedback.

Hi, I'm adding some Insteon motion sensors as occupancy sensors in my home. I'm then controlling lights using ISY programs to trigger lighting scenes. The light(s) should come on instantly with the motion ON signal but begin to fade off after the motion OFF signal is received. As it turns out, the time between motion detection and the lights coming on isn't instant, but I can live with that. The problem is that sometimes the ISY fails to get the ON notification from the motion sensor. I've verified this with the Log. I'm not sure why, other than maybe a wireless signal collision from multiple sensors. I have a SignalLinc plugged directly into the PLM. I've been trying to think of some ways to mitigate this problem, including: 1) Add the motion sensor directly to the lighting scene, but this creates a problem since I want the lights to slowly dim off after a period of no motion, not turn off instantly. I don't think there's a way to add the motion ON to a scene but the motion OFF to a different scene? 2) Create a scene with a LampLinc (no lamp attached) and the motion sensor and use it as a backup signal to the programs? Even if this worked, I'd need a LampLinc for each motion sensor -- not ideal. Any ideas would be greatly appreciated. Thanks.

Hi Michel, I am thinking of purchasing an EZIO6i. Have these issues been resolved? I did a search and this seems to be the latest thread talking about that device. If there are still problems with the EZIO, then I will just get separate I/O Lincs. Thanks.

IndyMike and Tim, Thanks for your replies. I think I'll go with a mix of EZIO6i, I/OLinc for garage door and TriggerLinc for wireless. I currently use an odd setup of X10 wireless and some hard wired sensors feeding into a controller (a Barix Barionet) that I custom coded to interface to my ISY. It seems to work fine, but I want to move away from that and go pure Insteon for the reliability and simplicity. This got me thinking that I will probably need to replace my 4 wired motion detectors with Insteon wireless. Thanks for the heads-up, Tim.

Hi, I have about 10 hard-wired on/off contacts (e.g. motion sensors, door switches, garage door contact, etc.) that I want to directly monitor and trigger programs using my ISY. The number of contacts will grow in the future. What are user experiences with the following and what do you recommend: - TriggerLinc (I can line them up and power via a power supply instead of batteries) - I/O Linc - EZIO8SA - Other? Thanks for your suggestions.

Hi, I purchased an ISY 99-i PRO a year ago and have successfully used it since. At the time of the purchase, I didn't think I would need any IR capabilities. Since then, I have installed a home theater system and realized how great it would be to control the room lights from my remote. After investigating, I found that the ISY 99-i/IR PRO would be the best fit. I sent an email to ISY this past Saturday asking how much to upgrade, figuring I was looking at $100 minimum. The next day (Sunday!), Michel emailed back and said he could log into my system and re-flash the firmware on my existing ISY device and send me an IR module at a very reasonable cost. I gave him the go-ahead, and later that day (still Sunday!) he logged in, re-flashed the device and updated to the latest firmware. I should be receiving my IR module soon. This service is by far the best I have received from any other company for any product. I am definitely checking out their other add-on modules. Randy Hughes

Hmmm. Well, that worked. I'm not sure what happened yesterday morning, but all seems fine now. I have an external app that I've developed that interacts with the ISY, so that may have caused some issues. I'll check it out more closely before I manually set the time if this happens again in the fall. Since others aren't having problems with NTP, it must be my network. I'll work through that. Thanks.

I'm using v 2.7.0. When my ISY-99 didn't update for DST yesterday, I noticed that the time wouldn't synch using NTP, so I synched with the computer, which worked. I've tried 3 different servers: pool.ntp.org, 192.43.244.18 (NCAR) and time-b.nist.gov with no success. I'm pretty sure I verified this worked before, but it was a while ago.

I'm having the same problem today with a -60006 error in the log.

Hi Rand, Thanks for your suggestions. It turned out to be two problems. The first was a small issue with my programs that I was able to fix. It occurred when my motion sensors fired again before the program finished (they have a fairly fast recycle rate). The other issue was signal quality. I moved the APs around, including putting one on the PLM, which helped. Thanks, again.