Open knonem opened 1 year 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!
(message by CodeOwnersMention)
fritzbox_callmonitor documentation fritzbox_callmonitor source (message by IssueLinks)
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
Thanks for the quick reply and letting me now about the planed event platform. Sounds interesting! Sure, makes sense to wait.
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.
I ran into the same issue, is there any progress regarding the handling of concurrent calls?
The problem
Following situation:
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