Setup
Get started
Monitee is two pieces: the app on your phone, and an agent you run on the server you want to watch. The agent does the work — install it first, then point the app at it.
The agent was called sys-API until recently. Same software, new name — older guides and the krillsson/sys-api image still work.
Install the agent on your server
Eight routes to the same agent. Pick the one that matches how your box is already set up — none of them is harder than the others, they are just different.
True of every route: you will set the user / password the app connects with — by editing configuration.yml, or in the add-on’s own Configuration tab on Home Assistant — and the agent listens on 8080 and 8443 unless you change them in application.properties. Whichever guide you follow, you are looking for Tomcat started on ports 8443 (https), 8080 (http) in the log.
NAS & appliances
Unraid, TrueNAS and Home Assistant, through their own app catalogues.
Linux, no container
Straight onto the host. Both routes need Java 21 or newer.
Add the server in the app
Install Monitee from Google Play and tap +. On your own network it usually finds the server by itself — the agent announces itself over DNS-SD, so there is often nothing to type at all.
On your network
The app broadcasts for the agent and offers it to you. If your network blocks discovery, type the LAN address instead — ifconfig on the server, under eth0 or wlan0.
192.168.0.166:8080And from anywhere
A server can hold two addresses — local first, public second — so the same entry works at home and on mobile data. Needs a static IP or domain, and 8443 or 8080 open. Find yours with curl ifconfig.me.
monitee.example.com SSL helpThen make it yours
Sign in with the credentials from configuration.yml, give the server a name and icon, and pick which drives and network adapters show on the dashboard. Turn on Notify when unreachable while you are there — it is the alert you will actually want.
If it will not connect
The usual four causes
- It is still starting — look for the Tomcat started line in the log
- Ports 8080/8443 were already taken, so it never bound
- Self-signed certificate — the app shows it to you, and you have to trust it before it will connect
- The credentials in configuration.yml are not the ones you typed