Problem/Motivation

Introduced in: home-assistant/core#37975 (part of Home Assistant 0.114).

Before:

automation:
  - alias: time trigger
    trigger:
      - platform: time
        at: "05:00:00"
      - platform: time
        at: "06:00:00"
      - platform: time
        at: "10:00:00"
    action:
      choose:
        ...

After:

automation:
  - alias: time trigger
    trigger:
      - platform: time
        at:
          - "05:00:00"
          - "06:00:00"
          - "10:00:00"
    action:
      choose:
        ...

Or:

automation:
  - alias: time trigger
    trigger:
      - platform: time
        at: ["05:00:00", 06:00:00", "10:00:00"]
    action:
      choose:
        ...

Proposed changes

Update all automations with multiple time conditions and merge those triggers into a single trigger.

ℹ️ Still need to thing about this all a bit more

Problem/Motivation

I need a rewrite of the Circadian Lighting.

While that custom integration is awesome, it does have its fair share of issues.

For example:

• It can only be configured via YAML.
• Every light or group of lights gets/needs its own circadian light switch.
• The switch toggle the automated lighting adjustments on the lights by the custom integration.
• The entity ID of the switches is not manageable (see: claytonjn/hass-circadian_lighting#18)
• When circadian light is switched on, it causes a lot of issues when turning lights off. This is well documented: https://github.com/claytonjn/hass-circadian_lighting/wiki/Frequently-Asked-Questions#q-why-cant-i-turn-off-my-lights-after-configuring-them-with-circadian-lighting. Worst part:

  Unfortunately, there's no good solution to this.

I think the custom integration is sub-optimal, mainly because of large configuration overhead and the last point, causing my lights not to turn off from time to time, which just sucks.

Proposed changes

The main problem with the circadian lighting integration is the "magic" / automatic handling/control of lights. I'd rather have a service available to manually set a light(s) to the current circadian rhythm.

The advantage of having a service for this, would be:

• No shitload of additional entities to manage
• Can easily decide for each light(s) when to apply the current rhythm, using simple automations
• All features automations have, e.g., with checking conditions apply. This removes the issue with manual control/overrides and turning lights off.

Implementation

• Simple integration that can be added via the UI.
• Provides sensor entities for the values from the circadian rhythm.
• Provides a single service call.
• Should determine ct/rgb/xy or brightness only to use based on the feature set of a light

Considerations

• Provide an options in the integration UI, to set global:
  • Min/max brightness
  • Min/max color temp
  • Sunset/Sunrise offsets
  • Update interval for the sensors
  • Default transition value
  • Initial transition when light goes from off -> on

Service call circadian.apply

Simple service call that accepts lights to adjust to the current state of the circadian rhythm.

Example automation

Simple example:

description: Adjust rhythm of garden light
alias: garden_automatic_lighting
id: f59ff023-a412-41b2-946f-8ea05da26c2f
mode: single
trigger:
  - platform: state
    entity_id:
     - light.garden_dining_table
     - sensor.circadian
condition:
  - condition: state
    entity_id: 
      - input_boolean.garden_automatic_lighting
      - light.garden_dining_table
    state: 'on'
action:
  - service: circadian.apply
    entity_id: light.garden_dining_table

I have to be able to cope with the different situations at home, which are out of the ordinary.

Introduce a mechanism that allows me to put the house into:

• Cleaning mode
• Vacation mode
• Guest mode

These states put the system into different behavior. For example, guest mode would influence the (future) presence detection, cleaning mode might disable tons of automations and turn on all to lights (in a bright white color).

Have you thought about how the recent change to push towards embedded platforms will change your structure? home-assistant/core#19948

Problem/Motivation

The Verisure integration for Home Assistant is a pretty old school one. It need to update it in order to get to its full potential.

Right now, it is configured via YAML and more importantly, the entities lack an unique_id. This causes I cannot rename (both in terms of name, icon and entity ID) and thus not fit my naming schema. It is possible to grab unique IDs from Verisure.

References

• Integration Documentation: https://www.home-assistant.io/integrations/verisure
• Integration source: https://github.com/home-assistant/core/tree/dev/homeassistant/components/verisure
• Python library: https://github.com/persandstrom/python-verisure
• API Specifications: https://github.com/Cebeerre/VerisureEUAPI

Homeassistant[customize] not loading properly as a package.

What you expected to happen

https://github.com/frenck/home-assistant-config/blob/master/config/integrations/homeassistant.yaml
Should load the customizations for entitites on the customizations/entities folder

What actually happened)

Customizations not beeing applyed at all

How can someone else make/see it happen

Just load a config with that and add a customization to a entity file on customizations/entities

How will it actually work

homeassistant:
  packages: !include_dir_named integrations
  customize: !include ../customize.yaml

Problem/Motivation

I have live data from our boiler, including the use of hot tap water.
The boiler only supplies hot water to our shower, so this provides a great way to know if someone is in the shower.

Proposed changes

Ensure the central ventilation is turned on as soon / as long there is hot tap water usage.

Does the split !include trick work for dashboards? I saw your example of it for automations, but can't seem to get it working for a yaml dashboard view to load cards from 2 places.

#from your autmoation integration yaml:
automation: !include ../automations.yaml
automation split: !include_dir_list ../automations

#what I want to do in my dashboard view, but it doesn't work:
cards: !include cards.yaml #file contains a list of includes to common cards I share between views
cards split: !include_dir_list ../cards/view1 #folder of cards for this dashboard

#alternative that I like better because 1 less file, but it doesn't work either:
cards:
  - !include ../../common/cards/test.yaml
  - !include ../../common/cards/test2.yaml
cards split:  !include_dir_list ../cards/view1

#also tried this, both with and without the hyphen on the 3rd item:
cards:
  - !include ../../common/cards/test.yaml
  - !include ../../common/cards/test2.yaml
  - !include_dir_list ../cards/view1

#This is viable, if I do a lot of individual stub files that each just !include the common cards.
#That's a lot of tiny files that feel unnecessary
cards: !include_dir_list ../cards/view1

#This is also viable, if I individually !include every card I want.
#It's not dynamic like the !include_dir_list, but it does give me better control of the card order.
cards:
  - !include ../../common/cards/test.yaml
  - !include ../../common/cards/test2.yaml
  - !include ../cards/view1/card1
  - !include ../cards/view1/card2

Related question: how do you control the card order when you use !include_dir_list? Are they alphabetical by file name?

Problem/Motivation

I've recently received a Xiaomi Curtain rail for the hall for testing. General goal: If this works and we like it, to buy more of them in other places around the house.

Tasks still to do:

• Add a small hook to the right side of the motor, so the curtain can be attached to that. Covering the motor from being visible.
• The device is currently paired to a Xiaomi Gateway in order to get the curtain motor calibrated / aware of the length of the rail. Needs to be unpaired and paired with ZHA.
• Make sure calibration is still OK after repairing on ZHA.
• Expose the curtains to Google Assistant.
• Expose the curtains to HomeKit.

Automations:

• Automatically open the curtains at 8:10 every day, except on Saturday 10:00. Sundays or holidays, the curtains will remain closed and not open automatically.
• Automatically close the curtains at 19:00 every day.
• Automatically close when the alarm is armed, do not open when the alarm is armed.
• If the front doorbell rang and motion is detected in the hallway right after that (e.g., a 1 minute time window) -> Open the curtains.
• Close curtains if hall occupancy is clear and the curtains should be closed normally at the current time (see above).

Other improvements idea:

• Add a Xiaomi door sensor to the front door. If the door would be opened from the outside, it can quickly open the curtains. Also, allows preventing the curtains from being closed while the door is open.

Problem/Motivation

Automatically check ESPHome configuration against the available ESPHome version using GitHub Actions.

This is currently done by GitLab CI, which I want to move away from.

Attempt done in: 7f54c3a

Unfortunately, that failed:

Not sure why yet, removed it for now, created this issue to take a look later.

wrong place :)

