Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Go to 'After some time (usually 30 min or more, watch the node change to the status of outlet 1 change to be status of outlet 0
Expected behavior
Have 2 nodes for 192.168.0.10/0 & 192.168.0.10/1. 2 inject nodes which getInfo every 2 minutes. Both notes output to a text. Outlet nodes are both set to Connection/Event poll of 1000, output payload getInfo
Using the Kasa app the outlet can be turned on/off individually and reports correctly but NodeRed only updates correctly for outlet 0.
Rebooting the raspberry the status returns correctly for both outlets.
Desktop (please complete the following information):
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior Have 2 nodes for 192.168.0.10/0 & 192.168.0.10/1. 2 inject nodes which getInfo every 2 minutes. Both notes output to a text. Outlet nodes are both set to Connection/Event poll of 1000, output payload getInfo
Using the Kasa app the outlet can be turned on/off individually and reports correctly but NodeRed only updates correctly for outlet 0.
Rebooting the raspberry the status returns correctly for both outlets.
Desktop (please complete the following information):