All topics

Communications and remote access

Communications shows network/collector health. Remote access opens the panel outside the LAN when supported.

Available options depend on your version, permissions and hardware. For missing actions, see Security and Diagnostics.

Step by step

  1. Review last reading, success rate, latency, timeouts and CRC errors.
  2. Verify local monitoring and Internet before enabling remote access.
  3. Enable and wait for an active status/hostname; test sign-in from another network.
Communications and remote accessCommunications and remote access
Reference screenshot; panel labels may be in English.

Options explained

Responding/frozen/no communication
inspect evidence and reading age.
Remote access
uses the product tunnel; no router port opening is required.
Enabled/active
configuration and a working connection are different states.
Availability
deployment/provisioning dependent; not every Docker installation has a tunnel.

Troubleshooting

If only remote access fails, check tunnel and Internet. If local access also fails, check collector, bus and network first.

Common problems
Communications and remote access | HelioPulse | HelioPulse