I have 27 covers in my house, which I can freely position within LCN. As is stands, your motor integration is not supporting this feature. Is there a particular reason for not offering that?
I am thinking about workarounds. One way would be to send key presses from HA to LCN, for which the respective position command is then programmed with LCN-Pro. In the documentation I saw some examples how to use this. What I am uncertain about is if one can send short/long/released for a key. Or is a key hit always interpreted as short?
Hi @Sourcer63 ,
having time based positioning turned out to be not very reliable with LCN when I tried to implement that. So I postponed that as I do not need it for myself. I wanted to give it another try one day but I have other things with higher priority on my todo list.
You can send any key press event you want using the send_keys service action. There is also an example in the docs.
Until now I thought that the positioning command is transparent, i.e. only the command is issued and the infrastructure is doing the rest. In LCN I have for example programmed things like âposition motor 1 to 120â and the cover will move accordingly. Admittedly, I donât see any PCK command that would do that.
Actually I am using a small Linux system, called LinHK, that does the same as PCHK but offers a lot of additional possibilities, e.g. the cover positioning. Positioning requires that I store individual up and down times for each cover in the system. These behave as if there was a physical BS4 present.
So the path forward will be to send key presses instead. That requires 25 unused keys.
Is this then always a âshortâ key press or can I also send âlongâ or âreleasedâ triggers?
Whatever method you choose, you will have issues with reading the actual cover position back into Home Assistant.
Maybe you simply should try out solutions like this one (also available via HACS).
Itâs not super convenient but I would expect that it works as described.
The positioning infrastructure is working reliably. I would rather prefer to be able to position the cover. Seeing this in HA is not a top priority and more a nice-to-have than a must.
Anyway, at this moment I am in a testing phase and would like to experiment a little bit with the different possibilities first. I checked your LCN documentation but am uncertain about the PCK address semantic. what does myhome in your examples stand for and where is it defined?
myhome is the name of your LCN integration entry (itâs pchk by default if I remember correctly).
The format is <integration entry>.<segment id>.m<module id>
However, I am about to change the action services in the near future so this format will vanish and be replaced by the device_id. Configuring actions will be a lot easier then.
So the positioning command is correctly transmitted, but sadly not recognized by the control software. There is a support forum, yet I havenât been on for years and wouldnât even know if the programmer is still around. We will see.
Currently there is a bug in the address determination: If you renamed the integration entry after creating it, then the service actions will not adapt to that new name.
You have to use the original name (unfortunately it is not visible in the UI after changing it).
That bug will be fixed with the service action rework I mentioned above.
So the positioning command is correctly transmitted, but sadly not recognized by the control software. There is a support forum, yet I havenât been on for years and wouldnât even know if the programmer is still around. We will see.
I donâ remember if I changed the name but I am able to control all entities placed on a dashboard, switch lights etc. on and offâŚ
What is not working is the manual control under Development Tools | Actions.
This will systematically throw an error regardless of the selected pck command and whether I use the s and m address prefixes or not. I can see âinvalid hostâ errors in the log but this time nothing is received by the connecting software, hence I assume that nothing gets sent.
I am a little bit confused because putting any command into the configuration.yaml seems to be issued by the integration.At least R8MxGO is received by my coupling software (I didnât explicitely test the PI command in yaml). I assume that the manual control should not be different from the yaml, or is it? Maybe this will be cured with your next release.
Basically all automations defined in the configuration.yaml should call exactly the same functionality as called with the UI. I have no idea why the one method works while the other one doesnât.
Can you please check that you entered the integration name exactly as shown in the HA LCN integration settings (including upper/lowercase)?
In one of your posts itâs âLinHKâ but in your screenshot itâs âlinhkâ.