Local. Even when the internet takes a break.

The intelligence stays at home.

We plan core functions to run on site wherever possible. Home Assistant runs on local hardware. Suitably connected sensors, switches and devices can communicate with the controller without sending every command through a manufacturer’s cloud.

The benefit becomes clear when the internet connection fails: local routines can keep working, provided the controller, power supply and required local connections remain available.

Local means checking every connection.

Putting a cloud function on a shared dashboard does not make it local. For each important function, we check where it runs, what it depends on and what happens during an outage.

• On site: Suitable lighting control, local scenes and sensor-based routines can run without the internet.
• With the internet: External weather data, online services and access while away need a connection, depending on the solution.
• With a fallback: Useful manual controls, defined fallback values and clear indications when devices are unavailable.

Access from outside? Only if you want it.

Your home is not a public control panel. External access is set up deliberately and only by agreement. Personal accounts, strong unique passwords, multi-factor authentication and carefully limited administrator rights are part of our planning. Support access is an agreed permission, rather than a quiet master key.

Nabu Casa: encrypted access, without port forwarding.

One option is Nabu Casa’s optional remote-access service. Your local controller establishes an outgoing connection itself. This does not require incoming port forwarding on the router.

According to Nabu Casa’s documented security architecture, remote access remains end-to-end encrypted between your device and your Home Assistant controller. The connection uses TLS and a Let’s Encrypt certificate; the private key is stored on your local controller. Relay servers pass the encrypted data along.

There is a difference between reachable and controllable. When remote access is enabled, the sign-in page may be reachable over the internet. That does not make the controls freely accessible. An address alone does not give anyone permission to join in: authentication, multi-factor protection, suitable permissions and ongoing updates are what matter.

Remote access is disabled by default and can be switched off again. Allowing it to be reactivated from outside is a separate setting that we agree deliberately. Nabu Casa’s optional service requires its own subscription; local control does not need that subscription.

The provider explains the technical principles: Nabu Casa security architecture and How remote access works. See also: Recommendations for securing Home Assistant.

No internet is not the same as no power.

These are different situations. A suitably planned uninterruptible power supply can keep selected components running temporarily. It does not make the whole building self-sufficient or replace normal electrical and safety planning.

An open foundation. Clear responsibility.

Open source enables transparent, adaptable solutions. We combine that foundation with planning, configuration, testing and clear documentation. Optional cloud services remain a deliberate choice, rather than a blanket requirement for every function.

At handover, we demonstrate which agreed routines work offline. Dependencies and recovery after an interruption are documented.

More about the underlying principle: Home Assistant without an internet connection.

Remote access is an option. It is not a requirement.
If you do not need it, it stays off. Suitable local functions keep running without the internet. Your lights should not clock off just because the internet does.