Bernd Gewehr
Bernd Gewehr
pi@volkszaehler ~ $ ldconfig -p | grep lsasl2 pi@volkszaehler ~ $ Wenn das hilft? Ich bekomme kein Ergebnis!
Stimmt! pi@volkszaehler ~ $ ldconfig -p | grep libsasl2 libsasl2.so.2 (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libsasl2.so.2 libsasl2.so (libc6,hard-float) => /usr/lib/arm-linux-gnueabihf/libsasl2.so pi@volkszaehler ~ $
So waiting is the solution?
Auch aus dem Homematic UI bleibt der Switch ohne Funktion 
Improved handling of DISCONNECT events
Small bug fixed
See here the output to the log (in case the active line matches the configured incomingLines): [3/2/2021, 7:46:11 PM] [CallMonitor] RING on line 54XXXXX2 by caller 01XXXXXXX36 with incomingLines config:...
Small addition to readme
I'd agree to what 0rangeX said. A sensor saying Nr 123456 was called would help a lot for automation purposes. Any chance to add a filter to the device config?
IMHO, this should be enough to achieve the requested functionality: https://github.com/grover/homebridge-callmonitor/pull/7/files