(EDGE Driver-Mc): Z-Wave Switch and Child Mc. Added Inovelli Gen1 Dimmers (NZW31) and Gen1 Switch (NZW30)

Devices & Integrations Community Created Device Types
,
1

New Edge Driver for Inovelli Gen1 Dimmers (NZW31)

At the request of @milandjurovic71, I have added the 5 Inovelli Gen1 dimmers, which are in the DTH inovelli-dimmer-nzw31-w-scene.groovy, since so far inovelli has only converted some newer models to edge driver

     fingerprint mfr: "015D", prod: "B111", model: "251C", deviceJoinName: "Inovelli Dimmer"
     fingerprint mfr: "051D", prod: "B111", model: "251C", deviceJoinName: "Inovelli Dimmer"
     fingerprint mfr: "015D", prod: "1F00", model: "1F00", deviceJoinName: "Inovelli Dimmer"
     fingerprint mfr: "0312", prod: "1F00", model: "1F00", deviceJoinName: "Inovelli Dimmer"
     fingerprint mfr: "0312", prod: "1F02", model: "1F02", deviceJoinName: "Inovelli Dimmer" // Toggle version NZW31T
  • I have added 2 buttons to receive and emit the events of: push, 2x, 3x,4x,5x, held and hold of each dimmer button and to be able to execute scenes or automations
  • Added 4 fingerprints of inovelli DTH Inovelli Dimmer NZW31.groovy without scenes
        fingerprint mfr: "0312", prod: "0118", model: "1E1C", deviceJoinName: "Inovelli Dimmer"
        fingerprint mfr: "015D", prod: "0118", model: "1E1C", deviceJoinName: "Inovelli Dimmer"
        fingerprint mfr: "015D", prod: "1F01", model: "1F01", deviceJoinName: "Inovelli Dimmer"
        fingerprint mfr: "0312", prod: "1F01", model: "1F01", deviceJoinName: "Inovelli Dimmer"
  • Added these settings parameters in preferences:
  INOVELLI_NZW31 = {
    MATCHING_MATRIX = {
      mfrs = {0x0312, 0x015D, 0x051D},
      product_types = {0x1F00, 0x01F01, 0x1F02, 0xB111, 0x0118},
      product_ids = {0x1F00, 0x1F01, 0x1F02, 0x251C, 0x1E1C}
    },
    PARAMETERS = {
      dimmingStep = {parameter_number = 1, size = 1},
      minimumLevel = {parameter_number = 2, size = 1},
      ledIndicator = {parameter_number = 3, size = 1},
      invert = {parameter_number = 4, size = 1},
      autoOff = {parameter_number = 5, size = 2},
      defaultLocal = {parameter_number = 8, size = 1},
      defaultZWave = {parameter_number = 9, size = 1},
    }
  },

image
image972×2486 180 KB

  • Added to this date version of edge Driver Z-Wave Switch and Child Mc 
┌─────────────┬──────────────────────────────────────┐
│ Name        │Z-Wave Switch and Child Mc                     │
└─────────────┴──────────────────────────────────────┘

Link to the shared channel

SmartThings. Add a little smartness to your things

Link to devices supported Z-Wave Switch and Child Mc

4 Likes
2

Very nice! I’m sure these will be popular. :sunglasses:

2 Likes
3

@DiegoAntonino I think that your Inovelli nzw30 device is supported too. Would you be kind to try Mariano’s driver, and report if it’s working

1 Like
4

Hi @Mariano_Colmenarejo and @milandjurovic71, it does work Inovelli nzw30 as well. :slight_smile:

I dont see the “buttons” infomration though (perhaps it’s not suported).

inovelli NZW30
inovelli NZW301066×1407 85.5 KB

Anyways, thanks a lot for this guys!

5

It seems to me that it has not been paired with the Z-Wave Switch Mc driver or with the profile that I made.

Could you please send the fingerprint?

6

New Edge Driver for Inovelli Gen1 Switch (NZW30)

At the request of @DiegoAntonino I have added the 4 Inovelli Gen1 switches, which are in the DTH Inovelli Switch NZW30 w/Scene.groovy , since so far inovelli has only converted some newer models to edge driver

	fingerprint mfr: "015D", prod: "B111", model: "1E1C", deviceJoinName: "Inovelli Switch"
    fingerprint mfr: "015D", prod: "1E00", model: "1E00", deviceJoinName: "Inovelli Switch"
    fingerprint mfr: "0312", prod: "1E00", model: "1E00", deviceJoinName: "Inovelli Switch"
    fingerprint mfr: "0312", prod: "1E02", model: "1E02", deviceJoinName: "Inovelli Switch" // Toggle version NZW30T
  • I have added 2 buttons to receive and emit the events of: push, 2x, 3x,4x,5x, held and hold of each switch button and to be able to execute scenes or automations
  • Added 4 fingerprints of inovelli DTH Inovelli Switch NZW30.groovy without scenes
	    fingerprint mfr: "0312", prod: "0117", model: "1E1C", deviceJoinName: "Inovelli Switch"
        fingerprint mfr: "015D", prod: "0117", model: "1E1C", deviceJoinName: "Inovelli Switch"
        fingerprint mfr: "015D", prod: "1E01", model: "1E01", deviceJoinName: "Inovelli Switch"
        fingerprint mfr: "0312", prod: "1E01", model: "1E01", deviceJoinName: "Inovelli Switch"
  • Added these settings parameters in preferences:
  INOVELLI_NZW30 = {
    MATCHING_MATRIX = {
      mfrs = {0x0312, 0x015D},
      product_types = {0x1E00, 0x1E01, 0x1E02, 0xB111, 0x0117},
      product_ids = {0x1E00, 0x1E01, 0x1E02, 0x1E1C}
    },
    PARAMETERS = {
      ledIndicator = {parameter_number = 3, size = 1},
      invert = {parameter_number = 4, size = 1},
      autoOff = {parameter_number = 5, size = 2},
    }
  },
  • Added to this date version of edge Driver Z-Wave Switch Mc 
┌─────────────┬──────────────────────────────────────┐
│ Name        │ Z-Wave Switch Mc                     │
│ Version     │2022-03-04T15:06:42.406131            │
└─────────────┴──────────────────────────────────────┘
5 Likes
7

It works as a charm @Mariano_Colmenarejo ! Thanks a lot!

4 Likes
8

Awesome guys thank you so much @Mariano_Colmenarejo for creating these and @milandjurovic71 and @DiegoAntonino for testing it out!

Really a big help for the community.

@erocm1231 I’m sure is super appreciative to have this taken off his plate.

3 Likes
9

Thank you for your words. @Eric_Inovelli

What I miss about the part of the classic manufacturers, such as Inovelli, Fibaro… that after 6 months of the Edge Beta phase, have not been more clear in communicating the policy to follow. At least I haven’t seen it on the forum.

Customers expect from these serious manufacturers a clearer communication of the future, not only for new products, but also for those that are no longer manufactured and that work very well and continue to retain loyalty.

I think it’s not that hard to say to customers, don’t worry about your devices that you are already using, we will convert the DTH controllers so that you can continue to use them and we will also add the new and better devices.

Due to the complexity of the conversion process, I think there is no excuse for not doing it and I think many users will appreciate it.

4 Likes
10

I would respectfully disagree.

Edge is still in a developers’ beta phase. Lots of changes, lots of features not yet completed, lots of glitches. (For example, no word yet on how multi gang devices will work with voice assistants.)

Once the developers’ beta phase is completed and SmartThings is ready for the consumer beta phase, that’s when I would expect the developers to publish instructions. Before that, they would just end up spending a lot of time and energy on things which hopefully will be smoothed out before it’s officially open to the general public.

JMO, of course. :sunglasses:

2 Likes
11

Do we know any edge drivers that allow the black series to have child devices for remote control, local control and led colors?

12

I think it is not superfluous to write a post in a forum like this saying: Don’t worry, we will do our best to get all our devices to have their edge driver before groovy disappears.

In August 2021 Zooz did it in a post on TheSmartestHouse and inovelli said that what he had seen of edge with the red series seemed impressive to him, that he would like to be able to say something more and they would do their best to implement it as soon as possible.
In November he opened a beta channel with 2 drivers, red series switch and dimmer and we are in April with nothing new. I guess they will have things done before the user beta starts!
If I were a client, I would miss a little more information, which may be on their website, I don’t know, but I was referring to this forum in which they usually participate.

I am not telling you anything about Fibaro, which in Europe has many clients and I have only seen him open his mouth to tell a user that he cannot help him because he does not know how the smartthings hub works to match his Fibaro devices, that if he used the fibaro hub yes could help you, hahahaha what a help!!!

I was just thinking out loud what I think the users deserve, since the users are testing and debugging all the edge drivers in the developers beta phase. Are many users who make their devices and time available to everyone else.

That manufacturers communicate with smartthings and plan their future is logical, but these forums must take care of the link with users as well

3 Likes
14

Hey @Mariano_Colmenarejo - I appreciate the feedback regarding being more open around Edge drivers. You’re right, I probably could’ve been more clear around what to expect and give assurance that we will support all of our products, even the discontinued ones.

What I personally struggle with (and the point of me writing this is to provide some context - I am listening to feedback - I’m just caught in a rock and a hard place sometimes) is what can and cannot be said due to NDA’s that are signed between us and SmartThings.

It’s a bit different when you’re a volunteer coder to create these drivers for the community and as I mentioned, we’re extremely grateful for people like you. But when you’re a manufacturer, there’s a lot more that we know then the average customer due to many privy conversations. The one you referenced is a perfect example. It was a conference call between @erocm1231 (our CTO), myself and four of the lead engineers of SmartThings, plus one of the guys from the Edge program.

I specifically asked them if I could share anything with our community. I’m not sure if you hang out in our community, but I’m very open with everyone about the good and the bad of our company and I wanted to talk about Edge bc we do get a lot of customers who write in and are freaking out (rightfully so) about whether or not their products they purchased from us will be supported on Edge.

I was told I was not able to say anything at all until everything is official. We still have no clue when the official date is, so I’m at a standstill. Do I break the NDA and let people know everything that will be available via edge and risk losing any sort of partnership with SmartThings? Or do I just kind of sit on the sidelines and wait until I’m told it’s ok?

The best I can do is give assurance that we will support our products (which I did) and follow through on that request when things are official.

The other part that is challenging - again, I know it’s not your problem, but I’m trying to paint a picture from our side - is exactly what @JDRoberts mentioned… Bandwidth…

There are four of us that work at Inovelli. We’re not some huge company filled with engineers that have all the time in the world to mess around with beta projects.

Eric M is the only one on our team that knows how to write any of this. He’s been on the phones constantly with SmartThings trying to figure out how to get the advanced features working (notifications, scene control, etc). Some of the features are not even possible on Edge (notifications) but he’s working with them to make it possible.

So, we get these questions daily - when will drivers be released? What products are you supporting? What features are available?

And I emphasize with you bc I’m a SmartThings user too and I want to know these things, but I don’t have the answers. And somehow this gets taken out on us as the manufacturer bc we’re not transparent enough or perceived as not trying hard enough, but the truth is that we are in a very similar boat. However, our boat has a target on it and if we say something we shouldn’t or promise something that doesn’t come to fruition, it has serious repercussions that the volunteer coder does not have.

All that to say - I genuinely meant it when I said thank you. People like you who step up and help out take some of that risk off our plate and we do (and the community does as well) appreciate it.

Edit: just read your deleted comment and I genuinely hope you don’t feel that way.

6 Likes
15

These are the things that users can think when we do not have information from reliable sources.

I understand your business commitments not to give certain information, but I don’t share that smartthings secrecy that you refer to about a project that is exciting many people and that without being an expert, just a user, I also like it.

Surely your comments today have reassured many people and it is appreciated

Regards @Eric_Inovelli

5 Likes
16

Understood, whatever we can do behind the scenes, please feel free to reach out to me. We really want to help in anyway we can.

I know Eric would love to be in touch with anyone that is willing to help fast track some of these projects.

Thanks again for your help and I will definitely aim to be better at communicating!

2 Likes
17

@erocm1231 when you know more about the capabilities and what’s possible, can you answer this?

18

I believe the local control / remote control will have to be implemented as a custom capability. The current Edge driver that we provide does allow you to change the LED color, but it does not yet support notifications (which don’t exist on the black series anyway).

19

Thank you for your response! I know some people are doing great work with edge drivers and creating virtual devices, like:

Can we leverage something like this for the remote/local control?

20

Dang, I wish I would have found this thread before I switched to Edge drivers. I definitely need that child device for notifications. I guess I’ll switch back to the DTH.

21

I found the new edge drivers for the red series dimmer. They work great.