I love the flexibility of LimitlessLED, but the way HASS handles the status of bulbs is a bit annoying:
- Bulbs are turned off every time HASS is restarted
- HASS assumes bulbs are all of the correct status at all times
The consequences of this are that the whole house can do dark when you restart HASS, and bulbs can be in a different state to that of HASS, especially if they’re switched off while a change is made in HASS.
I agree that some people like the current system. But I would like to suggest a different approach.
In your configuration.yaml
, you have a new optional property called refresh_interval
that can either reside under platform
(universal across all bulbs) or under individual bridges. For example:
- platform: limitlessled
refresh_interval: 600
bridges:
- host: 192.168.1.10
groups:
- number: 1
name: Bedroom lamp
type: bridge-led
- number: 1
name: Bedroom ceiling
type: rgbww
- host: 192.168.1.11
refresh_interval: 15
groups:
- number: 1
name: Study ceiling
type: rgbww
- number: 2
name: Guest ceiling
type: rgbww
In this example, HASS will by default send bridges the status of all bulbs every 10 minutes, but every 15 seconds to the bridge at 192.168.1.11.