New/Current HE users here that are installing our switches. Please be aware that when you include our switches Hubitat seems to be enforcing to use their versions of the drivers which is fine for most cases but not if you are setting up 3-way. The HE versions of the drivers do not support this. You need to install our versions of the drivers to complete your 3-way setup.
This also applies to non-neutral setups. You MUST use our drivers to support this.
Would be nice if you could label the child device driver better,
name: “Switch Child Device”
name: “Inovelli Child Switch Device”
name: “Switch Level Child Device”
name: “Inovelli Child Switch Level Device”
I know how I can update the drivers both to reflect the change, but others might not. And I have seen people complain. Especially when they need to update a driver and everyone likes to use the generic name child device naming. Its minor but might be worth updating the code. IMO
Also for the Hubitat version, you still reference Smartthings within it. And unable to delete child devices without removing switch and re adding. (Please fix)
Hi @Almulder, thanks for the suggestions. I will definitely look into this going forward, but I am curious why the namespace isn’t a good enough indicator as to which driver is which. For example, the namespace is InovelliUSA so in a sense the driver is InovelliUSA:Switch Child Device. By default the drivers should look for their child device in the same namespace. So our InovelliUSA drivers will install the InovelliUSA child driver.
As for not being able to delete the child devices, I can definitely update that. It has to do with how they are created and I’m honestly not sure why Hubitat doesn’t allow you to delete them. There is a trick to be able to delete them even when they are in this state though.
The fix for deleting the child devices is in the latest drivers. The bad thing is that the child devices need to be recreated with the new driver in order to be deleted. So it will work on new devices you add, but the old child devices you will have to delete them first with the method above (which kind of defeats the purpose of the change but oh well).
Hubitat doesn’t show you the namespace in the driver dropdown, so if you have multiple manufacturers’ drivers that use the same name, it’s hard to tell when actually selecting the driver. But this isn’t really something users need to do for the Inovelli devices (they’re created automatically), so perhaps there’s another manufacturer or situation where this is needed that this user is thinking of. I’m not sure otherwise.
In any case, for Hubitat, Inovelli really doesn’t need to provide child switch or switch level drivers. Hubitat has them built into the platform. Here’s their Generic Component Dimmer driver (basically switch level; technically also includes the ChangeLevel capability–new to Hubitat compared to ST–but I can think of workarounds you can use to not really care about those functions), which is built into the platform:
There is a similar driver for generic component switches. It’s actually pretty similar to what Inovelli does with their own child drivers aside from passing the device vs. device DNI up to the parent. Here’s an example of how a parent device can handle this child (this is a demo only and not included in the platform, not that it would do much if it were):
So…with a few minor changes, you could probably spare Hubitat users from even needing to install the child drivers, or at least the switch ones (again, switch level is a bit more, but you could just document that startLevelChange/stopLevelChange either don’t work or go immediatlely to 100 or 0 or something to that effect).