(I have done this on a few Zooz devices--easy if you have an external Z-Wave stick, a bit of a pain if you don't use one as your primary Z-Wave radio.)
Inovelli has also hinted that they're partnering with a "major company" for a test of Z-Wave OTA updates. Coincidentally, SmartThings has also announces they're testing Z-Wave OTA updates. My guess is that these coincidences are not unrelated. (I would assume that would be simply another method, not the only method.)
You will need a Z Stick and a windows computer that can send OTA files to the device. You join the Z Stick to the Hubitat hub as a secondary controller and with the Windows software you use you send the OTA file to each device.
If we see this is necessary we will have appropriate instructions on the OTA file location.
Being able to add it as a secondary controller makes me feel a lot better. I was afraid that I would have had to remove and rejoin all my devices. This would be much easier.
I use Homeseer Zwave OTA updater to do this. I know there is other software out there is free which I will get a list of at some point to post on the Inovelli Community Forum.
I'm not sure I understand. Rule Machine isn't used to create scenes; it can be used to respond to Z-Wave Central Scene events (typically parsed as button events in the Hubitat and ST world). I'm guessing that's what you meant? So like an easy way to control smart lights (or anything else, I guess) using a scene-capable dimmer/switch?
FWIW, I also have [RELEASE] Dimmer Button Controller (configure Pico to emulate Hue Dimmer or any button device to easily control lights), which I wrote for a similar purpose. Basically, similar in concept to Button Controller or ABC, but different in that its intended actions are lighting only. (It gets tiring to constantly select the same devices in each action of a rule...). It's not Inovelli-specific and actually might be a bit confusing to use with Inovelli devices--it's meant for ones like a Pico remote or Hue-Dimmer-on-Hubitat that do not natively support multi-taps but where you still want the mulitple-pushes-cycle-different-scenes actions Ć la Hue-Dimmer-on-Hue. (So ignore the "Press 1," "Press 2," etc. and just use "Press 1," then use the right button events and button numbers from the switch/dimmer.)
Any of the above apps would be a lot easier to use with Inovelli's stock driver if their button events were named more logically on Hubitat (I can sort of understand why they did this on ST, which doesn't support "released," and the Hubitat driver is just a quick port of that), so I guess one way a dedicated Inovelli app could help is by masking the button events/numbers from the user and just letting them choose based on what they do to the switch and let the driver and app interact with each other in ways they already understand and the user doesn't need to. That should be quite helpful for some people.
That is not my driver. If you are using mine, child devices are created automatically if the drivers are available (you'll see an error or warning in the logs if not), which I think should really be the same for Inovelli's too. In any case, you can't manually create devices and then make them child devices of a different device, and if you're trying to use Z-Wave association from Inovelli's driver, that is a different thing and only works with two Z-Wave devices.
Testing this driver out, I think it's the best solution for the notifications turning off when manipulating the switch. Being able to change the default LED color in RM is great!
With that said, all the example rules I've seen show setDefaultLED(red, 10) as the example. For me using "red" is not working, I have to use the numeric 1 for red, 170 for blue, etc... Is this a change in the driver since inception?
Also, is there a color chart in this 0-255 range? I've just been banging in random numbers until I find the color I'm looking for lol
EDIT: When I change the device type, the old Notification 1 child device stays and can't be deleted.
setDefaultLED doesn't exist in this driver. There are separate commands for color and level, plus (optional) child devices. Are you sure you aren't using my older version? I don't use that one anymore but would have to check if you are and intend to be using it.
Definitely using the new one, I must just be looking at example rules from the old one. I'm using setDefaultLEDColor to change the colors and finally seeing the "notification" results I've been looking for since installing these switches.
Does this version support the named colors or just the 0-255 scale?
(I would assume that would be simply another method, not the only method.)
