A self-hosted dashboard, monitoring tool, and control center for T-Mobile Home Internet gateways.
TMHI Control Center provides a cleaner way to view gateway status, cellular signal information, connected devices, tower data, Wi-Fi settings, connectivity history, and watchdog activity—all from a local web dashboard.
Unofficial community project: TMHI Control Center is not affiliated with, endorsed by, or supported by T-Mobile.
The exact information and controls available depend on your gateway model, firmware version, and the local API exposed by the gateway.
Run the container:
docker run -d \
--name tmhi-control-center \
--restart unless-stopped \
-p 8095:8000 \
-v tmhi_control_center_data:/data \
--security-opt no-new-privileges:true \
--cap-drop ALL \
kevina1724/tmhi-control-center:latest
Open the dashboard:
http://localhost:8095
From another device on your network, replace localhost with the IP address of the Docker host:
http://192.168.1.100:8095
Create a file named docker-compose.yml:
services:
tmhi-control-center:
image: kevina1724/tmhi-control-center:latest
container_name: tmhi-control-center
restart: unless-stopped
ports:
- "8095:8000"
volumes:
- tmhi_control_center_data:/data
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
volumes:
tmhi_control_center_data:
Start the container:
docker compose up -d
View the logs:
docker compose logs -f tmhi-control-center
Stop the container:
docker compose down
Your settings, database, event history, credentials, and firmware backup information remain stored in the Docker volume.
http://localhost:8095.DRY_RUN enabled until gateway communication and reboot controls have been tested.Most T-Mobile Home Internet gateways use:
Gateway address: 192.168.12.1
Gateway API port: 8080
Username: admin
The Arcadyan TMO-G5AR may expose the TMI API over port 80. TMHI Control Center automatically attempts common same-host API variations when possible.
The container stores persistent data under:
/data
This includes:
/data/control-center.db
/data/control-center.env
/data/firmware-backups
Do not run the container without a persistent /data volume unless you are comfortable losing saved settings and history when the container is recreated.
Most settings can be changed directly from the web dashboard.
The application automatically creates and manages:
/data/control-center.env
Common settings include:
| Variable | Default | Description |
|---|---|---|
GATEWAY_HOST | 192.168.12.1 | Gateway LAN address |
GATEWAY_PORT | 8080 | Gateway API port |
GATEWAY_USERNAME | admin | Gateway API username |
GATEWAY_PASSWORD | Empty | Gateway admin password |
WATCHDOG_ENABLED | true | Enables connectivity monitoring |
DRY_RUN | true | Prevents automatic reboot actions |
CHECK_INTERVAL_SECONDS | 20 | Time between connectivity checks |
FAILURE_THRESHOLD_SECONDS | 180 | Required outage duration before reboot consideration |
STARTUP_GRACE_SECONDS | 60 | Initial delay before watchdog actions |
POST_REBOOT_GRACE_SECONDS | 480 | Delay after a gateway reboot |
REBOOT_COOLDOWN_SECONDS | 1800 | Minimum time between reboot attempts |
MAX_REBOOTS_PER_24H | 3 | Maximum automatic reboots per day |
MAP_RADIUS_KM | 0.8 | Nearby-tower search radius |
PUBLIC_IP_LOCATION_ENABLED | true | Allows approximate public-IP map positioning |
OPENCELLID_API_KEY | Empty | Optional key for tower searches |
LOG_LEVEL | INFO | Application logging level |
Environment variables passed directly to the container override values stored in the managed settings file.
Example:
services:
tmhi-control-center:
image: kevina1724/tmhi-control-center:latest
container_name: tmhi-control-center
restart: unless-stopped
ports:
- "8095:8000"
environment:
GATEWAY_HOST: "192.168.12.1"
GATEWAY_PORT: "8080"
GATEWAY_USERNAME: "admin"
DRY_RUN: "true"
WATCHDOG_ENABLED: "true"
LOG_LEVEL: "INFO"
volumes:
- tmhi_control_center_data:/data
volumes:
tmhi_control_center_data:
For better security, enter the gateway password through the dashboard instead of placing it directly in your Compose file.
Displays internet connectivity, gateway health, signal quality, cellular connection details, firmware information, uptime, and quick actions.
Displays connected LAN and Wi-Fi clients along with available Wi-Fi configuration and radio controls.
Displays the serving cell, saved gateway location, public-IP estimate, and nearby OpenCellID tower results.
Public-IP location is only an estimate and may point to a carrier or ISP exit location. Save your actual gateway coordinates for more accurate nearby-tower searches.
Displays connectivity probes, outage events, raw gateway data, and repeated diagnostic sweeps.
Manages gateway login details, map settings, watchdog behavior, theme preferences, OpenCellID configuration, and advanced modem-lab settings.
The built-in watchdog checks multiple internet endpoints and records connection failures.
Before issuing a reboot, it applies safeguards including:
DRY_RUN protectionKeep the following setting enabled during initial setup:
DRY_RUN=true
Only disable dry-run mode after confirming that gateway authentication, diagnostics, and reboot controls work correctly with your gateway model.
Test internet connectivity from inside the container:
docker exec tmhi-control-center \
python -m tmhi_control_center.cli connectivity
Test gateway communication:
docker exec tmhi-control-center \
python -m tmhi_control_center.cli gateway-test
Check the container health endpoint:
curl http://localhost:8095/healthz
View recent logs:
docker logs --tail 200 tmhi-control-center
Pull the newest image:
docker pull kevina1724/tmhi-control-center:latest
When using Docker Compose:
docker compose pull
docker compose up -d
Your settings and history remain in the persistent Docker volume.
TMHI Control Center includes an advanced lab area intended only for owner-controlled Arcadyan TMO-G4AR gateways, such as secondhand units that are not carrier-leased equipment.
The lab can help organize:
Important limitations:
Do not continue with firmware experiments unless you have verified both a stock backup and a working recovery method.
8095 directly to the public internet./data volume./data before using advanced features.TMHI Control Center is not a signal booster.
It cannot:
Source code:
github.com/kevin1724/tmhi-control-center
Report bugs or request features through the GitHub Issues page:
github.com/kevin1724/tmhi-control-center/issues
When reporting a problem, include:
Do not include your gateway password, API keys, public IP address, or other sensitive information.
TMHI Control Center is released under the MIT License.
This software is provided as-is without warranty. Gateway controls, reboot actions, firmware experiments, modem commands, and hardware modifications are performed at your own risk.
T-Mobile and the names of individual gateway manufacturers are trademarks of their respective owners.
Content type
Image
Digest
sha256:388aafba3…
Size
53.6 MB
Last updated
about 2 months ago
docker pull kevina1724/tmhi-control-center