How do you guys handle automatic power off in Hexnode? Any tips?Solved

Oh, I know exactly what you mean! Our retail kiosks used to stay on all night as well, and it was wasting so much power. What we ended up doing was setting a scheduled time trigger to power them off after office hours, and it works perfectly. Plus, nobody is actually sitting there, so there’s no disruption. 

That’s smart. I didn’t even think about scheduling it like that. For our warehouse tablets, we had a slightly different issue: some devices would wander off the network and stay on indefinitely. So, we started experimenting with location non-compliance triggers, which automatically power off a device if it leaves the warehouse. Sometimes we add a lock first before shutting it down, and other times we just hit power off directly. It really depends on how low the battery is and how much risk we’re willing to take. 

Ah, I see. That’s a clever approach, especially for devices that aren’t monitored all the time; it actually makes a noticeable difference in battery life. Right? 

Speaking of battery, our remote devices have a habit of running really low, so we set up a power off automation using the battery level filter. Any device that drops below a certain percentage automatically powers off. The automation only works for devices that are online when it runs, but it has saved us a lot of dead batteries and prevents wasted energy. Users still need to plug the device in, of course, but it keeps things under control. 

Desktops and laptops are a whole different story. For those, we schedule the power off at the end of the day, but only after a maintenance check script runs to confirm all updates are installed. It’s a nice way to give the machines a proper sleep, and it prevents any surprises for staff coming in the next morning. 

Wow… so it really does feel like every device type needs its own workflow. Tablets, kiosks, and desktops each require different triggers and action combinations to make the automation effective.