Hello,
I’ve been using tor add-on with android, orbot (with keys) and companion app for a few years without any problem.
Since 2026.3 (ha and companion) it stopped working.
Ha version: HA OS 2026.3 supervised;
Companion version: 2026.3.2
Tor add-on: latest
Orbot: latest
I tried different ways, even downgrading companion app, but the best result I got was to see a “not home assistant server” from companion’s log.
The addon declares everything is fine.
Orbot log says that connection doesn’t occur likely because the need for a key, but this happens both with and without keys (stealth mode) enabled.
I attached the picture of what companion says.
Does someone know why is this happening now?
I can attach other logs, but as I mentioned, everything seems to work fne for what I can see and understand.
Thank you in advance.
Hello ,
Supervised and Core is longer be supported with official updates after 2025.
Your App may not be responding because of this.
Thank you Sir,
Sorry, my mistake.
Real system info is:
- Installation method Home Assistant OS
- Core 2026.4.1
- Supervisor 2026.03.3
- Operating System 17.2
- Frontend 20260325.6
On a Raspberry pi 5.
1 Like
If this is only happening on your mobile when using the companion app, then it might be caused by the new(ish) Connection Security Level settings introduced in companion app version 2025.11.
EDIT: Your screenshot shows it’s attempting to connect on port 80 (http). I believe it should be connecting to port 8123 - that’s why you’re getting the “Il server non e’ Home Assistant” error.
Sorry for late answer and thank you for yours. I think port 80 is default for the app, not my choice at all. I thought the add-on had his way to forward ports. Is there a way to change this?
However, I too believe that the problem is in the new security layer, but I also thought other people would have had the same problem. Instead I don’t see many tor add-on complaints around.
Thank you again
Managed to find another issue where the screenshot shows port as 8123.
Check the Internal url in the Companion App Server settings - it should end in :8123. Also, make sure you set it to recognise your Wifi network, otherwise it won’t be able to determine if it should use the internal or external url.
If that still doesn’t work, try to set the security level to less secure as a quick test. If you manage to connect that way, then your issue is with the security level requiring you to turn on the VPN option due to Tor/Orbot.
Thank you so much,
I’ll try as soon as possible. Could you address me to an explanation on how to lessen security levels?
Also, I red the post you mentioned and I saw that, even if the requested port is 8123, the app still doesn’t recognize ha server and no explanation was given.
That makes me think port is not the only problem.
I’ll let you know asap.
Thank you again very much
It’s explained in the link I gave you previously. Here you go Connection security level | Home Assistant Companion Docs
Hello,
I tried different methods to force “most secure” and “less secure” prompt, but I couldn’t.
The fact that noone else is reporting such an issue could mean that my setup is broken?
I also expected some more information in Tor add-on documentation since the new security level was introduced, but reading it, it seems everything should work as before, out of the box.
I can only guess mine is an uncommon situation.
Thank you for help
update:
I managed to request port 8123 (it was enough to put :8123 at the end of .onioin address).
Also, since f-droid updated companion version to 2026.4.4 and tor-addon upgraded to ver. 8, I freshly reinstalled the add-on and the app and tried to rejoin the server.
I regained the possibility to choose between most and less secure, but nothing changed in the end.
I’d really like to know if someone is still able to connect through tor add-on nowadays.
Hello,
just to let you know, after what I think should be the 11th time I deleted and reinstalled the add-on, it finally worked. Not working in stealth mode, but fine enough.
Thank you again for your help.
