paulbates

If you are replacing an outlet, that outlet is fed by a Hot and Neutral today, it will be fine. Paul

Yes, It can be done, I had a hub 1 and PLM running side by side when I first migrated to the ISY. I moved Insteon devices from one to the other, one functional set of devices at a time If you do add the same insteon devices to both, it can get a little tricky. Paul

Hi Fred One at at time, press the set button on the remote link until it beeps. Find the device in the Main device tree, right click and "Restore Devices" Paul

Hi Nick, here's how One time config On the remote computer, browse to the portal: https://my.isy.io Enter your credentials and login At the bottom of the page, click Portal Login Select Go to my ISY --- and your ISY Web page will appear Edit: Portal interface changed, this step no longer needed Next to the ISY, pick Select Tool then Information, then ISY Information Copy the url next to Admin console URL Run the admin conoole and "catch" the finder before it moves to your local ISY Click Add, paste in the copied url Click save to save a copy of the config file .. java upgrades wipe it out Normal operation Run the admin console and pick the ISY with the URL Tricky part: Enter your portal credentials in to the ISY login, not your normal ISY credentials you Its also constrained by the network to the building, especially that networks uplink speed back to the internet. The advantage is that its a client server set up.... it might take a while for things to load and save, like programs, but you should be ok once they are loaded. Be patient when the ISY starts up and when you first click the programs tab Regards Paul

Low voltage transformers can inject significant noise when turned on. That makes them easy to turn on and hard and slow to turn off. Everything nearby might operate more slowly when it's on. Test things with the transformer off only. Did everything improve?

Hi Try factoy restetting and restore device on the Kitchen Island Any low voltage transformers involved? I do in my kitchen, had similar problems and had to filter. Paul

Andrew Glad things are working. My comments on 'bridging' in the above post is a topic that new Insteon users usually need to address... if you plan to keep adding more Insteon to your system. Typically houses have 2 120 volt legs that supply power. Approximately half of lights, outlets, etc are fed by 1 leg, half by the other. The Insteon powerline signal can not typically move across those legs on its own The symptom would be, sometime in the future you add something like an iolinc, and the ISY will not be able to communicate with it. There are Insteon devices to help with this and a way to test that the Insteon signal is bridging... or not. Maybe for now don't worry about it, but if you plan to significantly expand Insteon on your system, check the forum or start a post if you have trouble adding new Insteon plugin devices or switches. Paul

Hi Andrew Dimmers are specifically designed to dim light bulbs. They are not designed for other types of loads. There is inherent danger in trying other type loads like fans, appliances etc. It might technically work for a while before the dimmer or load are damaged (or worse), but its not something to consider. Paul

So, let me correct that.. it initially looked to me like you were replacing a bad PLM, not installing a new one from scratch. I recommend this, since you have no existing Insteon devices with links to restore: You'll need a ethernet CAT5E cable dedicated to the PLM Connect the Cat5e cable to ISY’s Port A and the other end to the PLM Unplug the ISY and PLM Plug in the PLM, wait 10 seconds Plug in the ISY, let it start up Start linking insteon devices Since you have no Insteon devices, the restore PLM steps will not hurt anything, but not do anything either. Also be aware of the need to bridge your power legs on your electrical system using 2 dual band devices, so that you can expand your insteon network with more devices. The PLM is one of those 2 dual band devices. http://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors Paul

Hey Andrew Throw the directions from the box away Follow these directions The actual interface is serial to the ISY, but it is supported by the cable with RJ45 plugs that you've been using between your PLM and ISY Paul

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