Skip to content

Commit dc01806

Browse files
amelchiofrenck
authored andcommitted
Explain workaround for limitlessled assumed_state (home-assistant#4856)
* Explain workaround for limitlessled assumed_state * ✏️ Tiny grammar change
1 parent ad10b7b commit dc01806

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed

source/_components/light.limitlessled.markdown

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,3 +90,16 @@ When starting Home Assistant, the last recorded state will be shown. This might
9090
If you control your LimitlessLED lights via the MiLight mobile application or other means while Home Assistant is running, Home Assistant can not track those changes and you may observe obsolete information.
9191

9292
This lack of synchronization is due to a LimitlessLED limitation.
93+
94+
<p class='img'>
95+
<img src='/images/screenshots/limitlessled_assumed_state.png' />
96+
</p>
97+
98+
Because LimitlessLED lights may have an obsolete state, Home Assistant shows the power switch as two buttons rather than a toggle. This ensures that the power can be set with a single click even if the assumed state is wrong. You can change to use the power toggle with [Customize](/docs/configuration/customizing-devices/):
99+
100+
```yaml
101+
homeassistant:
102+
customize_domain:
103+
light:
104+
assumed_state: false
105+
```
Loading

0 commit comments

Comments
 (0)