Remote recovery
Wake a NAS or PC from Telegram or ntfy and get a message when its configured port answers or the check ends. The ESP32 only needs a working Internet uplink to the notification service and local network access to the device. You can skip Tailscale during setup.
Set up Telegram or ntfy without a Tailnet
- Skip Tailnet registration during first boot, or leave it disabled. Keep the ESP32 powered and connected to your LAN.
- Save the NAS or PC by name and MAC address in Devices & Recovery → Wake-on-LAN.
- In Devices & Recovery, select the saved device. Choose Local uplink subnet only, enter its LAN address or hostname and a TCP port that answers when it is up. Set Recovery timeout (5–600 seconds) and Maximum checks (at least 2 for
recover). You can also verify a separate service port. Enable Notify manual results and new outages, then save the device profile. - In Automation → Notifications, configure Telegram or ntfy and set Remote commands to Info, Wake-on-LAN and verified recovery. Leave Poll commands only while Tailscale is down off for this setup. Save and run Send test.
For Telegram, send the commands below to your bot after sending it /start. For ntfy, publish the command as a message to the configured private topic. See the integration settings.
Command reference
| Command | What the ESP32 does | What you receive |
|---|---|---|
wol NAS | Sends the Wake-on-LAN packet. | Confirmation that the packet was sent, or a send error. |
recover NAS | Checks first, sends Wake-on-LAN if needed and waits for the configured check to pass. | An acknowledgement, then the result if notifications are enabled for NAS. |
check NAS | Checks the saved address and configured port. | An acknowledgement, then the reachability result if notifications are enabled for NAS. |
probe NAS_Web | Tests a saved IPv4 address and TCP port. | An acknowledgement, then the reachability result. |
checks | Lists the saved TCP checks without running them. | The latest result for each saved check. |
info | Reads the gateway's operational status. Enable the channel's Allow info command option. | Gateway status and device counts. |
Replace NAS with the saved name. Use check for one device at a time. A new manual job for the same device has a one-minute cooldown. Reachable means the configured port answered. Not reachable means it did not answer within the time or attempt limit. Inconclusive means the gateway could not establish reachability. A port check cannot prove that the device is powered off.
Check a saved TCP service
Under Devices & Recovery → Health & Resources → Saved TCP checks, add a name, IPv4 address and TCP port. Keep the interval at 0 for manual checks or choose 30–3600 seconds for a schedule. Enable outage notifications to learn when a previously reachable port stops responding. The checks do not need a MAC address.
Use the Web UI over Tailscale
Requirements
If Tailscale runs only on your NAS, shutting the NAS down also removes that access point. The ESP32 runs as a separate Tailnet node: open its Web UI remotely and send Wake-on-LAN without keeping another Linux server or Home Assistant running. See the actual firmware interface.
- A target that supports Wake-on-LAN, with WoL enabled in its firmware/OS and standby power.
- The ESP32 powered independently of the target, on the same LAN broadcast domain.
- A known TCP port on the target to check (SSH may be disabled on some NAS systems; pick a port that is really listening).
Procedure
- Add the device in Devices & Recovery → Wake-on-LAN (name and MAC address).
- Open Devices & Recovery, choose the target, check port, optional service port and timeout.
- Use Check now to observe, or Recover with WoL to precheck, wake if needed, wait and check again.
Verify
The result lists each step's evidence: precheck, whether a magic packet was sent, and the post-wake check. A sent packet is not proof of power-on; an open TCP port is not application health.
Enable result notifications on a saved device to receive one result for each manual check or recovery through the enabled ntfy, Telegram and email integrations. Scheduled monitoring alerts when the device becomes unreachable after a successful check.
Recovery access point
If the saved WiFi is not seen for 60 seconds, the ESP32 brings its access point back for local administration and keeps it until the WiFi returns. Short reconnect retries do not postpone this timer.
Limits
- Cannot hard-reset a frozen machine, cut power, or provide KVM/BIOS access. Not out-of-band management.
- Telegram and ntfy require Internet access and a reachable notification service. Remote Web UI access through Tailscale requires a working Tailnet connection.
- One job at a time, MAC cooldown, cancellable; jobs never replay after a reboot.
Security
Remote commands are off by default. Restrict Telegram commands to your configured chat and ntfy publishing to a private authenticated topic. Use TLS and restrict command topics when using MQTT. Guides: Smart Recovery, NAS recovery checklist.