LCN - Module output does not work

OHLemon · November 25, 2020, 5:07pm

Hello
I have just started to set up openHAB with my LCN. The basics are working, openHAB is finding all my modules.
Now I am running into some trouble. Good to knwo, I have modules from 2009 and from 2017, they behave a little bit different. Okay, let me try to explain.

I can read out the actual state of all outputs - On or Off
If they are On, I can switch them Off
If they are Off, I can’t switch them On
Now to the messages:

I get following answer in the log:
2020-11-25 18:04:23.978 [ome.event.ItemCommandEvent] - Item ‘OG_S_D’ received command ON

==> /var/log/openhab2/openhab.log <==

2020-11-25 18:04:24.110 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:04:28.077 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:04:32.106 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:04:36.036 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M020: Module did not respond to command: A1DI100000

==> /var/log/openhab2/events.log <==

2020-11-25 18:04:54.253 [ome.event.ItemCommandEvent] - Item ‘OG_S_D’ received command OFF

==> /var/log/openhab2/openhab.log <==

2020-11-25 18:04:54.383 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:04:58.163 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:05:02.218 [WARN ] [ubhandler.LcnModuleMetaAckSubHandler] - S000M020: NACK received: Command not allowed by module’s configuration

2020-11-25 18:05:06.139 [WARN ] [ding.lcn.internal.connection.ModInfo] - S000M020: Module did not respond to command: A1DI000000

What means:

NACK Received
Command not allowed by module’s configuration

Thanks for any help and hints.
Greetings
Jan

fwolter · November 26, 2020, 4:07pm

NACK received: Command not allowed by module’s configuration

This means, the module received the command correctly, but cannot proceed because it is not programmed to execute the command.

This happens if you want to control a dimmer output, when the outputs are not yet enabled in LCN-PRO.

Module did not respond to command: A1DI100000

I observed this log message, too, but didn’t investigate it, yet. I’d say you can ignore it.

OHLemon · November 28, 2020, 10:13am

Hi Fabian, thanks for this hint…I think it was too late! Yes, that improved. Now I have another issue.

Here is the log:

2020-11-28 11:05:28.435 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command ON
2020-11-28 11:05:30.222 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command OFF
2020-11-28 11:06:29.218 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command ON
2020-11-28 11:06:33.123 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command OFF
2020-11-28 11:06:38.376 [vent.ItemStateChangedEvent] - OG_S_L changed from OFF to ON
2020-11-28 11:06:46.500 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command OFF
2020-11-28 11:06:46.825 [vent.ItemStateChangedEvent] - OG_S_L changed from ON to OFF
2020-11-28 11:06:50.643 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command ON
2020-11-28 11:06:53.926 [ome.event.ItemCommandEvent] - Item ‘OG_S_L’ received command OFF

The point that I can switch the light OFF with openHAB and get also the actual status (ON or OFF), but I am not able to switch the output of the LCN module to ON. The log says (like the first row: “received command ON”), but the physical light is still off (dark). Then I used the physical switch (3rd row: received command ON) and I can see in the openHAB the bulb and switch as ‘on’, and I can switch it off (4th row).

No error messages any more, but also no reaction on the output of the module.
By the way, relay outputs connected to I-Connector are working fine and as required.

Thanks for any hint.

fwolter · November 28, 2020, 1:09pm

Did you chose the correct dimming resolution in the config parameter mode LCN - Bindings | openHAB ?

Do you see the correct ON command in the bus monitor of LCN-PRO or the PCHK monitor?

You could set the log level of the LCN binding to TRACE, to get more insights: <Logger name="org.openhab.binding.lcn" level="TRACE" /> Or set the log level via the karaf console.

OHLemon · November 28, 2020, 3:55pm

Thanks a lot for this hint!

The Dimmer Resolution in the PCHK Thing was different (200) than the modules via LCN-PRO (50)
In my personal opinion this point is not described in detail in the LCN Binding instruction or at least has to be pointed out!

Thanks again.

fwolter · November 28, 2020, 3:57pm

Can you make a proposal how to make that clearer?

OHLemon · November 28, 2020, 4:19pm

Maybe like this:

IMPORTANT: You need to configure the dimmer output resolution in the LCN-PCHK Thing (mode)

like the ‘steps’ in the LCN-PRO settings under Options/Settings/Expert Settings. See the screenshot below. This setting is valid for the whole LCN bus. The setting is either 0-50 steps or 0-200 steps.

Thanks.

fwolter · November 28, 2020, 7:09pm

I tried to improve the documentation. Please have a look at the pull request.

OHLemon · November 29, 2020, 1:01pm

I have to be honest, how github works is actual unclear to me. I found some ‘comment’ which are looking fine to me. Then the relation between the ‘mode’ and the LCN-PRO setting will be more clear! - Thanks for your time and help.