Home Assistant guides for advanced home automation

Home automation has taken a giant leap forward in recent years, and Home Assistant has positioned itself at the heart of this change. More and more homes are running on automation systems, sensors, and connected devices, but what makes the difference isn't just the hardware, but how you control and integrate everything conveniently, securely, and, ideally, without relying on the cloud.

In this article you will find a complete and very practical guide based on two key pillars of the ecosystem: My Home Assistant (the universal linking system) and task lists. todo These serve as the engine for smart automations. We'll see what they are, how they work, how they differ from Home Assistant Cloud, how to create links, how to use local task lists and those connected to external services, and several real-world examples of automations that you can copy and adapt to your home.

My Home Assistant: the secure bridge between the web and your instance

My Home Assistant is a service designed to simplify life for anyone using Home Assistant by connecting documentation, forums, blogs, and tutorials to your own instance, without compromising your privacy or exposing your system to the outside world. The idea is very simple: you click a link on a website, and the corresponding screen opens in your Home Assistant.

Imagine you're reading a guide about a new integration and you come across a button like "Add this integration to my Home Assistant." Clicking it doesn't open a generic wizard, but rather the configuration form for that integration directly on your server. That's exactly what My Home Assistant does, acting as an intermediary that simply redirects to your instance's URL.

The most interesting thing is that My Home Assistant isn't a typical cloud service ; it doesn't save your settings, connect to your home, or manage your devices. It only knows the address to send you to, and little else. It's a layer of convenience on top of your setup, not a remote system that intrudes on your network.

This minimalist and privacy-focused philosophy is what has made it an indispensable tool for the community: it allows you to share guides, blueprints, dashboards, or configuration screens without forcing anyone to expose their server or depend on third parties.

How My Home Assistant works inside

The inner workings of My Home Assistant are as simple as they are ingenious.The first time you click on a link like this... https://my.home-assistant.io/...The service asks you to enter your instance URL: it might look something like http://homeassistant.local:8123, the local IP, or a remote domain if you have it configured, for example the one Nabu Casa gives you.

That address is stored exclusively in your browser's local storage ; it's neither uploaded to external servers nor associated with an account. This way, the service knows where to redirect you without having to store personal data or information about your home network. If you change browsers or devices, you'll have to enter the URL again, precisely because there's no copy in the cloud.

When you click on another link in My Home Assistant , the server checks what type of action you want to perform (adding an integration, opening logs, importing a blueprint, going to a specific dashboard, etc.) and internally generates the appropriate URL using your saved domain. It then seamlessly redirects you to the exact screen within your Home Assistant.

A key security feature is that My Home Assistant never performs actions on its own . Even if a link points to, for example, importing a blueprint or configuring a device, you make the final decision within the Home Assistant interface. There is no way a link on a website can turn off lights, open doors, or change settings without your explicit confirmation.

This design, based on redirects and user confirmation, prevents basic attacks such as malicious links attempting to launch sensitive services. You will always see the corresponding screen and will have to accept, save, or confirm within your own system.

Differences between My Home Assistant and Home Assistant Cloud (Nabu Casa)

It's very common to confuse My Home Assistant with Home Assistant Cloud , but they are actually very different services with almost opposite goals. One focuses on making navigation and setup easier; the other on offering remote access and simplified voice functions.

Home Assistant Cloud, managed by Nabu Casa, is a subscription service that provides a secure URL of the type https://xxxxx.ui.nabu.casa To access your instance from outside your home without opening ports, and easily integrate voice assistants like Alexa or Google Assistant. It's the "headache-free" option for those who want remote control without dealing with certificates, DNS, or routers.

My Home Assistant, on the other hand, is completely free and doesn't give you remote access . It only works with the URL you already have (local or remote). If your instance is only accessible within your network, My Home Assistant links will work as long as you're connected to that same network, but not magically from anywhere in the world.

To make it clearer, you can keep this idea in mind : My Home Assistant is a generator and manager of smart links to your Home Assistant; Nabu Casa is an encrypted tunnel and a package of optional cloud services for you to reach your instance from outside and connect it with external platforms.

Feature	My Home Assistant	Home Assistant Cloud (Nabu Casa)
Principal function	Redirecting links to your instance.	Secure remote access and support for voice assistants.
Ribs	Gratuitous.	Monthly paid subscription.
Remote access	It does not provide remote access on its own.	Yes, via encrypted URL without opening ports.
Privacy policy	The instance URL is saved only in the browser.	End-to-end encrypted traffic in the Nabu Casa cloud.
typical use	Configure integrations, import blueprints, open views.	Control your home remotely using Alexa/Google Assistant.

Real-world use cases for My Home Assistant links

Where the value of My Home Assistant is truly appreciated is in everyday use , when you're reading documentation, browsing forums, or following a tutorial, and with a single click, you jump to the exact section of your interface you need.

One of the most common examples is importing blueprints . Instead of copying and pasting YAML from the official forum, the author usually adds an "Import into Home Assistant" button. Clicking it opens the blueprint import screen for your own instance, with the URL and parameters already set up.

It's also very useful for technical support . If someone is helping you in a forum or Telegram group, they can share a link that opens the "Devices and Services" page, the "Logs" section, or a specific Developer Tools panel. This way, you don't have to go through each menu trying to find what's there.

The official Home Assistant documentation makes excellent use of these links , especially in the integrations section. Instead of saying "go to Settings > Devices & services > Add integration > Search for this name", they simply provide a link that already includes the integration identifier, making the entire process much more straightforward.

Another interesting use is sharing Lovelace dashboards or specific views with other users in your household. You can create links that point to a particular panel (for example, the weather or entertainment panel) and share them so your family members can go directly to the view they're interested in, without getting lost among cards and menus.

How to create your own links with the My Home Assistant generator

If you create content, share automations, or simply want custom shortcuts , the official My Home Assistant shortcut generator is your best friend. No programming knowledge is required; just choose what you want the shortcut to do from a few menus.

The first step is to go to the link building page, available in https://my.home-assistant.io/create-link/From there you will see a very simple wizard with a drop-down menu listing the supported actions: open the integrations page, import blueprints, go to a specific dashboard, open a settings panel, etc.

When you choose the action, the generator will show you additional fields. depending on your selection. For example, if you choose “Add integration”, you will need to specify the integration domain (something like shelly, hue, mqttetc.). If the link is for a Lovelace dashboard, you will be asked for the specific path to that dashboard.

Once you've filled in the information, the tool generates a ready-to-use link and a small snippet of HTML code with a badge that you can paste into your blog or forum. This way, you not only have the URL, but also a visually appealing button that readers can click.

The result is a universal link that adapts to each user : it doesn't matter if your Home Assistant is on a local IP, on your own domain or using Nabu Casa, because My Home Assistant will take the URL saved in your browser and redirect you correctly.

The service call interface: a lab for your automations

Within Home Assistant, the service call interface has become the standard for testing actions, adjusting automations, and debugging scripts. You'll find it under Developer Tools > Services , and it's essentially a panel where you can launch any service available on your system.

The beauty of this interface is that you no longer need to memorize the YAML syntax. to run a quick test. You select the service from a dropdown menu (for example, light.turn_on), you choose the entity or device you want to affect and the interface itself offers controls to fill in the necessary data.

If you work with lights, you'll see options for brightness, color, color temperature , and other parameters in sliders, color pickers, checkboxes, etc. You adjust what you want, and when you press the run button, the service launches instantly on the chosen entity—ideal for fine-tuning the behavior before incorporating it into an automation.

This same visual layer is reused in the automation and script editor , so when building an automation, you're not blindly inventing parameters, but rather using the same forms and controls. If you're old school and more comfortable with YAML, you can always switch to advanced mode and edit it manually, combining the best of both worlds.

For beginners, this interface is a kind of testing ground where you can see in real time what each service does, what parameters it supports, and how your system responds. Once you understand it, you encapsulate it in automations, scripts, or blueprints so it runs automatically.

Veteran features that are now essential in Home Assistant

Many of the features we now use without thinking emerged years ago and have matured into fundamental components of the ecosystem. Some, like zone control or percentage-based fan control, completely changed how we organize and manage our homes.

Home Assistant's "Areas" are a good example . They allow you to group devices and entities into logical zones of your home: living room, kitchen, bedroom, garage, etc. Thanks to them, you can create automations that apply to an entire area without struggling with endless lists of specific entities.

