Failed to load blueprint: while parsing a block mapping in “/config/blueprints/automation/kalhimeo/knx-light-entities-control-beta.yaml”, line 1, column 1 expected , but found ‘-’ in “/config/blueprints/automation/kalhimeo/knx-light-entities-control-beta.yaml”, line 524, column 1
very cool Blueprint and it works fine.
BuT I have one question: is it possilbe to implement a switch that a dimmable light always starts with 100%? Normally when i turn off a dimmable light with e.g. 25% and return it on, it goes again on with 25%.
Thank you very much!
Hi Martin, this should usually be a setting on your light itself instead of the switch. I don’t know which light protocol you try to trigger, but maybe have a look there ?
Does this Automation runs smoothly for everyone in here? I’m really desperate. If I configure it, it runs great for a few hours but then the configured GAs wont’t trigger the automation. I even tried beta version but no success. Look at this:
Here you can see my defined GAs
Is there any Information you are missing? I just asked if there is anyone else, having this problem. I provided a Trace of the automation, screenshot of the automation config and of the Bus monitor, I think these are the key informations?
Hi, the problem must be somewhere in your KNX or blueprint configuration, it seems to work for everyone else (including me). Your screenshots do not show anything which can help unfortunately. Check the trace log steps to see where it stops/fails.
Funny thing is that since the last Home Assistant OS updates it works like charm again and I changed NOTHING… Absolutely no clue. @kalhimeo the blueprint has gotten not even triggered… But let’s wait and see…
Hello,
I’m fairly new to HA but I have a problem with this Blueprint.
Maybe it’s me who doesn’t know how to configure it properly, but I can’t control my relatively dimmable lights.
I did set the right address groups but I can’t figure out how to change the variation afterwards.
I tested it by removing the “Brightness” from my KNX light configuration, as I could see it wasn’t the right DPT.
I’ll probably need a little help to configure it.
I’m putting up a few screenshots to guide me if I need to remove just one little thing.
Maybe it’s silly, but I can’t figure it out at all.
Thanks to those who will see this
Salut ;),
J’ai ajouté une lumière pour le test via le File Editor et redirigé le Blueprint vers la nouvelle lumière créée mais rien n’y fait, cela ne change pas lorsque je module la lumière sur l’élément.
I’ve added a light for the test in the File Editor and redirected the Blueprint to the new light created, but it doesn’t work, it doesn’t change when I modulate the light on the element.
The connection between my KNX IP interface and Home Assistant is active, and all the other non-dimmable lights are working properly. I just can’t modulate the intensity of some lights via HA that are already dimmable in my house using the buttons.
When I retrieved all the Group Addresses that were linked to the dimming parameter, I did a test from the group monitor on ETS to check that it was working and I did have parameters returning for example “Increase - 80%” or “Decrease - 30%” linked to DPT 3.007 and visually, my light was increasing and decreasing in intensity.
I think that you are missing the point of this blueprint. The goal is to use a KNX switch (ie. a wall push button) to control any light entity from Home Assistant. If you try to control a KNX light via a KNX switch, you should rather configure that only on the KNX side (via ETS).
You should never have to configure a KNX light to work with this Blueprint.
I now have a better understanding of my mistake and I had misunderstood the purpose of this Blueprint, and I think I’ve got a better idea of what I need to change in my configuration. I’m going to start again from ETS and redo the tests linked to my variation problem. Now that I’ve understood the real purpose of this Blueprint, it’s really quite incredible x) and will help me with other things.
I had a similar issue:
I have multiple lights (hue) which are controlled through homeassistant using KNX switches.
This blueprint always worked fine so far.
Now today, I updated homeassistant to the newest version and the automations stopped working for all lights controlled through this blueprint.
the blueprint was not triggered. Unfortunately, I don’t know where to debug this. there is no trace since the automations were not triggered at all. Looks like the automations using this blueprint did not get any information about new telegrams…
In the group monitor I saw all the incoming telegrams from my switches as expected, though.
I tried reloading the KNX integration, but noting changed.
What I tried then was to “resave” the automation with one of the not working blueprints: I changed the group address of one light to something else and changed it back just after. Magically, all the switches started working again…
To me it looks like the automations lost their connection with the KNX interface (in homeassistant) and resaving an automation solved this again.
One additional comment:
I had ETS open when I rebooted homeassistant. Not sure whether this could have anything to do with the problem, since I saw all incoming telegrams in homeassistant…
Hello, your blueprint looks awsome! Thank you so much.
Unfortunately, I miss the option to dim the color temperature and HSV-Color relatively. I’m using the MDT Glastaster II Smart | Serie .02 and it only supports relativ dimming (DP3.007) for TunableWhite (Status DP5.001 )and RGB/HSV (Status 5.003 ?!).