paulbates

Hi Jim That will filter out all RF communications to and from the PLM, but not between dual band devices on your network. The nature of dualband devices, including access points / range extenders... is that they are dumb and simply bridge when they see a signal come to them. So there will be significant amount of powerline communications even with the plm in a filterlinc. Dualband devices are designed to work dual band. My efforts debugging rf involve a combination of: observing where the wiring for an outlet or switch actually goes, there can be some big surprises trial and error with dualband devices and access points. I've found it better to take care of all of the basics like bridging, and address problem areas / circuits as identifiable problems appear. Paul

There was a recent thread on memory, and you are more than inside of the limits published there. I suggest telnet-ing in to the ISY and running SM -a. Post your original post and the results of the SM -a over in the 5.07 thread. Paul

V5 variables are not my specialty, but would there be some way to do it with an ISY program and the new date / time variable features in V5? Save the time to a variable hourly in one program based on date (Nov and March) and time ranges (1:00am to 3:00am) Do a compare hourly just after the hour, comparing the variable in another program bounded within a date (Nov and March) and time range (1am to 3am)? The idea is, within boundaries, I'd expect the variable after 1am + 1h = 2. If variable+1 <> 2 // (eg 3 or 1), I know that DST changed then: do a notification, .... Alternatively, write one program for each condition... when variable+1 = 3 or when variable+1 = 1 and have distinct notifications for spring and fall. That may not be exactly the right parameters, but something along those lines could work, for those that have worked this feature better than me. Paul

Hi To be clear, you serial-ed in and got the 'ISY Shell' menu? CT is the command to configure IP. You'll need to have the subnet mask and router address and DNS (the last 2 are most likely the same for most consumer routers) Did CT not work, and if so what happened? Paul

The only memory diagnostic I know of is to telnet to the ISY, login in and type SM. I'm not sure how to equate what that gives you to program memory, or if there is a way to ultimately try to plan around it. The added variable complexity to this equation is how many lines the program have. Chris has provided target upper limits, hopefully that works until you can move to V5 and reduce program count. Paul

In addition to Gary's comment, the ISY has finite memory and a real time operating system. The RTOS needs dedicated memory to operate in and be protected from crashing by unmanaged features, as well as space allocated to future, to-be defined features. Paul

Hi, welcome to the forums! They can take the heat and cold, but do not do well in heavy, sustained rain. The symptom is, after about 12 hours after the sustained rain, they will just start triggering every 10 seconds for no reason.. when it gets to that point, no amount of factory resetting, etc, will do anything to get them working again, in my experience. Like you, I have a spot that is just perfect and I can cover most of my yard and drive with one sensor, but its out in the open. I've tried various ways to seal the case seams, but I think it gets in where the lens hits the bezel. If at all possible, have something over the top of it to keep rain off of it. Paul

Hi, welcome to the forums! Here are some questions: Can you review and/or post your ISY event log? Try to find around when it changed I saw that you mentoned programs. Have you tried leaving the PLM in but disabling the programs to completely eliminate them as a potential suspect? How old is your PLM? PLMs over 2 years old are suspect of being end of life and can display erratic behavior Paul

NP, please let us know how that worked. Its true that the ISY thinks much more like an industrial event driven controller, and can not afford the luxuries of a full development language. The general 2 program approach outlined above is a common way to do things for me. I had to learn from others here on the forums to look at things this way. It does build up the number of programs, so program naming and folders become important to keep your sanity Paul

Hi djm - I would suggest 2 programs, no variables. The second program disables the first for the amount of time you specify to stop the motion sensor detection from starting the program over again. MotionSensed If Motion sensor is switched on Then Run Program 'BellRelay' (then path) else BellRelay if then Disable Program 'MotionSensed' Set 'Kitchen.Den / Bell Relay' On Wait 4 seconds Set 'Kitchen.Den / Bell Relay' On Wait ??? minutes or seconds (to stop it from happening for a while) Enable Program 'MotionSensed else The second program has no if clause and does not need it. You probably don't have to, but I would disable BellRelay so it doesn't run on its own, just when called by MotionSensed Paul

