EnOcean, MQTT connection config check

HarterHorst · April 14, 2020, 11:01am

Hi all,

after a long time of trial and error, I have figured out the following binding and I’d like to have some feedback from some “silverbacks” in this forum.

Setup:

Raspi 4+
Openhab (Version 2.5.3)
HW: NodON PIR (PIR 2-1-01) and NodOn SmartPlugSwitch (MSP-2-1-11)

Goal:
EnOcean Sensors/Actors should post changes (e.g. Motion, etc.) via MQTT and actors should receive MQTT commands and act accordingly.

Status:
Everything works as desired except that the switch sometimes does not respond to the MQTT message in the first place. If I switch again (sent MQTT message again) it works. I have the feeling that openHAB sometimes has issues with CPU resources and misses some commands.

Questions:

Can you see anything that can be improved in my config?
Any ideas why the switch misses some commands coming in via MQTT?

Thanks a lot.
Horst

Here are my config files:

EnOcean.things

Bridge enocean:bridge:gtwy "EnOcean Gateway.SCR" [ path="/dev/ttyAMA0", espVersion="ESP3", rs485=false, rs485BaseId="00000000" ] 
{
    Thing measurementSwitch MicroPlugSwitch "EnOcean MicroSwitch.SCR" @ "MicroSmartPlug" [ enoceanId="0582F709", senderIdOffset=1, sendingEEPId="D2_01_0E", receivingEEPId="D2_01_0E", broadcastMessages=false, suppressRepeating=false, pollingInterval=300] {
       // Channels appear automatically somehow:
    }
    Thing occupancySensor EnOceanPIRSensorscr "EnOcean Occupancy.SCR" @ "NodON PIR" [ enoceanId="058AEC49", senderIdOffset=2, sendingEPPId="A5_07_03", receivingEEPId="A5_07_03", broadcastMessages=true,  suppressRepeating=false, pollingInterval=300] {
        Channels:
            State Number : Illuminancescr "Lux" []
            State Number : batteryVoltagescr "Battery Voltage" [] 
            State Switch : motionDetectionscr "Motion" []
    }
}

MQTT.things

Bridge mqtt:broker:andimqttbroker "MQTT Broker.SCR" [host="192.168.0.2", secure=false] 
{
 Thing topic MQTTNodOnPIRSensor "MQTT Occupancy Sensor SCR" @ "NodON PIR" 
    {
        Channels:
            Type switch : PIRNodOn "PIR Sensor scr" [ stateTopic="openhab/PIR", commandTopic="openhab/PIR/set", retained=false, postCommand=false ]
            Type number : PIRIllumi "PIR LUX scr" [ stateTopic="openhab/PIR/Lux", commandTopic="openhab/PIR/Lux", retained=false, postCommand=false]
            Type number : PIRVoltage "PIR Voltage scr" [ stateTopic="openhab/PIR/Voltage", commandTopic="openhab/PIR/Voltage", retained=false, postCommand=false]
    }

    Thing topic MQTTNodOnMicroSmartPlug "MQTT MicroPlugSwitch SCR" @ "MicroSmartPlug"
    {
        Channels:
            Type switch : MicroSmartPlugSwitch "MicroSmart On/Off" [ stateTopic="openhab/SmartPlug", commandTopic="openhab/SmartPlug/set", retained=false, postCommand=true ]
    }
}

Sensors.items

// PIR Motion Sensor
Number batteryVoltagescrn "Battery Voltrage SCR"    {channel="mqtt:topic:andimqttbroker:MQTTNodOnPIRSensor:PIRVoltage"  [profile="system:follow"], channel="enocean:occupancySensor:gtwy:EnOceanPIRSensorscr:batteryVoltage"}
Number Illuminancescr "Lux SCR"                     {channel="mqtt:topic:andimqttbroker:MQTTNodOnPIRSensor:PIRIllumi"   [profile="system:follow"], channel="enocean:occupancySensor:gtwy:EnOceanPIRSensorscr:illumination"}
Switch MQTTmotionDetectionscr "MQTT Motion"         {channel="mqtt:topic:andimqttbroker:MQTTNodOnPIRSensor:PIRNodOn"    [profile="system:follow"], channel="enocean:occupancySensor:gtwy:EnOceanPIRSensorscr:motionDetection" }

