Inovelli LZW30-SN Double tap

I've used double tap on this switch for a long time without issue. About a week ago it stopped working. The logs show like I just turned button 1 and button 2 pushed instead of double tapped. I tried pulling the gap plug for a minute. Anything else to try? If I click the doubletap from the device page, my rule fires like normal. But the physical switch is not seeing double taps. Thanks!

The fact that manually running the "double tap" command from the device detail page works isn't surprising; that just simulates an effectively virtual event, doesn't depend on the physical device at all, and with this type of device is mostly just useful for triggering things that would otherwise be triggered by the real event.

The first thing I'd do is make sure that parameter 51 (disable physical on/off delay) is set to 1 (do not disable). If it already looks correct, try changing it to 0 and then back to 1. If you're using Inovelli's custom driver, there is a preference built in for this; if you're not, the Hubitat "Basic Z-Wave Tool" driver can do it (parameter 51, size 1, value 1 ... or 0 if you need to try the other way first). The LZW31-SN also has an additional parameter to customize the delay if enabled, but I don't think that ever made its way to the LZW30-SN, so I can't think of what else this could be here.

The above is particularly likely to be the case if you recently updated the device firmware (it was added in some update and does not seem to be initialized to the default value), though since you didn't mention that, I'm assuming it's not the case. If you aren't on at least firmware 1.19, you also won't have this option, but in that case, I suppose you could try updating and see if it helps. :slight_smile:

SWEET. that was it. I upgraded the firmware about a week ago and suspected that something went awry. I had to switch to the Basic Z-Wave Tool to make the change to 51/1/1. The "correct driver" is something I always struggle with on HE. Wish the was a definitive recommended list of devices/drivers. Thanks so much for this! I'm up and running once again.

Glad it helped!

The best-match built-in driver for all "officially" compatible devices are listed in the documentation: https://docs.hubitat.com/index.php?title=List_of_Compatible_Devices

However, some devices have more features than the built-in drivers expose (e.g., the LZW30-SN can do up to 5 taps in each direction; Hubitat's driver only supports up to a double-tap, presumably because they didn't want to extend the button capabilities of the platform itself to support more or do button-number-math workarounds like other drivers have to in order to support this). In that case, you may prefer a community driver. This is just a preference, not the "correct" driver to use for everyone. :smiley:

(And sometimes there are even more options--I use neither and wrote my own because I'm picky: I want all the features, but a more Hubitat-y driver.)

1 Like

So the Inovelli drivers in HPM. Which are those. Yes, I'm confused.

The only ones I'm aware of in HPM are Inovelli's own (mine aren't there), though it's possible Bryan has some from his pre-staff days still in there, too. The author should be listed next to the name. InovelliUSA is the GitHub username for Inovelli, so these are theirs:

Inovelli Drivers (Gen 2) by Inovelli USA

HPM provides the ability for developers to provide links to docs and whatnot, though they seem to be available only after install. If @csteele thinks it's worth adding some way for users to take a look before installation (and there's an easy way to do that), maybe it's something he can consider in a future update--just an idea. :smiley:

Short Term, an Install is not a commitment. :slight_smile:

Go ahead and Install:
Screen Shot 2022-07-25 at 9.06.08 AM

then look in View Apps & Drivers:

Screen Shot 2022-07-25 at 9.06.59 AM

Only to find they don't identify documentation :smiley:

Then follow up with an Uninstall:

Screen Shot 2022-07-25 at 9.08.35 AM

Reminder, an Install simply copies the code to the hub.. it does not force it to be in use.

Anyone want to ask the Eric's (@Eric_Inovelli , @ericm ) why they don't include a doc link? I guess I just did :smiley:

1 Like

Do you mean a link here?

image

I set that all up when HPM first hit the scene and I don't know if a link was possible back then. I don't remember that being discussed. From that point I have just updated the files necessary to show what has been changed and to make it so HPM sees that there is a change so people will be notified. Haven't really messed with it other than that.

I'll have to check out what others have been doing in that regard.

1 Like