Difference between revisions of "Home-assistant"

From DWIKI
⧼monobook-jumptonavigation⧽⧼monobook-jumptosearch⧽
m
m
Line 1: Line 1:
Home assistant
 
 
 
  
 +
Home assistant
  
 +
 
  
 +
 
  
 +
 
  
 
= Links =
 
= Links =
Line 17: Line 18:
 
*[https://github.com/chipriley/lovelace-css-values CSS values/themes]  
 
*[https://github.com/chipriley/lovelace-css-values CSS values/themes]  
  
*[https://analytics.home-assistant.io/ Usage analytics]
+
*[https://analytics.home-assistant.io/ Usage analytics]  
  
 
== Home assistant and MQTT ==
 
== Home assistant and MQTT ==
  
*[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/]  
  
 
= Cards =
 
= Cards =
 +
 
*[https://github.com/resoai/TileBoard TileBoard]  
 
*[https://github.com/resoai/TileBoard TileBoard]  
 
*[https://github.com/kalkih/mini-graph-card mini-graph-card]  
 
*[https://github.com/kalkih/mini-graph-card mini-graph-card]  
*[https://github.com/RomRider/apexcharts-card Apexcharts-card]
+
*[https://github.com/RomRider/apexcharts-card Apexcharts-card]  
 +
 
 +
= HOWTOs =
  
=HOWTOs=
+
== Add rfxtrx device ==
==Add rfxtrx device==
+
 
*https://www.home-assistant.io/integrations/light.rfxtrx/
+
*[https://www.home-assistant.io/integrations/light.rfxtrx/ https://www.home-assistant.io/integrations/light.rfxtrx/]
  
 
but when you don't see new switch. enable debugging in configuration.yaml:
 
but when you don't see new switch. enable debugging in configuration.yaml:
 +
 
  logger:
 
  logger:
 
   default: info
 
   default: info
Line 42: Line 47:
 
   debug: true
 
   debug: true
  
and look for  
+
and look for
 +
 
 
  homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 1ed0732_3 Class: LightingDevice Sub: 0, Pkt_id: 0b10000101ed071303010f60)
 
  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:
 
and use the Pkt_id in your configuration:
  
Line 52: Line 59:
 
       name: myswitch1
 
       name: myswitch1
  
==Migration to mysql==
+
== Migration to mysql ==
*https://www.srm.im/2017/06/11/home-assistant-migration-from-sqlite3-to-mariadb-mysql/
 
 
 
  
 +
*[https://www.srm.im/2017/06/11/home-assistant-migration-from-sqlite3-to-mariadb-mysql/ https://www.srm.im/2017/06/11/home-assistant-migration-from-sqlite3-to-mariadb-mysql/]
  
 +
 
  
 +
 
  
 +
 
  
 
= FAQ =
 
= FAQ =
  
 
== Platform configuration is deprecated ==
 
== Platform configuration is deprecated ==
 +
 
"platform" being used in configuration file, while the integration no longer needs that
 
"platform" being used in configuration file, while the integration no longer needs that
  
Line 145: Line 155:
 
           }
 
           }
  
=Terms and meanings (or my guesses at it)=
+
= Terms and meanings (or my guesses at it) =
==device==
+
 
 +
== device ==
 +
 
 
seems to exist only if discovered?
 
seems to exist only if discovered?
==service==
 
  
 +
== service ==
 +
 +
== entity ==
  
==entity==
 
 
a gnome?
 
a gnome?
  
==deconz==
+
 
===pydeconz.errors.Unauthorized: /lights/2/state unauthorized user===
+
 
 +
== Platform ==
 +
 
 +
[https://developers.home-assistant.io/docs/creating_platform_index/ https://developers.home-assistant.io/docs/creating_platform_index/]
 +
 
 +
 
 +
 
 +
== binary_sensor ==
 +
 
 +
[https://esphome.io/components/binary_sensor/homeassistant.html 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
 
I found simply restarting home-assistant made this go away again
  
=Customizing home-assistant=
+
= Customizing home-assistant =
==Module card-mod==
+
 
 +
== Module card-mod ==
  
 
==Custom-UI
 
==Custom-UI

Revision as of 11:22, 29 August 2021

Home assistant

 

 

 

Links

Home assistant and MQTT

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

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