// MicroPlugSwitch 
Switch CHMicroPlugSwitch "EnOcean.Switch2" {channel="mqtt:topic:andimqttbroker:MQTTNodOnMicroSmartPlug:MicroSmartPlugSwitch" [profile="system:follow"], channel="enocean:measurementSwitch:gtwy:MicroPlugSwitch:generalSwitch" }

Thedannymullen · April 14, 2020, 2:12pm

Have you looked at the logs? This will tell you if messages are being received.

HarterHorst · April 14, 2020, 2:39pm

Of, course:

First click “on” - Switch turns on -> OK
First click “off” - Switch does not turn off -> failure
Second click “on” - no change, because Switch is already on ->
Second click “off” - Switch turns off -> failure

Every time when only one “Successfully published value “ON/OFF” to topic …” is in the logs, the switch does not work. (see 16:38:07.142)


16:38:05.268 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
16:38:05.274 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
16:38:05.299 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
16:38:05.316 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:05.633 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:07.096 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
16:38:07.103 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
16:38:07.123 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
16:38:07.142 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
16:38:09.191 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
16:38:09.198 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
16:38:09.218 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
16:38:09.232 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:09.515 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:11.219 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
16:38:11.225 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
16:38:11.243 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
16:38:11.253 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
16:38:13.373 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
16:38:13.379 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
16:38:13.399 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
16:38:13.419 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:14.084 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:15.358 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
16:38:15.365 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
16:38:15.382 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
16:38:15.392 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
16:38:15.734 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
16:38:17.474 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
16:38:17.480 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
16:38:17.501 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
16:38:17.513 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
16:38:17.787 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set

H102 · April 14, 2020, 2:59pm

What MQTT broker are you using?

rossko57 · April 14, 2020, 3:01pm

That’ll be to do with your follow profile.

I’m a bit lost with what you “click”, is that the CHMicroPlugSwitch Item on your UI?
That would issue a command to the enocean:measurementSwitch:gtwy:MicroPlugSwitch:generalSwitch channel only.

If at some point, the CHMicroPlugSwitch Item receives a state update, that will be converted into a command for the mqtt:topic:andimqttbroker:MQTTNodOnMicroSmartPlug:MicroSmartPlugSwitch channel (the one with follow profile), and so sent on commandTopic openhab/SmartPlug/set

Note that if you send a command to the Item, it only sends on the enocean channel.
That command may or may not cause an Item update (it often would) which in turn would convert via follow profile to an MQTT command.
Is that what you intended?

There is a trap there; if the MQTT device responds to commands with a status update, resulting in OH Item update, the follow profile will once again convert to a command and send on MQTT. if the MQTT device responds to commands with a status update… etc.

HarterHorst · April 15, 2020, 7:53am

Sorry, for not making my use case clearer. Let’s simplify.

I have the impression that not all MQTT commands that should initiate an action on the switch are successful.

So I have created a NodeRed workflow that sends out a MQTT Message via an external MQTT Broker (Based on Linux) turning the switch on and off every 10 seconds. This is not a real world scenario, but a good test to identify any problems.

So the message flow is as follows:

