I’m using Vera light with 1.7.481 firmware.
I have Aeon Smart Energy switch connected to a lamp. Today I added Aeon minimote to my Vera controller.
I want to be able to toggle Smart switch with first button, but I can only turn it on or off, not toggle.
When I created scene, I went to advanced option, deleted SmartSwitch device and re-added it with “ToggleState” action. Now when I press button, light turns off and then immediately on 
What am I doing wrong?
Here’s screenshot of advanced setting window.
Make sure that the problem isn’t that the remote is double activating the scene. Does the scene work correctly when you run it manually, or does it behave as you describe?
Make sure that nothing else is acting on the device. There should be no triggered scenes or anything that might act on the device when you change its state. Such as another scene that also toggles the device.
I don’t use UI7, so I can’t tell you with certainty whether or not that GUI’s ToggleState action directly maps to the LUUP toggle state command that only inverts the present state, or if it is supposed to work as you describe(I doubt this).
To rule out the above possibility, you could try removing the action from the scene and adding the following code to the LUUP tab of the scene.
luup.call_action("urn:micasaverde-com:serviceId:HaDevice1", "ToggleState", {}, 6) Then run the scene.
I don’t think you are doing anything wrong… BUT…
The 1.7.481 (v7.0.3) is an older firmware… Many of the older firmware releases have issues with the MiniMote not working correctly… This may be your issue…
The other thing I noticed is that the screenshot you posted shows the “ToggleState” action, but does not display the serviceId… The scene I have to do exactly the same thing, shows both the serviceID and the “ToggleState” action… so, the action may not have been set up correctly by the scene wizard… This may be a bug in the v7.0.3 firmware, as there were many complaints of erratic and strange operation when the firmware was released…
First step… Upgrade your firmware…
second step… Delete the scene and create it again…
The ToggleState action does invert the present state… well, so of… If the device is On (or any level above 0% for a dimmer) it will turn it Off… If it is Off, it will turn it On (or 100% for a dimmer).
Thanks guys!
Cybrmage, after updating firmware and re-creating scene, it started to work!!! 
;D
Can the togglestate be used from an HTTP call as well or just Luup?
http://yourVeraIP:3480/data_request?id=lu_action&output_format=xml&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:HaDevice1&action=ToggleStateChange DeviceNum=6 to the appropriate device number.
Yep! I figured that one out last night. Thanks for the help!!!