I have an unrooted GrapheneOS phone. I was surprised that it doesn’t offer a native option to limit battery charging to a specific upper limit (e.g., 80%) to preserve battery health and prolong the battery’s life.
To work around this, I decided to implement a charging limit feature using automation software and a Wi-Fi-controllable plug. After some research, I bought a Shelly Plug S for this purpose. I’m trying to keep things open-source, so I avoid Google Play apps when possible. The closest Tasker alternative I found on F-Droid is Easer. Unfortunately, Easer seems to lack some crucial features that would make this process easier, such as switching Wi-Fi networks or starting external apps.
Here’s my plan so far:
My phone’s charger is plugged into the Shelly Plug S, which is connected to my Wi-Fi network.
I want to use Easer to automate the process: It would turn on the plug when the charger is connected, monitor the battery level, and, once it reaches 80%, turn off the Shelly Plug S by making an HTTP call to its local web interface (or an API call).
I prefer to block the Shelly Plug from accessing the Internet entirely (to avoid leaking data to the cloud) by setting up firewall rules that restrict its access to only my local network.
However, Easer seems to have some limitations that make this more challenging than expected:
Easer cannot switch Wi-Fi networks: I was hoping to use the Shelly Plug’s local access point (AP mode) for a more portable solution, but since Easer doesn’t have permission to switch networks, I’m restricted to my home network.
Easer cannot start external apps: It also can’t trigger external apps that might help with network switching or more advanced controls.
At the moment, I’m stuck with these limitations and was wondering if anyone has experience with similar setups or has already written code to implement something like this. Specifically:
Has anyone written or seen code to automate switching off a Shelly Plug once a certain battery level is reached?
Are there any workarounds for Easer’s limitations, or should I consider switching to a different automation tool that fits my FOSS preference?
I would greatly appreciate any tips, code snippets, or discussions around best practices for this type of setup. Ideally, I’d love to make this work while keeping the setup local and portable, but I’m open to suggestions!
Should be pretty easy if you use Nginx. You can just proxy the full URI and params.
Main network: 192.168.1.0/24
Restricted network: 10.10.10.0/24
ShellyPlug IP: 10.10.10.5 (assuming it's REST API is on port 80, but adjust if needed)
Reverse Proxy IP: 192.168.1.10
Nginx "conf.d/shellyplug_proxy.conf":
server {
listen 80;
server_name shellyplug.lan;
location / {
proxy_pass http://10.10.10.5:80;
}
}
As long as your reverse proxy (Nginx) on your main network can reach 10.10.10.5 port 80 on the restricted VLAN, it should work, and you should be able to use call the api from your main network at http://shellyplug.lan (or http://192.168.1.10) just as you would to it directly to the plug on its restricted network.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
In that case, a reverse proxy on your “main” network that can access the Shelly Plug on the “restricted” network should work.
Yes, it should. I hope someone has already implemented this setup and can confirme that it works as we think it does.
Should be pretty easy if you use Nginx. You can just proxy the full URI and params.
As long as your reverse proxy (Nginx) on your main network can reach 10.10.10.5 port 80 on the restricted VLAN, it should work, and you should be able to use call the api from your main network at
http://shellyplug.lan (or http://192.168.1.10)just as you would to it directly to the plug on its restricted network.HTH