[RELEASE] Inovelli Device Drivers

Thanks a bunch! The 8x taps got the feature enabled.

1 Like

So it looks like Hubitat doesn't yet support the "protection" command class which is what the driver uses to enable / disable the relay. So it looks like the 8x tap is how to do it for the time being.

As for the 2-Channel drivers, I have updated them so that they use parent / child relationship. I'll link to the required child device handler in the first post.

1 Like

Thanks for these! I just got the two-channel indoor plug (NZW37) with scene support and have two questions about the drivers:

  1. The only one I see on GitHub doesn't appear to support scenes (it does implement PushableButton but nothing else is handled as far as I can see). Is this for the older version without scenes or am I missing something?

  2. Is there a way with this driver to make each outlet separately controllable via, for example, automations or voice control? I'm thinking of the Hampton Bay Fan Controller ZigBee module, which has the option of enabling two "child" devices that show up under the "parent"/main device in the IDE but also expose themselves as full-fledged devices to apps and whatnot. Maybe my question is more about how multichannel Z-Wave devices work on Hubitat in general (this is my first), but I'd like to think there's something cleaner than ST where the last time I used it I had to create virtual devices and "sync" them via a custom app (yours, if I'm not mistaken) with their corresponding channel on the parent. The way this ZigBee device is handled looks great to me.

Thanks for any help!

Hi there. Let me try to answer your questions:

  1. It looks like the scene support may not be in the handler that is on github right now. I'll have to fix that.

  2. The handler should create child devices for the individual channels. They should automatically be created, but if they aren't for some reason, you might need to click the preferences save button:

Oh, and you need to have the child device handler installed:

I have updated the driver for the NZW37 for scene support. It supports 1 scene by pressing the button 4x. It is interpreted in Hubitat as button 1 pushed.

2 Likes

Just wanted to mention some driver updates that I just posted to Github. Because of firmware updates by the Hubitat team, the NZW30/S & NZW31/S now support all of their features including Local Protection from the driver preferences and direct Z-Wave association support using the Z-Wave association tool (Hubitat/Apps/z-waveat at master · InovelliUSA/Hubitat · GitHub).

Thanks to @mike.maxwell and the Hubitat team for working on those Z-Wave command classes!

5 Likes

I hope hubitat will get git repo integration working soon just for this reason!

So I have to update my DH ?

Yep, just update the code. Hopefully some way to easily keep code up to date will come down the road.

FWIW, I had to click 'save' under Features as @ericm suggested, but it otherwise worked right away!

1 Like

Thank you BIGTIME @ericm for hooking us up on the Inovelli devices...HUUUUGE help!
The steps that worked for me for my Inovelli ShowHome ZW37 are like this:

  1. Add the device drivers for the parent and child as mentioned earlier in this thread.
  2. Put the HE in 'Z-Wave Exclude' Mode via Settings, Z-Wave Information, 'Z-Wave Exclude' Mode and then click discover devices.
  3. Press On/Off on the device 5+ times quickly. DONE!!
    The Parent and 2 Child Switches are discovered and displayed in your device list.
    GOOD STUFF!
1 Like

Couple things.

  1. My NZW30 switch found and identified properly

  2. My NZW31 dimmers identified as "device" (obviously not problem changing the DH but just an FYI)

  3. Can someone explain how the child devices of the 31 work?

  4. And is there someplace that describes all the options on the 31 DH? There are some in there I have no idea what they are for.

Thanks.

Hi there, can you post a screen shot of the inclusters for the nzw31?

For the child devices, they are to allow you to change configuration options for the switch with basically any app that can control a dimmer or switch. For example, if you want to have the default level for the switch be 20% after 8pm, you can use rule machine to change the level of the "Default Level" child device to 20% at 8pm. This was created as a workaround for not being able to change device preferences from apps. It was created for SmartThings and ported over to Hubitat, but to be honest, I haven't tested them on Hubitat. They should work though.

As for config options, which ones are you wondering about?

image

Default Local Level (On/Off)
Default Z-Wave Level (On/Off)

ASSUMING the following are all for Association groups?
Send Command on Local Action (On/Off)
send command on 3 way action (on/Off)
Send command on zwave action (on/Off)
send command on auto off timer (on/Off)

It's just the way the options around grouped in the HE page...it's not very clear sometimes.

Also it seems as if there is a default ramp in the switch over a few seconds. Any way to change that?

Otherwise...I'll admit...I just dumped a bunch of GE/Jasco switches and just put in about a dozen Inovelli's....I like them that much. VERY fast and easy to use.

Since we are on the topic...the ONLY GE's I have left are the models with the motion sensor built in....so...if you were looking for more product ideas. PLEASE! :smiley:

Ok, so default local level is the level that the switch turns to when you turn it on at the wall. By default, it goes to the previous level it was on before being turned off. The default config value for that is 0 (0=previous level). If you want the switch to always come on at say 10% when controlled at the wall, then you set this config value to 10. Maybe you don't want the light to come on at a blinding level in the middle of the night when you are going to the bathroom for example.

The Default Z-Wave level is the same concept, except this is for when the on command is sent to the switch via z-wave. What level do you want it to go to when telling the switch "turn on".

As for the other settings you mention, yes, they are association related. You get to choose which actions send commands to the associated devices. For example, if you want a particular switch to turn off 1 hour after it is turned on you set the auto-off config to 60. You have a couple other switches associated with that switch, but you don't want those switches to turn off after 60 seconds so you turn off the option that says "send command on auto off timer".

So you really just get to customize things how you want them to work.

Thank you very much!

Don't forget about adding those motion sensors :wink:

Awesome support..which is why I'm swapping out all my switches with Inovelli!

Any chance of a Black Friday sale?

J

1 Like

Oh yeah, sorry, forgot to comment on that. That is actually a product that was recently brought up among the team. It is on our radar, but no plans to make something like it at this time.

@GatVlieg I don't think we have one planned, but I will throw it out to our marketing team.

1 Like

I have a few questions.

  • If I want to adjust the default on level during certain times I would need to do so using the 'child device' ? That essentially creates a virtual version (where that option can be controlled) of the actual dimmer switch ? Am I understanding that correctly?

  • Any idea when the paddle switches will be back in stock? Had to order another brand this week. I still need like 20 more switches on top of the 14 I have now.

  • I have a nightmare of a basement with 5 switches all controlling the same 4 lights in the common area/hallway. Can the on/off work with that many dumb switches as long as they're 3way and not 4way or is the limit 3?

Let me try to answer:

  • You are correct. That is the purpose of the child devices is to automate your device settings with other apps such as Rule Machine. I have the default local level setup like this: Rule Machine sets the child device to 99% during the day, 50% in the evening, and 10% after 10PM. This way, when someone turns on a light in the middle of the night it doesn't blind them but goes to 10%.

  • This is a tough one to answer. We are in the process of switching to a much better manufacturer and hope to have our devices in stock at the beginning at the next year. I am truly sorry about that and wish it could be different, but we are working as hard as possible to get our devices out to customers.

  • Currently the limit is 4-way (if the line and load are in the same box), or 3-way if they are in different boxes. We do support setting up direct associations between switches that can accommodate more switches, but then the extra switches would be Inovelli switches and not dumb switches.

1 Like

Makes sense now for the child device. Guess I need to install that now. No biggie on the out of stock issue. I most likely won't buy anymore until after the holidays anyway.

What do you mean by the limit being 4-way? I'm under the impression that tandard 4-way wiring supports many more switches than 3 as long as there is a 3 way at the beginning and end of however many 4-ways in between. Or do you mean the inovelli only supports two dumb switches at a time ? I misspoke before. I have 4 switches controlling 3 lights. I'm doubtful that all the lights come down into the same box though. Haven't bothered opening them yet since I'm still buyign for upstairs atm