Myro Control Forum
Shared Networking & Integration Guides => Networking & Remote Access => Topic started by: Myro Control on October 22, 2026, 01:35:26 pm
-
Applies to: Myro:Home Helper, Pro and Classic. Start by getting everything working on your home Wi-Fi. This guide distinguishes reaching the Helper Mac from reaching the automation controller itself.
1. Connect your phone to the Helper Mac
- Install Tailscale on the always-on Mac running Helper and on your phone or tablet. Sign your own devices into the same private Tailscale network, or invite household members with their own sign-ins and appropriate access.
- Keep Helper connected to the controller. Keep the Mac powered on, awake and connected to the home network.
- At home, open Pro or Classic and let it connect to Helper once while Tailscale is running. Supported current versions remember the addresses Helper reports, including its VPN address.
- Test away from Wi-Fi, on cellular with Tailscale connected. Bonjour discovery stays on the local network; a fresh app installed away from home may have no remembered Helper address yet.
Helper's web control normally uses port 9393. Its sign-in still applies when using a VPN. Reaching the Mac does not automatically give the phone a route to the controller's private LAN address.
2. Reach an HAI / Leviton or NESS / ELK controller
The mobile app normally connects directly to the controller. A controller cannot run Tailscale itself, so use an always-on subnet router on the home network.
- Choose a supported subnet-router device that can reach the controller locally. The Helper Mac can serve this role when separately configured.
- Advertise the actual home subnet, approve that route in the Tailscale admin console, and allow the phone to reach the intended controller under the tailnet's access rules. Route approval and access permission are separate.
- Use the controller's routed LAN address in the app's connection settings. A public DDNS name or a .local discovery name may not resolve to the right destination remotely.
- Test on cellular. HAI Omni-Link commonly uses port 4369; ELK commonly uses 2601. Follow the interface settings for your system.
A subnet router routes traffic to LAN devices. An exit node routes general Internet traffic; turning on an exit node alone does not replace subnet-route setup.
Savant
PRO's direct Savant connection also needs a route to the Savant host. A reachable Helper is not proof that the host is reachable. Use a subnet router and the host's LAN address, retain Savant Local User authentication, and confirm the expected host identity. Savant support in the current Helper release remains a preview.
Common fixes
- Helper works but the panel does not: check the subnet route, approval, access rules and controller address.
- Works at home but not away: first establish a local Helper connection; then check Tailscale on both devices and the Mac's availability.
- Local discovery breaks when an exit node is on: enable Allow LAN access / Allow local network access, or stop using the exit node for that connection.
- Works on cellular but not a hotel's Wi-Fi: check for overlapping private subnets and competing VPNs.
Do not open Helper's port to the public Internet for this setup. After private remote access is verified, review and remove any router port forwarding that it replaces, then test again.
Official Tailscale subnet-router instructions (https://tailscale.com/docs/features/subnet-routers)
Official Tailscale exit-node and LAN-access instructions (https://tailscale.com/docs/features/exit-nodes)
For help, reply with the app version, device/OS, controller model where relevant, what you expected, and what happened. Remove passwords, controller keys, security codes, API tokens and private camera URLs from screenshots and logs.