core: zamg integration time parsing error

The problem

zamg (https://www.home-assistant.io/integrations/zamg) fails to initialize (see logs)

image

What version of Home Assistant Core has the issue?

2022.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zamg

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zamg

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-12-14 15:21:00.363 ERROR (MainThread) [homeassistant.components.zamg] Unexpected error fetching zamg data: time data '2022-12-14T14:10+00:00' does not match format '%Y-%m-%dT%H:%M:%S+00:00'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 225, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/components/zamg/coordinator.py", line 44, in _async_update_data
self.data["last_update"] = self.zamg.last_update
File "/usr/local/lib/python3.10/site-packages/zamg/zamg.py", line 142, in last_update
return datetime.strptime(
File "/usr/local/lib/python3.10/_strptime.py", line 568, in _strptime_datetime
tt, fraction, gmtoff_fraction = _strptime(data_string, format)
File "/usr/local/lib/python3.10/_strptime.py", line 349, in _strptime
raise ValueError("time data %r does not match format %r" %
ValueError: time data '2022-12-14T14:10+00:00' does not match format '%Y-%m-%dT%H:%M:%S+00:00'

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 20 (5 by maintainers)

Most upvoted comments

Any idea when a new HA version gets released which includes this bugfix? my home is really broken without this integration…

A! Sorry & thanks, misunderstood your post…

I changed to a different station, but same result as CHoerby has posted in the image. There must be a time parsing problem.

There is a pull request waiting to be merged which will fix this issue.