Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

[fritztr064]Binding tries to connect to the callmonitor without item usage #5858

Open
Confectrician opened this issue May 9, 2019 · 1 comment

Comments

@Confectrician
Copy link
Contributor

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:

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)

  1. Install the binding and do not activate the call monitor interface
  2. Do not configure call monitor items.
  3. 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
@J-N-K
Copy link
Member

J-N-K commented May 9, 2019

Unfortunately an OH1 binding. A very useful one that has quite a lot of flaws...

@kaikreuzer kaikreuzer transferred this issue from openhab/openhab-addons May 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants