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
As far as I can tell the tapo-p100 plugin isn't polling the plugs to check on current power state. Power control works but if the plug's power state is changed externally this isn't reflected in Homebridge (at least not until Homebridge is restarted).
To Reproduce:
Configure at least one P100 in tapo-p100 plugin
Turn on debug mode in Homebridge interface (problem happens without this but useful for showing behaviour)
Plugs will show up up in Homebridge interface with correct power state (as of last restart) and you can change the power state using the interface as expected
Use the manual button on the plug to change power state.
This change isn't reflected in Homebridge interface.
Whilst testing this I was using tcpdump on the host running Homebridge to look for traffic to/from the plugs and once it had got the plug's state at startup there was no more traffic (unless I used the Homebridge interface to change the power state).
Expected behavior:
I expected that the changed power state would be reflected (after some delay) in the Homebridge interface.
Logs:
Before running this test I removed two of the plugs from the config (using the plugin's interface) to keep things slightly simpler.
Comparing the code for updateState in platformTPLinkAccessory.ts (which I think is the one used for P100 plugs and in platformL510EAccessory.ts I see that the 510 version has the following code at the end ...
which I reckon gets called when the request to the device succeeds. The P100 version doesn't seem to have the equivalent for the happy path which would explain why we get the plug's state at initialisation but never again.
As far as I can tell the tapo-p100 plugin isn't polling the plugs to check on current power state. Power control works but if the plug's power state is changed externally this isn't reflected in Homebridge (at least not until Homebridge is restarted).
To Reproduce:
Whilst testing this I was using
tcpdump
on the host running Homebridge to look for traffic to/from the plugs and once it had got the plug's state at startup there was no more traffic (unless I used the Homebridge interface to change the power state).Expected behavior:
I expected that the changed power state would be reflected (after some delay) in the Homebridge interface.
Logs:
Before running this test I removed two of the plugs from the config (using the plugin's interface) to keep things slightly simpler.
Plugin Config:
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: