aetjansen/homeassistant-config

Home Assistant configuration files and scripts

homeassistant-config's Issues

Fibaro Dimmer 2 switches off load automatically after some time

Behavior started after doing a foced auto-calibration and I cannot seem to figure out why or how to stop it, but very annoying...

Meterreading values not passed into iftt trigger

Energy package: the calculated values for daily energy usage, should be passed into the IFTTT trigger to be stored in a spreadsheet. Right now, the literal string of the input_number ends up in the spreadsheet as opposed to the value of the input_number.

Asked for help in the forums: https://community.home-assistant.io/t/one-state-used-in-two-automation-actions-but-different-behaviour-values/45418

make a separate night_mode group

Make a group containing automations (and possibly switches and other things) that need to be disabled/off when night_mode is activated and on when night_mode is deactivated. That way, the condition check for night_mode state can be removed from many automations and adding something new is only a matter of adding it to the night_mode group.

Disabling night_mode does not re-activate disabled automations

Upon activating night_mode, some automations are disabled. But, they are currently not enabled again when night_mode is no longer active.

prevent bathroom vent when outdoor abs humid >= indoor abs humid

bathroom ventilation can now be on for hours trying to get indoor humidity below threshold (60%), drawing in air from outside. But if the absolute humidity ( grams/m3) is equal to or larger than the absolute humidity in the bathroom, it makes no sense to keep the ventilator on.

Publish all sensor state changes to mqtt

Improves persistence, more flexibility

Fix use of data and data_template

in a service call, data: is used when no jinja is passed, and data_template when jinja is passed along for processing. Could also use data_template everywhere at (probably) a minimal performance loss, maybe a bit more startup time.

Using data: and passing along jinja code, will not work and cause the jinja code to be taken as literal strings

Uniform naming of automations

Makes debugging a lot easier I think :-)

Unified naming of objects

Go through config and setup everything according to a naming convention. This improves readibility and allows for easier templating.

Additionally, the diy multisensors I have built should have a firmware upgrade to have a specific mqtt topic per sensor (as opposed to one mqtt message with all sensor data in the payload everytime).

With that, setup specific sensors by using mqtt subscriptions, for example:
sensor.livingroom_temperature
sensor.livingroom_humitidy
sensor.livingroom_lightlevel
sensor.livingroom_motion

etc