Open Stianker1 opened 1 year ago
With following steps I can see the problem like you said always.
To work around, will need to restart the homebridge service OR restart the Child Bridges(depends on plugin config) every time after camera rebooted.
Hi,
is this still a problem with the recent version 2.3.4?
Best Regards X23
I'm not sure about the original poster's issue is exactly the same as me or not. But with my steps, the issue still exist in v2.3.4.
And which is fine for me now, i had a work around for it by another plugin "[homebridge-cmdtrigger]"
So my use case were connecting my TAPO cam to a homekit power switch, so whenever i turn on the switch i make a delay 3 minutes wait for TAPO cam boot finished and use plugin to execute "kill -15 $(pidof 'homebridge: homebridge-tapo-camera')". ==> this will restart the TAPO plugin.
It is solve?
Hello, Since the last update of the tapo homebridge plugin and the last update from tapo it has stopped registrering motion on my c200 cam. Via the tapo app i can detect motion but not via homebridge plugin.
Expected behavior: Motion detection
Plugin version : 2.2.3 Homebridge version : 4.50.2 Node.js version : 18.16.0 OS: raspbian GNU/Linux Bullseye (11)