Home-assistant

Home assistant

Links

• Homepage
• Home Assistant Glossary
• Installing in python virtual environment (remember to pip install --upgrade pip first)
• a lot of examples
• Cookbook, more examples
• Awesome Home Assistant

• CSS values/themes

• Usage analytics

Home assistant and MQTT

• https://www.home-assistant.io/integrations/mqtt/

Triggers

Trigger

On multiple triggers logical OR applies

Internal structure in venv

.homeassistant

Default location for configuration files and logs

.storage

Cache and stuff

core.device.registry

The devices and their entities

Cards

• TileBoard
• mini-graph-card
• Apexcharts-card

HOWTOs

Logging

See logger

Add rfxtrx device

• https://www.home-assistant.io/integrations/light.rfxtrx/

but when you don't see new switch. enable debugging in configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.components.rfxtrx: debug

rfxtrx:
 device: /dev/ttyUSB0-RFX433XL
 debug: true

and look for

homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 1ed0732_3 Class: LightingDevice Sub: 0, Pkt_id: 0b10000101ed071303010f60)

and use the Pkt_id in your configuration:

switch:
  platform: rfxtrx
  devices:
    0b10000101ed071303010f60:
      name: myswitch1

Splitting configuration

https://www.home-assistant.io/docs/configuration/splitting_configuration

Including files in configuration.yaml

group: !include groups.yaml

In groups.yaml:

samplegroup:
  name: my.samplegroup
  entities:
  - binary_sensor.one
  - binary_sensor.two

Automations

Using this line your automations get saved here

automation: !include automations.yaml

script: !include scripts.yaml

templates

template: !include templates.yaml

TODO CHECK THIS In templates.yaml:

- binary_sensor:
  name: "Is closed"
  state: >-
    {{ is_state('binary_sensor.openclose_30','on') 
or is_state('binary_sensor.openclose_31','on') }}

Migration to mysql

• https://www.srm.im/2017/06/11/home-assistant-migration-from-sqlite3-to-mariadb-mysql/

Update letsencrypt cert

certbot certonly --standalone
/etc/letsencrypt/live/hass.example.com/* ~hass/.homeassistant/certs/

Conditions

Multiple conditions

AND by default

Sunset/sunrise

• Sun condition

Upgrading home-assissant

For this is, as user hass:

 

cd homeassistant
#python -m venv . ??
source bin/activate

1. geen --user in venv

pip3 install --upgrade homeassistant

FAQ

ModuleNotFoundError: No module named 'pip'

Check homeassistant/bin/pip

FAQ

The device is disabled by Config entry.

Means disabled, just click on edit icon and enable it

 

This entity does not have a unique ID

probably means adding "entity_id: foo.bar"

Error during logbook entry retrieval

refresh browser

Offset

-1:15:00

Binary sensors

Door open or closed

on  = Open

offf = Closed

 

In a group:

Open + Closed = Open

 

 

Platform configuration is deprecated

"platform" being used in configuration file, while the integration no longer needs that

Config error. See dev-info panel for details.

That's under "Developer tools" tab "Logs"

 

 

Find new zigbee device via conbee/deconz

Assuming phoscon already found it: Go to Developer Tools->Services and enter

deconz.device_refresh

and then look in home-assistant.log for a lines like

INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.deconz entity: sensor.temperature_20

after a while it should also show up in Configuration->Entities (TIP: here change the Entity ID to something more useful)

The name you give the device on the deconz interface will show up in HA under "Devices"

Reload configuration.yml

That's done by the "restart server", make sure to run "check configuration" first

Where did "check configuration" go?

Developer Tools->Services

reload configuration from commandline

hass --script check-config ??

Unable to open database "home-assistant_v2.db": file is encrypted or is not a database

try

sqlite3 home-assistant_v2.db

 

Test templates

ansible localhost -m debug -a 'msg=Template:"0.005"'

 

homeassistant.exceptions.HomeAssistantError: Entity id already exists

In at least one case restarting home-assistant fixed it (deconz sensor)

Unable to open the Home Assistant UI in a browser.

??

AttributeError: module 'homeassistant.util.yaml.loader' has no attribute 'Secrets'

An integration needs upgrading

UI showing "restored" in red

was re-enabled but without data (yet?)

 

Frontend

Show badge only when condition met

https://community.home-assistant.io/t/conditional-badge-at-all-possible/133313/5

       style: |
         :host {
              display: {% if states('sensor.motion_living_battery') | float > 90 %} none; {% endif %}
         }

Terms and meanings (or my guesses at it)

device

seems to exist only if discovered?

entity

a gnome?

 

Platform

https://developers.home-assistant.io/docs/creating_platform_index/

 

binary_sensor

https://esphome.io/components/binary_sensor/homeassistant.html

deconz

pydeconz.errors.Unauthorized: /lights/2/state unauthorized user

I found simply restarting home-assistant made this go away again

ZHA

Zigbee Home Automation Probably the best way to use zigbee now