Hi,
I have an inovelli blue 2n1 switch that is using the inovelli driver.
When I enable the home kit integration, the switch shows up in the "outlet" section.
Is there a way I can change it to export the device as a dimmer switch to homekit.
Yes, in the HomeKit integration app, you can enable the Show accessory classes and characteristics option, then you should see an "Export as" option under the device:
In your case, selecting Dimmer sounds like what you want.
2 Likes
Thank you! that was the trick.
I don't know why that isn't enabled by default.
Normally, it would be, but it's possible the driver declares some unusual capabilities that made the integration guess wrong.
1 Like
Ah, I wasn’t complaining that Hubitat chose the wrong device type. I recognize that may happen from time to time.
I was musing that having the “show accessory classes” switch off by default was a sub-optimal decision. If it was enabled by default, I wouldn’t have had to ask the question because it would have been obvious.
But I did t notice the “show accessory classes” nor would I have made the connection because “class” isn’t the word that I use to denote device type.
UI design is hard. Hubitat is getting better but ui design is why I left Hubitat for homey pro. The reason I am keeping the Hubitat going is because of the lack of Inovelli integration in homey pro.
I'd guess it's because most of the time, the defaults are OK, so the extra text would be clutter and possibly confusing, and the advanced option exists to enable where unusual cases exist where that didn't happen. You just happened to run into one. 
You're likely using a custom driver for this device, too, and it could be the specific mix of capabilities or specific attribute values they chose that contributed to this issue.
But it's an easy enough, documented solution if ever needed. Glad it helped in your case!
