Releases: andlo/ha-meshcentral-addon
Releases · andlo/ha-meshcentral-addon
Release list
v0.2.15
Added
mstsc- enable/disable MeshCentral's built-in web-based RDP client (agentless RDP). Enabled by default, matching MeshCentral's own default.ssh- enable MeshCentral's built-in web-based SSH client (agentless SSH). Disabled by default, matching MeshCentral's own default. A startup warning is logged if enabled together withagent_pong/browser_pong, since agentless SSH is incompatible with those keepalive options.
v0.2.14
Added
- Reverse proxy / tunnel options — makes MeshCentral fully usable behind Cloudflare Tunnel, NGINX Proxy Manager, Traefik, etc. (thanks @ddcash, #9):
alias_port— the publicly visible HTTPS port (e.g.443behind Cloudflare Tunnel). Without it, agent installers point at port 4430 and agents behind a proxy can never connect.agent_alias_port/agent_alias_dns— same aliasing for the dedicated agent portagent_pong/browser_pong— WebSocket keepalive intervals; needed behind proxies that drop idle connections (Cloudflare: ~100 s)
minify— serve reduced-size web pagesconfig_override— advanced: raw JSON object deep-merged on top of the generated config.json as the last step, making every MeshCentral setting reachable even without a dedicated add-on option
All new options default to off/empty — no behavior change for existing installs.
Note: this is #9 without the OIDC single sign-on feature it was originally stacked on — that's staying separate as #8 until an admin-panel issue reported there gets sorted out.
v0.2.13
Added
plugins— enable the MeshCentral plugin system. Adds a Plugins tab under My Server where administrators can install, update and remove plugins. Installed plugins are stored in the add-on's persistent data folder and persist across restarts, updates and backups. Disabled by default. (#7)
Changed
- Persistent storage — MeshCentral's database, certificates, backups and recordings now live in the add-on configuration folder (
/addon_configs/<slug>_meshcentral) instead of/data. This folder survives add-on updates, rebuilds and uninstall/reinstall, and is reachable via the Samba addon_configs share. Existing installs are migrated automatically on first start. (#10)
Contributors
Thanks to @ddcash for both changes in this release:
- #7 — Add plugins option to enable the MeshCentral plugin system
- #10 — Store data in addon_config so it persists across reinstalls
ddcash also has two more PRs in progress (#8 OIDC single sign-on, #9 reverse-proxy/alias-port support) which will land in a future release.
v0.2.12
Added
allow_login_token— enable per-user Login Tokens (~t:...username format). Required when using the MeshCentral HA integration with accounts that have 2FA enabled, since the integration authenticates using a Login Token instead of a password. Disabled by default. See ha-meshcentral#12.
0.2.11
What's new in 0.2.11
15 new configuration options
All configurable directly from the HA add-on Configuration tab — no JSON editing needed.
Domain / appearance
site_style— login page style (1 = classic, 2 = modern)welcome_text— custom text shown on the login screennew_accounts_pass— optional password required to create a new accountguest_device_sharing— enable/disable guest sharing links for desktop sessionsauto_remove_inactive_devices— automatically remove devices offline for N days
Security
no_2fa— disable two-factor authentication requirementmax_invalid_login_count/max_invalid_login_time— brute-force login protection policyallow_framing— allow embedding MeshCentral in an iframe
Features
allow_high_quality_desktop— cap remote desktop image quality to reduce bandwidthagent_port— optional dedicated HTTPS port for agent connections only
Backup
backup_interval_hours— how often automatic backups run (default: 24h)backup_keep_days— how many days of backups to retain (default: 10)backup_zip_password— optional encryption password for backup ZIP files
Documentation
- README fully rewritten with a complete configuration reference covering all 30+ options
v0.2.10
Fixed
- Use
homeassistant.localas cert hostname instead of dynamic IP - IP-based cert was fragile (DHCP, varies per installation).
homeassistant.localworks on any local network via mDNS and is stable - Fixes "Invalid origin in HTTP request" after login
- Browse to
https://homeassistant.local:4430orhttp://homeassistant.local:4431
v0.2.9
Fixed
- Set
certin config.json to HAs actual IP address so MeshCentrals origin check matches what the browser sends in the Origin header - Remove old certificates on every start so they are always regenerated with the current IP/hostname — fixes "Invalid origin in HTTP request" error after login
v0.2.8
Fixed
- Bind MeshCentral directly on ports 4430/4431 inside the container — fixes "Invalid origin in HTTP request" error after login
- When container ran on 443 but HA mapped to 4430 externally, MeshCentrals origin check rejected the browser request. MeshCentral now listens on the same ports it is accessed on.