You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2021. It is now read-only.
The call monitor feature works not as expected and throws warnings constantly.
Expected Behavior
If one doesn't want to use the call monitor feature, he/she should be able to use the binding without activating the call monitor interface via phone, to gat a warn free log.
Current Behavior
Even without items that use the callmonitor feature, the binding tries to connect to the callmonitor.
If one doesn't want to use this feature, he/she has to activate the call monitor interface via phone.
Docs reference:
Only if you want to use the call monitor feature (items starting with callmonitor_...), enable the interface by dialing #965 You may disable it again by dialing #964
Possible Solution
No investigation done on this.
Steps to Reproduce (for Bugs)
Install the binding and do not activate the call monitor interface
Do not configure call monitor items.
Log should show that the binding anyway tries to connect to the call monitor
Context
Your Environment
Openhab 2.4 stable
Raspberry PI with openhabian
The text was updated successfully, but these errors were encountered:
Reference (German forum):
https://knx-user-forum.de/forum/supportforen/openhab/1340724-warnung-g-fritzboxtr064-internal-callmonitor-beim-fritzbox-tr064-binding
The call monitor feature works not as expected and throws warnings constantly.
Expected Behavior
If one doesn't want to use the call monitor feature, he/she should be able to use the binding without activating the call monitor interface via phone, to gat a warn free log.
Current Behavior
Even without items that use the callmonitor feature, the binding tries to connect to the callmonitor.
If one doesn't want to use this feature, he/she has to activate the call monitor interface via phone.
Docs reference:
Possible Solution
No investigation done on this.
Steps to Reproduce (for Bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: