I have the Enerwave 7 Button Scene selector (ZWN-SC7). I would like to have one of the buttons trigger a scene, or run a routine that triggers a scene. This is seeming a little more difficult than I expected.
Since the device type handler defines it as a button controller, you should just be able to use it directly with the official smartLights feature or with a routine. Both have an option to activate a scene when a button is pressed. You wouldn’t need a simulated button or webcore. The SC7 is already treated as a button controller.
So just start with the official smart lighting feature, select the scene you want to activate, then say when the button is pressed, and you should see your SC7 on the list of button devices to choose from. If not, I would ask the follow up question in the author thread for the device type handler. The other smart app won’t matter.
@JDRoberts - I went down this path, however I don’t think this Enerwave 7 Button Scene controller is “officially” supported by ST or the SmartLighting App. When I try to add the SmartLighting Smart App, and choose my Enerwave button controller, it shows the whole thing as 1 button, and therefore will only let me assign an action to button 1. If the SmartLighting App would recognize all 7 buttons, then yes… this would be exactly what I need.
Interestingly, the SmartLighting Smart app works with an Aeon MiniMote that I have, and correctly recognizes all 4 buttons. Is this an issue with the Device Handler that I’m using for the Enerwave?
I will look around to see if I can find some examples of adding the code to run a routine as @tgauchat recommended. If anyone knows of some good snippets, I would appreciate a link.
Yes, it’s the device type handler. There was a change about a year ago that now requires device type handlers to specify how many buttons they have. It’s just like a two line change. Then once you have that, smart lighting and web core and routines and other standard code can identify the individual buttons. The following thread has the code you will need if you can’t find a more current device type handler that already fixed this issue.