Any progress on this?
My installation has old covers which do not report any position. Actually, I don’t want HA to store any position information at all since any cached value gets incorrect as soon as somebody opens or closes covers using a KNX wall switch.
Try this (example):
cover:
- platform: knx
name: Kitchen.Shutter
move_long_address: '3/0/0'
move_short_address: '3/0/1'
Thanks for everyone’s suggestion.
I tried Joca‘s configuration, but was not successful (because there is no position state address, home assistant can‘t read the current state / position of the cover).
Right now, I‘m using following configuration:
- platform: knx
name: "Terasse OG Storen kleine Terasse"
move_long_address: '10/5/224'
move_short_address: '10/5/223'
position_state_address: '2/4/37'
travelling_time_down: 15
travelling_time_up: 15
invert_position: true
But the state address still doesn’t really work, because home assistant expects an 8bit value, but my cover only supports 1bit state (up or down).
It would be really great if in a future release the knx integration allows using either a position_state_address or a state_address.
Hello,
same issue here. My cover as no position_state_address. My KNX cover is definded like this:
cover:
- platform: knx
name: "Arbeiten"
move_short_address: '1/3/1'
move_long_address: '1/3/2'
travelling_time_down: 12
travelling_time_up: 12
The status after reboot is
current_position: 0
After reboot I try to send tho cover down. Directly from the service test page with cover.close_cover. But nothing happens.
If I manually move the cover up (down I cant press in the UI) I hear the actor clicking. Only after that move I can use the service successful.
Seems like a bug to me. Can anyone test this on his installation. Comment the position_state_addressout and try to send the cover down directly after reboot from the service web console. I would like to understand if this is a general issue or if I can do anything about it.
Current result is that covers dont work until once manually and only in the UI of HA are moved. Moving them on KNX is not helping. This makes automation for the blinds rathe useless atm.
Regards
Ralf
Same situation here - I would rather prefer that the down/up arrows gray option would be enabled if it’s too hard to change the KNX <-> HA mapping with 1-bit / 8-bit.
Actually the covers are unusable in this situation.
Hello there!
I’ve created a feature request, please vote it, so we can try to get something 
Where do I find the feature request to upvote?
Tnx. Voted.
Hello,
is there any update on this issue? WAF is significantly down bc blinds not working properly.
Regards
Ralf
I think that recently (less than 10 years) all knx shutter actuators has 1byte status position object.
Are your knx actuators old?
Yes. I started my journey 13 years ago. Not one device failed since then. I don’t want to replace them when this can be done with a few lines of code. I solved it for now. I only have now 0/100% states for position. Better than nothing. I also worked on an appdaemon class which takes care of monitoring position. Works like a charm. Still one piece missing. I continue to work on this topic.
Same for modern actuators running electronical controlled motors with soft-start/stop. Absolute Position is unreliable in this case.
@farmio, I saw you closed the topic in github on this matter and created a merge request. Thank you very much.
How can I find out in which HA version your newly created patch will be included?
Sure. I have (yet) no clue what a custom component is. I will learn quickly. I am running hassio. Can this be installed via HACS or alike?
$ find / -name "*xknx*"
$
The custom component is an external (as in not shipped with HA) integration. We use it for testing. It has the platform name “xknx” instead of “knx” to allow it to run along each other. It doesn’t autoinstall a specific xknx version but just uses whatever it finds in pythonpath - so PRs or branches can be tested.
(version conflicts could occur if standard knx is or was used in the Installation - I Never tested running both with different xknx versions)
Tbh I don’t know. Some say it works on hassio, some say it doesn’t. I don’t think it is in Hacs.
I can only link to the doc on how to install it for a standard installation: https://xknx.io/home_assistant
I tried it years ago with Hassos but it didn’t work then. But there has been a lot of change. With pip install or docker it works for sure.
Hi Matthias,
I updated to 0.115.2. The cover can now be moved and the up and down symbols in the UI now represent quite good the status. Say you have a cover which drives 12sec. If you run it form open to closed for 6 sec both directions can be used in the UI. This was not the case earlier.
Big thank you.
I was in the impression that the attribute current_position is updates as well to say 50% in the example above. This seems not the case for me. Is this expected behaviour?
Best Regards.
Ralf
It works on my setup. The slider in the UI card moves when I open/close and if I drag it a movement of the cover is initiated.