AEMET OpenData doesn't clarify if the hourly data timestamp is UTC or not, but
after correctly formatting the town timestamp in ISO format, it is clear that
the timestamp is provided as UTC value.
Therefore, the only values not provided as UTC are the ones related to the
specific daily and hourly forecast values.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* aemet: catch TypeError exceptions
format_float() and format_int() should also catch possible TypeError
exceptions.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* aemet: correctly parse temperatures with a value of 0
Right now, when a temperature with a value of 0 is provided by the API, the if
condition isn't satisfied, return None instead of 0.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* aemet: group format int/float exceptions
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* A platform is not a component
* Fix dynalite
* SUPPORTED_PLATFORMS --> PLATFORMS
* In tests
* In tests 2
* Fix SmartThings
* Fix ZHA test
* Fix Z-Wave
* Revert Z-Wave
* Use PLATFORMS const in ambient_station
* Fix ihc comment