Limych / ha-gismeteo

Gismeteo Weather Provider for Home Assistant
Other
117 stars 21 forks source link

The component stopped working #13

Closed avbor closed 3 years ago

avbor commented 3 years ago

Versions

Configuration


- platform: gismeteo
  forecast: true
  monitored_conditions:
    - rain
    - snow
    - storm
    - geomagnetic

Describe the bug

Errors in HA log:

Logger: homeassistant.components.weather
Source: custom_components/gismeteo/__init__.py:336
Integration: Weather (documentation, issues)
First occurred: 15:24:20 (1 occurrences)
Last logged: 15:24:20

gismeteo: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 358, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
    await task
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/gismeteo/weather.py", line 85, in update
    self._wd.update()
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 285, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/gismeteo/__init__.py", line 336, in update
    xml = etree.fromstring(response)
  File "/usr/local/lib/python3.8/xml/etree/ElementTree.py", line 1320, in XML
    parser.feed(text)
  File "<string>", line None
xml.etree.ElementTree.ParseError: mismatched tag: line 6, column 2

To Reproduce

Restart HA

Expected behavior

Screenshots

image

strannick-ru commented 3 years ago

+1

Repsionu commented 3 years ago

+1 Something changed at provider side I guess...

Limych commented 3 years ago

It's was not a this component bug -- but Gismeteo bug. Invalid data response from server. But now server send correct response.

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.