fritzbox_callmonitor: Wrong call-state when 2nd parallel call is ended.

[knonem]

The problem

Following situation:

• Call 1 is established. Call-monitor state = 'talking' -> Expected behavior
• Call 1 still established, 2nd call is initiated, Call-monitor state = either 'ringing' or 'dialing' -> Not ideal (would be nice to somehow see that this is call no. 2), but tolerable.
• Call 2 is established. Call-monitor state = 'talking', All attributes change to the 2nd call (Name, duration, device, ...)
• Call 2 is ended, Call 1 is still established. Call-monitor state = 'Idle' -> Should go back to 'talking' together with all other attributes because of Call 1.

What version of Home Assistant Core has the issue?

core-2023.6.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

fritzbox_callmonitor

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?

No response

Additional information

FritzBox 7590AX, FritzOS: 7.56

[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.

_{^{(message by CodeOwnersMention)}}

---

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

[cdce8p]

Thanks for bringing this to my attention @knonem! I can understand the issue. To be honest, the current implementation doesn't really account for two and more lines.

At the moment, there is a proposal to add a new event platform. That might help. I would like to wait how it progresses before I rewrite the integration just to fix this issue. https://github.com/home-assistant/architecture/discussions/929

[knonem]

Thanks for the quick reply and letting me now about the planed event platform. Sounds interesting! Sure, makes sense to wait.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ecdlguy]

I ran into the same issue, is there any progress regarding the handling of concurrent calls?