Draw a small dependency map
Choose three everyday actions, such as turning on a lamp, opening a camera view and running an evening routine. For each, note the device, controller or bridge, network connection and app or service involved. A few named boxes and arrows are enough to reveal that different actions take different routes.
A physical button might send a command locally, while a voice request travels through an online service. The same lamp can therefore respond through one method and fail through another. Describing the whole lamp as either online-only or offline-capable can hide this useful distinction.
Separate three kinds of failure
An external internet interruption can leave the home's Wi-Fi and wired network running. A router being switched off can remove those local connections as well. A wider power cut can stop the router, bridges and mains-powered accessories together. Battery-operated sensors do not make the rest of their control chain battery-powered.
Before testing, choose a safe, nonessential action such as a table lamp. Tell others what you are doing, and avoid disrupting equipment they depend on. Do not use locks, heating, alarms or other consequential devices as a casual outage experiment.
If you cannot interrupt only the external connection without affecting other services, rely on the manufacturer's documented behaviour and arrange a better-controlled test later. Unplugging random cables is not a useful substitute. It may also remove telephone or other services supplied through the broadband equipment.
Check each control route
With the local network powered but internet unavailable, try the supported local app control, physical controller and automation separately. Make sure the test phone remains on the home network; mobile data can give its app an external connection and make the result harder to interpret. Record exactly what succeeded and what failed.
Matter provides local connectivity, but services built around a Matter device can still have online dependencies. Likewise, a Wi-Fi accessory is not automatically cloud-only. TP-Link documents local control for certain Tapo plugs while distinguishing the requirements of Smart Actions. Use the exact model's support page rather than inferring behaviour from the radio technology alone.
Try the action again after restoring internet access. A routine that works while already configured may behave differently after equipment loses power and must recover its time or connection. If the manufacturer describes such a limitation, include it in your household notes.
Treat cameras as a separate question
For a camera, ask three questions: can it record, where does that recording go, and can you view it at that moment? These are not interchangeable. Some models can store a limited amount of footage while offline and upload it later. Others require a separate recorder or have no useful offline recording arrangement.
Google's documentation distinguishes offline recording by supported Nest models from the inability to record when a camera has no power. That is a model-specific capability, not a reason to assume another camera retains events. Check capacity, power and playback restrictions in the relevant manual.
Do not promise yourself continuous coverage based on a battery icon or a memory-card slot. Confirm whether the selected recording mode uses that storage and what happens when it fills. If the camera is needed for a particular purpose, its actual gaps matter more than an optimistic product-category label.
Keep ordinary tasks ordinary
Make sure people can still turn on useful lighting without reconstructing the network. Keep physical controls obvious and explain their limits. A printed note identifying the hub and router can help somebody restore a switched-off power supply without resetting devices unnecessarily.
Avoid using factory reset as the first response to an internet outage. Resetting can erase a working configuration and create a setup job while the required service is still unavailable. Check power and service status first, then follow the manufacturer's recovery process if a device remains unresponsive after connectivity returns.
Update the dependency note when you add a controller or change a routine. The goal is not to make every feature survive every failure. It is to know which useful actions remain available, which temporarily disappear, and how the household can carry on without guesswork.
