Home Assistant release with the issue:
0.100.2 and previous
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio.
Integration:
IPMA
Description of problem:
Random crashes.
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
N/A
Traceback (if applicable):
2019-10-14 12:34:53 ERROR (MainThread) [homeassistant.components.weather] ipma: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/ipma/weather.py", line 129, in async_update
self._forecast = await self._station.forecast()
File "/usr/local/lib/python3.7/site-packages/pyipma/station.py", line 73, in forecast
_forecasts = await self.api.forecast(self.station.globalIdLocal)
File "/usr/local/lib/python3.7/site-packages/pyipma/api.py", line 86, in forecast
await self.wind_type_classe()
File "/usr/local/lib/python3.7/site-packages/pyipma/api.py", line 114, in wind_type_classe
data = await self.retrieve(url=API_WIND_TYPE)
File "/usr/local/lib/python3.7/site-packages/pyipma/api.py", line 25, in retrieve
async with self.websession.request('GET', url, **kwargs) as res:
File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__
self._resp = await self._coro
File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 504, in _request
await resp.start(conn)
File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 847, in start
message, payload = await self._protocol.read() # type: ignore # noqa
File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 591, in read
await self._waiter
concurrent.futures._base.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 292, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 446, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/ipma/weather.py", line 130, in async_update
self._description = self._forecast[0].description
File "/usr/local/lib/python3.7/site-packages/async_timeout/__init__.py", line 45, in __exit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.7/site-packages/async_timeout/__init__.py", line 92, in _do_exit
raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError
Additional information:
N/A
Hey there @dgomes, mind taking a look at this issue as its been labeled with a integration (ipma
) you are listed as a codeowner for? Thanks!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
This is not solved.
@dgomes , any light on this, please?
There is a new version of the component coming up in the next weeks, please wait :)
I'm facing the same issue on the latest version
Next release of HA will hopefully fix your issues, since the PR just got accepted
@dgomes apparently its fixed but now air pressure always reads -99hpa
(that is not related to this bug)
we have been playing catchup with IPMA :(
I just pushed an update in 0.106.1
Please check that version as soon as it's released
The component is working fine after the update to 0.106.1 but Wind Speed reads -99 km/h ()
, probably due to a problem on IPMA API. Can you confirm that @dgomes ?
The fix in 0.106.1 should have solved it
apparently it's happening again
error ?
Can't see any error on the home-assistant.log but weather is currently unavailable.
This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.
remove the integration and add it again
Worked, thanks!
Most helpful comment
The fix in 0.106.1 should have solved it