[ISSUE]: Not powering off TP-Link Plug

[oxicottin]

Describe the bug
I have been using this life saver Plugin for a few months without any trouble. Yesterday I printed and at my prints end my plug never powered down and shut everything off. I thought maybe it was a conflicting plugin so I removed all of them and still same issue and its even an issue if I set my Idle Timeout to one minute and it counts down to shut down and nothing happens at the end. I even tried a separate TP-link plug and same thing it didn't shut off. So with that I decided to reinstall Octoprint and just the TP-Link Plugin and still same issue exists.

[jneilliii]

I think this is a duplicate of #250. If you disable the gcode trigger options the idle timer will work as it's supposed to. You don't need both enabled in your use case anyway.

[oxicottin]

@jneilliii the images are what worked for me for at least 4 months and several prints. I tead #250 before posting and I tried your suggestion with the settings below and still after 1 minute it wont shut down plug. I have the correct plug IP so that isn't it and like I mentioned I tried a second TP plug and still same issue. Thanks,

[jneilliii]

Could you enable debug logging and restart octoprint and run through another round of testing and then share your octoprint.log and plugin_tplinksmartplug_debug.log files here by dragging them into a comment? That will help me diagnose a little further.

[Jack77777777]

That's really starge. For me it is working when gcode trigger is disabled. Do you have an cloud account at kasa or guest and have you changed anything in kasa lately? Firmware Update perhaps ? My HS100 are Hardware version 4.0 and firmware 1.1.5

[oxicottin]

@jneilliii I also wanted to say the lightning bolt does nothing, It doesn't turn off or disconnect nor does it turn on. It just spins for a sec and stops, no color change for indication.

[jneilliii]

Ok, that is strange. The plugin sees the plug as on the network, but the firmware is not responding to it when it sends commands. This is very similar to what was happening in #218. Like @Jack77777777 mentioned have you recently connected them to the cloud or run firmware updates on these plugs that may not be blocking local access?

[oxicottin]

No I havent messed with updating the firmware of the plug or anything with it.

Any sugestions? And im using a HS105 plug FM:1.5.6

On a side note, should I buy a different TP-Link plug? If so what version is best?

[jneilliii]

I'm stumped since as you said it worked before and all of a sudden stopped working and doesn't work on another plug as well. The only thing I can think of is that the plug just isn't responding or doesn't have access to send the command to the plug. The HS105 is a plug that I've never tested personally but have received reports that it works (including from yourself). I have personally tested HS100, HS107, HS110, and HS300. Have you tried unplugging your HS105 from the wall and back in just to see if it's a random communication issue? For me, I have all mine that I can configured for local only mode in the kasa app.

[oxicottin]

How can you configure it local only? I poked around in kasa app and dont see that. I just ordered a HS100 to see if that works. I havent unplugged it.

[jneilliii]

https://www.tp-link.com/us/support/faq/2707/

[Jack77777777]

Removed Plugs from Kasa app, deinstalled plugin with deletion of data. Re-added devices with guest account to Kasa app.
Added devices to plugin and configured. Same behaviour as before. As soon as gcode trigger is enabled idle power off not working.
Tested with 0.9.26 and 1.0.0rc2. When i login to Octoprint the idle timer starts and printer powers off. It seems that the plugin needs a API request with my configuration. At least when gcode trigger is enabled for one device.

config.yaml.txt
octoprint.log
plugin_tplinksmartplug_debug.log

[Jack77777777]

@jneilliii
One more test: Removed @TPLINKOFF after print and it works. Light goes on with print start TPLINKON and off when idle like the printer. For me this is something i can live with at the moment.

Attaching more logs for analyzing:
plugin_tplinksmartplug_debug.log
octoprint.log
config.yaml.txt

[jneilliii]

Yep, I figured it out @Jack77777777 thanks for all the details. Now I just have to figure out how to adjust the code for it.