Understand what continues when the internet connection is lost

What can still work

If the internet is down, some installed schedules and local sensor routines can keep running on their assigned hub when the hub clock, installed version and supported local inputs are still available. A routine with cloud steps may continue only in part. Local effects can continue while cloud effects stay unavailable. The routine does not move to another executor just because the internet is lost.

Commissioned local devices can keep their local transport. That does not mean a disconnected app or web page can send a new command. A hosted app or web request still needs its WAN service path. A self-hosted API needs the actual local network path and a current authenticated session.

Stored settings and local observations can still be present, but they keep their original age and authority. If data is missing or old, treat it as unknown. It does not prove that a device is off or that nobody is home.

Voice, music and announcements

Local microphone wake detection can continue even when a full voice turn is unavailable. Recognition, reasoning, speech synthesis and speaker playback have separate connection and processing needs. Local wake alone does not prove that the whole voice interaction completed locally.

Music and announcements depend on reachable local media or speaker paths. Cloud synthesis and streaming need their own service paths. Cloud-only devices, cameras and streaming services still depend on their third-party cloud services.

When service returns

When the connection recovers, ALYT keeps the last valid configuration, refreshes state and checks the original action records. It does not repeat an expired button press or replay an uncertain transmitted action.

Read fresh device evidence before you treat an unknown or partial result as confirmed. If microphone consent needs to change, use the current Owner settings when that service path is reachable.

How to check your home

1. Check hub power, local device connection and your own internet connection separately.
2. Open Devices and inspect the affected device when your normal service path is available.
3. Record the home, device, time, expected change and observed reading if you need Support.
4. Keep existing installed routines and credentials intact. Do not re-enrol a working home just because the hosted interface is disconnected.

Troubleshooting

• If a local routine stopped, check the hub clock, installed version and local sensor inputs first.
• If a command did not send, confirm whether the app or web page still has its WAN service path or whether you are using a self-hosted API that needs the local network path and a current session.
• If a reading looks old, treat it as stale information until you refresh the device view.
• If voice wake works but speech does not, check the local media or speaker path and any cloud service the turn depends on.