Illusion

I had exactly the same thought about Smarthome eventually fixing the hardware. I posted in their forum and spoke with Customer Service about this issue. Then I waited 5 months and asked for a replacement. And got garbage. So on your load demand scene.... If the module is off and the load active light is on, will you see your lamplinc turn on, and then go off if the load active light goes off? If that is the case at least with the revision Smarthome got the load demand scene to work with the load active LED. Something my first try never did. I cannot bring myself to care enough to try this for myself, as I am currently very frustrated about this issue. As I got the module when it first came out I had a tough time with the install. The first versions had extremely short lead cables and it affected my install process very negatively. I reported this to Smarthome and the cables on the replacement were nice and long. I was happy to see that but for me the change out of modules was very difficult because of the short cable issue from the original module. So I am very upset to wait 5 months, get a replacement, change it out, and find out that in many ways it performs further away from their marketing than the original!!!

lawr1000, I am totally with you and I understand your situation. First, this device is a POS when it comes to the 'load active' and load sensing portion. For clarity, lets call the load sense "load demand" to separate it from what everyone else thinks we mean because of the use of the load sensing features included in other Insteon modules to date. As I write this, my first 2477SA2 is sitting in a box waiting to be shipped back to Smarthome because of this failed load demand feature. My load active light was also on when it should not have been. The load active light should never light with the controller switched off. But of course it was. You can see that this is outside of expected operation as there is a table of LED conditions in the full manual and sure enough there is no situation where this condition should exist. The replacement 24777SA2 is even worse. My first one was accurate at load demand if the controller was on but the replacement is wrong most of the time. The load active light on the replacement is almost always on, even though the load is not in demand. I think my load active light is on about 80% of the time with this new module regardless of the module being off or on. I was never able to get my first 2477SA2 to properly control a load demand scene. It would turn on the load demand scene if the 2477SA2 was on and off if the 2477SA2 was off, completely ignoring the load active LED. That may have been because it was brand new when I bought it and it was revision 1.0B. I have not tried to manually link a load demand scene to my replacement 2477SA2 because: 1. If I cannot use it in the ISY I do not care about it. I have mentioned the need for a second node for this device several times but I do not think it is yet understood by the UD team what the load demand scene is and how it is different from load sensing from modules in the past. 2. The load demand function on this module does not work at all. I have tested the modules (the first one and the replacement) with a 240V load I could control. With the module off the load active light would light sometimes regardless of the load being connected or not. The load active light should be off any time the module is off regardless of load demand. But it appears the load active light has little to do with the load side when the module is off. 3. My replacement module incorrectly reports load demand even when the module is on. The first one (which I believe was a beta unit due the the revision number) at least was right if the module was on. 4. Even if the ISY supported this feature, and I put the original 2477SA2 back in the system this feature is still useless because the device will report load demand when the module is off. Even without a load connected!!! I would say to ask for a replacement like I did, but what you get will be no better than what you have. Smarthome agrees the module is not working correctly. Their solution was to send me another one that also does not work correctly.

Confirmed. Just did it to make sure it worked and indeed I now have readings in C

Just today I looked on the wiki for this exact info. It has a great breakdown of the info in the event viewer. Just click on the wiki in the help menu from the Admin Console and type "event viewer" in the resulting search box on the home page of the wiki. Learned lots, not like the knowledge in LeeG's brain, but lots.

Sorry. No event trace from me. Happens way too infrequently to capture. I do not leave my computer on.

I think the wind speed could definitely be used for some type of storm warning. You could play with a combination of average wind speed and gust speed both being over a certain value. Even average wind speed seems to update frequently in my experience.

LeeG, I will be most interested if his level 3 event viewer trace shows using Peek/Poke instead of the 2E extended command for this function for this switch. If indeed it does show this it will be an exact duplication of the problem you helped me solve in this thread: http://forum.universal-devices.com/view ... 9743#19743 My solution was to switch to device detected link management mode, change the toggle mode, and then switch link management mode back to automatic. Or you can manually get the button to go to non-toggle mode by following the tap method from the device user manual. This has always worked for me.

Yep, it just happened again. Switch is going to get replaced. I had not thought about calling Smarthome about this one. I will do that. Good idea.

IM, Does your SWL dimmer throw out the control command when it switches off? I know Insteon devices are not supposed to turn themselves on and off and they have clearly shown themselves to be very resistant to this. Especially when compared to their X-10 ancestors. I would be concerned if my light were turning itself on and off. I am down right alarmed that the device is functioning as though someone had pressed the switch. This switch does not control any other devices, but if it did it would be activating them as well. I would be very interested if anyone else has seen this. Not just where the devices is incorrectly turned on or off, but where the device reports it has physically been switched on or off when it has not been touched, which is what is happening in my case.

Good thought, but not in this case. The first time the event occurred there was no activity at my house at all. I was away and the house was inactive. The other two times that I know of was not in response to any known event.

