I’m trying to migrate from OpenHAB to Home Assistant, but I’m having problems to migrate all my KNX items.
My sensor.yaml file looks like:
- platform: knx
name: 'Heizung KG Wartung Stellantriebe'
address: '2/0/4'
The error I get is the following:
Error while setting up platform knx
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/knx/sensor.py", line 26, in async_setup_platform
async_add_entities_config(hass, config, async_add_entities)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/knx/sensor.py", line 47, in
async_add_entities_config
value_type=config.get(CONF_TYPE))
File "/usr/local/lib/python3.7/site-packages/xknx/devices/sensor.py", line 49, in __init__
value_type=value_type)
File "/usr/local/lib/python3.7/site-packages/xknx/devices/remote_value_sensor.py", line 71, in __init__
raise ConversionError("invalid value type", value_type=value_type, device_name=device_name)
xknx.exceptions.exception.ConversionError: <ConversionError description="invalid value type" device_name="Heizung KG Wartung Stellantriebe" value_type="None"/>
I just tested as you suggested, but still get the same error: xknx.exceptions.exception.ConversionError: <ConversionError description="invalid value type" device_name="Heizung_KG_Wartung_Stellantriebe" value_type="None"/>
What kind of sensor are you using?
If it is a binary sensor, you have to use the binary sensor category (you can´t use it in the sensor.yaml file). Yo must use it in binary_sensor.yaml file or put the code inside or use it directly in the configuration.yaml file.
Example:
Hi,
I already had a look at the supported knx types. The problem is, that this KNX type (DPT 2.001 - 2 bit) is not supported. So, I’m looking for a workaround to get my heating service activated.
KNX documentation about DPT 2.001 is saying:
These datapoint types are intended for applications offering a priority control that
has precedence over the normal (manual) operation. In other words, if an actuator
is switched via its priority datapoint, switching via its usual DPT 1.xxx group objects
is disabled. Switching with priority is ensured via 2-bit datapoint types. The interaction
between the 2 and the 1 bit datapoint functions according to the underneath diagram:
Hi Joca,
wondering how this would work?
Let’ assume I have a light with a switch (1bit) address. Besides I have my priority control switch.
Scenario: I want to disable the priority and let the switch decide how the light status is. Having just 1 bit we would need to set the priority control to 0.
Scenario: I want to enable the priority control and have the light off, so the actor ignores the switch status. How can this be achieved if I only have two states in the priority control?
Maybe you can do the same but differently (without priority).
I think I have something similar with my KNX motion sensors. The sensors have a lock function (1bit), where I choose to lock with “0”. The same blocking address I put on the actuator output, so when I send the blocking order to the detector it also turns off the light.