I think we need to back up a bit here. the dimmer child devices are for setting default dimmer levels and one for disabling local control thats it. Furthermore the child devices are created in the dimmer driver preferences, you do not create them yourself.
It sounds to me that you are talking about wanting a double tap to activate a scene. this is something different, am i correct?
I was attempting to do this with the non dimmer scene switch and using the child driver (without the level wording)
Once I tried on the dimmer switch, I got two child devices created (one for local and one for zwave) I think I am on the right track now. Wonder why the non dimmable switch doesn’t seem to work.
Just need to play with it some more to fully understand its potential.
Yeah, I’d like to get the double tap , triple tap etc.. working. I assume these are treated as buttons. I see them in the events, but when I create a rule to perform a task based on the “taps”, it doesn’t seem to react to them.
It looks like both scene enabled switches (dimmer and on/off) use the same child device driver "switch level child device". It just creates the child devices based on the toggled setting in the switch driver preferences.
As far as the tapping goes certain taps correspond to a "button".
2 taps UP on the switch registers as button number 2 PUSHED in the button controller app.
2 taps DOWN on the switch registers as number 2 button HELD in the button controller app.
And so on...
Just dont use button 1 it is obviously reserved for the OEM
I've talked about it in the past, but it has kind of been put on the back burner. I'm 100% ready to make any adjustments the Hubitat team sees fit in order to get them there.
@mike.maxwell@bravenel@patrick Sorry - I'm not sure who to tag, but I'd love it if Inovelli devices were natively supported. It looks like there's a desire on the Inovelli side to play nice with Hubitat, perhaps?
Actually, I just reached out to @mike.maxwell. Our office was supposed to send him out some samples and seems like they haven't. I'll ask them again to send them out.
My house is full of these switches and dimmers, they work wonderful, and when they dont inovelli is right there to help, it would be great to see them native
Hey @jrfarrar -- I'll personally check on this tomorrow. I know some were sent maybe two weeks ago (or at least were supposed to). Feel free to PM me as well if I get side-tracked, but I've sent an email to our internal customer service guy to double-check what was sent.
Sorry for the confusion here. Eric M. has definitely asked us a few times about this.
Ive been using the NZW97 to control my garage doors but seeing the following error in the logs coming from the driver. It still seems to be working but this error keeps repeating in the log and thought I would report it.
I've never messed with the associations on zwave. I do everything through the hub. So basically add to the hub and use. Not sure though if this could have happened some way.
I do see that you made an update to the driver. Going to give that a try and see.
Yeah, I put the importUrl in before it was specified to put it into the meta information. Back in the day you had to copy & paste it into the import text field.