You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new Shelly integration does not support switches as lights and dimmers as non-dimmable lights.
It's coming for Shelly Dimmers to be used with non-dimmable bulbs, mostly because unlike Shelly 1's, they don't require the neutral line. I had issued a PR for it in the HACS package (StyraHem/ShellyForHASS#423), but since you're including Shelly as a native integration, it'd be great to see that capability included here too!
Environment
Home Assistant Core release with the issue: dev
Last working Home Assistant Core release (if known): N/A
Link to integration documentation on our website: N/A
Additional information
@balloob Given that you're rewriting the Shelly integration, would you mind including the ability to mark switches as lights and dimmable lights as non-dimmable?
I also use Shelly Dimmer 2 devices for non-dimmable lights and I am not sure whether I configured the Shelly itself correctly. Would you mind sharing your configuration with me?
I have the impression that the bulb is not fully switched on since it makes noises.
What I tried so far:
Set to 100%
"Transition Time": 0
Disable "Warm-up"
The problem
The new Shelly integration does not support switches as lights and dimmers as non-dimmable lights.
It's coming for Shelly Dimmers to be used with non-dimmable bulbs, mostly because unlike Shelly 1's, they don't require the neutral line. I had issued a PR for it in the HACS package (StyraHem/ShellyForHASS#423), but since you're including Shelly as a native integration, it'd be great to see that capability included here too!
Environment
Additional information
@balloob Given that you're rewriting the Shelly integration, would you mind including the ability to mark switches as lights and dimmable lights as non-dimmable?
See here: StyraHem/ShellyForHASS#423
Thanks
The text was updated successfully, but these errors were encountered: