fastest way to get this working may be to add the values to the command class description of the node in you active zwcfg. Not familiar with your device but something like this is an example of what worked for me:
Once you get that working in the zwcfg you can add the device to you OZW config device database and the same configuration will be applied on discovery of new nodes.
@Devanl I am trying to figure out if you ever got that Cooper Aspire 5-button scene controller to work…I’m not clear from your above comments. I have been searching for a LONG TIME for some in-wall multi-button switch I can use to trigger automations in HA, and if you’re telling me this one works I would be incredibly happy
I wrote something up to create a sensor platform that reports indicator as the entity state and has a service for calling the set command.
Traveling right now so I haven’t had time to even validate the syntax on this but, here you go if you want to take a peek. As a disclaimer, I have no idea what I am doing when it comes to the home-assistant architecture (still reading the checklist/guidelines).
I got indicator working but I’m having second thoughts about this approach. May go in and just have it setup groups on scene controller to fire scene event on HA when button is activated (pressed with indicator light off).
I will be working on this soon. I really want to move away from ZWay, and this is the only thing holding me back at this point. I implemented it as an “App” in ZWay here, so I understand the details for how this controller works.
The execution environment for ZWay is a severely handicapped V8 implementation. For the life of me, I can’t understand why they didn’t just follow standard Node.js practices and implement all of this as a npm package.
Looks cool. I just read over it quick, looks like this code doesn’t handle any of the association work to notify the controller on button press, correct?
I’m thinking if I start this over again I would have the device creation do that and then just get the indicator status on a button press. Ran in to some confusion around how to direct the scene configuration/association with openzwave.
Also couldnt decide whether this made more sense as a scene controller, remote or group of switch device(s).
Not that I see time for this coming soon but, any thoughts?
That is correct, associating the controller with button needs to be setup beforehand. I do use those association groups to link up to my zwave switches so I get the hold to dim up and down. I didn’t want to mess with that here. The code isn’t anything I’m proud of, but I knew I would be moving away from Zway eventually anyways. The biggest thing I needed to accomplish was syncing the buttons across multiple controllers. This code will ensure that if any of the lights that are in the association groups are on, the indicator is on. Also, if all of the lights are off, the indicator is set off. This allows multiple scene controllers to stay in sync if you associate the same lights with buttons on multiple controllers. It also keeps them in sync if the light is turned on automatically via HASS.
I was thinking about implementing it as a group of switch devices when I port it over to HASS. You just have to fetch the indicator status on the generic scene off event since it doesn’t tell you what button actually turned off. There are some other quirks with the SceneConfiguration command class for these controllers. They aren’t the easiest to work with, but I wasn’t able to find anything comparable.
Started working on this today. It is my next project. I was able to get the scene events to show up similar to all the other central scene devices by adding this to my zwcfg_*.xml file.
I can also see the basic_set=0 event when I turn off a button. My current plan is to create a custom component that creates 5 switch components and checks the indicator value to determine the on/off status.
Sounds great, you should be able to do this by editing the discovery schema in the existing Zwave component?
So the Component would listen for the BasicSet events and then refresh the indicator, then this would result in an event for the switch entity to trigger automation? I like it.
That’s what I am thinking. I know there are already some workarounds needed for the Schlage deadbolts, so I am planning to try and use that as an example.
@Devanl in a different thread, you mentioned that you were able to get the indicator commands to work. Can you share the details of what you got to work?