NodeRed ( openhab/smartplug “0” or “1” -> external MQTT Broker -> OH -> Physical EnOcean Switch

In OH it goes
MQTT Message receive: mqtt:topic:andimqttbroker:MQTTNodOnMicroSmartPlug:MicroSmartPlugSwitch
switch item: CHMicroPlugSwitch which is also linked to
send: enocean:measurementSwitch:gtwy:MicroPlugSwitch:generalSwitch sending EnOcean telegram.

Not every MQTT switch command comes through to the physical switch.

09:37:37.945 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
09:37:37.952 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
09:37:37.990 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
09:37:38.007 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
09:37:38.336 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
09:37:42.974 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
09:37:42.980 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
09:37:43.003 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
09:37:43.011 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
09:37:47.945 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
09:37:47.951 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
09:37:47.971 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
09:37:47.983 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
09:37:52.940 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
09:37:52.949 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
09:37:52.973 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
09:37:52.986 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
09:37:53.273 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
09:37:56.937 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
09:37:57.948 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
09:37:57.954 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
09:37:57.974 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
09:37:57.990 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
09:38:02.937 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
09:38:02.943 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
09:38:02.963 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
09:38:02.982 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
09:42:57.488 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set

Regarding the status update you are right. The physical switch sends out status updated (EnOcean telegrams) after every switching action which obviously leads to the double “Successfully published …” messages. But this should not affect the switching process.

If i remove the system.follow profile and fall back to system.default the entire process does not work. I’m not sure if this is all correct, so I asked to give me some feedback if there are any improvements to the configuration.

HarterHorst · April 15, 2020, 7:59am

It’s an external broker on another debian machine. mosquitto version 1.4.10

rossko57 · April 15, 2020, 11:09am

That all seems terribly complicated.
Test rule

rule "test switch toggle"
when
   Time cron "0/10 * * ? * * *" //every 10 secs
then
   if (CHMicroPlugSwitch.state == ON) {
      CHMicroPlugSwitch.sendCommand(OFF)
   } else {
      CHMicroPlugSwitch.sendCommand(ON)
   }
end

test Item

// MicroPlugSwitch 
Switch CHMicroPlugSwitch "EnOcean.Switch2" { channel="enocean:measurementSwitch:gtwy:MicroPlugSwitch:generalSwitch" }

so that you are confident every enocean command is processed, not duplicated, etc.

I see now you have the option for that in MQTT channel settings, postCommand=true. That means that a payload recieved with stateTopic=“openhab/SmartPlug” will not do the usual Item update but will be transformed into an openHAB command.
(It’s never clear to me if the usual state update takes place alongside the command, or not.)

You also have a commandTopic= set on the same channel. Any command to the linked Item will be published on topic "openhab/SmartPlug/set"

As you can see, this setup is at risk of disappearing up its own backside. I think this is okay here though, because the topics are different.
Essentially any payload received on openhab/SmartPlug will be republished on
openhab/SmartPlug/set … if and only if the channel is linked to an Item that will act as command router.

However, this channel is not linked to an Item in the ordinary way. You applied the follow profile, which is essentially about reversing the command/state traffic.
What follow is intended for is to notice every Item state update, and send those as commands instead to the linked channel. That’s useful for having some external device track the state of an OH Item - most binding channels only transmit commands and ignore states.

Again, it’s not clear to me if follow’s “inversion” is complete - does it just ignore Item commands, or does it convert those into state updates? It certainly could just ignore - openHABs regular autoupdate feature already exists and acts on commands to guess a likely outcome and issue a state update (the Predicted messages in your events log)

Alright, let’s unravel this rat’s nest.

I will assume an ON payload has arrived on MQTT topic openhab/SmartPlug
The channel is set up to issue that as a command to a linked OH Item.
The link here has the follow profile applied … but as sending commands from binding to Item is unusual in openHAB, I’m going to guess the follow profile does not interfere (it’s task is listening to Item events, not to the binding)
So, end result, Item gets command.

At this point, that command will get passed to any binding channels linked to this Item.
So, one straightforward result, published to enocean.

Second result, command gets passed to MQTT binding. But the follow profile stands in the way, and it is not actioned.

Third result, command is passed to OH autoupdate feature (which is enabled for each Item by default).

Autoupdate does its thing - predicts the likely outcome of the command, and pre-emptively updates the Item state.

Ah, now then, that follow profile was listening for updates. That now acts, and converts state update to command and passes to MQTT channel.
The channel is set up to publish commands to openhab/SmartPlug/set -

And that’s the direct effect of the command concluded.

Meanwhile, we sent a command to a real enocean device. I know nothing of enocean, but a usual binding/device/command outcome would be that at some time the device responds with its new status, which in turn gets converted to an Item update.
Autoupdate has already pre-empted that, so providing autoupdate guessed correctly there will be no change in Item state. Nothing will get recorded in events.log.
But - there is still an update - to the same state.

Ah, now then, that follow profile was listening for updates. That now acts, and converts state update to command and passes to MQTT channel.
The channel is set up to publish commands to openhab/SmartPlug/set -

The unexpected second MQTT publish, some arbitrary time after the process began.

So, why does the next command OFF cycle shown in your log have three MQTT publishes? Guesswork - enocean has routine periodic reporting at some level, as well as direct command-response, resulting in extra Item updates. Look at times closely.
Every update results in an MQTT publish, as directed by the follow profile.

Which is really all about MQTT and your odd test arrangements, nothing about whether your enocean works as expected.
I’d adopt my earlier test suggestion for that, so that you can see the wood for the trees.

Thedannymullen · April 15, 2020, 1:34pm

Have you stopped openHAB, watched these topics on an explorer like mqtt explorer or mqtt fx.

Do this with your node red flow running. It will show what the switch is sending. It appears to me the physical switch could be the issue but we need to prove this one way or the other prior to moving to openHAB.

HarterHorst · May 14, 2020, 10:09am

Hi, it took me a while to process your input. Strange times.

I have implemented the test rule that turn the switch on/off.

Here is the log from openHAB

17:27:50.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:27:50.042 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:27:50.064 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:27:50.084 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:27:50.760 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:00.015 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:28:00.040 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:28:00.061 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:28:00.074 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:28:10.017 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:28:10.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:28:10.058 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:28:10.070 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:10.344 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:20.016 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:28:20.050 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:28:20.077 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:28:20.090 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:28:30.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:28:30.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:28:30.060 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:28:30.073 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:40.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:28:40.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:28:40.056 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:28:40.071 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:28:50.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:28:50.037 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:28:50.057 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:28:50.074 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:50.767 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:00.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:29:00.035 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:29:00.054 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:29:00.065 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:00.423 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:10.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:29:10.033 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:29:10.049 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:29:10.062 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:10.356 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:20.010 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:29:20.031 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:29:20.048 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:29:20.059 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:20.769 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:30.011 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:29:30.034 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:29:30.056 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:29:30.070 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:30.391 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:40.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:29:40.042 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:29:40.066 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:29:40.079 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:40.363 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:29:50.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:29:50.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:29:50.060 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:29:50.068 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:29:50.792 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:00.016 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:30:00.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:30:00.054 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:30:00.068 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:30:10.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:30:10.040 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:30:10.067 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:30:10.076 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:10.413 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:20.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:30:20.034 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:30:20.056 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:30:20.065 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:30:20.340 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:30:30.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:30:30.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:30:30.054 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:30:30.064 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:30.783 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:40.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:30:40.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:30:40.058 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:30:40.076 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:30:40.432 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:30:50.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:30:50.041 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:30:50.067 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:30:50.080 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:30:50.344 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:00.015 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:31:00.039 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:31:00.063 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:31:00.064 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:31:00.765 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:31:10.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:31:10.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:31:10.055 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:31:10.065 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:10.420 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:17.000 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:20.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:31:20.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:31:20.067 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:31:20.071 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:31:20.370 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:31:30.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:31:30.037 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:31:30.067 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:31:30.072 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:40.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:31:40.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:31:40.059 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:31:40.075 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:31:50.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:31:50.039 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:31:50.066 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:31:50.071 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:31:50.781 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:32:00.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:32:00.039 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:32:00.063 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:32:00.077 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:32:00.408 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:32:10.021 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:32:10.064 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:32:10.084 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:32:10.096 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:32:10.360 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:32:20.020 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:32:20.048 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:32:20.069 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:32:20.084 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:32:30.016 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:32:30.041 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:32:30.060 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:32:30.069 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:32:40.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:32:40.037 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:32:40.060 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:32:40.076 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:32:40.765 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:32:50.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:32:50.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:32:50.056 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:32:50.073 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:33:00.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:33:00.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:33:00.054 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:33:00.066 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:33:10.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:33:10.039 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:33:10.059 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:33:10.076 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:33:15.221 [INFO ] [smarthome.event.ItemStateChangedEvent] - Illuminancescr changed from 3329 to 3584
17:33:15.237 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value 3584 to topic openhab/PIR/Lux
17:33:15.246 [INFO ] [smarthome.event.ItemStateChangedEvent] - MQTTmotionDetectionscr changed from ON to OFF
17:33:15.250 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value 3.04 to topic openhab/PIR/Voltage
17:33:15.267 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/PIR/set
17:33:20.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:33:20.034 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:33:20.051 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:33:20.064 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:33:20.412 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:33:22.664 [INFO ] [smarthome.event.ItemStateChangedEvent] - Illuminancescr changed from 3584 to 3840
17:33:22.667 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value 3840 to topic openhab/PIR/Lux
17:33:22.678 [INFO ] [smarthome.event.ItemStateChangedEvent] - MQTTmotionDetectionscr changed from OFF to ON
17:33:22.684 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value 3.04 to topic openhab/PIR/Voltage
17:33:22.700 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/PIR/set
17:33:30.011 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:33:30.035 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:33:30.053 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:33:30.067 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:33:30.372 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:33:40.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:33:40.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:33:40.057 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:33:40.077 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:33:40.774 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:33:50.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:33:50.037 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:33:50.054 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:33:50.075 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:33:50.413 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:34:00.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:34:00.035 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:34:00.053 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:34:00.064 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:34:10.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:34:10.050 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:34:10.073 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:34:10.094 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:34:10.371 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set

In parallel I have setup a second raspi with an USB300 EnOcean Stick to wiretap (wireless tap) the EnOcean traffic.

17:27:50:0071 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:27:50:0390 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:28:00:0071 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:28:10:0071 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:28:10:0326 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:28:20:0086 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:28:30:0072 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:28:40:0071 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:28:50:0070 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:28:50:0757 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:29:00:0070 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:29:00:0405 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:29:10:0068 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:29:10:0339 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:29:20:0067 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:29:20:0754 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:29:30:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:29:30:0385 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:29:40:0081 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:29:40:0337 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:29:50:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:29:50:0751 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:30:00:0066 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:30:10:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:30:10:0400 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:30:20:0063 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:30:20:0334 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:30:30:0077 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:30:30:0765 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:30:40:0078 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:30:40:0396 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:30:50:0077 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:30:50:0333 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:31:00:0063 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:31:00:0750 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:31:10:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:31:10:0399 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:31:16:0853 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 03 1e 
17:31:16:0965 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:31:20:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:31:20:0352 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:31:30:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:31:40:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:31:50:0063 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:31:50:0766 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:32:00:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:32:00:0399 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:32:10:0095 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:32:10:0351 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:32:20:0081 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:32:30:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:32:40:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:32:40:0752 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:32:50:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:33:00:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:33:10:0080 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:33:15:0208 | Message Origin: 05 8A EC 49 | Message Destination: ff ff ff ff  | R-ORG: a5  | Data: 98 0e 00 08 
17:33:20:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:33:20:0400 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:33:22:0636 | Message Origin: 05 8A EC 49 | Message Destination: ff ff ff ff  | R-ORG: a5  | Data: 98 0f 00 88 
17:33:30:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:33:30:0321 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:33:40:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:33:40:0764 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 
17:33:50:0064 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:33:50:0400 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 
17:34:00:0065 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:34:10:0081 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:34:10:0353 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4

Here are some details on the log.

FF:B0:72:81 - OpenHAB Raspi
05:82:f7:09 - EnOcean Switch
Data to turn switch on: 01:01:01 - Feedback from Switch via broadcast (on): 04 60 e4
Data to turn switch off: 01:1e:00 - Feedback from Switch via broadcast (off): 04 60 80

From the log I was able to see that not every telegram changes the switch state. At time 17:28:20 - 30 and 40 several commands are sent to the switch without any feedback. I observed the switch and it didn’t change the state.

17:28:20:0086 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:28:30:0072 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01 
17:28:40:0071 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 00 
17:28:50:0070 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 1e 01

–

17:28:20.016 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:28:20.050 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:28:20.077 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:28:20.090 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:28:30.014 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:28:30.038 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:28:30.060 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:28:30.073 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:40.012 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command OFF
17:28:40.036 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become OFF
17:28:40.056 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from ON to OFF
17:28:40.071 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value OFF to topic openhab/SmartPlug/set
17:28:50.013 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'CHMicroPlugSwitch' received command ON
17:28:50.037 [INFO ] [arthome.event.ItemStatePredictedEvent] - CHMicroPlugSwitch predicted to become ON
17:28:50.057 [INFO ] [smarthome.event.ItemStateChangedEvent] - CHMicroPlugSwitch changed from OFF to ON
17:28:50.074 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set
17:28:50.767 [DEBUG] [mqtt.generic.AbstractMQTTThingHandler] - Successfully published value ON to topic openhab/SmartPlug/set

I also observed this directly on the switch. That leads me to the assumption that the switch has a problem.

So I setup a FHEM installation on the same raspi with another SD-Card to cross check the software stack. And I was surprised to see that my first test approach (via NodeRed) successfully switched the switch all the time. Very reliably. So I am close to rule out the physical switch as the root cause.

The telegram data also differ between the OpenHAB and FHEM telegram.

OpenHAB Turn on data: 01 1e 01
FHEM Turn on data: 01 00 64

I checked the EPP Specs. for EPP D2:01:0e

Byte - Command ID. (Seems to be OK)
Byte - DIM Value & IO/Channel: 0x1e to Switch all out put channels, 0x00 to switch the first channel (should not make a difference, because the switch only has one channel)
Byte - output Value: value from 0x01 to 0x64 to turn switch on: 0x00 to turn off (seems to be OK)

I would say that the OpenHAB implementation is closer to the EPP Spec, but there seems to be no effective difference.

So it looks like the physical switch does not answer to OpenHAB EnOcean Telegrams sometimes. Which is strange.

Here are the logs from FHEM.

10:36:27:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:36:27:0852 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:36:32:0164 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:36:32:0499 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:36:37:0164 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:36:37:0452 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:36:42:0164 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:36:42:0498 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:36:47:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:36:47:0870 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:36:52:0197 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:36:52:0580 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:36:57:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:36:57:0420 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:02:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:02:0931 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:07:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:07:0501 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:12:0166 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:12:0438 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:17:0168 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:17:0869 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:22:0181 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:22:0517 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:27:0166 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:27:0453 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:32:0181 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:32:0884 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:37:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:37:0484 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:42:0181 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:42:0453 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:47:0165 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:47:0868 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:37:52:0182 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:37:52:0500 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:37:57:0166 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:37:57:0453 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:38:02:0182 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:38:02:0869 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:38:07:0167 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:38:07:0534 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:38:12:0183 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:38:12:0454 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80 

10:38:17:0171 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 64 
	10:38:17:0872 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 e4 

10:38:22:0188 | Message Origin: FF B0 72 81 | Message Destination: 05 82 f7 09  | R-ORG: d2  | Data: 01 00 00 
	10:38:22:0567 | Message Origin: 05 82 F7 09 | Message Destination: ff ff ff ff  | R-ORG: d2  | Data: 04 60 80

To sum all this up. The FHEM communicates to the switch without any problems. All telegrams are received by the switch, the physical switch changes the state and feedback is given via broadcast. The openHAB approach has problems to perform a reliable switching behaviour. Both approaches on same hardware.

HarterHorst · May 14, 2020, 10:10am

Hi, yes I checked the MQTT Traffic with MQTT FX and everything is ok.

phambinh97 · May 27, 2020, 7:09am

Hi, HarterHorst
Can I have a question please? How do you connect between enocean and openhab? Can I use USB300db enocean to connect? If I need to connect between openhab and enocean, what is the syntax in the declaration in “things”? can you help me I just started working on openhab so I don’t know much

HarterHorst · May 28, 2020, 9:18am

Hi,

it’s the EnOcean.things file from my original post. I used an EnOcean PI which appear as ttyAMA0 in the Linux Device list. It also works with the USB300 which should be ttyUSB0 as far as I remember. You just have to adjust the according line in the EnOcean.things file and the Gateway should be available.

I’m afraid you have to dig through the documentation regarding the file syntax. The config files above can give you an indication how the files should look like.

phambinh97 · May 30, 2020, 5:02pm

Hi HarterHorst
Thanks for your answer. Can you tell me where the document can be found? And I want to ask : I have 1 temperatureHumiditySensor sensor of enocean and I want to connect with openhab to display two separate values: humidity and temperature, what should I do? I hope you can help me. Thank you very much
Regards

system · July 11, 2020, 9:02am

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.