Home-assistant: Difference between revisions

From DWIKI
mNo edit summary
mNo edit summary
Line 2: Line 2:
Home assistant
Home assistant


 
 
 


= Links =
= Links =
Line 23: Line 18:


*[https://www.home-assistant.io/integrations/mqtt/ https://www.home-assistant.io/integrations/mqtt/]  
*[https://www.home-assistant.io/integrations/mqtt/ https://www.home-assistant.io/integrations/mqtt/]  
==Automations ==
== Triggers ==
https://www.home-assistant.io/docs/automation/trigger
On multiple triggers logical OR applies


= Cards =
= Cards =
Line 89: Line 92:
=== Door open or closed ===
=== Door open or closed ===


On = Open  
On = Open Off = Closed
Off = Closed


== Platform configuration is deprecated ==
== Platform configuration is deprecated ==

Revision as of 10:58, 11 September 2021

Home assistant


Links

Home assistant and MQTT


Automations

Triggers

https://www.home-assistant.io/docs/automation/trigger On multiple triggers logical OR applies


Cards

HOWTOs

Add rfxtrx device

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

Migration to mysql

 

 

 

 

FAQ

The device is disabled by Config entry.

Means disabled, just click on edit icon and enable it

 

Error during logbook entry retrieval

refresh browser

 

Binary sensors

Door open or closed

On = Open Off = Closed

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"

 

 

Upgrading home-assissant

For this is, as user hass:

 

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

Find new zigbee device via conbee/deconz

Assuming phoscon already found it: Got 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)

Reload configuration.yml

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

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

       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?

service

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

Customizing home-assistant

Module card-mod

==Custom-UI