Skip to main content

Turn off a PC with Arduino and an IR remote

I have the bad habit of watching or listening something from my computer before I go to sleep while already lying in bed. Often when I am on the verge of falling asleep, it is frustrating to get up and turn off the computer. Usually, I put on a timed shutdown so that when I fall asleep, the computer won't wake me up in the middle of the night. However, I wanted to have some other way which does not involve getting up from bed nor having to light up any screen (like my phone) which would interfere with the process

I thought about the problem from time to time and it was earlier this year when I bumped into an Instructables post in which somebody had made a remote controller for his PC with Arduino as a "keyboard". I thought I would do something similar to solve the shutting down problem because as it happened, I had a spare Arduino lying around

After playing around with it for a while, I found out that in my Arduino Uno was lacking HID support so it was not going to work as a keyboard with official firmware and I was not too keen to try out some custom firmware. This was not a real issue since I would not really be needing a keyboard functionality. Simply one script which is run when I push a button from an IR remote is sufficient.

I made a small python script which listens to the COM port (USB) to which the Arduino is plugged and runs the shutdown command on a set input from the serial port.

I purchased an IR receiver from my local electronics shop, put that to a breadboard and connected it to the Arduino via some jumper wires. I decided to use the remote for my speakers to send the shutdown command since I already am using that to adjust the volume but rarely use it to shut down the actual speakers.

I downloaded an IR library and installed it on the Arduino. Then all that was left was just to check what signal (translated to HEX by the library) the remote was sending when the shutdown button was pressed, write the input to the serial port and modify the python script accordingly to call shutdown -s -t 60.


The IR receiver is on the left, on the right, a thermometer


Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker

Careful with externalTrafficPolicy

On a project I am working on is hosted in an EKS cluster with the NGINX ingress controller (the one maintained by Kubernetes). It is deployed using it's official official Helm chart, which I realized, after a lengthy debugging session, was a mistake. The initial setup I aimed to improve had several flaws. Firstly, we were using the AWS Classic Load Balancer in front of the nginx ingress in the cluster, which has been deprecated for some time (years?). Continuing to use it makes little sense to us. The second issue was that we were only running one(!) nginx pod, which is quite sketchy since the exposed web services had essentially no high availability.  I switched to the Network Load Balancer (NLB), which was straightforward - I just needed to change the ingress-nginx service annotation to specify the load balancer type as NLB: service.beta.kubernetes.io/aws-load-balancer-type: nlb However, increasing the replica count turned out to be tricky. When I bumped it up to two, I began to ...