Basic Do Not Disturb in Home Assistant Without YAML

This article may contain affiliate links. If you buy through these links, the price is the same for you and the store pays me a small commission that helps keep Tecnoyfoto running.

Albert BarnosellEditor and publisher of Tecnoyfoto

After publishing my advanced Do Not Disturb system, several people who were just getting started with Home Assistant asked for a simpler version. This guide answers that request: build a basic Do Not Disturb mode entirely in the visual interface, without editing YAML.

By the end, you will have a virtual toggle, a start time, an end time, and two automations that enable and disable quiet mode every day. You can then add one condition to each non-essential announcement you want to suppress during those hours.

Result: Home Assistant automatically silences only the announcements you choose.

Video: basic Do Not Disturb step by step

The video below shows the complete process in the real Home Assistant interface. The narration is in Spanish, while this English guide contains every step, clarification, and limitation in writing.

What you are going to create

• A Toggle helper named Basic Do Not Disturb.
• A time helper named Basic Do Not Disturb start.
• A second time helper named Basic Do Not Disturb end.
• An automation that turns the toggle on at the start time.
• Another automation that turns it off at the end time.
• A condition that blocks only non-essential announcements.

Helpers are virtual entities. A Toggle helper stores an on or off state, while Date and time helpers store the adjustable times used by the automations.

1. Create the Do Not Disturb toggle

1. Open Settings → Devices & services → Helpers.
2. Select Create helper.
3. Choose Toggle.
4. Name it Basic Do Not Disturb and save it.

This toggle is the center of the system. On means that selected announcements must remain quiet; off means that they may run normally. Adding an icon is optional and does not affect the logic.

2. Create the start and end times

Create two more helpers. Choose Date and/or time for both and enable time only, not date.

• Basic Do Not Disturb start: when quiet mode begins.
• Basic Do Not Disturb end: when normal announcements resume.

For example, set the start to 10:00 PM and the end to 7:00 AM. Because these are helpers, you can later change either time from your dashboard without editing the automations.

3. Put the controls on your dashboard

This step is optional but convenient. Edit the dashboard where you want to control the system, add an Entities card, and include all three helpers. You can then enable quiet mode manually or adjust its schedule in seconds.

A manual override lasts until the next scheduled boundary. If you turn it on in the afternoon, for example, the end automation will still turn it off at the configured time.

4. Create the automation that enables quiet mode

1. Go to Settings → Automations & scenes.
2. Select Create automation → Create new automation.
3. Under When, add a Time trigger.
4. Choose the value of a date/time helper and select Basic Do Not Disturb start.
5. Under Then do, target Basic Do Not Disturb and choose Turn on.
6. Save it with a clear name such as Enable Basic Do Not Disturb.

Choose Turn on, not Toggle. A fixed action prevents an unexpected previous state from producing the opposite result.

5. Create the automation that disables quiet mode

Create a second automation in the same way, changing only two elements:

• The trigger uses Basic Do Not Disturb end.
• The action on the toggle is Turn off.

Name it Disable Basic Do Not Disturb. Automations created in the visual editor become active as soon as they are saved; you normally do not need to reload automations or helpers.

6. Apply Do Not Disturb to an announcement

The toggle does not silence anything by itself. Add it as a condition to each automation whose announcement you want to stop. Imagine an automation that announces through a speaker whenever the front door opens.

1. Open that automation.
2. In the And if section, select Add condition.
3. Choose a state condition and select Basic Do Not Disturb.
4. Require the toggle to be Off.
5. Save the automation.

When the door opens, Home Assistant checks the toggle first. If it is off, the announcement runs. If it is on, the condition fails and the action is skipped. Conditions are evaluated after a trigger fires and before actions run.

Do not add this condition to smoke, water-leak, security, or other alerts that must wake you.

7. Test it without waiting until tonight

1. Leave the Basic Do Not Disturb toggle off.
2. Temporarily set the start helper one or two minutes ahead of the current time.
3. Wait and confirm that the toggle turns on automatically.
4. Set the end helper to the following minute and confirm that it turns off.
5. Restore your final schedule.

If the test fails, confirm that both automations are enabled, each one references the correct helper, and the actions are Turn on and Turn off. Automation traces show which trigger fired, which condition was evaluated, and where a run stopped.

What this setup does and does not do

• It does: maintain an automatic quiet state with an editable schedule.
• It does: let you choose which automations respect that state.
• It does: work with Alexa, Google, speaker, or phone alerts when their automation includes the condition.
• It does not: enable the Do Not Disturb setting on your phone.
• It does not: decide which alerts are urgent.
• It does not: replay a time trigger that occurred while Home Assistant was offline.

That last point is a limitation of the basic approach. If Home Assistant was not running at the exact trigger time, the state may remain wrong until the next scheduled change. This is usually acceptable for a simple home setup, but critical systems need more robust recovery logic.

Basic or advanced: which version should you use?

If this version becomes too limited, continue with my advanced Home Assistant Do Not Disturb system. It covers urgent exceptions, shift-based schedules, a central voice-announcement system, and volume control.

Frequently asked questions

Does this method require YAML?

No. You create the helpers, automations, and condition in the Home Assistant visual interface.

Can I enable Do Not Disturb manually?

Yes. Turn the helper on or off from your dashboard. The next time trigger will apply the scheduled state again.

Does it silence every Home Assistant notification?

No. It blocks only the automations where you added the condition requiring Do Not Disturb to be off.

Does a schedule that crosses midnight work?

Yes. One daily automation enables quiet mode at night and the other disables it the following morning.

Conclusion

You do not need to begin with a large notification framework. Three helpers, two automations, and one condition are enough to stop normal Home Assistant announcements during the night. The setup is easy to understand, controlled from the dashboard, and ready to grow when you need advanced exceptions.