I've adopted your substitution/include strategy. Sadly as part of the process I "lost" the OTA password. Is there a way to upload the new firmware short of opening the device and using the serial interface? I don't exactly understand the various fallback mechanisms.

Thanks!

is the hassio:~ still needed?

I don't have it and I have the supervisor panel enabled.

https://github.com/frenck/home-assistant-config/blob/master/config/integrations/hassio.yaml

Here's the Weekly Digest for frenck/home-assistant-config:

ISSUES

Last week 1 issue was created.
It is closed now.

CLOSED ISSUES

❤️ #41 ✨ Add ESPHome config check to CI, by eliseomartelli

LIKED ISSUE

👍 #41 ✨ Add ESPHome config check to CI, by eliseomartelli
It received 👍 x1, 😄 x0, 🎉 x0 and ❤️ x1.

NOISY ISSUE

🔈 #41 ✨ Add ESPHome config check to CI, by eliseomartelli
It received 1 comments.

PULL REQUESTS

Last week, 1 pull request was created, updated or merged.

MERGED PULL REQUEST

Last week, 1 pull request was merged.
💜 #41 ✨ Add ESPHome config check to CI, by eliseomartelli

COMMITS

Last week there were 5 commits.
🛠️ 🚑 Fix double checkout in ESPHome CI by frenck
🛠️ Fix ESPHome CI by frenck
🛠️ ✨ Add ESPHome config check to CI (#41) by eliseomartelli
🛠️ ⬆️ Upgrade Home Assistant to 0.114.0.dev20200729 by frenck
🛠️ ⬆️ Upgrade Home Assistant to 0.114.0.dev20200723 by frenck

CONTRIBUTORS

Last week there were 2 contributors.
👤 frenck
👤 eliseomartelli

STARGAZERS

Last week there were 8 stagazers.
⭐ fabiosaboia
⭐ jwalton512
⭐ gitgnm
⭐ lpfann
⭐ dykandDK
⭐ smkelly
⭐ Brunty
⭐ oz9els
You all are the stars! 🌟

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository frenck/home-assistant-config to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

You wrote "figure out how to document that all". Any plans for actually doing this? :)

