Home Assistant integration for MeshCentral

[andlo]

Hi,
I've built a Home Assistant custom integration that connects to MeshCentral via the WebSocket API (/control.ashx).
It provides real-time device monitoring and control directly from Home Assistant:

Online/offline status via nodeconnect events (real-time push)
Wake-on-LAN using the wakedevices action
Power control (reboot, shutdown, sleep, hibernate) via poweraction
Windows Security Center status (antivirus, firewall, Defender)
Hardware details via getsysinfo

One thing worth noting for others: login with 2FA accounts works perfectly using Login Tokens (~t:... username format). Also, for tlsOffload: true setups, the integration connects via plain HTTP/WS even on port 443.
The integration is open source and installable via HACS:
https://github.com/andlo/ha-meshcentral
Thanks for building such a great platform — the WebSocket API made this integration a pleasure to build.

[si458]

thats amazing!
now if you can built an addon to RUN meshcentral @Ylianst would love you to the end of the earth!
its the 1 thing he really really really wants but just not had time to make one haha

EDIT: shared on discord announcements :)
https://discord.com/channels/891895284005752893/1301575039530832024/1498025670956155073

EDIT2: please can you share screenshots or video in the repo or here for others to see 👍

[si458]

i hadnt spotted that, thank you!
1 issue,
you need to add certUrl: "https://my.domain.com" under the domains section of the config.json
and the url will be the domain you use, so you might need to update the readme!
this is required for machines to connect correctly and verify the SSL connection
either my your reverse proxy or cloudflare tunnels for example

[andlo]

Thanks for the feedback and for sharing on Discord! 🙏

Good catch on certUrl — I've added it as a configuration option in the add-on. Users will need to set it to their external URL (Cloudflare tunnel, Nabu Casa etc.) for agents outside the local network to connect correctly. README has been updated.
Screenshots are a great idea — I'll add some. The add-on just got its first successful build for all 5 architectures (amd64, aarch64, armhf, armv7, i386), so it's ready to test!
Add-on repo: https://github.com/andlo/ha-meshcentral-addon

[andlo]

[si458]

@andlo few more issues ive found,

1. cleanErrorLog is NOT a valid config.json value
2. mstsc should be removed or set to true, you have set it to false which disables RDP access!
3. you run meshcentral with --datapath which is perfectly fine!
   HOWEVER the is multiple folders which get created next to the datapath
   like meshcentral-backups, meshcentral-web, meshcentral-files, meshcentral-recordings
   NOW you can force -files path using --filespath
   AND you can customise the -recordings folder using the filepath inside of sessionRecording in domains of config.json
   AND you can customise the -backups folder too using the backupPath inside of autoBackup in settings of config.json
   BUT ALSO -web folder CANNOT be changed sadly at the moment

PS: all possible config.json options are here https://config.meshcentraltools.com

[andlo]

Thanks @si458 — all three fixed in andlo/ha-meshcentral-addon@bcd6f4d

cleanErrorLog removed
mstsc: false removed — good catch, didn't want to accidentally disable RDP!
--filespath flag added to the startup command, and backupPath/sessionRecording.filepath set in the generated config so all data folders stay under DATA_PATH. I noted in the README that meshcentral-web can't be redirected.

Very helpful feedback, thanks for taking the time! 🙏

[Ylianst]

@andlo - Oh! I am going to be trying this for sure on my servers. This is very cool. I was wondering if I could have all of MeshCentral be an add-in to Home Assistant at some point running as a Docker contained within HA with the config file being exposed for HA to setup. Anyway, congratulation on this. I am going to be looking at it for sure.

[andlo]

@Ylianst
I think it should be posible.....Lets make tha t the goal.

Also thinking of making every setting posible in the addon to confiure from UI, but one step at a time....

[michaelmikelas]

This is just incredible... But need to figure out what I'm missing because I constantly get an auth failure when trying to set up this integration.

Setup:
Mesh (docker) behind local NPM (docker), HomeAssistant (Proxmox VM). Public domain for external access behind CloudFlare. Mesh using 2FA so I have tokens for auth, and I'm also using LoginKey within my Mesh config so I'm curious if that might be presenting auth challenges with this integration. I've tried the public FQDN, local docker IP, NPM IPs, etc. with the tokens and always get auth failure.

[andlo]

Hi @michaelmikelas — I've tracked this down and implemented a fix.

The root cause is the LoginKey (3FA) setting on your server — when active, MeshCentral requires ?key= on all requests, including the login POST and WebSocket connection. The integration wasn't passing it anywhere, so auth failed before credentials were even checked.

Fix is in branch fix/loginkey-support on the integration repo: andlo/ha-meshcentral#13
If you're willing to test it before I merge and release, that would be a huge help since you have exactly the setup that triggers this. To install from the branch directly in HACS:

Remove the existing MeshCentral integration entry in HA
In HACS → Integrations → ⋮ → Custom repositories, update the URL to:
https://github.com/andlo/ha-meshcentral
After installing, manually replace the files in custom_components/meshcentral/ with the ones from the branch — or clone the branch and copy them over

