Nice and simple: On warm spring days we often open the doors during the day but want to keep the heating on in the evenings and there's no need to heat the garden. Still waiting on my door sensors, though.

Very easy enhancement: Setting the elevation of our house should make the sun level slightly more accurate.

I'd like to get a notification in Telegram when there is an update to Home Assistant.

Now that the nginx proxy manager which I rely upon for location tracking requires Maria DB I should move the Recorder over, too.

YAML configuration was deprecated in HA 0.109.

It just stays at TV light.

About 1 in 10 times when starting HA the fritzbox integration does not connect to the device with the error message "The following components and platforms could not be set up: fritzbox. Please check your config." That means that many devices and a significant part of the presence detection are missing. A simple restart fixes the problem.

I still don't know how I should list custom built stuff.

Often when watching TV its status changes from on to off. This seems to be an issue with webOS when connected via WiFi. Possibly fixed with home-assistant/core#29296 but not too sure about it. Looks like I will need a longer cable.

And I have no idea why!

Tonight it turned on at 5:16. The dining room state was empty and has been for a while. The sun was still below_horizon. Looks like the cat triggered one of the motion sensors in the dining room at 4:41 but occupancy probability never rose above 10%. Nothing here should have triggered the lights turning on.

That would be weird, right? Also ask my wife if she is okay with me putting her name in the repository. 🤓

In rooms where we can turn on the lights by hand and also automatically (eg motion sensors) it should transition from On to Automatic instead of from On to Off when the conditions for the automatic lights are fulfilled.

I want to be able to check the UI config into the repository. To do so I need to change Lovelace to YAML mode. First I need a sensible concept of how to structure the config so I don't end up with one big file.

To reliably switch the house state to night and back it would be nice to detect when we are actually in bed instead of relying on some mostly-true-but-sometimes-very-much-not-so time triggers. I will use this issue to aggregate what I researched and found out to maybe someday implement a proper detection.

It'd be nice to get an approximation of how far away the other person is. Included in the bot main menu it would take five taps. HA should have all the information needed.

For easier nightly navigation without disturbing the other person the room could be illuminated from under the bed whenever somebody touches the ground.

Needed hardware

• 3x LED strips
• 2x Motion sensor #3

When devices switch from unavailable they should be assigned a default state. The same goes for nearly everything when Home Assistant starts.

These were introduced in HA 0.113 and should make the room state automations much easier: https://www.home-assistant.io/docs/scripts/#choose-a-group-of-actions

When anything with a battery falls below a threshhold I want to receive a notification via Telegram.

When the living room is occupied during the night the TV backlighting does not turn off again when the room turns empty.

Most times the bathroom thermostat does not switch to eco when we go to bed or leave the house and back to comfort when we get back or wake up (but sometimes it does?).

This seems to be an issue with the automation. The thermostat works properly when switching presets on the web interface.

I installed a big Floalt light in the middle of the kitchen. It and the included Tradfri remote are already paired with the Conbee. Before installing the remote as a wall mounted switch the renovation of the room must be completed but I can start with the automations right now.

• Kitchen states "On", "Occupied" and "Empty" set the correct light scene with respect to the house state. I don't think the kitchen needs modes (yet).
• The switch sets the kitchen state to On or Off. I currently don't see anything I could do with the other buttons as the kitchen does not have modes.
• A motion sensor sets the kitchen to Occupied or Empty.
• Automatic light temperature according to time of day. Flux integration is already active but pretty hard to test when the light is not kept on all the time.

The whole current setup should be documented in md files right in the folders where they belong. This way the documentation is actually in the repository and does not need to be updated externally like in the current wiki.

Over night every thermostat is switch to the eco preset and every morning they are turned back to comfort. The thermostat in the bathroom however is not switched back to comfort in the morning. It's still working the other way around in the evening and for the living room thermostats.

Now that the Hyperion integration is fixed in 0.116 I can simplify the automations controlling what the TV backlighting does by turning Hyperion on and off.

