Shelly has a range of DIN-rail mounted z-wave switches (fits inside your electrical "cabinet" aka "breaker box" in US), which allows you to control stuff "at the source". They are probably based on Shelly's WiFi-versions (same device, different connectivity protocol). And no, I do not want the WiFi versions.
DIN rail stuff is not a good solution for single lighting and single plug control, but it really is the best for controlling "bigger stuff" (since you don't need to put a switch somewhere on the line and can control the whole feed from the breaker box).
I have a friend who got several of these (https://www.shelly.com/en-se/products/product-overview/shelly-qubino-wave-pro-3) and they paired "automagically" with his z-wave hub (seems the Qubinos come with their own built-in z-wave scheme that the hub can download from device during setup, getting everything working perfectly).
However, while a lot of Shelly/Qubino stuff is on the Hubitat compatibility list, these are not. The 3-channel device is fairly new (I think), but the 1- and 2-channel versions have been around for a while. And I can't remember anything about Hubitat downloading drivers from z-wave device firmware and setting up drivers/control "automagically"...(?)
But the question is; does anyone happen to know if the Shelly Qubino Wave Pro-series of devices work with Hubitat?
In addition to the 1/2/3-channel switches there is DIN-mountable shutter/garage door controller and DIN-mountable dimmer is in the works (which would allow you to dim "a whole electrical feed" at once).
If you need/want DIN-mounted z-wave devices here in the EU, Shelly Qubino is currently the best option, and getting better. It would be really nice to get them on the compatibility list... (and be sure that they will work).
How do I get it to create child devices for the channels?
The Shelly Qubino Wave i4 is a 4-channel z-wave mains-connected switch input/scene controller. It sends tap, double-tap and hold commands (or alternatively on-off button state/change) to the hub.
The device connected and installed to Hubitat just fine using the normal pairing procedure, but the controls/handles for the 4 different "pushbuttons" don't show up. Using the "Generic Z-Wave Button Controller" as "Type" (it installed itself as "Device") there is just one set of "Double Tap", "Hold", "Push" and "Release" commands showing up in Hubitat's device interface.
I couldn't find info on how to "get my z-wave device to make children" , so any info on "populating" the controller would be appreciated.
I expected some hands-on handling from choosing Hubitat, but this is a device that just about every "smart home"-retailer is selling over here, from one of the bigger manufacturers, and the normal connection procedure is simply using the "smart way", which means either scanning a QR-code or just connecting it (and let it talk things through with the hub). So being stumped getting this device to work feels both ridiculous and irritating.
But that might be my fault, for just not knowing how to go about it. So far I have gotten most things to work, but they have mostly been simple zigbee switches and the like, using generic drivers. So if there is some other procedure or some trick I have to use, please let me know.
I don't think it is relevant to the problem, but here is a link to the manual (for the Shelly Qubino Wave i4, pdf-version):
Continuing my testing (trial and error is my preferred way of learning stuff, suffer from serious RTFM-syndrome...) I noticed that everything does seem to work, it was just too simple for me to understand. My bad (which feels good, I'd rather blame my stupidity/ignorance than Hubitat ).
When I connected actual physical buttons to the device and press/tap/hold the buttons it is read by the driver, and reported in the Hubitat device interface under "Current States".
There are four "states" listed: "switch", "pushed", "held" and "released", and when I push, hold and release the numerical values changes according to the channel (1, 2, 3 or 4). The "switch" value is always "off" (but that might be related to configuring the device to work with an on/off-position button (instead of a push rocker button, that I have).
And I can (of course) use these states as triggers for all kinds of actions, which was what I was trying to do.
Sorry for wasting bandwidth, everything actually works perfectly, the problem was me. And I just ordered three more of Shelly Qubino button controllers.
I still have to figure out what happens if I input numbers into the four "Command"-boxes, but I'll save that for a rainy day...
Once the device is paired, it should automatically create the child devices. check to see if there is an arrow next to the device on the DEVICES page and click that, it should expand everything below that.
I might be blind (or dumb), but I can't find a way to get to separate child devices, and the reason is probably that they don't exist.
The problem was that the driver logic was different from what I expected. I expected a control system based on the (four) buttons, but the driver actually reports "states", with the button (number) that set that state only as a parameter (of the last state change). So it is "states with buttons", not "buttons with states" .
Once I figured that out (using some basic trial and error) I got everything to work just fine (also with rules). It still seem counter-intuitive to me, because "the button is the thing you press and then something happens". But I assume there is some solid logic behind having a system based on "something happened, which button was it?"...
... which, when you say it out loud and give it a thought, is how the actual control of smart home stuff is supposed to work...
Sorry but there is just way too many words up there for me to read all that, so I may have missed something.
Sounds like two different types of devices? Some switches and then a button device?
A multi channel switch should have child devices so you can control each switch. A button device will not usually have child devices, multiple button numbers can all post to the same parent device and there is nothing to control, only receiving events.
For the multi channel switches, what driver are they set to?
Try: Generic Z-Wave Plus MultiSwitch
After switching, turn on debug logging, open a logs tab and then press the configure command on the device page.
, so any info on "populating" the controller would be appreciated.
).
