OctoPrint-TPLinkSmartplug VS uhubctl

I have a tplink socket on my printer so im using the TP-Link Smartplug plugin and iv got it configured with as:

My TP Link HS103 stopped working with Octoprint likely as a result of the recent firmware update. And what's weird is that there is a workaround to get the HS103 working again with the TPLinkSmartPlug plugin, which I followed. Octoprint started controlling the smart plug again - yay! But it stopped working again after a while. Boo. :(

2022-01-07 17:16:28,821 /home/pi/oprint/bin/python3 -m pip --disable-pip-version-check install file:///tmp/tmpy9sw1vew/Octoprint-Smart-Filament-Sensor-master.zip --no-cache-dir pip install "https://github.com/jneilliii/OctoPrint-TPLinkSmartplug/archive/master.zip

The P100 seems to be known to not be able to function at all: https://github.com/jneilliii/OctoPrint-TPLinkSmartplug/issues/131

I want to use this plugging for octoprint: https://github.com/jneilliii/OctoPrint-TPLinkSmartplug But i have fluid, is it possible ? I installed fluid after Nero's 3D video : https://youtu.be/gfZ9Lbyh8qU

I use this one: https://github.com/jneilliii/OctoPrint-TPLinkSmartplug It should be available from your octorpint dashboard, that's how I downloaded it a year ago. Best upgrade ever, I can leave prints overnight and when they're done the printer and a light connected to it turn off automatically after cooldown.

Follow the setup instructions on the main plugin page for inputting your plug's IP address. Make sure "Enable GCode Trigger", "Auto Connect", and "Auto Disconnect" are checked on.

In my experience this support was rare. I had an issue a few years ago with multiple USB 3 cameras (Intel Realsense) on a mobile robot that would periodically freeze up and need to be hard-reset, and a power-controllable hub seemed like the least-bad way to hack around it. I found my way to this tool, with its convenient list of compatible hardware:

https://github.com/mvp/uhubctl

Of the USB 3 options on the list, several were EOL or impossible to find, and when I ordered one each of the remainder, there was only one I could get working, and it wasn't reliable about being able to reset a device that had frozen to the point where Linux no longer had sysfs entries for it.

We ended up instead using a hub with an internal jumper to disable bus power, and then putting the self power line through a separately-controllable relay.

Best you can tweak is to disable the WiFi / Bluetooth and possibly the USB ports (edit - USB look no go https://github.com/mvp/uhubctl)

There's an extremely useful feature called USB Per-Port Power Switching, that's somewhat rare because nobody knows about it. If you use a Unix-family operating system, then here's a C driver. Windows doesn't currently have this feature, but could add it in the future -- let's hope they do!

https://github.com/codazoda/hub-ctrl.c or https://github.com/mvp/uhubctl can be used if the hubs have "Per-port power switching". The second link also has a long description.

If you were using a USB-powered drive and Linux/Mac/Unix, you could use uhubctl with one of the (uncommon) hubs that support Per-Port Power Switching (PPPS).

Actually some of the Pi boards USB ports can be controlled by Uhubctl but you have to note the restrictions on the board you are using - mainly how many you effect and the "minor" fact of the USB also controls the Ethernet and WiFi power on some boards!

Agreed this is not the right sub for this, but you got me curious. Without diving too deep, check out https://github.com/mvp/uhubctl

I've also used Qlab on both ends to trigger USB led flashes via OSC using uhubctl. You'll need a usb hub for that.