Openocean item update is not working after restart


I am currently using openhabian on a raspberry and I am experiencing a strange issue with a nodon window sensor.

My setup is pretty simple :

  • raspi 3B+ with an enocean pi
  • Linux openHABianPi 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux
  • Java (Zulu8.38.0.163-CA-linux_aarch32hf) (build 1.8.0_212-b163)
  • openhab 2.4 (stable)

I have several enocean things and all seam to be working without issue but on all my Window sensors (Nodon SDO-2-1-0x, EEP D5-00-01,

On theses sensors, when I discover the thing, I am able to link items to follow the receiving status and the contact status.

Both values are correctly updated on OPEN/CLOSE event :

2019-06-03 19:25:08.622 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2019-06-03 19:25:08.625 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2019-06-03 19:25:08.630 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _1BS for 050F8405 payload D508050F84050000FFFFFFFF5200 received
2019-06-03 19:25:08.633 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload D508050F840500 for 050F8405 received
2019-06-03 19:25:08.659 [vent.ItemStateChangedEvent] - Velux2_contact changed from CLOSED to OPEN
2019-06-03 19:25:08.664 [vent.ItemStateChangedEvent] - Velux2_status changed from Rssi 88, repeated 0 to Rssi 82, repeated 0

But If I restart openhab (using “sudo openhab-cli stop”), and after waiting the proper time for enocean initialisation, I get only the receiving status update, but no contact status update :

2019-06-03 19:30:08.993 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2019-06-03 19:30:09.001 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2019-06-03 19:30:09.010 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _1BS for 050F8405 payload D508050F84050000FFFFFFFF5600 received
2019-06-03 19:30:09.016 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload D508050F840500 for 050F8405 received
==> /var/log/openhab2/events.log <==
2019-06-03 19:30:09.042 [vent.ItemStateChangedEvent] - Velux2_status changed from Rssi 85, repeated 0 to Rssi 86, repeated 0

I have tried to do several solutions (like linking an other contact item, changing some attributes, …) and I am never able to get the contact status back.

My other enocean things works without problem, only theses window sensors show the same issue.

The only solution I have found is to delete the contact thing, reassociate to openhab using enocean binding and it will work up to the next openhab restart !

I just upgraded my setup to use openhab 2.5.0M1 and I get the exact same problem.

Looking at the various databases (/var/lib/openhab2/jsondb), the sensors get the same attributes before removing it and adding it back using enocean discovery.

I suspect that the thing get some attributes during the discovery that are not saved on the jsondb and so not restored at startup.

The various log:set TRACE on org.openhab.binding.enocean, org.openhab and smarthome.event do not shows any more informations.

Do you have any clue on where to look at to try debugging this issue ?


Try posting over in the eoncean binding thread New openHab2 EnOcean binding
I had the same problem on openhab 2.4 with my nodon door window contact New openHab2 EnOcean binding and but for me it disappeared ever since I updated to the Version of the binding where it was fixed.
Best regards Johannes

Hi Johannes,

I have deployed the openenocean plugin from @fruggy83 repository and this had fixed the problem ! So this was probably the issue.

Thank you for the feedback.