Another important change was the shift from fixed fan modes (low/medium/high) to percentage-based speed control between 0 and 100. This made devices from very different brands behave consistently and greatly facilitated integration with ecosystems like HomeKit, which rely precisely on this type of standardized control.

In the field of radio frequency, the transition to Z-Wave JS marked a turning point . This integration, which initially progressed at a frenetic pace, has become the official and recommended solution for Z-Wave devices, providing stability and advanced features.

Meanwhile, the Zigbee ecosystem has strengthened with ZHA and Zigbee2MQTT , which dominate a large portion of current installations. Combined with Home Assistant, they allow for the creation of very robust, fully local networks of sensors, lights, and actuators, independent of the manufacturer's servers.

Home Assistant guides for a 100% local home with no fees

Beyond the specific tools, many modern Home Assistant guides share the same philosophy : regaining control of the smart home, minimizing dependence on the cloud, and escaping monthly subscriptions that accumulate without you noticing.

The idea is simple: build a completely self-hosted home automation hub , typically on affordable hardware like a Raspberry Pi, small mini PCs, or even virtual machines on a home server. This hub runs Home Assistant OS or a supervised installation that centralizes all the devices.

You don't need to be a system administrator to get started , but you do need to be willing to experiment a bit. Well-structured guides are aimed at the advanced home user who values ​​privacy and local control, and they usually include step-by-step instructions for installing the system, configuring the network, and adding your first devices.

One of the cornerstones of this approach is network isolation . Many configurations recommend separating IoT devices into a specific VLAN or subnet, limiting their internet access, and allowing communication only with the Home Assistant server. This keeps your data within your network and reduces the risk of an insecure device becoming a problem.

The great advantage of setting up a system like this is that you decide the rules : what data goes external (if any), what integrates with Alexa or Google Assistant, and what stays strictly local. You don't depend on a company shutting down servers or changing its terms of service for your home to keep working.

Hardware integration: Z-Wave, Zigbee and more in a single hub

Any serious guide on Home Assistant will eventually touch on the topic of hardware . For a stable, low-latency network, the leading protocols remain Z-Wave and Zigbee, each with its own characteristics but both highly geared towards home automation.

Typically, a USB stick or gateway is used as a coordinator . In Zigbee, this can be a coordinator based on chips from Texas Instruments, Silicon Labs, or others; in Z-Wave, it's an adapter compatible with Z-Wave JS. You connect this stick to the server running Home Assistant and integrate it through the official integrations (ZHA, Z-Wave JS, Zigbee2MQTT, etc.).

A well-designed integration gives you a robust wireless mesh network , where each plugged-in device acts as a repeater for the others, extending the range and providing redundancy. This is key if you want your lighting, door and window sensors, or climate control to respond instantly.

Another essential feature is a dedicated troubleshooting and maintenance section . It's advisable to regularly review logs, update Home Assistant and integrations, and familiarize yourself with basic procedures: how to create backups, what to check if a stick stops responding, or how to re-pair a troublesome device.

With this preventative approach, your home automation hub can operate reliably for years , without you having to constantly put out fires. It's a little initial work in exchange for a lot of peace of mind in the long run.

Task lists in Home Assistant: more than just “buy milk”

To-do lists have evolved from a simple paper reminder to become a key component within Home Assistant. The entity todo It's not a minor gadget: when used correctly, it becomes a true automation engine for home management.

The "to-do list" type entity is identified with the domain todoUnlike a sensor or a switch, its state isn't "on" or "off," but rather the number of pending tasks it contains. For example, if your "Shopping List" has three unfinished items, the state will be 3.

Internally, each entity todo stores a collection of itemsEach task has its own status (completed or pending action) and other attributes. This allows you not only to visualize what remains to be done, but also to interact with the list through services: adding, modifying, or deleting tasks from automations or scripts.

This design makes to-do lists perfect for automating maintenance , recurring purchases, service reminders, or anything else you can describe as a task. The number of pending items then becomes a signal that your automations can use as a trigger or condition.

How to create and manage local to-do lists

Local lists are the simplest and most private optionBecause all data is stored solely within your Home Assistant instance. The classic example is the built-in shopping list, which is now based precisely on this entity system. todo.

To create your first local to-do list , you'll typically go to Settings > Devices and services and open the Helpers tab . From there, you can add many types of helpers, including a "To-Do List."

