Home-assistant: Difference between revisions

From DWIKI
mNo edit summary
Line 6: Line 6:
*[https://github.com/geekofweek/homeassistant/ a lot of examples]
*[https://github.com/geekofweek/homeassistant/ a lot of examples]
*[https://www.home-assistant.io/cookbook/ Cookbook, more examples]
*[https://www.home-assistant.io/cookbook/ Cookbook, more examples]
*[https://github.com/resoai/TileBoard TileBoard]


=HOWTOs=
=HOWTOs=

Revision as of 14:17, 20 April 2020

Home assistant

Links

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

FAQ

Config error. See dev-info panel for details.

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


Find new zigbee device

Assuming deconz/phoscon: Got to Developer Tools->Services and enter

deconz.device_refresh


Reload configuration.yml

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

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)

Terms and meanings (or my guesses at it)

device

seems to exist only if discovered?

service

entity

a gnome?

deconz

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

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