HEART connectivity.link-lost H-03001

Network link lost. A network link is down.

Likely causes

• The Wi-Fi access point or router is off, restarting or out of range.
• A changed Wi-Fi password, or a router replaced by a new one.
• No mobile signal, such as a tracker in thick woods or underground.
• A cable unplugged or damaged.
• The network operator or internet provider has an outage.

How to fix or prevent it

1. Check that the router or access point is on, and that other devices can connect.
2. Move the product or the access point closer, or add a repeater.
3. Re-enter the Wi-Fi details if the network changed.
4. Check cables and connectors.
5. To prevent it: a stable access point within good range, and a wired link for important equipment.

What the HEART does by itself

It goes on working without the network: it keeps watching, keeps private events on the product, and may try to reconnect. It sends this alert when the link is back, so a watcher may first see system.flatline. It resolves when the link works again.

When to call service

If the link drops every day, or the product cannot rejoin a network that works for everything else.

Related codes

• connectivity.link-unstable H-03002: Network link unstable
• system.flatline H-01003: No Pulse (flatline)
• connectivity.dependency-unreachable H-03003: A service it relies on cannot be reached

Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written HEART storage.full. Things that simply happen, such as system.started, are event types, not faults. The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7. All of it, as data: fault-codes.json.

All fault codes, by area · All fault codes, by H-number · Problem types (API errors)