I assumed you knew about this as it has been an issue since 2.7.4: http://forum.universal-devices.com/view ... 1127#21127 I only mentioned it now because you have changed from Beta to RC2 and I wanted to let you know about it again before an official release. In my case it is 100% repeatable, and has been on every version I have used since at least 2.7.4, regardless of java upgrades and operating system upgrades. Using the Admin.jnlp application or the admin console through the browser selecting a scene with lots of devices in it and using the scroll bar mouse drag method to scroll down the list will result in incorrectly rendered level and rate slider indicators. The indicators will render on the far left of the detail window instead of on the slider bars. Bringing up another window on top of the admin console will return the sliders to their bars, but it will leave the incorrectly rendered indicators on the left of the scene level/rate window as well. This only happens on my Mac, not my Windows machine

Update: Several weeks after the initial incident I noticed that my bathroom vanity light was on. This is odd since I am home and when I turn the lights on in the bathroom I do not use the switch that controls the vanity. I use the switch that turns on the track lights, of which the vanity is a scene member. So if I turned the lights on or off in the bathroom the vanity should never be on by itself unless turned on by an ISY program. No ISY programs should have been running at the time. I thought this might be related to my earlier post but had no way to be sure I did not hit the vanity button by accident at some point. So I created another program that is always active: If Control 'Bathroom / Bathroom Vanity' is switched Off Or Control 'Bathroom / Bathroom Vanity' is switched On Then Wait 33 seconds Send Notification to 'Email' Else - No Actions - (To add one, press 'Action') And today I notice the vanity on by itself again. I had not been in that bathroom for several hours and the lights were off when I last left it. I open my email and sure enough the bathroom vanity control had been switched on while the bathroom was empty. Looks like I have a failing switch that turns itself on. This is a new one for me. I pulled the cover off the switch for inspection. No unusual issues. Clean interior, no strange protrusions on the plunger from the switch face. I went ahead and vacuumed it anyway for good measure. I factory reset and restored the device in the event it is a software event. I at this point have no way of knowing if the event is internal software or hardware related. I would imagine an unintentional closure of the micro switch is just as likely as a firmware glitch. If it happens again I will report here and replace the switch.

I am pretty sure you guys are aware of it but: On the Mac the slider indicators for on level and ramp rate in a scene get all screwed up if the scroll bar is used to scroll down the list of devices included in the scene.

All good so far. As a Mac user I have had to use HTTPS for all updates for a while else it gets stuck at 12% or 13% with various errors. The HTTPS method has worked flawlessly for updates. I have had to use this method exclusively since 2.7.13.

I did mean the 2477. I did not realize you wanted it in a normal switch size. The only mention I saw in the discussion above was a limited enclosure size and no access to a neutral, but I did not realize that the limited enclosure size was that of a standard switch.

The new Insteon 220V switches no longer need a neutral.

STOP!!! Do not do "Remove PLM" function without reading and understanding this post: http://forum.universal-devices.com/view ... =3401#3401

Yes it will

Yeah, they are still going. Test has been contaminated a bit. I had to replace my PLM. As a result I had to put the MD into programming mode which takes a bunch more energy than just detecting motion. One of the MDs batteries did not have enough energy to power the programming mode even though it was detecting motion just fine. So it had to be replaced to complete the PLM replacement. The one MD that underwent the battery change is in a heavily used area with at least 10 triggers per day every day for the past year. Other test units are working fine still even after the heavy energy usage of re-programming. All MDs are exterior and are in an operating environment that has ranged from 17˚F to 103˚F over the past year. I will report when the others start to die that are still in use with the original batteries.

A quote from a random Insteon Manual, a Switchlinc in this case: NOTE: Unless they have been Unlinked, INSTEON devices that have been previously Linked to SwitchLinc will still respond to paddle presses, even after a factory reset. The reason is that the INSTEON devices themselves have not been Unlinked from SwitchLinc. See Unlinking a Controlled INSTEON Device from SwitchLinc. This, or very similar text, can be found in almost ever Insteon controller's manual. You can see this dynamic for yourself in a very controlled way outside the ISY. Get a controller, tap link a responder to it. Factory reset the controller. Hit the button on the controller and the test responder will still turn on... I believe this is referred to as a half-link or a broken-link. Not a desired situation as the controller cannot send clean-up commands to the responder since it does not know about it. This is what I believe is happening in your Rlinc case: The responder links are there in the responding devices (the ISY put them there when you created or added the devices to the scenes) and they see the group command coming from your Rlinc and respond, but the Rlinc does not know it is trying to talk to those specific devices because the lincs to those devices have not yet been programmed into the Rlinc since you have not put it in programming mode. I also believe this is a major cause of your scene testing problems which I have been following closely. Specifically, the poor ISY has forever been trying to program your Rlinc, and apparently tries to every time you change the state of something, but never succeeds because the Rlinc is never in programming mode. This could explain all kinds of slow communication issues if the ISY is always trying to contact the Rlinc without success every time it tries to do anything.

Justin, You did not program your Rlinc without pressing the dim bright buttons. You did program the responders to the scene, and they are still reacting to the button press on the Rlinc, but the Rlinc is still waiting to be programmed. This is why you have to disable it to get the scene test to work. First order of business is to put that Rlinc into programming mode and let the ISY do the desired updates!!!!

