Need to access time sensor

alternatively, use now

template:
- trigger:
- platform: time_pattern
seconds: "/1"
sensor:
- name: time
state: "{{ now().strftime('%H:%M:%S') }}"

{{ now().strftime("%I:%M %p") }}

{{ as_timestamp(state_attr("device_tracker.android_9050f88e39898022", "last_time_reachable")) | timestamp_local }}
{##{{ state_attr("device_tracker.android_9050f88e39898022", "last_time_reachable").strftime('%H:%M:%S') }}##}

- condition: template
value_template: '"{{ now().timestamp()+300 < (as_timestamp(state_attr("device_tracker.android_9050f88e39898022", "last_time_reachable")) | float)
}}"'

Change attribute value via automation

https://community.home-assistant.io/t/how-to-manually-set-state-value-of-sensor/43975/21

- id: automation 3

trigger:

platform: time_pattern

minutes: '/1'

action:

service: python_script.set_state

data_template:

entity_id: sensor.cold_water_rate

state: 42

new HA OS on RaPi4

http://192.168.178.52:8123/

create user

user: bora, pass: bora

select location

activate advanced mode under profile settings

install add ons

Samba share

username: homeassistant, password: bora, workgroup: WORKGROUP

add a new network location: \\192.168.178.52\config

file editor

duckdns

domains:
- habora.duckdns.org
token: 799093a4-0b34-454f-99cb-25a4637bf404
aliases: []
lets_encrypt:
accept_terms: true
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem
seconds: 300

MariaDB

databases:
- homeassistant
logins:
- username: homeassistant
password: password1234
- username: read_only_user
password: password1234
rights:
- username: homeassistant
database: homeassistant
- username: read_only_user
database: homeassistant
privileges:
- SELECT

recorder:
db_url: mysql://homeassistant:password@core-mariadb/homeassistant?charset=utf8mb4

Nginx Proxy Manager

Open WebUI → admin@example.com / changeme

Hosts – Proxy Hosts → Add Proxy Host

Domain Names: habora.duckdns.org

Als Scheme wählt Ihr http, unter „Forward Hostname / IP“ tragt Ihr die IP eures Home Assistant ein. → 192.168.178.52

Bei Forward Port gebt Ihr den Port ein, unter dem euer Home Assistant erreichbar ist. (Standardmäßig ist das der Port 8123)

Aktiviert abschließend noch den Punkt „Websockets Support„.

Anschließend wechselt Ihr auf den Reiter SSL.

Hier wählt ihr unter „SSL Certificate“ den Eintrag „Request a new SSL Certificate“ um ein neues Zertifikat zu erstellen aus.

Aktiviert nun den Punkt „Force SSL„, tragt eine gültige Email-Adresse für eure Zertifikat ein und akzeptiert die Let’s Encrypt Bedingungen durch aktivieren der Option am unteren Rand der Dialog.

Bestätigt nun die Eingaben durch einen Klick auf „Save“ und wartet, bis der Vorgang abgeschlossen ist.

Dann werden im Hintergrund die Zertifikate von Let’s Encrypt generiert. Das kann einen Augenblick in Anspruch nehmen.

Das registrieren des Zertifikates funktioniert nur, wenn die eingetragene Domain auch auf eure externe IP zeigt, und die Ports 80 und 443 auf die Home Assistant IP weitergeleitet sind.

configuration.yaml

http:

use_x_forwarded_for: true

trusted_proxies:

- 127.0.0.1

- 172.30.33.0/24

- ::1

Let's Encrypt

domains:
- habora.duckdns.org
email: boraers@googlemail.com
keyfile: privkey.pem
certfile: fullchain.pem
challenge: http
dns: {}

add to configuration.aml
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

influxdb

no adaptation of configuration was needed

http://192.168.178.52:8123/api/hassio_ingress/FJZMGvrT7OnlTzBKdUP9jKiKEe4yp4V4D5VT4zHP5cQ/sources/0/hosts

http://192.168.178.52:8123/hassio/ingress/a0d7b954_influxdb

