KNX und Home Assistant

ngeurten · November 22, 2020, 12:38pm

Hallo Zusammen,

KNX an sich funktioniert prima, Home Assistant im Grunde auch, ich bekomme nur die beiden nicht zusammengeschlossen.
Die Grund-Einstellungen habe ich richtig, denke ich.

Configure a default setup of Home Assistant (frontend, api, etc)

default_config:

Text to speech

tts:

platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

knx: !include xknx.yaml

knx:
config_file: ‘/config/xknx.yaml’

Und dann das Config File

knx:
tunneling:
host: ‘192.168.0.211’ //knx ip gateway
port: 3671
local_ip: ‘192.168.0.244’ //HA

knx:
cover:
-name: “Buero klein”
move_short_address: ‘2/0/8’
stop_address: ‘2/4/0’

Aber wie bekomme ich nun die Entitäten hinzugefügt, damit Home Assistant das erkennt ?
Das verstehe ich irgendwie nicht.

Und kann ich irgendwie testen, ob der KNX Ip Gateway auch richtig funktioniert?
Danke!

farmio · November 22, 2020, 1:27pm

Das sollte weg. Nimm einfach alles aus dem config file und kopiere es in configuration.yaml. Unter ‘config_file:’ wird etwas anderes erwartet.

Es sollte nur 1x ‘knx:’ in der config vorkommen - nicht vor jeder Platform (Cover, light, etc). Siehe KNX - Home Assistant

Den ganzen ‘tunnelling’ Block kannst du weglassen - der ist optional.

Wenn’s ne eigene Datei sein muss kannst du das immer noch machen wenn alles funktioniert. Splitting up the configuration - Home Assistant

Wenn du hier deine configs in ``` ```stellst kann man sie auch besser lesen

Burningstone · November 22, 2020, 4:01pm

Und das nächste Mal bitte auf Englisch.

ngeurten · November 22, 2020, 4:08pm

Oh, sorry.

ngeurten · November 22, 2020, 4:13pm

default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
#knx: !include xknx.yaml

#knx:
#  config_file: '/config/xknx.yaml'

