[quote=“micasaverde, post:5, topic:164869”]But, to get around the limitation of a scene only controlling lights, we invented our own workaround: method #2. Vera tells the scene controller that Vera is a light. Vera programs scene #1 to set Vera to 1% dim level. Scene #2 programs Vera to 2%, etc. Now, when Vera gets the ‘Light switch go to 2% dim level’ Vera says “Aha, scene button #2 was pushed”, and runs the scene which has the ‘scene button #2’ event attached. In this way the scene can set the thermostat, turn on an X10 light, turn off the TV with infrared, etc. So with method #2, Vera is acting as the intermediary. This is the ‘treat scenes as events’ option.
Now you see the problem with the ‘off’ buttons, right? The off button just sends a ‘go to level 0’ to whatever node it otherwise would turn on. Since scene buttons #1 through 5 all just turn “Vera the light switch” on to different dim levels, the ‘off’ for scenes #1 through 5 all do the same thing: ‘turn Vera the light switch off, to level 0’. Vera can’t know which one you pressed.
The limitation, therefore, is not from Zensys. It’s because Intermatic did a ‘hack’ to get the off concept to work, since Zensys scenes don’t have an off. And Vera did a ‘hack’ with method #2 to let scenes to do more than lights. And the 2 hacks are not fully compatible.[/quote]
This was a quote from another thread that explained the problem very well…
So in short this has nothing to do with DEC to HEX as I first presumed but a much more involved issue.
However there is a bug in so much as if Vera is including itself to each button at a defined ‘dim level’ for some reason it stopped at 9 instead of 12.
In short and to my best guess internal and hidden to us… When you add a HA07 Vera does the following as per the info posted by MCV above.
Button #1 – set Vera to dim level 1%
Button #2 – set Vera to dim level 2%
Button #3 – set Vera to dim level 3%
Button #4 – set Vera to dim level 4%
Button #5 – set Vera to dim level 5%
Button #6 – set Vera to dim level 6%
Button #7 – set Vera to dim level 7%
Button #8 – set Vera to dim level 8%
Button #9 – set Vera to dim level 9%
SO when Vera gets sent a dim message to a specific value from a HA07 it knows what button is pressed… And yes given the issues involved this happens to be an elegant solution. However the folks a MCV dropped the ball when they forgot to add…
Button #10 – set Vera to dim level 10%
Button #11 – set Vera to dim level 11%
Button #12 – set Vera to dim level 12%
This also explains why they can’t tell WHAT off button is due to the way Intermaitc? Or zwave?? Handle turning scenes off… When the HA07 looks at what devices are included in/under button #1 it just send a level of 0 to each and thus Vera can’t just inject other dim levels in the off scenes … Since they really don’t exist but are created on the fly by looking at the devices each button controls.
In a perfect world It would be nice if Vera could create virtual zwave devices because then Vera COULD simply add a different ‘virtual-Vera’ to each button.
Something like this:
Button #1 – set virtVera1 to dim level 255%
Button #2 – set virtVera2 to dim level 255%
Button #12 – set virtVera12 to dim level 255%
If they could have pulled this off then they could very well track buttons ON and OFF for all 12 buttons.
Well now that I know what the issue is… All MCV needs to do is add the missing three dim levels 10% 11% and 12% to the missing three buttons 10 11 and 12 and at least we can get full use of all 12 buttons on our HA07s.