Automatically trigger the lets encrypt add-on, to refresh my certificate when it almost expires.

Problem/Motivation

It's possible to improve the structure of the configuration

Proposed changes

It's possible to group components "per-area".
Example:

switches
|-bedroom
   |-switch.bedroom_desk.yaml
   |-switch.bedroom_cupboard.yaml

Not an issue, more of a question.

I am looking to follow your config layout and just had a question about if you prefer to use the GUI for what you can or if you prefer to do it in yaml? For example the home location, do you set that in the gui or in your config? Installing integrations (that can be) through HACS or manually? eg zones?

Hello, mate!

I have a similar setup to yours, I just accepted the fact that I can't edit automation as they are not in the automations.yaml but I never dug it about it. You also can't edit them? Or there's a workaround?
Thanks!

Hey Frenck!

This issue was filed because I am so happy using this configuration scheme and all the addons you provided!
(I will close it immediately after creation, it's just a big thank you :))

I hope you will keep going like this, maintaining and creating addons, helping developers and making cool stuf!

Keep up the good work :)

Thanks for sharing your config, has been a great cleanup!

Problem/Motivation

Using your package config split, my switches don't work.

Expected behavior

A file for every switch would result in the entities showing up in the state tab.

Actual behavior

No entities available related to the configured switches, without anything in the logs.

Steps to reproduce

See config
Config that doesnt work

/config/components/packages/switch.yaml

# This file loads up my switches
#
# https://www.home-assistant.io/components/switch/
#
switch: !include_dir_list ../switches

/config/components/switches/laptop.yaml

platform: template
switches:
  laptop:
    value_template: "{{ is_state('device_tracker.laptop', 'home') }}"
    turn_on:
      service: shell_command.laptop_wol
    turn_off:
      service: shell_command.laptop_suspend

/config/components/switches/pc.yaml

platform: template
switches:
  pc:
    value_template: "{{ is_state('device_tracker.steam', 'home') }}"
    turn_on:
      service: shell_command.steam_wol
    turn_off:
      service: shell_command.steam_suspend

Config that does work (workaround)
/config/components/packages/switch.yaml