Hi Peter- + 1 for mwester's suggestion I'm in Michigan, and have four outletlincs on the outside of the house and non-attached garage for low voltage yard lights. We get -20F /-30C in winter, and those work fine in the cold. I had an appliancelnc out there for a few years too and it also worked fine. One note: I had problems with an older intermatic 80w low voltage transformer and the outletlinc. When that transformer was plugged directly into the outletlinc on a 6' cable, the line noise from the transformer would make the outletlinc "freeze up" and I had to put a filter linc in. I recently switched to led yardlights with 40w transformers, no problems with those, filterlinc not needed any longer Paul

Its a matter of preference and how elaborate you want your programs to function. I do it the same way you do. I imagine the programs with variables help those that have a lot of sensors and want a systematic approach to 'corral-ing" them Paul

Gary The green flash after a second or so is a diagnostic, it means that whatever insteon device the keypad is controlling sent a response to being controlled and the keypad saw it. If it flashes red after a few seconds, the devices that key is controlling did not respond, or the keypad did not see the response. If you keep getting intermittent problems, I would factory reset all of the devices that had problems and use 'restore device' on them Paul

Two additional thoughts: 1-What is the load, how big is it? Are the loads the same for all the new outletlincs? 2- Devices don't acknowledge a scene command.... but they do acknowledge an on/off. Are there any delays with the on/off? Does it sometimes take a few seconds to turn the device on versus other outletlincs? I would set the event viewer to level 3 and do several on/off commands, it will show communication problems. Post that back here Paul

Paul Hate to say it, but that doesn't sound good. I passed the 2 year mark from installation on mine 2 months ago. It was a "refurb" so its probably even a few month more older than that. I have a spare PLM in a box ready to go.... Paul

Paul Did you try factory resetting the PLM? Sometimes unexpected behavior is addressed that way

Hi Yep, just for the ones that have unusual behavior or a 0101 icon next to is. I've had a few do to when I've swapped PLMs. In rare cases, airgapping a switch or even factory resets have been needed... again, only for those where the procedure didn't work. Paul

Hi, review / follow these directions http://forum.universal-devices.com/topic/19331-my-plm-died-and-i-bought-a-new-one-what-should-i-do-next/ Do not use Delete Modem Paul

I've had 2 different alarm systems with wireless since I've had dual-band Insteon. I've never noticed a problem. My current alarm system has the capability to sense and notify when its being interfered with or jammed. I have not seen a message like that in its log Paul

Ed These kinds of problems are hard, especially when intermittent. Let's hope this gets it. Paul

Ed Gotcha. All of the programs (the 6 log rows above the red) were sending scene commands at exactly the same time. I think that is related to what's going on. Can you create a new scene with all of those lights in it and use that just to turn them all off with that one scene with one program when the sensor stops sensing motion? The UDI recommended practice is to put a 2 second 'Wait' gap in programs between the 'If' sensing from a sensor, and commanding the devices to act. Paul

Was this initiated by a motion sensor? Its interesting that there was all of the events above exactly at 06:40:22 from the program log. That could potentially to be both a battery panic from a motion sensor and the source of what opened the door.

That sure happens to me occasionally for black-outs and especially brown outs.

Steven- Agree with Larry. I'm an Insteon only user and have been on V5 since last November. Go to 5.04 and plan on staying there until the upcoming zwave changes are made and "shaken out"... eg Do not upgrade to 5.05 when its released. There are a few little bugs but they are livable.. You'll get some error messages starting the admin console. They can be ignored. Also, there are the Control, Status statements in programs.. and Control (old) and Status (old).. Some devices with multiple controllers in them like keypads and EZ Floras need to use the (Old) version. Someday that will be fixed, for now use the (old) versions and move on.. No performance impact, and this kind of thing is expected in the beta. I would migrate to 5.04 and backup as Larry stated. Let programs stay the way they were, then start making changes slowly and make backups. There are new features and nodeservers, these capabilities more than outweigh the few little things to be addressed. Paul

If the noise is significant enough, it can cause component (Capacitor) failure in the 2413 PLM. This is a known problem with the 2413 due to component quality, and was not an issue for the 2412. The diagnostic behavior, when this has happened to me in the past, is that the PLM will start losing links and then eventually fail. Since this is happening repeatedly to multiple PLMs for you, my guess is that something on the powerline is causing the PLM to fail. What you are exactly describing happened to me when using a PLM with Homeseer, not the ISY.