[homeassistant.components.fritzbox_callmonitor.sensor] Connection has abruptly ended

[StefanoGiu]

The problem

[homeassistant.components.fritzbox_callmonitor.sensor] Connection has abruptly ended

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

fritzbox_callmonitor

Link to integration documentation on our website

No response

Diagnostics information

[homeassistant.components.fritzbox_callmonitor.sensor] Connection has abruptly ended

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[mib1185]

I'm missing an issue description, just throwing an error message, without any context, is not really something, which could be analysed. So please provide a proper issue description - help us to help you Thx 👍

[StefanoGiu]

The log is full of this error and the integration doesn't seem to work. I tried to delete and reinstall this integration but the result is the same.

[mib1185]

please provide the full logfile, thx 👍

[StefanoGiu]

The log is full of this: [homeassistant.components.fritzbox_callmonitor.sensor] Connection has abruptly ended

There is no other error...

[mib1185]

there are really not any other messages in the log, besides this?

[StefanoGiu]

Yes, no other errors...

[mib1185]

i'm not asking for other error, but for any other messages in the log. Further question would be, did this ever work for you? if yes, since when does it not work anymore (eq. HA update or FritzOS update or any other change on your network/fritzbox/homeassistant/...)?

[StefanoGiu]

it was working long time ago (maybe 2024.4.0) but since then it stopped working. Any other messages in the log, not relevant to fritzbox integration are not of any help here...

[mib1185]

it was working long time ago (maybe 2024.4.0) but since then it stopped working

this is half a year ago - why reporting it now and not already than?

Any other messages in the log, not relevant to fritzbox integration are not of any help here...

ok, than with the given log messages i can only tell you, that the fritzbox did cut off the connection to ha. i can't say why or when or make any assumptions about the cause, without knowing more about your environment (like configuration, network setup, system event log on fritzbox, other HA log messages around the timeframe of the fritzhox connection issue, ...).

You can try to enable enable debug logging, restart the integration and download and provide the log file after the issue occur again.

Further if possible please download and provide the diagnostics data for this integration.

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

thx 👍

[StefanoGiu]

I'm running HA in a docker container under WSL in windows. Do I need to open/publish a specific port on the container/windows server in order to make this integration work, like with netsh portproxy?

[home-assistant[bot]]

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)}}

[mib1185]

Do I need to open/publish a specific port

based on the prerequisites section in the docs, HA needs to be able to reach the fritzbox on tcp/1012 and tcp/80 (maybe also tcp/443 if you're fritzbox redirects http to https)

[StefanoGiu]

from inside the container:

XXXX:/config# nc -zv 192.168.1.1 1012 192.168.1.1 (192.168.1.1:1012) open XXXX:/config# nc -zv 192.168.1.1 80 192.168.1.1 (192.168.1.1:80) open XXXX:/config# nc -zv 192.168.1.1 443 192.168.1.1 (192.168.1.1:443) open

[mib1185]

system event log on fritzbox, other HA log messages around the timeframe of the fritzhox connection issue

than "we" should still have a look at these things from https://github.com/home-assistant/core/issues/127916#issuecomment-2400130704