I just installed some CA600 switches, and thought that they were capable of remembering the last dim level that was set. However when I turn the lights off and then back on again, it always goes to maximum brightness. Am I doing something wrong or did I misunderstand the capabilities of this switch?
Anyone using a CA600 switch… when you turn it back on, does it or doesn’t it remember the last dim level that was used? The instructions make it sound as though it should: “Automatically returns to last level in the event of power fluctuations.”
Thanks!
[quote=“gcristof, post:2, topic:172700”]Anyone using a CA600 switch… when you turn it back on, does it or doesn’t it remember the last dim level that was used? The instructions make it sound as though it should: “Automatically returns to last level in the event of power fluctuations.”
Thanks![/quote]I do not have a CA600 installed, but to me, that means the switch remembers its state during a power outage.
If the light is at 50% and the power goes out (meaning “line/hot” goes dead - not turning the switch off), when power is restored, it will return to 50%. And if it is off, it will remain off.
Yes, I thought about that too… however if the switch does have the capability to remember dim level during power fluctuations, wouldn’t it be kinda dumb for the manufacturer to not allow it to remember dim levels when there are no power fluctuations? ![]()
Anyone out there using a CA600? How about it? ???
Just double-checked. The CA600 does not “remember” the last dim level. It goes to full brightness. Your options would be to manually hold the paddle switch until the desired brightness is reached, or use in conjunction with a scene controller.
Did you verify that it actually can do that? Say: set the dimmer to 20%; cut power; apply power. Does it go back to 50%, or perhaps full on, etc.?
I haven’t checked that and am not planning to. Doesn’t seem like a useful feature.
Well, that was only to establish if the device actually ‘remembers’. If so, I’d propose another test; but we can cut to the chase:
Manually dim to some low value. Then turn off the dimmer. Then do the following from the Luup sandbox ([tt]Apps[/tt] > [tt]Develop Apps[/tt] > [tt]Test Luup code (Lua)[/tt]):
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='<nodeID>',Data='32 1 255'},1)
[size=8pt]Replace [tt]nodeID[/tt] with the [tt]ID[/tt] of the dimmer from its [tt]Settings[/tt] tab (not [tt]Device#[/tt]).[/size]
I will give that a try and report back here.
I would find it a very useful feature, particularly in the kitchen where we have several very bright recessed lights. Occasionally we need them at 100%, but most of the time we need them at about 75%.
[quote=“oTi@, post:8, topic:172700”]Manually dim to some low value. Then turn off the dimmer. Then do the following from the Luup sandbox ([tt]Apps[/tt] > [tt]Develop Apps[/tt] > [tt]Test Luup code (Lua)[/tt]):
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='<nodeID>',Data='32 1 255'},1)
[size=8pt]Replace [tt]nodeID[/tt] with the [tt]ID[/tt] of the dimmer from its [tt]Settings[/tt] tab (not [tt]Device#[/tt]).[/size][/quote]
I’m willing to try that too, but am very new to this… How do I get to the Luup sandbox and use it?
I would find it a very useful feature, particularly in the kitchen where we have several very bright recessed lights. Occasionally we need them at 100%, but most of the time we need them at about 75%.[/quote]
The ‘feature’ being referred to is about remembering the dimming level after a power outage. That’s great if you use your breakers as a light switch.
oTi@,
I tried your Luup code. I get a “Message sent successful” pop-up, but I assume there’s some other result that you’re looking for?
Oh! I see now. Yes, your code snippet does turn on the light and return the light level to the previous dim setting. Interestingly, it does not show up in UI5 until the device is polled.
Thanks for testing! Interesting. So the switch does remember the previous setting. Apparently a design decision to have it go to 100% when switched manually. Or the behavior may be configurable through a parameter, although I don’t believe I saw anything mentioned in the instruction sheet.
Interestingly, it does not show up in UI5 until the device is polled.This particular command bypasses the usual way to interact with Vera, and more or less goes straight to the Z-Wave chip. UI5 therefore won't know what happened until the poll is done.
The Luup sandbox is under the [tt]Apps[/tt] tab, then pick [tt]Develop Apps[/tt], then select [tt]Test Luup code (Lua)[/tt].
Regarding your use case, if the Dashboard updates quickly with the new status for the switches in the kitchen, then you could try a scene triggered by ‘A device is switched on’ and set the dim level to 75%, and see how it performs.
sorry for my delayed reply, I got tied up with a family matter…
Ok, so I hit the breaker switch on the line that the CA600 switch is on and left it off for 1 minute. When I restored power the light came back on to the previous dim level - it remembered it.
I also tried the Luup code snippet, and yes it worked for me as well. The light comes back on to the previously used dim level.
Unfortunately, it takes to long for the status to get updated in Vera to make this useful. I’m following this Mios issue: [url=http://bugs.mios.com/view.php?id=2346]http://bugs.mios.com/view.php?id=2346[/url], perhaps if that bug gets fixed I’ll be able to use that code to get the behavior I’d like.
Thanks!
Glad I found this thread - my wife hated the fact she had to stand there and hold the paddle down to dim the lights when initially turning them on…So now I’ve got a trigger setup, when light switched on to dim to 70%! LOL if only I would have realized this months ago!
Are you using a CA600 switch? Don’t you find that there is a long delay between the light being turned on and your trigger being run?
Yep CA600…and yes there is a delay, but not a big deal for the wife, as long as she doesn’t have to stand there and hold the paddle to dim…of course it would be nice if it was more instantaneous but at this point it works…