Clicking on “+ CREATE ASSISTANT” will show you a list of available types . Choose the task list option, enter a clear name (for example, “Household Chores”, “Weekly Maintenance” or “Shopping List”) and, if you want, assign an icon to help you quickly recognize it in the interface.

Once created, the list will appear in the sidebar and you can manage it manually : add items, mark them as completed, delete them, reorder them, etc. You can also add a "To-do list" card to your Lovelace dashboards to keep it readily available.

The advantage of local lists is twofold: they are very fast and completely offline . As long as your Home Assistant is turned on, they will work even if your internet connection drops, and no one but you will have access to that data, because they are not synchronized with any external service.

Connect Home Assistant with Todoist and Google Tasks

If you already use Todoist or Google Tasks daily , it might make more sense to integrate them than to duplicate the information in local lists. Home Assistant handles reading and writing to those lists, while you continue using the official apps on your phone or browser.

The integration process is very similar for both services . From Settings > Devices and services , tap + ADD INTEGRATION and search for “Google Tasks” or “Todoist” in the catalog of available integrations.

When you select the integration, an authentication flow opens where you'll need to grant Home Assistant permission to access your Google or Todoist account. This is usually done via OAuth, so you'll see an official page from the provider asking for confirmation.

Once the process is complete, each list from the external platform appears as an entity todo within Home Assistant. For example, your main Todoist list might be displayed as todo.todoist_principal, ready to be used in automations, scripts and interface cards.

The great advantage of this integration is that you get the best of both worlds : you have the native apps of Todoist or Google Tasks, with their notifications and widgets, and at the same time you can trigger Home Assistant automations based on what's in those lists or modify them from your rules.

Local lists vs external integrations: which to use in each case

Choosing between local lists and external services depends largely on your workflow . There's no single right answer, but each approach has clear advantages that you should consider before building all your automations around one or the other.

Local lists are far superior in terms of privacy and network dependence . Your data stays on your server, doesn't require internet access to function, and the only requirement is that Home Assistant is active. If you're concerned about your data being exposed or want a system that can withstand a fiber optic outage, this is usually the best option.

The integrations with Todoist and Google Tasks shine in terms of usability and ecosystem . They offer dedicated apps for mobile, desktop, and web, with reminders, advanced filters, projects, tags, and custom views. If you already use them daily, integrating them with Home Assistant adds a layer of automation without requiring you to switch tools.

In terms of automation power, both options offer the samebecause they end up exposing entities todo with the same services available: adding items, updating them, marking tasks as completed, deleting, etc. The real difference lies in where the data is stored and how you manage it outside of Home Assistant.

Feature	Local lists	Todoist / Google Tasks
Privacy policy	Data only on your server.	Data in the provider's cloud.
Operation without internet	In short, as long as HA is on.	Limited, requires online synchronization.
Applications and ecosystem	Home Assistant interface only.	Native apps, widgets, extensions, etc.
Automation capability	Same logic with entities todo.	Identical list of services.

Examples of automation using task lists

When you combine the entities todo with sensors, schedules and presence statusesReally useful workflows start to emerge. It's not just about remembering things, but about the system anticipating needs and helping you with home maintenance.

A classic example is the regular maintenance of equipment . You can schedule tasks to be added to a "Household Chores" list at regular intervals so you don't forget to clean filters, check sensor batteries, change reservoirs, etc. A typical example would be automatically generating the task "Clean air conditioner filters" every three months.

Another very practical example is linking sensors to your shopping list . If you have a smart dishwasher or washing machine that reports the salt, detergent, or rinse aid levels to Home Assistant, you can create an automation that adds "Buy dishwasher salt" when the sensor indicates a low level.

To-do lists also work very well with contextual reminders.For example, you can use presence (entities) person) to send a notification to your mobile phone when you leave home on a garbage collection day and the task "Take out the garbage" is still pending on your "Household Chores" list.

The general idea is to automate repetitive tasks : the system detects conditions (date, time, sensor status, presence), updates lists, and notifies you or performs actions without you having to manually record everything. Little by little, your home anticipates what you know will be needed.

Combining all of the above —My Home Assistant, lists todoExternal integrations, Z-Wave, Zigbee, and network best practices— You can build a home automation system that is not only powerful and flexible, but also private, stable and free of monthly fees, with automations that truly adapt to your lifestyle at home.