Acas
(Acas)
April 9, 2021, 8:00am
1
Hello, I was able to make normal knx configuration working like this
knx:
light:
- name: "rgbwtest"
address: "1/0/9"
individual_colors:
red:
brightness_address: "2/0/5"
blue:
brightness_address: "2/0/6"
green:
brightness_address: "2/0/7"
white:
brightness_address: "2/0/8"
BUT… my normal config is in XKNX format.
my xknx.yaml does not render a RGB wheel if i address the individual groups with the syntax in https://xknx.io/light.html but only a generic on off switch that does nothing.
Anyone has got any clue?
Or… Is possible to do a hybrid knx + xknx config?
my xknx.yaml:
general:
own_address: "15.15.249"
groups:
light:
DimmerRGBW:
group_address_brightness_red: 2/0/5
group_address_brightness_green: 2/0/6
group_address_brightness_blue: 2/0/7
group_address_brightness_white: 2/0/8
Thanks
farmio
(Matthias Alphart)
April 9, 2021, 9:10am
2
xknx.yaml and config_file:
is deprecated and will be removed next version.
You can use https://xknx.io/config-converter/ to convert to HA yaml Schema.
Acas
(Acas)
April 9, 2021, 1:24pm
4
i have this kind of problem:
to turn the lights OFF i have to send a 0 brightness value to the knx groups for each of RGBW
because there is no switch on/off groups in the knx device i am using, i just need to send a 0 value
White is sending 0 as brightness and it works, but the minimum brightness for the other three channels (RGB) in hassio seems to be 1.
If i do something like this using a dummy knx group address for “off switch”:
automation :
trigger:
- platform: state
entity_id:
- light.dmx
to: "off"
action:
- service: persistent_notification.create
data:
message: 'start dmx off'
- service: light.turn_on
target:
entity_id:
- light.dmx
data:
white_value: 0
rgb_color:
- 0
- 0
- 0
brightness: 0
- service: persistent_notification.create
data:
message: 'end dmx off'
the rgb channels are still on… has anyone got a clue on how to send a 0 in rgb channels in hassio?
- name: "dmx"
address: "1/0/9"
individual_colors:
red:
brightness_address: "2/0/5"
blue:
brightness_address: "2/0/6"
green:
brightness_address: "2/0/7"
white:
brightness_address: "2/0/8"
farmio
(Matthias Alphart)
April 9, 2021, 1:48pm
5
You can use the knx.send service from your automation to send the value directly.
What kind of device is this? It’s very untypical for a knx device not having a 1bit on/off communication object.
Acas
(Acas)
April 9, 2021, 1:56pm
6
it’s a KNX to DMX gateway.
I can map every DMX channel as it was a dimmer and it works fine, but to turn off the DMX channel i have to send a zero
Thanks for the knx.send hint, i will look into this immediately
Acas
(Acas)
April 9, 2021, 2:30pm
7
doing like this seems to work, but i fear for my mental health (i have to do hundreds of these)
However: thanks!!
automation 2:
trigger:
- platform: state
entity_id:
- light.dmx
to: "off"
action:
- service: persistent_notification.create
data:
message: 'start dmx off'
- service: knx.send
data:
address: 2/0/5
payload: [0]
- service: knx.send
data:
address: 2/0/6
payload: [0]
- service: knx.send
data:
address: 2/0/7
payload: [0]
- service: knx.send
data:
address: 2/0/8
payload: [0]
- service: persistent_notification.create
data:
message: 'end dmx off'
farmio
(Matthias Alphart)
April 9, 2021, 2:33pm
8
Not sure if you will be very happy with this. The knx light device relies on the “address” you set up as dummy GA for it’s on/off state - that’s why it is required in config.
Maybe using a template light with knx.send and knx_event is a better way with your special setup.
farmio
(Matthias Alphart)
April 9, 2021, 2:38pm
9
You can send to multiple GAs like this:
- service: knx.send
data:
address:
- 2/0/8
- 2/0/9
payload:
- 0
And if your GA structure allows, maybe you could even use templates to have one automation trigger all light entities depending on eg. the dummy address.
farmio
(Matthias Alphart)
April 30, 2021, 10:01pm
11
XKNX:main
← farmio:individual_colors
opened 09:58PM - 30 Apr 21 UTC
<!--
You are awesome! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template!.
-->
## Description
<!--
Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.
List any dependencies that are required for this change.
-->
- Support individual color lights without switch GAs
- Change individual_color light unique_id to use brightness instead of switch GAs
I guess there are more individual color lights with just brightness than just switches.
Fixes # (issue)
## Type of change
<!--
Please tick the applicable options.
NOTE: Ticking multiple options most likely indicates
that your change is to big and it is suggested to split it into several smaller PRs.
-->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update
## Checklist:
- [x] I have performed a self-review of my own code
- [x] The documentation has been adjusted accordingly
- [x] The changes generate no new warnings
- [x] Tests have been added that prove the fix is effective or that the feature works
- [x] The changes are documented in the changelog
- [ ] The Homeassistant plugin has been adjusted in case of new config options
It will require some changes to the HA integration too - mostly the Schema and unique_id.
I’m curious, what kind of project is this?
farmio
(Matthias Alphart)
May 17, 2021, 11:10am
12
This is now merged to current dev. Will be useable in 2021.6