We now have our first speakers that integrate into Home Assistant so it would be nice if the music would follow us around the house automatically. This is probably several new features in one.

The current favicon has a completely transparent background. That doesn't look great in certain situations, especially Chrome Dark Mode. The favicon should have a background, eg. a grey border and white background.

There's some times when all lights can be turned off safely:

• When everybody is gone (house changes to states Empty or Vacant)
• Every night at 2am just to be sure

Also every light (except for the bedroom) can be turned of as soon as the house changes to Night after I implement a better night mode detection

When the motion sensor in the kitchen hasn't registered anything for a few minutes the light should turn off regardless of the current state.

The device triggers are a bit more complicated to setup but it looks like they can do much more than the event based triggers.

A device trigger can be created by going through the automation creation web interface and showing the trigger as YAML.

The front door light is not connecting to the ZigBee network. Weird thing is the battery driven motion sensor right next to it happily detects motion and triggers the corresponding automations. The light actually does work when put right next to the Conbee.

When the ein state is on and the sun sets while motion is detected the room state changes to occupied and the light dims and turns off soon thereafter.

This seems to be what breaks the Travis build. I have no idea why this should even work in HA so I guess that's what you get for letting the configuration here and on the machine drift apart.

https://github.com/Friedenspanzer/yggdrasil/blob/4a184a653859708958b7335a1d13fbbd8005702e/automations/infrastructure/light_scheme_colors.yaml#L115

I should get a Telegram message when Home Assistant sucessfully started but I don't. It'd be great to know that the automatic update was successful.

When watching something the TV backlighting sometimes switches to the mood lights for a few seconds and then back to Hyperion lighting. That's because the TV sometimes detects as off for a few seconds. For the room state I use a timeout of 12 seconds (see here for example). But I cant really use that timeout here. When turning off the TV for real Hyperion supposedly stops sending signals because whatever device was connected was turned off before the TV. With the room state still set to dimmed, no Hyperion lighting and no TV the room would just turn dark for these 12 seconds.

Currently the thermostats are switched to the eco preset at a fixed time. If the balcony door is closed after that time (eg to let the cat in) the thermostats go back to comfort and never change back overnight.

For lighting half the kitchen counter we will need some under cabinet lights. Existing solutions (like IKEA Strömlinje) won't fit the corner and the gap so I guess I'm going with something custom built.

I will need these devices:

• At least 2m of LED strips (I'm already building it myself so I guess I'll go with RGB WW)
• LED strip controller
• LED strip connectors (one for the corner, one for the gap)
• LED strip diffusers fit for the cabinets

The travel time is updated every minute, but the phones do not send updates that often. The zone leave notifications however are sent the moment a phone leaves a zone. That way the travel time is near guaranteed to use the previous position.

The travel time should be updated before sending the notification. If possible it should also update whenever the phone position changes significantly instead of on a timer.

The concept of modes I initially planned is not used for much and I don't really know what to do with it. The only thing currently relying on it is the living room lights and I could easily build this with another state. To make thinks easier I should eliminate modes for now and maybe rethink the concept when I actually know what to do with it.

The current automatic configuration update reads from the GitLab repository (and doesn't always work). It must be moved to this repository.

I need a good backup strategy to account for hardware failures and wrong software configurations.

In our old flat HassOS was configured to connect via WiFi so the Pi could be placed closer to the ZigBee devices. This is not needed anymore and the old unused WiFi connection details should be deleted.

I love home automation for issues like this tbh.

Owntracks provides the easiest way to enable positional tracking without using a cloud service. Some infrastructure is need though to make it work without exposing all of HA to the internet.

Since we got the new fridge it happened multiple times that we left it open by accident. The way the door is built promotes this and we have to carefully check if it is really closed. An alert when we left the door open for some time would make this much easier.

My current idea is to just plug a door sensor on there to see if it is open and send a Telegram notification after a few minutes. A cool addition would be to change the lightning in the kitchen based on how long the fridge was open.