jtara92101 Posted November 2, 2010 Posted November 2, 2010 This is probably related to my ongoing issues related to having replaced my PLM with a dual-band model... I can't change the local ramp rate on any of my "old" Switchlincs. The ISY acts like it is changing it, and the log produces traffic when I change it. But the change doesn't take effect. The ramp rate doesn't change. Changes to local on-level do work correctly, though. As well, changes made to the ramp rate in scenes work correctly. Recently-installed devices work as they should. This includes both old (never installed) stock and newly-purchased devices. If I factory-reset a device, it resets the ramp rate back to .1 second. If I remove the device from the ISY, restore the ISY, and restore the device, the ramp rate gets programmed to whatever it was in the database. So, it IS able to change the ramp rate! But the only way I can change the ramp rate is by doing a "restore device". Example: I had all my devices set to 2 seconds, but I want them at 0.5. A few days ago, I was able to change all my devices to .5 seconds. But, apparently I forget to change one of them, or else the problem started when I tried to change that device... If I factory-reset that device, it goes to 0.1 second. If I remove it, restore the ISY, and restore device, it goes to 2 seconds. If I change it to, say, 30 seconds - it stays at 2 seconds! I don't know that I'm going to convince SmartHome to replace all of my old devices.
oberkc Posted November 2, 2010 Posted November 2, 2010 My recollection is that certain "older" models required a power cycle (not full factory reset) in order for certain changes to take effect. Perhaps this is what you are experiencing? Then again, perhaps this only applied to changing of settings from a program (my recollection on this is a bit fuzzy). Still, it is easy enough to quickly check.
fitzpatri8 Posted November 2, 2010 Posted November 2, 2010 That's correct, 'vintage' Insteon SwitchLincs require a warm reset to lock in changes to the local settings. After changing the settings with the ISY, flip the circuit breaker off for a minute then back on (or 'air gap' the switch, whichever is easier for you) to put the new settings into effect at the switch. This power cycle isn't necessary if you change the local settings by tapping buttons at the switch, only when programming it remotely.
jtara92101 Posted November 2, 2010 Author Posted November 2, 2010 Indeed, air-gapping the Switchlinc does make the ramp setting "stick". Thanks! As well, setting the ramp rate by setting the brightness level with the paddle and then double-tapping works as well. (But, of course, isn't accurate, and won't program over the full available range.) The dimmer is marked V3.3, and reports V2.7 in Administrative Console. (Guess these are a hardware and firmware version?) These aren't really ancient. Strange thing is, I swear this used to work. But maybe I just never noticed. I seldom use local controls (lots of Keypadlincs that control groups of dimmers). I guess the ramp rates would be made permanent the next time I have a power outage or flip the breaker, LOL. And when you are installing switches, the probability of flipping the breaker is increased. (I don't know about YOU, but...) I wonder, though, if Universal changed something about how it goes about setting the ramp rate? It's just so strange I never noticed this before! I mean, what's the first thing you want to do with a Switchlinc? Fiddle with the ramp rate, of course!
Michel Kohanim Posted November 2, 2010 Posted November 2, 2010 Hello jtara92101, We have changed many things but what you are experiencing is a limitation of older INSTEON devices over which we have never had any control. With kind regards, Michel
jtara92101 Posted November 2, 2010 Author Posted November 2, 2010 Thanks, Michael. I guess I just hadn't paid much attention to the local ramp rates, since I rarely use paddles, since I have a KPL in every room that sets a scene (or scenes) for the room. The only stand-alone dimmer I have right now is a brand new one (5.15), so there was no problem programming the ramp rate.
Recommended Posts