fritzbox_callmonitor: Sensor problem

Jautze82 commented 1 week ago

The problem

My Sensor fritz_box_fon_wlan_7390_anrufmonitor_telefonbuch did not work.

In the protocoll I find this:

`Protokolldetails (FEHLER) Logger: root Quelle: components/fritzbox_callmonitor/sensor.py:227 Erstmals aufgetreten: 15:05:24 (1 Vorkommnisse) Zuletzt protokolliert: 15:05:24

Uncaught thread exception Traceback (most recent call last): File "/usr/local/lib/python3.12/threading.py", line 1073, in _bootstrap_inner self.run() File "/usr/local/lib/python3.12/threading.py", line 1010, in run self._target(*self._args, **self._kwargs) File "/usr/src/homeassistant/homeassistant/components/fritzbox_callmonitor/sensor.py", line 219, in _process_events self._parse(event) File "/usr/src/homeassistant/homeassistant/components/fritzbox_callmonitor/sensor.py", line 227, in _parse isotime = datetime.strptime(line[0], df_in).strftime(df_out) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/_strptime.py", line 554, in _strptime_datetime tt, fraction, gmtoff_fraction = _strptime(data_string, format) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/_strptime.py", line 333, in _strptime raise ValueError("time data %r does not match format %r" % ValueError: time data '01.01.-30 03:10:5' does not match format '%d.%m.%y %H:%M:%S'`

What version of Home Assistant Core has the issue?

core-2024.11.2

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

AVM FRITZ!Box Call Monitor

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

`Protokolldetails (FEHLER)
Logger: root
Quelle: components/fritzbox_callmonitor/sensor.py:227
Erstmals aufgetreten: 15:05:24 (1 Vorkommnisse)
Zuletzt protokolliert: 15:05:24

Uncaught thread exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.12/threading.py", line 1010, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/src/homeassistant/homeassistant/components/fritzbox_callmonitor/sensor.py", line 219, in _process_events
    self._parse(event)
  File "/usr/src/homeassistant/homeassistant/components/fritzbox_callmonitor/sensor.py", line 227, in _parse
    isotime = datetime.strptime(line[0], df_in).strftime(df_out)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/_strptime.py", line 554, in _strptime_datetime
    tt, fraction, gmtoff_fraction = _strptime(data_string, format)
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/_strptime.py", line 333, in _strptime
    raise ValueError("time data %r does not match format %r" %
ValueError: time data '01.01.-30 03:10:5' does not match format '%d.%m.%y %H:%M:%S'`

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @cdce8p, mind taking a look at this issue as it has been labeled with an integration (fritzbox_callmonitor) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `fritzbox_callmonitor` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign fritzbox_callmonitor` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

fritzbox_callmonitor documentation fritzbox_callmonitor source _{^{(message by IssueLinks)}}

cdce8p commented 6 days ago

Hi @Jautze82 👋🏻 Thanks for the report. Tbh this looks a bit strange. Could you enable debug and reproduce the issue? https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

Jautze82 commented 4 days ago

Hi @cdce8p how can I send this file to you. I don't want to upload it to here.

Best regards Marcel

cdce8p commented 4 days ago

Hi @cdce8p how can I send this file to you. I don't want to upload it to here.

You can find me on the HA discord server, same username. Should be possible to send me a DM there.

I'm mostly interested in one particular line: Received event: ... right before the error occurred and maybe one more without an error. Feel free to replace any personal information with *.

Jautze82 commented 1 day ago

Gelöst. Es war eine falsche Zeiteinstellung in der Fritzbox

home-assistant / core