create database: home_assistant

create user: homeassistant, pass: homeassistant, permissions: ALL

mosquitto

Logins:
- username: note4
password: note4

MQTT integration configuration:
127.0.0.1 ← not core-mosquitto
1883
note4
note4
MQTT protocol: 5

Grafana

env_vars:
- name: GF_SECURITY_ALLOW_EMBEDDING
value: "true"
- name: GF_AUTH_ANONYMOUS_ORG_NAME
value: Main Org.
- name: GF_AUTH_ANONYMOUS_ENABLED
value: "true"
- name: GF_AUTH_DISABLE_LOGIN_FORM
value: "false"

SSL: false or true, depending on having ssl set up

Network:
3000

http://192.168.178.52:8123/hassio/ingress/a0d7b954_grafana

in web panel

add data source: InfluxDB

URL: http://a0d7b954 -influxdb:8086

database, user, pass

Terminal and SSH

integrations

HACS

github credentials required

OpenWeatherMap

API Ke:

solarman

re-use old config files

automations

blueprints

bosch_shc

custom_components

group

images

python_scripts

www

alarm_control_panel.yaml

automations.yaml

climate.yaml

configuration.yaml

influxdb.yaml

mqtt.yaml

scenes.yaml

scripts.yaml

secrets.yaml

sensor.yaml

move to external SSD

che

Home-Assistant script template