Sure, I will let you know. Never happened before in over a thousand hours of being enabled. Not sure what to think of this. Maybe a fly hit the switch really hard flying around in the morning. Ghost? I assume you have never heard of an issue like this before from anybody?

Because this is the text I received at 5.41AM: Subject: MANUAL ACTIVATION!!! : Alert MANUAL ACTIVATION!!! 'Bathroom Vanity (B 4F B2 1)' set On at 2010/10/25 5:41:10 AM.

Switch in question is a 2476D v.27 Program that sent notification is a simple as: If Control 'Bathroom / Bathroom All Off Control' is switched On Or Control 'Bathroom / Bathroom All Off Control' is switched Off Or Control 'Bathroom / Bathroom All On Control' is switched Off Or Control 'Bathroom / Bathroom All On Control' is switched On Or Control 'Bathroom / Bathroom Fan' is switched On Or Control 'Bathroom / Bathroom Fan' is switched Off Or Control 'Bathroom / Bathroom Fan Control' is switched Off Or Control 'Bathroom / Bathroom Fan Control' is switched On Or Control 'Bathroom / Bathroom Floor Heater' is switched On Or Control 'Bathroom / Bathroom Floor Heater' is switched Off Or Control 'Bathroom / Bathroom KeypadLinc' is switched Off Or Control 'Bathroom / Bathroom KeypadLinc' is switched On Or Control 'Bathroom / Bathroom NIght Light Control' is switched On Or Control 'Bathroom / Bathroom NIght Light Control' is switched Off Or Control 'Bathroom / Bathroom Shower Fan' is switched Off Or Control 'Bathroom / Bathroom Shower Fan' is switched On Or Control 'Bathroom / Bathroom Shower Heater' is switched On Or Control 'Bathroom / Bathroom Shower Heater' is switched Off Or Control 'Bathroom / Bathroom Shower Light' is switched Off Or Control 'Bathroom / Bathroom Shower Light' is switched On Or Control 'Bathroom / Bathroom Sink Heater' is switched On Or Control 'Bathroom / Bathroom Sink Heater' is switched Off Or Control 'Bathroom / Bathroom Track Lights' is switched Off Or Control 'Bathroom / Bathroom Track Lights' is switched On Or Control 'Bathroom / Bathroom Vanity' is switched On Or Control 'Bathroom / Bathroom Vanity' is switched Off Or Control 'Garage / Garage Flos' is switched On Or Control 'Garage / Garage Flos' is switched Off Or Control 'Office / Office KeypadLinc.D' is switched Off Or Control 'Office / Office KeypadLinc.C' is switched Off Or Control 'Office / Office KeypadLinc.C' is switched On Or Control 'Office / Office KeypadLinc.B' is switched On Or Control 'Office / Office KeypadLinc.B' is switched Off Or Control 'Office / Office KeypadLinc.A' is switched Off Or Control 'Office / Office KeypadLinc.A' is switched On Or Control 'Office / Office KeypadLinc Main' is switched On Or Control 'Office / Office KeypadLinc Main' is switched Off Or Control 'Kitchen / Kitchen Flos' is switched Off Or Control 'Kitchen / Kitchen Flos' is switched On Then Send Notification to 'Text' Wait 33 seconds Send Notification to 'Email and Text' Else - No Actions - (To add one, press 'Action') And this switch is an original install, so it has been part of this program for as long as the program has existed, which was shortly after getting my original ISY-26... you know, back when we were both just kids.

I have a program that is enabled (via folder conditions) only when I am not home. This program monitors many of my switches and will notify me if one is touched when no one is supposed to be in my home. At 5.41.10 today while at work I got such a notification for the first time ever! I have had this program running for a long time with never a failure watching lots of switches so I was deeply concerned. It appeared that someone had pressed the switch controlling my bathroom vanity light! After investigating I cannot find any cause. I look in the log and find this: Bathroom / Bathroom Vanity Status 100% Mon 2010/10/25 05:41:10 AM System Log at the time the alert was sent. Immediately preceding this event is this: Scene:Front Compound Lights On 255 Mon 2010/10/25 05:41:09 AM Program Log Front Yard / Floods - Bedroom Status 100% Mon 2010/10/25 05:41:09 AM System Log Front Yard / Laura's Flood - Front Status 100% Mon 2010/10/25 05:41:09 AM System Log Front Yard / Laura's Front Porch Status 100% Mon 2010/10/25 05:41:09 AM System Log Bathroom / Bathroom Vanity Status 100% Mon 2010/10/25 05:41:10 AM System Log Which shows a scene that has been called due to an outside motion detector tripping. Bathroom Vanity is not part of this scene. And even if it were and got turned on by the scene, that is not the same thing as 'Control'. I am stumped. I have no Idea how this could happen, nor how to prevent it from happening in the future. I did just replace my PLM and built a whole bunch of new scenes. I could understand a light coming on when I did not want it to due to a bad link or some such, but the ISY mistaking a status change in a light for the switch being pressed is unheard of as far as I know. For all I know the light was never even on, let alone having the paddle pressed. Thoughts?