Open tekstaker opened 6 years ago
Having the same issue here
Can you wireshark the "bad" one when your using the app ?
I had the same problem as above, and was very puzzled, because only one out of four HS100 and HS200 devices received my connections on port 9999, although all of them worked fine in the Kasa app. The working device had the same hardware and firmware revision as the failing devices.
I eventually solved the problem by rebooting my router, which is running OpenWRT. All I can guess is that the OpenWRT state gets crufty over time leading to bad behavior. Perhaps the reason the Kasa app worked is that it goes through the cloud API? Anyway, now I can hit port 9999 on all the devices, so I'm (mostly) happy.
Me too have error trying to use the setwifi commands. It was working at the start the next day it doesnt't work anymore and this error pop up as shown in the picture.(only setwifi was errored the rest poweron/poweroff still works)
Thanks for this library, it works really well... Except for one plug of mine(lets call it 'M3'). When I try to query or trigger an action, I get a timeout message:
I have another HS100 that I bought at the same time and it works as expected, so I know what a good one is supposed to do. If I run a port scanner against the good one I see that port 80 and 9999 are open. The same scan against the bad plug shows NO open ports.
However, the Kasa app works fine with both plugs! So I'm not sure if the encryption or something is different with the bad plug.
Any ideas of what I could try or what other info I could provide to help diagnose and fix this problem plug?