jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Explain workaround for limitlessled assumed_state (#4856)

Browse source 
* Explain workaround for limitlessled assumed_state

* ✏️ Tiny grammar change
This commit is contained in:
Anders Melchiorsen 2018-03-14 21:39:30 +01:00 • committed by Franck Nijhof
parent ad10b7ba14
commit dc018062c0
2 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
source/_components/light.limitlessled.markdown
View file

@ -90,3 +90,16 @@ When starting Home Assistant, the last recorded state will be shown. This might
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.
This lack of synchronization is due to a LimitlessLED limitation.
<p class='img'>
<img src='/images/screenshots/limitlessled_assumed_state.png' />
</p>
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/):
```yaml
homeassistant:
customize_domain:
light:
assumed_state: false
```

BIN
source/images/screenshots/limitlessled_assumed_state.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 8.2 KiB