Alternatively, just grab the 4 changed files directly from the branch:

client.py
config_flow.py
coordinator.py
const.py

Drop them into custom_components/meshcentral/ on your HA instance, restart, delete and re-add the integration — you should now see a Login Key field in the setup form.

Note: the Login Key field is for the server-level 3FA key (--logintokenkey), which is separate from your per-user Login Token (~t:... username). You may need both.

[michaelmikelas]

Thank you... Let me give this a try and I'll report back... have some business related travel this week so may not be able to test before the coming weekend.

[michaelmikelas]

@andlo - this worked from an authentication perspective and I see the recurring websocket request in the Meschcentral server trace but the integration isn't pulling in any of my devices... have enabled debug but not seeing any logging on the HA side to help troubleshoot the integration not pulling in my devices.

[andlo]

Hi @michaelmikelas,

Glad the authentication is working! The recurring WebSocket request you see in the MeshCentral trace is the integration keeping the connection alive — that part is working correctly.

For devices not showing up, the most common cause is that debug logging isn't fully enabled. Please make sure you have this in your configuration.yaml:

logger:
  default: warning
  logs:
    custom_components.meshcentral: debug

After restarting HA, you should see log entries showing what data is being received from MeshCentral. Look for lines mentioning meshes and nodes — if those responses are empty, the integration has nothing to create entities from.

A few things to check:

1. Mesh group permissions — Does the account you're using have access to devices in the MeshCentral web UI? The integration only sees what your user account has access to.
2. Domain — If your MeshCentral uses multiple domains, make sure the account has devices in the default domain.
3. Debug log output — If you can share the relevant lines from the HA log after enabling debug, I can help narrow it down further.

Feel free to open an issue on the repo if you prefer: https://github.com/andlo/ha-meshcentral/issues

[andlo]

@michaelmikelas — thanks for spotting that URL bug! Fixed in the fix/loginkey-support branch. The ?key= param is now correctly appended after the path (/login?key=xxx) instead of before it. See issue #12 for details — would be great if you could test the branch!

[michaelmikelas]

Andreas, I found that it actually wasn't working, but I've been able to massage the code to get it to work in my environment. I'll move this conversation and my findings over to the integration github. Thanks, -Mike

…

On Sat, May 30, 2026 at 7:50 AM Andreas Lorensen ***@***.***> wrote: Hi @michaelmikelas <https://github.com/michaelmikelas>, Glad the authentication is working! The recurring WebSocket request you see in the MeshCentral trace is the integration keeping the connection alive — that part is working correctly. For devices not showing up, the most common cause is that debug logging isn't fully enabled. Please make sure you have this in your configuration.yaml: logger: default: warning logs: custom_components.meshcentral: debug After restarting HA, you should see log entries showing what data is being received from MeshCentral. Look for lines mentioning meshes and nodes — if those responses are empty, the integration has nothing to create entities from. A few things to check: 1. *Mesh group permissions* — Does the account you're using have access to devices in the MeshCentral web UI? The integration only sees what your user account has access to. 2. *Domain* — If your MeshCentral uses multiple domains, make sure the account has devices in the default domain. 3. *Debug log output* — If you can share the relevant lines from the HA log after enabling debug, I can help narrow it down further. Feel free to open an issue on the repo if you prefer: https://github.com/andlo/ha-meshcentral/issues — Reply to this email directly, view it on GitHub <#7770?email_source=notifications&email_token=A56MF56PYSWR452ICVULGZD45LDIZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZRGE2TMOBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17115684>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A56MF5ZUIMKF4ZB652QSD2L45LDIZAVCNFSM6AAAAACYHAOSZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMJRGU3DQNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[andlo]

Update for anyone following this thread:

Both projects have come a long way since April — thanks in large part to the feedback and testing here.

ha-meshcentral-addon is now at a solid place: pretty much every setting is configurable from the add-on's GUI (no more editing config.json by hand) — domains, certUrl, data paths, backups, session recordings, reverse proxy, the works. Big thanks to @si458 for the early config.json corrections (cleanErrorLog, mstsc, the data-folder paths) — those went straight into the add-on.

ha-meshcentral (the integration) now creates entities reliably and they actually work end-to-end: online/offline, power control, security sensors, device tracking, and running remote commands (including a full console/PowerShell command service). Thanks to @michaelmikelas for patiently working through an auth issue with LoginKey (3FA) setups and multi-domain configs with me — that turned into a proper fix rather than a workaround. And thanks to @sammyke007 for pushing for a dedicated "run console command" service, which is now in.

@Ylianst — still very much keeping your original idea in mind (MeshCentral itself running as a Docker add-on with config exposed to HA). The add-on already runs MeshCentral in a container within HAOS, so a chunk of that groundwork is there.

Repos, if anyone wants to try the latest:

github.com/andlo/ha-meshcentral-addon
github.com/andlo/ha-meshcentral

Feedback and issues always welcome.