knx:
  tunneling:
  host: '192.168.0.211' //knx ip gateway
  port: 3671
  local_ip: '192.168.0.244' //HA

  cover:
  -name: "Buero klein"
  move_short_address: '2/0/8'
  stop_address: '2/4/0' ```

It´s not working now !
What is wrong?

Error Log:

Error loading /volume3/@appstore/homeassistant/var/config/configuration.yaml: while parsing a block mapping
  in "/volume3/@appstore/homeassistant/var/config/configuration.yaml", line 19, column 3
expected <block end>, but found '<scalar>'
  in "/volume3/@appstore/homeassistant/var/config/configuration.yaml", line 20, column 25

farmio · November 22, 2020, 4:21pm

ngeurten:

knx:
  tunneling:
    host: '192.168.0.211' # knx ip gateway
    # port: 3671 # this is default anyway
    # local_ip: '192.168.0.244' # optional

  cover:
    - name: "Buero klein"
      move_short_address: '2/0/8'
      stop_address: '2/4/0'

Indentation / spaces matter!
// isn’t marking comments. # is.

ngeurten · November 22, 2020, 4:39pm

farmio:


# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

knx:
  tunneling:
  host: '192.168.0.211'

 cover:
  - name: "Buero klein"
    move_short_address: '2/0/8'
    stop_address: '2/4/0'

It´s not working.
I find no errors.

Error loading /volume3/@appstore/homeassistant/var/config/configuration.yaml: while parsing a block mapping
in “/volume3/@appstore/homeassistant/var/config/configuration.yaml”, line 3, column 1
expected , but found ‘’
in “/volume3/@appstore/homeassistant/var/config/configuration.yaml”, line 18, column 2

farmio · November 22, 2020, 4:49pm

cover: is still missing a Space and host: ... 2 spaces. Maybe try to use an editor that helps you lint your yaml (eg VSCode).
Or just copy&paste from above ^^

ngeurten · November 22, 2020, 10:22pm

Thanks, it´s working now.
But I found no entities, how can i integrate this, my example “Büro”.

farmio · November 22, 2020, 10:34pm

It should be available as entity when configured right after a restart of HA.

ngeurten · November 22, 2020, 10:50pm

OK, i have done that.

But I found only this:

2020-11-22 23_50_04-Übersicht - Home Assistant

I found no office like my config

cover:

name: “Buero klein”
move_short_address: ‘2/0/8’
stop_address: ‘2/4/0’

farmio · November 23, 2020, 5:58am

¯_(ツ)_/¯ where are you looking? Are there log entries? Are you sure your yaml is correct?

Meenzer1234 · November 23, 2020, 9:48pm

Hi , i have the same problems since updating HA to 0.118.0 no KNX Entities anymore … i dont make changes on my configuration.yaml. Is the same as before:

> homeassistant:
>   packages: !include_dir_named Packages
> 
> # Configure a default setup of Home Assistant (frontend, api, etc)
> default_config:
> 
> # Text to speech
> tts:
>   - platform: google_translate
> 
> group: !include groups.yaml
> automation: !include automations.yaml
> script: !include scripts.yaml
> scene: !include scenes.yaml
> 
> frontend: 
>   themes: !include_dir_merge_named themes

and in the Packages folder is the knx.yaml

>##########################
> #KNX Ip Interface
> ##########################
> knx:
>   tunneling:
>     host: '192.168.2.11'
> 
> ##########################
> #Licht
> ##########################
>   light:
> #Dachgeschoss
>     - name: 'Büro'
>       address: '4/4/15'
>       state_address: '1/2/23'
>     - name: 'Bad DG'
>       address: '1/0/24'
>       state_address: '1/2/24'

and some more Lights, and covers … etc-

farmio · November 23, 2020, 10:03pm

which version were you running before? any warnings in the logs? is the xknx integration started (log entry like INFO (MainThread) [xknx.log] XKNX v0.15.4 starting tunneling connection to KNX bus.)?

Meenzer1234 · November 23, 2020, 10:15pm

thats what i dont understand , i dont usw xknx but i have in the logs errors.

farmio · November 23, 2020, 10:31pm

Xknx is the Library used by the knx integration - HA takes care of installing and using it.

The 3rd entry is the interesting one. It should tell you where your configuration problem is. 1st and 2nd can be ignored for now.

Again: which version were you running before updating to 0.118?

Meenzer1234 · November 24, 2020, 9:37am

0.117.x … (x= last one).

So before i worked with exact this configuration

farmio · November 24, 2020, 10:25am

So what is the “error during Setup of component knx” in your screenshot…

Meenzer1234 · November 24, 2020, 12:37pm

Logger: homeassistant.setup
Source: components/knx/factory.py:105
First occurred: 23. November 2020, 17:08:03 (1 occurrences)
Last logged: 23. November 2020, 17:08:03

Error during setup of component knx
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 213, in _async_setup_component
    result = await task
  File "/usr/src/homeassistant/homeassistant/components/knx/__init__.py", line 154, in async_setup
    create_knx_device(platform, hass.data[DOMAIN].xknx, device_config)
  File "/usr/src/homeassistant/homeassistant/components/knx/factory.py", line 40, in create_knx_device
    return _create_light(knx_module, config)
  File "/usr/src/homeassistant/homeassistant/components/knx/factory.py", line 105, in _create_light
    return XknxLight(
  File "/usr/local/lib/python3.8/site-packages/xknx/devices/light.py", line 68, in __init__
    self.switch = RemoteValueSwitch(
  File "/usr/local/lib/python3.8/site-packages/xknx/remote_value/remote_value_switch.py", line 31, in __init__
    super().__init__(
  File "/usr/local/lib/python3.8/site-packages/xknx/remote_value/remote_value.py", line 42, in __init__
    group_address_state = GroupAddress(group_address_state)
  File "/usr/local/lib/python3.8/site-packages/xknx/telegram/address.py", line 202, in __init__
    self.raw = self.__string_to_int(address)
  File "/usr/local/lib/python3.8/site-packages/xknx/telegram/address.py", line 227, in __string_to_int
    raise CouldNotParseAddress(address)
xknx.exceptions.exception.CouldNotParseAddress: <CouldNotParseAddress address="7//20" />

farmio · November 24, 2020, 1:07pm

Well, did you read it?