How can I continue to use the dynamic text via NodeRed? Before the new LCN integration, it worked quite simply via address, but now I just get the message “no connection”. The bus itself works, though, because I can switch and query other things, just not via NodeRed.
Hi @CarstusKaktus
unfortunately I can’t help with NodeRed. I don’t know if there are any issues when HASS actions are called with NodeRed. The actions (service calls) for the LCN integration itself did not change at all.
Btw.: The address parameter for the actions will soon be deprecated and replaced by the device_id. Addressing a module via the device_id is the HASS intended way to do it (see this PR).
OK. I found out that something has changed in the syntax in Node-Red. Now I get the message that the host name “lcn”, which I chose during the integration, is rejected by HA when I want to send a dynamic text there. Message: “HomeAssistantError: Invalid host name.”
Problem solved: HA only accepts uppercase letters in the address. It works now with the address line “LCN.010.091” instead of “lcn.010.091”.
The address is case sensitive (not only uppercase). That wasn‘t the case when using the yaml configuration.
Unfortunately, changing the integration name does not change the address name due to some design decisions by the HA core developers. That‘s also the reason, why the address parameter will be marked as deprecated in 2025.01 and replaced by the device_id for identifying LCN modules.
Well, it makes automation configuration via the UI a lot easier…
And where do I get this device_id from? It is not included in any LCN module. I have already tried the name, the hardware number, the module number, but nothing works.
You can create a new automation via the UI. In the trigger or action field select the respective LCN module. Then use the three-dots-menu to switch to yaml-mode. There you will see the device id.
As I said, I don‘t like this way of addressing LCN modules but I was told to do it that way. Well, as long as you stay with the UI, you will never see or even need the device_id. 
1 Like
good joke. when exactly will the real integration come. sorry, but who decides to change such rubbish? whatever, luckily I’m only playing with the HA and haven’t used it in any important areas. 
Nobody forces you to use this integration or Home Assistant.
Good luck with the alternatives in the future. 
As another option you could also use a template as described here to obtain the device_id. Just use the module name as it is show in the UI or defined in LCN-PRO:
device_id: "{{ device_id('Module Name') }}"
1 Like