Noob questions

Configuration
1

hi,
I’m new here and with ha.
I wanted to discover ha. I installed it with the preconfigured vmdk.
The backbone of my setup is knx, but i have other protocols.
I don’t really understand how ha works and what lies behind entity or device.
At the start ha discovered my sonos play one and my phoscon gateway.
I have only 4 or 5 zigbee devices but i see that a device or entity came up : " configuration tool"
what is it ?

Then i wanted to add my first knx device. I read the docs but struggled with conf files.
Finally, for easing things i put all the conf in the configuration.yaml and i was able to see my first light.
The problem is it isn’t editable in ha as it doesn’t have a unique id.
I have certainly misconfigured something but i can’t see what.
Here is my config:


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

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# 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.21'
    port: 3671
    local_ip: '192.168.0.104'

light:
  # See "sensor" remarks above for an explanation of the resulting entity_ids
  platform: knx
    # switched light
  name: 'Lumière Bureau'
  address: '0/0/32'
  state_address: '0/1/32'
2 
- platform: knx
3

Thnak you for your answer.
tried that and restarted the server but same result.
I also tried with double quotes around the name.

I think i also will have to learn xknx syntax as i have several hundreds of group adress.

4

try getting rid of the funky e.

5

also what is the issue exactly? I’m not sure what you mean in your first post.

6

when i go to config/entity it appears to be read only.
When i go to config/integration i don’t see an integration related to knx.
i changed the “è” for “e” but same result.

7

are you refering to the interface where all devices are? if so, that’s normal. All items configured in yaml will behave that way.

If you want to use your light, just add it to the interface and use it.

8

This should not be necessary. Just use HA configuration style.

9

ok got it.
I destroyed my conf and use xknx now.
It’s working but i don’t find this very user friendly coming from jeedom.

10

i must admit i’m a bit lost. I can use a light with ha or xknx but for now it’s very simple configuration.
I can not imagine how i’ll do the equivalent of i have now.

If i use xknx conf style i have to declare

knx:
  config_file: 'xknx.yaml'

and use xknx syntax like

general:
  own_address: '15.15.249'

connection:
  tunneling:
    gateway_ip: '192.168.0.21'
  
groups:
  light:
    Bureau.Light_1: {group_address_switch: '0/0/32', group_address_switch_state: '0/1/32'}

If i use ha conf style i have to declare a conf file like knx.yaml

knx: !include knx.yaml

and the use syntax like

light:
  platform: knx
    # switched light
  name: 'Lumière Bureau'
  address: '0/0/32'
  state_address: '0/1/32'

Am i correct ?

11

Yes almost right - you need to do a yaml list for the lights. So it’s

light:
  - platform: knx
    address: '1/0/9'

Note the - and the indentation.
And light is not defined in Knx config. So I’d just use

knx:
# init Knx before including lights. No arguments needed for tunneling connections. 
!include: light.yaml
# lights are defined at the same level as knx 
# this file would hold all lights for all your platforms.

In my opinion xknx style has no advantages (except maybe for Routing connections because of own_address).
HA style is better documented so I’d stick with this.
Im not sure if you can use both config together.

12

thanks i had light one level under knx :grinning:

13

i spoke too soon. I can’t have it working with !include
Syntax is a nightmare

14

My bad, sorry. It should be

light: !include: light.yaml

according to https://www.home-assistant.io/docs/configuration/splitting_configuration/
I have not tried this myself yet… I’m using a huge configuration.yaml for too long now xD

15

doesn’t work either
i also tried:

light: !include light.yaml

with no luck

16

got it.
i started lights.yaml with light:
you have to start with - platform

17

Did you not make that change when I posted it on the second post?

I wasn’t making a guess, I was telling you that was wrong and should have been fixed.

18

Yes i made that change.
What i meant is if you split conf with include directive, for example for the lights,
in configuration.yaml you write light: !include lights.yaml
then in the lights.yaml file you mustn’t start with light:
but directly with - platform

Now i see how to declare my devices even if then don’t appear in devices.
I have not found how to put them in a room.
I have to find out if i can use all of my devices and then how to translate my automations scripts and i have around 50 written in php.

19

Hello,
So did you find you to setup your KNX device into a room?
Am trying HA (I am using at this time Jeedom), I hace the same behavior as you that “The problem is it isn’t editable in ha as it doesn’t have a unique id.”

20

Knx entities still don’t have unique ids. So they can’t be assigned to rooms unfortunately.

1 Like