# This file loads up my switches
#
# https://www.home-assistant.io/components/switch/
#
#switch: !include_dir_list ../switches
switch:
  - platform: template
    switches:
      pc:
        value_template: "{{ is_state('device_tracker.steam', 'home') }}"
        turn_on:
          service: shell_command.steam_wol
        turn_off:
          service: shell_command.steam_suspend
  - platform: template
    switches:
      laptop:
        value_template: "{{ is_state('device_tracker.laptop', 'home') }}"
        turn_on:
          service: shell_command.laptop_wol
        turn_off:
          service: shell_command.laptop_suspend

Proposed changes

Please advise

Your github workflow uses both checkout v1 and v2. Is this for a specific reason? Why are they different?

Problem/Motivation

Since the last core update of HA 2024.4 there are problems with the appdeamon and NSPANEL
trying to fix this is resulting in a big mess with the files and where they should be.

can you please provide an extended summary on which location exactly these files should be on the home assistant:

apps.yaml
configuration.yaml
appdeamon.yaml

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Hello!

I was wondering if you maybe did an updated version of your configuration/integration files and folders.
So much has changed in time and i am still using the structure of pointing all integrations to there own folders.
Also was wondering if MariaDB or the default DB is used now.

Thanks!
Rick

Hi frenck,
How do you use your split-folder/one-file-per-thing config system with unique IDs and do they allow you to manipulate i.e. an automation in GUI?
Thanks!

Problem/Motivation

I've have got myself two of those Xiaomi Light sensors on Zigbee 3:

I've quickly paired them to Home Assistant over ZHA, but have not put them to use yet.

Install them outside, in bit rain protected area (they are kinda waterproof a bit ish...). They should not be influenced by artificial light sources so placing them in weird areas is needed.

Use these two, I can get an average of the daylight level outside and use that for my automations instead of relying on things like the position of the sun.sun.

This should improve my automations around lighting, as relying on the actual light condition outside makes more sense (e.g., a cloud came in or with bad weather).

Tasks:

• Install sensor 1 at the back (garden?) of the house.
• Install sensor 2 at the front of the house.
• Make sure they are named and paired with ZHA correctly.
• Create a new template sensor based on the average of the above sensors.
• Add the three new entities to InfluxDB.

After recording the values to InfluxDB for a while, allows me to learn about the values I can automate on.

Frenck... Just watched a youtube video you posted a while back on splitting HA configs.
I was attempting to model your configuration since you posted it here (github).

Please let me know if there are hidden objects/folders.. etc in your repo?
I'm having a difficult time following everything

For example (this references the ../entities/sensors directory)

....but when I navigate your tree, I do not see the sensors directory.
So how is this working for you?

Would you be able to upload your current configuration so the missing parts/pieces are present?
THanks
Ben

To track the build status of this configuration repository.

Add-ons using my SSL certificate must be restarted when the certificate refreshes.

Problem/Motivation

Most of the configs in Cookbook are just committed config folders, so the config folder is a repo itself (contains .git). The same approach is described in a guide about sharing configuration on GitHub.

On another hand, your configuration repo contains the whole configuration in config folder of the repo. I suppose you store your repo somewhere else and somehow sync the /config folder with a config folder in the repo.

How do you do that? How do you keep the configuration in a folder within a repo? How do you sync this config folder with your instance?

Thanks for answer!

Problem/Motivation

This issue serves as a simple collection for Home Automation ideas/brainfarts:

• Not sure about yet
• Not ready to do yet
• Not yet worthy of its own issue
• A rough idea
• Something picked up somewhere.

The list

• Start using announcements on my Google devices
• Notifications for washing machine status based on power usage
• Notifications for dryer based on power usage
• Battery monitoring / notifications / alerts
• notification when the Roborock vacuum cleaner needs its dustbin emptied or other maintenance

Hi Frenck,

Short queston about your configuration. I'm very interested in this setup (files/folders).
In your configuration you reference the sensor.bathroom_humidity sensor for example.
This sensor is also used in some automations (for example the ventilation).

Where do you define this entity? Maybe not in YAML but in UI only? How does this work?
BTW; love your streams!

