Inovelli Red

[lairdknox]

I recently received a new switch - the first one was stolen - and am having some issues with it. I setup both drivers and it looks to have installed OK. I created a couple of notification alerts and I see the virtual drivers.

I am able to use the switch with Rule Machine and was able to get actions to take place when I single and double click on the top paddle. Where I can't get anything to happen is in the device screen.

Pressing on, off, or Up x1 I don't hear the relay engage. The light doesn't change. Also clicking on/off in the child virtual device doesn't change anything on the LED.

Up x1, Down x1, Up 3x on the switch itself returns the following:

OK, I just tried the Up 1x and Up 2x buttons on the device screen and the RM rules fired so I guess they are talking. I must have a setting in the config set to not control the relay.

Going into the first child device I clicked on, off, on and see this in the logs:

But the LED does not respond. Am I not understanding something here?

Finally, how would I read the paddle clicks in a custom app? Do I subscribe to the switch itself or would I have to subscribe to each button press, 2x, 3x, etc? Does anybody have a bit of sample code that works with the switch?

Thanks in advance!

[scottgu3]

Based on my experience with finding the Dimmer driver, I'm going to ask...Do you have the Dimmer or the Switch?

I ask, because I could do some things with the switch driver, on my dimmer, but once I found the right driver(!), for the dimmer, all became well.

Probably not your issue, but...just in case!

S.

[lairdknox]

I believe it is the switch. The packaging says on/off switch so that’s a good sign. I do hear the relay engage when I manually operate it.

I only saw a single Inovelli driver. I suppose it is possible I got the wrong one.

[bertabcd1234]

You do have the wrong one if you have the switch. The scene (Red series) switch is model LZW30-SN, while the scene (Red series) dimmer is LZW31-SN. The cheaper, non-scene models (Black series) are the same without the "-SN."

• Red Series (scene-capable) switch driver, LZW30-SN: Hubitat/inovelli-switch-red-series-lzw30-sn.groovy at master · InovelliUSA/Hubitat · GitHub
• Red Series (scene-capable) driver, LZW31-SN: Hubitat/Drivers/inovelli-dimmer-red-series-lzw31-sn.src at master · InovelliUSA/Hubitat · GitHub

and for the sake of completeness:

• Black (non-scene) switch driver, LZW-30: Hubitat/Drivers/inovelli-switch-lzw30.src at master · InovelliUSA/Hubitat · GitHub
• Black (non-scene) dimmer driver, LZW-31: Hubitat/Drivers/inovelli-dimmer-lzw31.src at master · InovelliUSA/Hubitat · GitHub

and for the scene ones, if you create child devices for notification purposes, you'll also need:

• Hubitat/switch-child-device.groovy at master · InovelliUSA/Hubitat · GitHub
  (which it looks like you already have, but I anticipate needing to reference this post in the future, so...for the same of completeness again )

A lot of the features will work with one driver instead of the other, but the notification LED parameter number is one of the differences between the two (besides device capabilities), so that would definitely explain that problem.

[Terk]

Make sure the Disable Remote Control didn't get enabled.

[scottgu3]

OK, @bertabcd1234 lists all the drivers in his reply, but based on your screenshots, you are definitely running the Dimmer Driver for the LZW31-SN, when you really want the LZW30-SN for the switch, if indeed you have the switch, and not the dimmer.

Basically, you're encountering the same problem I did, just in reverse!

S.

[lairdknox]

@bertabcd1234

You do have the wrong one if you have the switch.

You are correct. It took a bit of sorting out. Notifications still weren’t working but it turns out I had an error in a parameter field but it didn’t tell me that. One field was listed as taking a value of 1..n with a default of 0. If you enter 0 in the field then the save fails. Go figure.

Anyway now the next part. How do I subscribe to the events. I’ve been poking around but can’t seem to get a handler to fire. I’ve played with various settings like these:

input "ino", "capability.pushableButton", required: true, title: "Inovelli"
input "ino2", "capability.holdableButton", required: true, title: "Inovelli"
input "ino3", "capability.switch", required: true, title: "

And

subscribe(ino, "pushableButton.1", buttonHandler)
subscribe(ino2, "holdableButton", buttonHandler)
subscribe(ino3, "switch.on", buttonHandler)

But I can’t seem to find the secret sauce.

[bertabcd1234]

Your inputs are OK (pick one, probably pushable), and your subscriptions will be something like:

subscribe(ino, "pushed", pushedHandler)
subscribe(ino, "released", releasedHandler)
subscribe(ino, "held", heldHandler)

...and your handlers something like:

def pushedHandler(evt) {
	log.debug "Button ${evt.value} was ${evt.name}"
}

(which would log something like "Button 1 was pushed")

Also note that the stock Inovelli driver doesn't report released, but the firmware does indeed report those events, so a custom driver could make use of them.

[lairdknox]

There it is. Thank you!

It is slowly starting to make some sense.

[lairdknox]

Ok, next question. To select one of the notification colors do I send a command to the switch or do I have to select each child object?

[bertabcd1234]

The switch driver doesn't have a native way to do it, but all you'd need to do is add a custom command to modify the relevant Z-Wave parameter. For the dimmer, it's 16 and requires a somewhat complicated-for-a-human calculation (pretty easy for a computer: 4 bytes wide, one byte for each of color, level, duration, and effect), which I explained on the Inovelli forums this morning. I also have a custom driver that can do this with a custom command, but I'm not 100% ready to offer that up yet since I think I broke their child-device creation thing in the process.

So...the only way to do it with what they offer is to use their driver to create however many child devices you want with your desired notification settings. Then turn that device on to activate that notification LED. Turning it off will clear the LED (returning to the default), but the LED notification will otherwise clear when your configuration tells it to or the user clears it from the switch, etc.

[lairdknox]

But I should be able to set the virtual child device on individually, right?

[bertabcd1234]

Yeah, that's what I meant--you can turn on whatever child device, and the most recent one that you turn on will cause the LED notification be modified accordingly (turning one on doesn't turn another off--nothing really does unless you do, even the notification being cleared after the timeout or from the switch [EDIT: or at least that's my experience, but it's possible I botched something with my custom driver]).

[Terk]

Turning a second child turns off the first for me, however i use groups so i have one place to add additional switches when necessary and then they don't unless maybe you use the option to use a group device to tell if any member is off? I use my notifications to tell me if HSM is armed, mail has arrived, an outside door is open, intrusion detected, and water detected. I want them to alert in that order of precedence and once one is no longer true i want it to fall back to a lower precedence notification if necessary otherwise to the defaults for each switch. So i had to make a single Inovelli notification rule with if statements for each notification type in the order of precedence so it all works how i want now but it took a few tries at the rule to get it right.