Because you created sensors with these settings, and for some reason look for data in the weather object.
All are work correctly.
This component can be used in two different ways: as a weather provider for any given coordinates and as a set of sensors for current coordinates of a house.
In latest HA 2021.2.3 Gismeteo integration went unavailable. Running core venv install, checked in HACS and configuration.yaml, reinstalled via HACS- nothing. Also no entries in logs about it
Anyone else? Some breaking change?
Best, JR
PS Saw that there is a issue filed on Github so nothing wrong at our side
It’s was not a this component bug – but Gismeteo bug. Invalid data response from server.
But now server send correct response. And I published new version of component with additional server response checks.
So is it possible to get a weather forecast with this somehow? I am thinking about linking to Google Assistant to get a spoken forecast that is more accurate than the default provider. I’m sure it will take a little work my end, but if this service allows me to query prediction for a particular component (e.g. rain) at a particular time (or time interval) then I can work with that to get something up and running I hope.
A major update to the Gismeteo Weather Provider component has been released.
To improve the reliability and speed of operation, the component has become asynchronous.
In addition, internal tests have been added, which, at the development stage, constantly check the correctness of the operation of each individual piece of the component.
And finally, the ability to integrate a component through the Home Assistant GUI has been added.
UPD: And minor feature: added sensor for current temperature of water.
2021-03-02 11:31:04 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py”, line 422, in _handle_request
resp = await self._request_handler(request)
File “/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py”, line 499, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py”, line 118, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 56, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 18, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 72, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 127, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 129, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/config/config_entries.py”, line 136, in post
return await super().post(request)
File “/usr/src/homeassistant/homeassistant/components/http/data_validator.py”, line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py”, line 69, in post
result = await self._flow_mgr.async_init(
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 130, in async_init
result = await self._async_handle_step(
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 213, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File “/config/custom_components/gismeteo/config_flow.py”, line 95, in async_step_user
default=self.hass.config.get(CONF_FORECAST, False),
AttributeError: ‘Config’ object has no attribute ‘get’
Hi there! Can’t figure out how to add several locations for sensors to be able to layout them at lovelace? There is an error [latitude] is an invalid option for [sensor.gismeteo]. Check: sensor.gismeteo->latitude.
My yams is
In YAML, there is no way to specify geographic coordinates for sensors. Sensors are created strictly only for coordinates from the basic settings of your HA.
This happened for historical reasons. And now I see no reason to change this behavior, because the current approach of creating the weather entity in one place, and the sensor entities in another, is very inconvenient to process.
If I change the behavior of the component, then it is reasonable to transfer all settings into one block in YAML. But this will require reconfiguring all HA instances that use this component.
И, да, можно по-русски, если так удобнее… Всё равно этим компонентом пользуются преимущественно только в СНГ, где все прекрасно понимают русский язык.
Есть два пути:
Либо создать два объекта weather и брать данные из их атрибутов.
Либо создать конфигурации полностью через пользовательский интерфейс HA.