I've got an HP LaserJet 8100N printer and a Windows 10 Pro machine running a shared queue to it. This happens to be the same PC running my HS3 install.
The printer is loud and consumes a fair amount of power. So leaving it up and running isn't ideal. I keep it around because a) it just won't die and b) it supports printing on 11x17 paper.
I've got the 8100's power controlled via a Lutron appliance module. I've got the Ra2 module for HS3Pro.
I've got it set up such that I can use "Alexa, turn on THE BEAST" to power up the printer. Which is kinda fun.
But it occurs to me this ought to be something that could be automated via HS3.
Anyone know what sort of scripting would be involved? I've only done a cursory search online for scripting of the print API.
I'm wondering if there's a hook somewhere that could be triggered when a job is detected? That would probably be ideal. Just let the print spooler service handle issuing a command to HS3 to get the printer powered up. From that point I'd imagine HS3 would then have to monitor the queue "somehow" to determine when the queue has been idle "for a while" and power off the printer.
Anyone wandered down this road using Homeseer?
The printer is loud and consumes a fair amount of power. So leaving it up and running isn't ideal. I keep it around because a) it just won't die and b) it supports printing on 11x17 paper.
I've got the 8100's power controlled via a Lutron appliance module. I've got the Ra2 module for HS3Pro.
I've got it set up such that I can use "Alexa, turn on THE BEAST" to power up the printer. Which is kinda fun.
But it occurs to me this ought to be something that could be automated via HS3.
Anyone know what sort of scripting would be involved? I've only done a cursory search online for scripting of the print API.
I'm wondering if there's a hook somewhere that could be triggered when a job is detected? That would probably be ideal. Just let the print spooler service handle issuing a command to HS3 to get the printer powered up. From that point I'd imagine HS3 would then have to monitor the queue "somehow" to determine when the queue has been idle "for a while" and power off the printer.
Anyone wandered down this road using Homeseer?
Comment