As documented in the OWM API (https://openweathermap.org/api/one-call-api), rain and snow are reported on a 1h basis:
current.rain
current.rain.1h (where available) Rain volume for last hour, mm
current.snow
current.snow.1h (where available) Snow volume for last hour, mm
* add reload service
* test for reload service
* missing file
* Revert "missing file"
This reverts commit 24391fe3b9.
* Revert "test for reload service"
This reverts commit 5bda48d070.
* Add Plex service to refresh a library
* Clean up rebase leftovers
* Re-run black
* Fix docstring
Co-authored-by: Charles Garwood <cgarwood@newdealmultimedia.com>
Co-authored-by: Charles Garwood <cgarwood@newdealmultimedia.com>
* Rename ipaddr to ip_addr
* Move custom services to entity services
* Remove platform data
* Change service setup to callback
* Rename ip_addr to host
* Use _host inside class
* Provide a logbook option entity_matches_only to optimize for single entity id lookup
When entity_matches_only is provided, contexts and events that do not
contain the entity_id are not included in the logbook response.
* Update homeassistant/components/logbook/__init__.py
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* api only takes a single entity
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* Store printer instances in hass.data
* Add SyncThru device registry support
* Use config entry id as hass.data key
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
* Use printer hostname as device registry name
* Handle non-syncthru device more gracefully on entry setup
* Use device identifiers rather than connections to link entities with devices
Co-authored-by: Paulus Schoutsen <paulus@home-assistant.io>
Prior 0.113 all lights and switches were reported as dimmable devices and this was fixed by #37978.
However, under some circumstances Alexa will not smoothly transition from those broken devices to the new ones as it cache the list of entities.
It is imperative to have Alexa rediscover all devices and then remove the now non-responding duplicates using the Alexa phone App. This can take quite a while if you have lots of devices.
An alternative would be to log to the Alexa web site and remove all the lights instead and then re-discover them all.
If you have multiple echo devices on your network, it is possible that the entries would continue to show as duplicates. This is due to an individual echo devices caching the old list and re-using it.
The only known solution for this is to remove your echo devices from your Amazon account and re-add them.
After that, have Alexa rediscover all your devices.
This is a one-off requirement.
Fixes#39503
It is no longer necessary to provide a list of entities to monitor
to the template platforms.
The template is now re-evaluated whenever
a referenced entity changes state, and new entities are automaticlly
discovered.
Automatic analysis can now determine the entities for all templates
without the need for manual setup.
* Start moving stuff to iOS
* Load config on to hass.data
* Remove un used logging
* Switch to Rest API
* Add schema
* Return whole config in new view and leave old 100 % the same
* Update doc strings
* MartinHjelmare feedback
* Move register view to async_setup_entry
jjlawren
Maciej Bieniek
Hendrik Schröter
J. Nick Koston
HomeAssistant Azure
Tomasz
Daniel Hjelseth Høyer
springstan
Charles Garwood
Xiaonan Shen
Ziv
Olivér Falvai
Michael Thingnes
Joakim Plate
Raman Gupta
Ville Skyttä
Paulus Schoutsen
Phil Bruckner
cgtobi
Erik Montnemery
Paolo Antinori
Simone Chemelli
Finbarr Brady
Chris Talkington
Bram Kragten
Arda ŞEREMET
Andrew Marks
On Freund
Jean-Yves Avenard
rajlaud
Tom Brien
SNoof85
Marvin Wichmann
jdelaney72