Shane Friedman

Interestingly, I still see a seg fault (and still seemingly in SDL): ``` Thread 1 "flex-launcher" received signal SIGSEGV, Segmentation fault. 0x00007ffff7cfcf5c in SDL_IBus_UpdateTextRect (rect=0x5555555f3c370), at ./src/core/linux/SDL_ibus.c:667 667 ./src/core/linux/SDL_ibus.c: Directory...

I'm having exactly the same problem! It would be great if there was a way to override the heuristics that this integration uses for determine what to expose in Home...

Thanks for responding so quickly!! So to be clear, this thing is a dimmer switch, not a light. Here's a link: https://residential.lutron.com/us/en/stand-alone-controls/smart-bulb-dimmer. I can't speak for @ajtatum, but I wish...

I'm actually using the official driver! Here's the output, it does seem to have the SwitchLevel capability: ```json { "id": "148", "name": "Lutron Aurora Controller", "label": "Second floor guest room...

Oh... huh! I just went and checked in Home Assistant, and actually there _is_ a level entity there! It was just disabled for some reason. I enabled it, I'll see...

Yeeeup, that works just fine! This at least resolves my issue; there may be another issue with the third party driver, but all that I was missing was that the...


> Are you overriding the device type, by chance? I would have expected that device to be detected as a light due to the presence of the SwitchLevel attribute, in...

It looks like it's still set up as a light; I had to override the device type to be "switch" to see the disabled level entity

Oh! This is built in to the Hubitat integration; when you submit the configuration in the UI, one of the confirmation panels asks you about whether any devices that it...