In order to be able to use the send-key function correctly, I have purchased an LCN VISU. After I had integrated it, I thought I would try the new LCN GUI, since the YAML Config is considered depricated.
Unfortunately, the new GUI only shows me my modules. The entities are not recognized automatically. The extended help says: “Klicke auf einen Eintrag in der Liste, um die zugehörigen Entitäten anzuzeigen und zu editieren.” I understand this to mean that the entities of the modules should be read out automatically.
The old config within the YAML worked well. Three modules, about 20 entities (although I didn’t include all modules in the HA).
Maybe I’m doing something wrong, or is there still a bug here? (This is the first version of the LCN GUI.
Hi @huffel
unfortunately there is no possibility to recognize entities using the interface language (PCK) provided by LCN. Only detecting modules is possible to a limited degree.
So, it‘s not a bug in the panel.
But your configuration previously stored in the configuration.yaml should have been imported to the panel and should be visible there.
In other cases you have to enter the entities manually. The configuration will then be backed up along with the HomeAssistant backup functionality.
I was just about to open a new thread when I saw this one and your reply. It might be helpful to add this info to the documentation to avoid similar questions from the community.in the future.
Actually not a big deal for me since I had just begun to set up my modules in a separate lcn.yaml. Although 42 modules with ten R8H, ten TS and I don’t know how many of Keytable B triggers will mean a lot of definitions work until I’ll have captured everything.
Although the scan did find all my modules, sometimes names were truncated or read wrongly. I adjusted all names manually, yet the change is ignored when you want to add entities to the modules.
For example this is what the LCN dialogue displays for the living
And this is shown in the entity configuration dialogue
I can always work along the module number but maybe this is easy to fix. I also have some special mdolues w/o real names (21x). These are “virtual” modules from a 3rd Party solution
Thanks for the feedback!
I will update the documentation. Btw.: Everyone is invited to update the docs as well if anything is unclear from user perspective.
Sidenote:
The reason for deprecating the yaml-configuration is this architectural decision.
Basically that means, that further improvements to the LCN integration would be (and were) rejected if it still sticks to the yaml-configuration.
I‘m thinking about some kind of import functionality to allow importing lcn-config files tobte UI to satisfy tech-afine users. But that‘s not prio 1, will be a lot of work and I‘m unsure about the added value.
I guess that‘s again a LCN related issue with telegram collisions in the bus. Well, I‘m currently working on a functionality to edit the module and entity properties but that will take some time.
Short term solution (not nice but it works): have a look at your /config/.storage folder. You might find some files related to the config-entry and the device registry. You can edit the module names in those files.
Long term solution would be to implement another scan-method. But that method would take ages to scan the modules (however, it would work).
Hi @alengwenus
I tried the method you recommend, and it works.
Before I tried a completely new config, so in this case no entities showed up.
A config-upload solution would be nice, when you have lager environments.
Thread could be closed! Thanks a lot Andre for this integration. That integration was the main argument to switch from ip-symcom to home assistant. And I didn’t shed a tear about it.
Actually it is more difficult than I thought. The file seems to contain a large amount of garbage, maybe from the previous LCN definition file before the recent integration update.
I wonder if this is worth the effort, given timing issues that here and there lead to truncated texts. Have you thought about storing the LCN information in a sql database rather than in text files? That would make any change very easy.
I don’t have any control about the device registry and how HA stores the information. That’s completely up to HA.
Main problems are still the message collisions in the LCN hardware bus which is not sufficiently handled by their hardware couplers. The last days I had a look at this topic and implemented some queue mechanisms and idle times into the underlying library. I hope that will help. I guess that will be used by HA in one of the patch releases of 2024.10.
Hey,
I am a HA beginner and my LCN integration via config.yaml worked for covers and lights (with dimmer) and binary sensors and some values.
With the new UI update it doesn’t work. I already tried to delete the complete LCN connection in LCN integration and restart by zero but the three lights I’ve tested with the new setup doesn’t work.
What could be the problem? Didn’t change anything else.
As of today the configuration.yaml import for the LCN integration has not been turned off (it is just marked deprecated). Basically the UI is just an addition to already existing functionality.
Are you sure this is due to the latest update?
You could also add the following to your configuration.yaml and have a look at the logs:
logger:
default: info
logs:
homeassistant.components.lcn: debug
pypck: debug
Thanks for reply and sry for late feedback. I am not able to set up my HA often.
I already had implemented it but in “protocols” nothing is shown. Just something for my tasmota Energie meter … another construction side
I made the latest updates and now it seems to work.
But how can I adjust an Output for dimmable light.
It is shown as on off light and works fine but I want to have it as a dimmable light.
Can’t find the setting to change it.
Hi @Olitepi ,
you need to delete the old light and create a new light with dimming enabled. Ensure that you choose the same entity_id as before so you don‘t have to fix your dashboard.
Unfortunately editing of intrinsic LCN entity properties is not yet implemented.