Problem/Motivation

Sometimes, I hear the relays of the central ventilation system switch a couple of times really fast.

It seems like automation is biting or causing it to flip out for a couple of seconds. At this point, it doesn't seem to do any harm, but it needs to be looked at.

https://github.com/frenck/home-assistant-config/blob/master/config/automations/areas/attic/central_ventilation.yaml

Add a sensor that checks the expiration of my certificate.

Problem/Motivation

I have two ordinary lights on my desk.
I have modified with an ESP chip running WLED and some LED strips. The other still has the ordinary light bulb in it, controlled with a Z-Wave wall plug.

Tasks:

• Rebuild the second light to match the first light. Adding an ESP chip and some LED strips.
• Add the modified light to Home Assistant.
• Create a light group containing both.

The freed up Z-Wave wallplug can be moved upstairs (hidden somewhere probably) to support the Z-Wave network.

Problem/Motivation

The kitchen lights automations and overall handling need to be different.

Idea:

• Automatically set the Kitchen lights to a "dim" scene in the evening. Which is a very low brightness ceiling light, just to notice it is on, but not enough to disturb anything.
• Trigger a "motion"/Walk-in scene when motion is detected when the dim scene is active. So if you enter the kitchen in the evening you have some light, but it won't burn out the eyeballs.
• Have a scene for during cooking?
• Have a scene for during cleaning?
• When not cooking, not cleaning, not dim... apply circadian lightning? until the evening falls and the "dim" scene kicks in.

Control options:

• Xiaomi Aqara motion sensor at the kitchen entrance
• Have a Philips Hue Remote by the kitchen entrance that allows:
  • Switching between different modes: auto, cooking, cleaning?
  • When not in auto mode, brightness buttons should work
  • Off button switch to auto mode, while ignoring the motion sensor for a minute?
• Voice control on modes for the different modes

Other:

• Announce change of mode via the Google Assistant on the bartop?

Problem/Motivation

Currently, I run my Home Assistant instance on a Debian VM in Proxmox, in which the Home Assistant Supervisor is running.

This installation method is now deprecated by Home Assistant. This means I need to migrate to a new system.

Announcement: https://www.home-assistant.io/blog/2020/05/09/deprecating-home-assistant-supervised-on-generic-linux/

• Set up a new VM in Proxmox based on the official VM images by Home Assistant.
• Take a snapshot of the old system.
• Shut down old system.
• Restore snapshot on the new system.
• Start new system.

Happy camper inbound 🎉

Problem/Motivation

Somehow my TTS for Google Assistant broke down in 0.109 (I think).

While I do not actively use TTS yet, I do plan on using it. While playing with it just now I noticed it not working.

My Google Assistants are on a different VLAN (IoT), but I have mDNS repeaters set up. Home Assistant does detect them and I am able to control them (e.g., volume, on/off) and see the current status:

Not sure why TTS does not end up with them. Could it be a streaming issue?

Unsure.

The bot config, labels & Templates are an copy of one of my add-ons.

My personal repo for my HA config is not a real match for this, hence it is time to revisit this.

Apologies in advance as I know this probably isn't the right place to be asking this but I've spent ages trying to figure it out and I've asked other people on the forums to no avail...

You have your config folder as a subdirectory to the repo but the git pull addon will checkout the repo within the config directory already which means I must have the configuration.yaml folder in the root of my repo or I end up with a structure like /config/config/configuration.yaml.

How do you get round this? Do you just not use the git pull plugin or is your system setup differently?

In order to keep track with updates on custom version of components and lovelace resources, I should add the Custom Updater component.

https://github.com/custom-components/custom_updater

GitHub

custom-components/custom_updater

📦 A component which allows you to track and update custom cards/components and python_scripts - custom-components/custom_updater

Problem/Motivation

The README of this repository is outdated (it wasn't much to being with).

This is a task for cleaning it up a bit.

Problem/Motivation

In order not to forget to put the waste bins out on pickup day, I need some sensors, automations and notifications.

References

• Twente Milieu Integration: https://www.home-assistant.io/integrations/twentemilieu