{## Imitate available variables: ##}
{% set my_test_json = {
"temperature": 25,
"unit": "°C"
} %}

The temperature is {{ my_test_json.temperature }} {{ my_test_json.unit }}.

{% if is_state("sun.sun", "above_horizon") -%}
The sun rose {{ relative_time(states.sun.sun.last_changed) }} ago.
{%- else -%}
The sun will rise at {{ as_timestamp(state_attr("sun.sun", "next_rising")) | timestamp_local }}.
{%- endif %}

For loop example getting entity values in the weather domain:

{% for state in states.weather -%}
{%- if loop.first %}The {% elif loop.last %} and the {% else %}, the {% endif -%}
{{ state.name | lower }} is {{state.state_with_unit}}
{%- endfor %}.

{% set tado_temp = states('sensor.tado_wohnzimmer_temperature')|float(20) %}
{% set room_temp = states('sensor.meter_plus_90b4_temperature')|float(20) %}
{% set current_offset = state_attr('climate.tado_wohnzimmer',
'offset_celsius') %}
{{ tado_temp|round(1) }}
{{ room_temp|round(1) }}
{{ current_offset|round(1) }}
{{ (-(tado_temp - room_temp) + current_offset)|round(1) }}
{{ (tado_temp - current_offset)|round(1) }}

{% set average_temp = 0 %}
{% set active_rooms = 0 %}
{% set temp_bedroom = states('sensor.radiator_thermostat_bedroom_temperature')|float(15) %}
{% set climate_bedroom = states('climate.room_climate_bedroom') %}
{% set temp_top = states('sensor.radiator_thermostat_child_top_temperature')|float(15) %}
{% set climate_top = states('climate.room_climate_child_s_room_1_top') %}
{% set temp_bottom = states('sensor.radiator_thermostat_bottom_temperature')|float(15) %}
{% set climate_bottom = states('climate.room_climate_child_s_room_2_botto') %}

{% if climate_bedroom not in ("unavailable", "unknown", "off") %}
{% set active_rooms = active_rooms + 1 %}
{% set average_temp = average_temp + temp_bedroom %}
{% endif %}

{{ average_temp/active_rooms|round(1) if active_rooms>0 else 77 }}

Python Scripts

https://www.home-assistant.io/integrations/python_script

Example 1

https://community.home-assistant.io/t/how-to-manually-set-state-value-of-sensor/43975/5

Scripts are placed in a python_scripts folder under the configuration directory, in my case it is /home/homeassistant/.homeassistant/python_scripts. You then need to either restart Home Assistant or click RELOAD SCRIPTS under Configuration, General, Configuration Reloading.

For what it’s worth, I have been hunting for a solution to this problem and I finally decided to make a small script:

# python_scripts/set_state.py

#==================================================================================================

# python_scripts/set_state.py

#==================================================================================================

#--------------------------------------------------------------------------------------------------

# Set the state or other attributes for the entity specified in the Automation Action

#--------------------------------------------------------------------------------------------------

inputEntity = data.get('entity_id')

if inputEntity is None:

logger.warning("===== entity_id is required if you want to set something.")

else:

inputStateObject = hass.states.get(inputEntity)

inputState = inputStateObject.state

inputAttributesObject = inputStateObject.attributes.copy()

for item in data:

newAttribute = data.get(item)

logger.debug("===== item = {0}; value = {1}".format(item,newAttribute))

if item == 'entity_id':

continue # already handled

elif item == 'state':

inputState = newAttribute

else:

inputAttributesObject[item] = newAttribute

hass.states.set(inputEntity, inputState, inputAttributesObject)

With this script in place, the action could be:

action:

service: python_script.set_state

data_template:

entity_id: Binary_sensor.sensor1

state: ON

Example 2

https://www.home-assistant.io/integrations/python_script#calling-services

Start by enabling the Python script and create the first script.

Add to configuration.yaml: python_script:

Create folder <config>/python_scripts

Create a file <config>/python_scripts/hello_world.py in the folder and give it this content:

# `data` is available as builtin and is a dictionary with the input data.

name = data.get("name", "world")

# `logger` and `time` are available as builtin without the need of explicit import.

logger.info("Hello {} at {}".format(name, time.time()))

Start Home Assistant to reload the script configuration.

Call your new python_script.hello_world service (with parameters) from the Services, using the YAML mode.

service: python_script.hello_world

data:

name: "Input-Text"

Running this script show absolutely no output on the screen, but it logs with level info. You must have the Logger enabled at least for level info.

Your confiuration.yaml should include something like this.

logger:

default: info

Flash ESPhome on ESP32 ESP2866 NodeMCU board

https://www.pieterbrinkman.com/2022/01/01/2022-update-flash-esphome-on-esp32-esp2866-nodemcu-board/

Install using esphome-flasher:

download compiled firmware: In the Install menu click Manual Download. The compilation will now start and the .bin file will download when ready.

Go to the esphome-flasher GitHub page and download the flasher for the OS you’re using. There is a esp home flash tool for macOS, Ubuntu and Windows :
https://github.com/esphome/esphome-flasher/releases

Connect your ESP board with USB to your laptop.

Open the flasher tool

Serial port: select COM port where the board is connected (there is probably only one option 😊).

Firmware: Browse to the location where you downloaded your compiled firmware and select your firmware.

Click Flash ESP and wait

The ESP will be flashed now, you can follow the progress in the console window. When finished writing the firmware the ESP will restart and connect to your WiFi.

The ESP will be ready after it states that it’s ready for Over-The-Air Updates and that he API server is ready.

Measuring DHT22

https://www.pieterbrinkman.com/2021/02/03/build-a-cheap-air-quality-meter-using-esphome-home-assistant-and-a-particulate-matter-sensor/

Note: Step 1 and 2 have been changed with new UI and features in both Home Assistant and ESPHome. Read the updated article to flash ESPhome on your ESP32 / ESP2866 NodeMCU board and skip step 1 and 2 below.

3. Wire the PMS5003 Particular Matter sensor and DHT22 to the ESP board

Wiring the DHT sensor is straight forward.

Connect the GND to any free GND pin on the ESP

Connect the VSS to any free 3V3 pin on the ESP

Connect the DATA to D4 on the ESP

4. Configure ESPHome to read the measurements and supply them to Home Assistant

Now it’s time to expose the measurement values to Home Assistant.

Open ESPHome and click EDIT on your node. The ESPHome configuration editor will now show. Add the following configuration at the bottom of the configuration.

uart:

When ready, press the Upload button and ESPHome will flash the new firmware OTA. Wait till ready and you should be good to go. ===> this can be done wirelessl now

You can verify the new switch and interval by going to Home Assistant and open the device. You will see that it will have a Start Measuring switch. Enable the switch and notice that the measurements value start changing.

Wait a two minutes and notice that the switch will be turned on for 20 seconds and then turned off again.

Now add the some graph to your dashboard.

6. Add air quality measurements to Home Assistant

For viewing the measurements in my lovelace dashboard I used a custom card called mini-graph-card, this card can be easily installed using HACS. I used the following Lovelace configuration.

type: 'custom:mini-graph-card' name: Air quality inside icon: 'mdi:server' line_width: 2 animate: true hours_to_show: 24 points_per_hour: 1.5 entities: - entity: sensor.particulate_matter_1_0um_concentration name: 1 µm > - entity: sensor.particulate_matter_2_5um_concentration name: 2.5 µm > - entity: sensor.particulate_matter_10_0um_concentration name: 10 µm >

Adding measurements of outside air

To create additional context I also use Luftdaten integration to get outside air quality measurements nearby. This way you could automate opening windows or triggering ventilation to get better quality air from outside.

Luftdaten is making the world a better place through community driven, open environmental data. The coverage within northern Europe is impressive.

Exposing both inside and outside air quality with a vertical stack card will provide a nice comparison view.

That’s it. Now it’s time to start measuring and learn more about the air quality in your house. Let me know if you have any questions and if you managed to make it work!

Working DHT11 on Berrbase NodeMCU ESP32

https://www.berrybase.de/esp32-nodemcu-development-board?sPartner=g_shopping&gclid=Cj0KCQiAnNacBhDvARIsABnDa68SnJ4bQ8qK-zWJiPZKsqYP245LF2rjMlnLhZHn7BHi7THLCbbWnOcaAvoOEALw_wcB

ESP32 NodeMCU Development Board

Artikel-Nr.: NMCU-ESP32

EAN: 4251266700609

Connection

DHT on breakout board with SMD resistors and LED was used → might need 10 kOhm resistor for bare DHT11

12 = GPIO12

VCC = 3.3V

GND = Gnd

test-esp32nmcu.yaml → test-esp32nmcu___working_20221211.bin

esphome:

esp32:

board: esp32dev

framework:

type: arduino

# Enable logging

logger:

# Enable Home Assistant API

api:

encryption:

key: "MI1DnjQWboPRECsx7PlLQS4BiR7SQQSpYczCuzpupS4="

ota:

password: "bb47b47929f02cd349e51eddd8602edb"

wifi:

#ssid: !secret wifi_ssid

#password: !secret wifi_password

#ssid: "FRITZ!Box Gastzugang"

#password: "zakihasalittlewiener"

ssid: "FRITZ!Box 7530 GD"

password: "78302839617779115068"

# Optional manual IP

manual_ip:

static_ip: 192.168.178.42

gateway: 192.168.178.1

subnet: 255.255.255.0

# Enable fallback hotspot (captive portal) in case wifi connection fails

ap:

ssid: "Test-Esp32Nmcu Fallback Hotspot"

password: "pJDTx6ABN80C"

captive_portal:

sensor:

- platform: dht

pin: 12

temperature:

humidity:

update_interval: 10s

model: DHT11

flashing using ESPHome-Flasher-1.4.0-Windows-x64

see above

activate the sensor in HA

after some minutes, the ESP32 should appear under Integrations with the initiall assigned name

How to integrate full functionality of Bosch smart home components

https://github.com/tschamm/boschshc-hass

shc11d14d

192.168.178.34

Connect via Samba share

add a Network Location in Windows Explorer

LAN: \\192.168.178.32\config

WLAN: \\192.168.179.43\config → not working??

user: homeassistant

pass: bora

cop following folders into the config folder on RaPi:

custom_components

images

tests

after restarting HA all components and functions should be available

Dashboard individualization

https://smarthomescene.com/guides/top-10-home-assistant-lovelace-themes/

If you have not enabled custom themes already, add this to your configuration.yaml file and reboot Home Assistant:

frontend:

Guest access

create a dedicated account for gests:

user: Guest

pass: guest

open http://192.168.178.32:8123

https://community.home-assistant.io/t/configuring-a-real-guest-user-an-alternative-approach/455910

Hi, I’d like to share the way I approached the configuration of a guest user in my HA and how I worked around some well-known limitations, especially those related to the lack of a global sidebar / default dashboard configuration.

My requirements:

Guest user allowed to login only from the internal network

Only specific views available to the guest user

No need for the guest user to switch to a different dashboard once logged in

No unnecessary items to show up in the sidebar for the guest user (including logbook, media, history, etc)

Basically a sort of kiosk mode without using frontend hacks (https://github.com/maykar/kiosk-mode 2 is now deprecated, https://github.com/Villhellm/custom-sidebar is no more working in latest HA versions, https://github.com/galloween/custom-sidebar-v2 works only for admin users).

Requirement #1 is the simplest: just create a guest user with a simple password and toggle the Can only log in from the local network option.

Requirement #2 is also stright-forward: create a dashboard, add a View for the guest user, under Visibility allow the guest user only to access that view, disable the guest user to access any other view of the dashboard.

Requirement #3 is tricky. As we know there is no global default dashboard configuration, it is per-user / per-device.
This means the guest user, upon the first login, lands in the over-complicated Overview dashboard and should go in his profile to change the default dashboard. Not something I want them to do neither I want to do it on their behalf.
After reading tons of posts here, the simplest approach I found is to take control of the Overview dashboard (if I need the same content I can always create a brand new admin-only dashboard) and put all my views there (both for regular and guest users).
True, the name of the Overview dashboard cannot be change as well as the icon but at least in this way every user (guests or not), when logging in, will land to a dashboard populated with the contents I want.

Requirement #4 was also a challenge. As we know also the order in which the items show up in the sidebar and which one is hidden or not is per-user / per-device. The way I approched it was the following:

I migrated all my dashbaords into views in order to have a single dashboard only (the Overview one). This is not mandatory of course, just an implementation choice, to avoid taking care of the order in which dashbaords are listed in the sidebar

I disabled in my configuration Energy, Map and Media since not using them at all (Ref. How can I hide the Energy/Media/Map tabs from the sidebar? - #9 by petro 5) resulting in the entries to disappear from the sidebar. This required switching from default_config to a long list taken from Default Config - Home Assistant 1 and commeting out those not needed

For Logbook and History, which are something I need as an admin but don’t want the other users to access and see, I made them available for admin users only, opting for the approach described in Admin only access for Logbook and History menus - #44 by dan_mc 8. This required to copy the code of the two components from /usr/src/homeassistant/homeassistant/components or core/homeassistant/components at master · home-assistant/core · GitHub 3 into config/custom_components, add version to the manifest file and making the views admin-only in async_register_built_in_panel() as described in the other post. Of course maintenance of this could be time-consuming since theoretically the code should be updated upon each upgrade

In this way not only guest user but also any user on any deice, has no need to touch the sidebar, hide unnecessary entries or set a default dashboard
Hope can be helpful

Thanks

Influx DB storing of Arduino data

Example 1

http://nilhcem.com/iot/home-monitoring-with-mqtt-influxdb-grafana

Example 2

http://www.iotsharing.com/2021/01/building-smart-home-system-with-home.html

Example 3

https://luigi-saetta.medium.com/evolving-my-home-automation-setup-af0323097d51

https://luigi-saetta.medium.com/evolving-my-home-automation-2-e9b30c2eae54

Example 4

https://randomnerdtutorials.com/esp32-influxdb/

https://randomnerdtutorials.com/esp32-esp8266-sensor-bme280-influxdb/

ssh into rapi via PUTT:

https://randomnerdtutorials.com/esp32-mqtt-publish-subscribe-arduino-ide/

https://diyi0t.com/home-assistant-mqtt-tutorial/

https://community.home-assistant.io/t/publish-mqtt/324939/2

https://www.home-assistant.io/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/

https://www.youtube.com/watch?v=U8f5FcnKdyw

Example 5

https://www.dummylabs.com/post/2019-01-13-influxdb-part1/

Home Assistant with InfluxDB on Synology

https://philhawthorne.com/getting-started-with-grafana-influxdb-for-home-assistant/

https://philhawthorne.com/installing-home-assistant-io-on-a-synology-diskstation-nas/

https://www.youtube.com/watch?v=rdvyYRBU7CM

Home Assistant on Linux VM with Docker, reverse proxy, MQTT and Node Red

https://selmi.medium.com/home-assistant-in-docker-the-ultimate-setup-16d4669dcb7

Presence detection options

https://philhawthorne.com/breaking-down-presence-detection-with-home-assistant/

https://philhawthorne.com/making-home-assistants-presence-detection-not-so-binary/

Automation of dumb devices

https://philhawthorne.com/making-dumb-dishwashers-and-washing-machines-smart-alerts-when-the-dishes-and-clothes-are-cleaned/

Using external Data Disk

https://peyanski.com/home-assistant-external-data-disk/

Home Assistant Operating System supports storing most data on an external storage medium (e.g. USB attached SSD or HDD). This data disk contains not only user data but also most of the Home Assistant software as well (Core, Supervisor etc.). This means a fast data disk will make the system overall much faster.

Graphics showing the architecture of the data disk feature

The data disk feature can be used on an existing installation without losing data: The system will move existing data to the external data disk automatically. However, it is recommended to create and download a full Backup before proceeding!

All data on the target disk will be overwritten!

The storage capacity of the external data disk must be larger than the storage capacity of the existing (boot) disk.

If you have been using a data disk previously with Home Assistant Operating System, you need to use your host computer to delete all partitions before using it as a data disk again.

USING UI TO MOVE THE DATA PARTITION

Connect the data disk to your system.

Go to Settings > System > Storage in the UI.

Press the three dots on the top right and choose “Move datadisk”

Select the data disk from the list of available devices.

Press “Move”.

Screenshot of the “Move datadisk” feature

USING CLI TO MOVE THE DATA PARTITION

To see the current data disk use:

$ ha os info

...

data_disk: /dev/mmcblk1p4

...

Copy

To get a list of potential targets which can be used by datadisk:

ha os datadisk list

Copy

To initiate the move to the new data disk use the move command:

ha os datadisk move /dev/sdx

Copy

The system will prepare the data disk and immediately reboot. The reboot will take 10 minutes or more depending on the speed of the new data disk; please be patient!

Using an USB attached SSD can draw quite some power. For instance on Raspberry Pi 3 the official Raspberry Pi power supply (PSU) only provides 2.5A which can be too tight. Use a more powerful power supply if you experience issues. Alternatively use a powered USB hub. Connect the Hub to one of the USB slots of your Raspberry Pi, and connect the SSD to the Hub. In this setup the power supply of the Hub will power the attached device(s).

Save DB on USB stick/drive (Hassio)

https://community.home-assistant.io/t/save-db-on-usb-stick-drive-hassio/82144/24

Running Home Assistant on a Raspberry Pi 3 from an external hard drive

https://mary.codes/blog/home_automation/running_home_assistant_from_an_external_hard_drive/

https://community.home-assistant.io/t/solved-mount-usb-drive-in-hassio-to-be-used-on-the-media-folder-with-udev-customization/258406/68

MQTT with RP2040

https://learn.adafruit.com/quickstart-rp2040-pico-with-wifi-and-circuitpython/internet-connect

https://www.tomshardware.com/how-to/send-and-receive-data-raspberry-pi-pico-w-mqtt

https://www.hackster.io/FrankDelporte/sending-sensor-data-from-raspberry-pi-pico-to-mqtt-445c97

Weather

accuweather

BoraEr

ineedweather_90

Follow instruction here to create new App: https://www.home-assistant.io/integrations/accuweather

app: ha_weather

API key: GV0GKNtlJZNUHYZ5YNW6YGySLVVz0Huq

search location key: https://www.accuweather.com/en/browse-locations

Leinfelden: 2604235, https://www.accuweather.com/en/de/leinfelden/70771/weather-forecast/2604235

create a sensor from the weather attributes to plot the data:

https://community.home-assistant.io/t/how-to-extract-temperature-from-weather-card/143260/3

# Temperatur-Attribut als Extra-Wert

sensor
- platform: template
sensors:
norwegian_temperature:
friendly_name: "met.no Temperatur Vorhersage"
unit_of_measurement: '°C'
value_template: "{{ state_attr('weather.home_musberg', 'temperature') }}"

openweathermap

https://www.home-assistant.io/integrations/openweathermap/

BoraEr

ineedweather_90

animated icons in weather card

https://community.home-assistant.io/t/animated-weather-icons/206736

https://github.com/wowgamr/animated-weather-card

read content of DB

https://sqlitebrowser.org/

InfluxDB: Removing or deleting data

https://community.home-assistant.io/t/influxdb-removing-or-deleting-data/292637

Read external InfluxDB in Home Assistant as a sensor

https://itobey.dev/index.php/read-external-influxdb-in-home-assistant-as-sensor/

Using both MariaDB and InfluxDB

https://smarthomescene.com/guides/optimize-your-home-assistant-database/

InfluxDB hassio add-on: changing default database location

https://community.home-assistant.io/t/influxdb-hassio-add-on-changing-default-database-location/172354/10

https://community.home-assistant.io/t/where-does-influx-store-db-files-in-hassio/105502

location of influxdb database: https://community.home-assistant.io/t/influxdb-location-of-database-on-hass-io/169916/15

Remote access

https://peyanski.com/home-assistant-remote-access/#What_if_Home_Assistant_Remote_Access_is_not_working_or_you_loose_your_local_access

https://siytek.com/home-assistant-remote/

https://community.home-assistant.io/t/how-to-configure-remote-access-with-lets-encrypt/391432

create DuckDNS subdomain:

Duckdns.org

account boraers@googlemail.com

type free

token 799093a4-0b34-454f-99cb-25a4637bf404

Domain: https://habora.duckdns.org

attention: if router is restartet, configuration of duckdns has to be updated!

to be accessed via the HA app:

https://habora.duckdns.org:8123/

https://192.168.178.32:8123/

https://habora.duckdns.org

habora.duckdns.org

duckdns.org

edit configuration of DuckDNS addon:

domains:
- https://habora.duckdns.org
token: 799093a4-0b34-454f-99cb-25a4637bf404
aliases: []
lets_encrypt:
accept_terms: true
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem
seconds: 300

install Let's Encrypt addon

domains:
- habora.duckdns.org
email: boraers@googlemail.com
keyfile: privkey.pem
certfile: fullchain.pem
challenge: http
dns: {}

port forwarding in fritz.box

Start Let's Encrypt addon

check access via calling the subomain (no https yet)

http://192.168.178.32:8123/

→ this can be done already from the internet

→ the login screen of HA should appear

Enable HTTPS on your HA Install

edit configuration.yaml:

http:

ssl_certificate: /ssl/fullchain.pem

ssl_key: /ssl/privkey.pem

attention: different HA installation need other paths:

https://community.home-assistant.io/t/remote-access-for-home-assistant/206072

Home Assistant OS or Supervised: → Let's Encrypt addon must be installed!

http:

ssl_certificate: /ssl/fullchain.pem

ssl_key: /ssl/privkey.pem

Home Assistant Container:

You’ll need to mount the location with your SSL keys and certificates to /ssl/ in the container.

http:

ssl_certificate: /ssl/fullchain.pem

ssl_key: /ssl/privkey.pem

Home Assistant Core:

http:

ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem

ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem

restart HA

after restart, HA should only be available via https:

internall: https://192.168.178.32:8123/

externall: https://habora.duckdns.org:8123/

Harden the Home Assistant Remote Access Security more

Harden the Home Assistant remote access even more by enabling MFA

Activating ip_ban_option and Multi-factor Authentication Modules is a must if you enable your Home Assistant Remote Access in the way that i’m showing with the port forwarding and SSL. So don’t skip this!

https://www.youtube.com/watch?v=jblBRuW1lu4

Fritz Box Aktualisierungsanforderung mit DuckDNS

https://avm.de/service/wissensdatenbank/dok/FRITZ-Box-7590/30_Dynamic-DNS-in-FRITZ-Box-einrichten/

Klicken Sie in der Benutzeroberfläche der FRITZ!Box auf "Internet".

Klicken Sie im Menü "Internet" auf "Freigaben".

Klicken Sie auf die Registerkarte "DynDNS".

Aktivieren Sie die Option "DynDNS benutzen".

Tragen Sie im Feld "Update-URL" die Update-URL für Ihren Anbieter ein. Falls die Aktualisierungsanforderung sowohl für IPv4 als auch für IPv6 durchgeführt werden soll und Ihr Anbieter für IPv4 und IPv6 verschiedene Update-URLs erwartet, tragen Sie beide Update-URLs mit einem Leerzeichen getrennt ein.

Hinweis:Beispiele für Update-URLs verschiedener Anbieter finden Sie unten in dieser Anleitung. Falls Ihr Anbieter da nicht genannt wird, können Sie die Update-URL wie im Abschnitt "Update-URL selbst erstellen" beschrieben selbst erstellen.

Tragen Sie im Feld "Domainnamen" den Domainnamen ein, den Sie bei Ihrem Anbieter festgelegt haben.

Tragen Sie im Feld "Benutzername" den Benutzernamen Ihres Benutzerkontos beim Anbieter ein.

Tragen Sie im Feld "Kennwort" das Kennwort Ihres Benutzerkontos beim Anbieter ein.

Klicken Sie zum Speichern der Einstellungen auf "Übernehmen".

Jetzt übermittelt die FRITZ!Box nach dem Herstellen jeder Internetverbindung ihre jeweils aktuellen IP-Adressen an den Anbieter und ist somit immer unter ihrem individuellen Dynamic-DNS-Domainnamen erreichbar.

DuckDNS.org

Die Update-URL für die IPv4- und die IPv6-Adresse:

https://www.duckdns.org/update?domains=<domain>&token=<pass>&ip=<ipaddr>&ipv6=<ip6addr>

GoogleNest TTS issues after setting up ssl

https://www.home-assistant.io/integrations/tts

https://community.home-assistant.io/t/tts-with-ssl-on/207875/3

DNS-Rebind-Schutz

https://avm.de/service/wissensdatenbank/dok/FRITZ-Box-7390/663_DNS-Auflosung-privater-IP-Adressen-nicht-moglich/

formatting of dates

filename: /Data/cams/{{ now().strftime("%Y-%m-%d %H.%M.%S") }} {{ entity_id.name }}.jpg

filename: ‘/tmp/armcrest_camera_{{ now().strftime("%Y%m%d-%H%M%S") }}.jpg’

filename: '/home/homeassistant/.homeassistant/www/armcrest_camera_{{ now().strftime("%Y%m%d-%H%M%S") }}.jpg'

filename: >-
/config/www/rtsp_esp32_{{ "%04d"|format(now().year) }}_{{
"%02d"|format(now().month) }}_{{ "%02d"|format(now().day)
}}_{{ "%02d"|format(now().hour) }}_{{ "%02d"|format(now().minute) }}_{{ "%02d"|format(now().second) }}.jpeg

HA Examples

https://www.home-assistant.io/examples/

Müllkalender

https://smarthomeyourself.de/wiki/homeassistant/muellkalender-darstellung-mit-tagen-datum-in-einer-zeile/

Der folgende Eintrag muss in die configuration.yaml

waste_collection_schedule:

sources:

- name: ics

args:

file: "www/abfall.ics"

customize:

- type: Restabfall

alias: Restabfall

icon: mdi:trash-can

- type: Papiertonne

alias: Papiertonne

icon: mdi:trash-can

- type: Bioabfall

alias: Bioabfall

icon: mdi:trash-can

fetch_time: "04:00"

day_switch_time: "10:00"

sensor: