* Prevent turning on tellduslive lights with 0 brightness
It was possible for the light compontent to get in a state where the last_brightness was set to zero, and when turning on (by calling turn_on) it would call the TellStick with 0 dim level, ergo not turning on the light.
With this, it will fall back on a 75% dim level if the level is set to zero.
* Wrap long log line over two lines
And using a more proper way of formatting the message
* Fallback to 100% instead of 75%
* Deprecate update_interval and replace with scan_interval
* Update tests
* Fix Darksky tests
* Fix Darksky tests correctly
This reverts commit a73384a223ba8a93c682042d9351cd5a7a399183.
* Provide the default for the non deprecated option
* Don't override default schema for sensors
* use async_call_later for update
* no need to timeout
* fixes
* move init tasks to hass.loop
* version bump of tellduslive
* fixes for @MartinHjelmare
* fixes task cancel
* don't return from new client
* fix for #19954, discovered tellsticks shows up to be configured
* fix for #19954, authentication issues
* updated tests
* move I/O to executer thread pool
* Apply suggestions from code review
Co-Authored-By: fredrike <fredrik.e@gmail.com>
* add hub- and device-info
* attempt to make I/O outside event loop
* add_executer_job
* coroutines
* async_get_hubs
Co-Authored-By: fredrike <fredrik.e@gmail.com>
* asyncio fixes
* do device_info IO when device is discovered
* it's called async_add_executor_job
* nicer unique_id
* add comment
* it's called `async_add_executor_job`
* hub always contains 'name'
* await each new device
* add comment to why gather is bad
* move component to a package
* move TelldusLiveEntry to separate file
* refactor
* move entities from a shared container
* using the dispatch helper instead for communication between component and platforms
* updated covereagerc and codeowners
* suggestions from MartinHjelmare
* don't make update async
* "Strip is good!"