New openHab2 EnOcean binding

fruggy83 · May 30, 2018, 7:30pm

Hi Thorsten (@ThAO),

my fault (reference comparision instead of value ).

It should work now. Sorry for that.

regards
Daniel

ThAO · May 31, 2018, 5:30pm

Great! Works now!

bruxi · June 15, 2018, 5:25pm

Hi,

just started my first experience with EnOcean and an Nod On SDO-2-1-05 door sensor.

The binding is running:

190 | Active | 80 | 2.4.0.201805301924 | OpenOcean Binding

It seems that the binding and the sensor communicate when I put the magnet near the sensor and remove it afterwards:

2018-06-15 19:17:05.248 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-15 19:17:05.350 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 11 optional length 7 packet type 1
2018-06-15 19:17:05.737 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-15 19:17:05.739 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 3053DC40A90C050F4EB00001FFFFFFFF5900
2018-06-15 19:17:08.490 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-15 19:17:08.592 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 11 optional length 7 packet type 1
2018-06-15 19:17:08.980 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-15 19:17:08.982 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 302A46125A99050F4EB00001FFFFFFFF5C00

But my item which I configured for the contact channel doesn’t change at all and stays at a value of NULL.

Status in Karaf console:

EnoceanDoorContact (Type=ContactItem, State=NULL, Label=Der Eumel ist, Category=exit_door)

Here’s the item definition:

Contact EnoceanDoorContact "Der Eumel ist [MAP(door.map):%s]" <exit_door> { channel="openocean:contactSwitch:66e6ad1b:050F4EB0:contact" }

This is what the sensor looks like in Paper UI:

Any ideas?

Thanks and best regards,
Jens

Matt77 · June 16, 2018, 9:02am

Hi Daniel (@fruggy83)

sorry for my late reply,
i re-added my NodOn module and it the right profile got added (EEP for sending commands
NodON SIN-2-1-0x (EEP: D2_01_12)
However i can’t see the option to enable the repeater mode.

im currently on OH 2.3 and your openocean 2.4.0.201805301924

Regards
Matthias

fruggy83:

Hi Matt (@Matt77)

I have got an answer from NodOn. Indeed you have to send a manufacturer specific command to the in wall switches to activate the repeater. I added two new NodOn specific profiles which are able to activate the repeater. If you do an auto discovery the correct profiles should be choosen for you. If not you have to select them manually .

You can set the repeater level 1/2 or deactivate the repeater. However it is not possible to request the current repeater setup of your in wall switch or get any feedback (“You have to know that you won’t get any confirmation from the module when the activation is done.” cit NodOn). So it is somehow tricky to test this feature. Maybe you can use the receiving state channel which also tells you the repeater count of the last received message. I would be glad if you could test this.

I hope I can implement the other functions (autoOff Timer etc.) in the next days.

Best regards
Daniel

fruggy83 · June 18, 2018, 5:03am

Hi Jens (@bruxi),

sorry for my late answer but I am currently on vacation till saturday. Your configuration seems to be ok to me however the received messages look strange. A contact message contains just one byte payload, together with the sender id, status byte and message type it should be just 7 bytes long not 11. Did you auto discover your contact?

Best regards
Daniel

fruggy83 · June 18, 2018, 5:07am

Hi Matt (@Matt77),

if I remember correctly I implemented this as an advanced channel. You find the repeater channel when you press „show more“.

Best regards
Daniel

bruxi · June 18, 2018, 8:33am

Hi Daniel,

yesterday I deleted the device three times and included it again and suddenly it worked. There came other messages up as before. I just pressed the teach-in button longer than in the tries before.
The process was as before: I started the auto discovery in Paper UI and pressed the teach-in button on the sensor. But this time I kept it pressed until the Received teach in message from 050F4EB0 message came up.

2018-06-17 21:41:06.432 [INFO ] [very.OpenOceanDeviceDiscoveryService] - Starting EnOcean discovery and accepting teach in requests
2018-06-17 21:41:10.167 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:10.269 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 11 optional length 7 packet type 1
2018-06-17 21:41:10.655 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:10.657 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 3013D88B98D4050F4EB00001FFFFFFFF4F00
2018-06-17 21:41:14.320 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:14.422 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 20 optional length 7 packet type 1
2018-06-17 21:41:14.995 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:14.999 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 352093FD4F4F4CDD33F5A2E3A4F16C050F4EB00001FFFFFFFF5000
2018-06-17 21:41:15.015 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:15.117 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 14 optional length 7 packet type 1
2018-06-17 21:41:15.566 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:15.568 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 3560F39177F3C5A7EB050F4EB00001FFFFFFFF5000
2018-06-17 21:41:15.586 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:15.688 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 11 optional length 7 packet type 1
2018-06-17 21:41:16.079 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:16.081 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 30F133B7F173050F4EB00001FFFFFFFF5000
2018-06-17 21:41:16.119 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:16.221 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 20 optional length 7 packet type 1
2018-06-17 21:41:16.798 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:16.799 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 352093FD4F504CDD33F5A2E3A4F16C050F4EB00001FFFFFFFF5000
2018-06-17 21:41:16.818 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:16.920 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 14 optional length 7 packet type 1
2018-06-17 21:41:17.370 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:17.372 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 3560F39177F3C5A7EB050F4EB00001FFFFFFFF5000
2018-06-17 21:41:17.390 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:17.492 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 11 optional length 7 packet type 1
2018-06-17 21:41:17.880 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for:
2018-06-17 21:41:17.882 [TRACE] [nal.transceiver.OpenOceanTransceiver] - 300D247C97FA050F4EB00001FFFFFFFF5000
2018-06-17 21:41:24.617 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:24.718 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:41:25.024 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:41:25.026 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D500050F4EB00001FFFFFFFF5000
2018-06-17 21:41:25.027 [INFO ] [nal.transceiver.OpenOceanTransceiver] - Received teach in message from 050F4EB0
2018-06-17 21:41:25.031 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'openocean:contactSwitch:66e6ad1b:050F4EB0' to inbox.
2018-06-17 21:41:34.792 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:34.898 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:41:35.204 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:41:35.206 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D500050F4EB00001FFFFFFFF4F00
2018-06-17 21:41:35.207 [INFO ] [nal.transceiver.OpenOceanTransceiver] - Received teach in message from 050F4EB0
2018-06-17 21:41:44.954 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:41:45.055 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:41:45.361 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:41:45.362 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D508050F4EB00001FFFFFFFF5500
2018-06-17 21:42:06.433 [INFO ] [very.OpenOceanDeviceDiscoveryService] - Stopping EnOcean discovery scan
2018-06-17 21:42:26.879 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=427, service.bundleid=190, service.scope=singleton} - org.openhab.binding.openocean
2018-06-17 21:42:26.887 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - Initializing open ocean base thing handler.
2018-06-17 21:42:26.887 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - initializeThing thing openocean:contactSwitch:66e6ad1b:050F4EB0 bridge status ONLINE
2018-06-17 21:42:26.986 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - Listener added: 84889264
2018-06-17 21:43:22.443 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'enocean.items'
2018-06-17 21:43:23.464 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'enocean.items'
2018-06-17 21:44:19.654 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'enocean.items'
2018-06-17 21:44:20.672 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'enocean.items'
2018-06-17 21:44:28.399 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:44:28.500 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:44:28.806 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:44:28.808 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5900
2018-06-17 21:44:28.809 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 21:44:36.401 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:44:36.507 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:44:36.813 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:44:36.814 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D508050F4EB00001FFFFFFFF5B00
2018-06-17 21:44:36.816 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D508050F4EB000 for 050F4EB0 received
2018-06-17 21:45:10.758 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:45:10.860 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:45:11.166 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:45:11.167 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5300
2018-06-17 21:45:11.169 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 21:45:16.141 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:45:16.243 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:45:16.549 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:45:16.551 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D508050F4EB00001FFFFFFFF5300
2018-06-17 21:45:16.552 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D508050F4EB000 for 050F4EB0 received
2018-06-17 21:49:35.309 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'enocean.items'
2018-06-17 21:49:36.330 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'enocean.items'
2018-06-17 21:49:43.634 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:49:43.736 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:49:44.042 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:49:44.043 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5B00
2018-06-17 21:49:44.044 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 21:49:50.614 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:49:50.716 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:49:51.026 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:49:51.028 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D508050F4EB00001FFFFFFFF5600
2018-06-17 21:49:51.029 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D508050F4EB000 for 050F4EB0 received
2018-06-17 21:51:11.468 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 21:51:11.570 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 21:51:12.037 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 21:51:12.038 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5C00
2018-06-17 21:51:12.039 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 22:19:15.626 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 22:19:15.728 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 22:19:16.034 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 22:19:16.035 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5600
2018-06-17 22:19:16.037 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 22:46:19.050 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 22:46:19.152 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 22:46:19.458 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 22:46:19.460 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5800
2018-06-17 22:46:19.461 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 23:06:21.544 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 23:06:21.646 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 23:06:21.952 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 23:06:21.954 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5E00
2018-06-17 23:06:21.958 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 23:31:24.474 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 23:31:24.576 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 23:31:24.882 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 23:31:24.883 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5C00
2018-06-17 23:31:24.885 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received
2018-06-17 23:54:27.213 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-06-17 23:54:27.314 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1
2018-06-17 23:54:27.620 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050F4EB0
2018-06-17 23:54:27.622 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D509050F4EB00001FFFFFFFF5C00
2018-06-17 23:54:27.624 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D509050F4EB000 for 050F4EB0 received

Maybe this helps you identifying the issue. After that discovery the item started to work as expected.

Best regards,
Jens

fruggy83 · June 26, 2018, 6:57am

Hi Jens (@bruxi),

I analysed your strange messages and cannot find a problem in my binding. Your messages have a correct syntax (data length and content of optional data) however there is no message type 0x30 or 0x35 defined in the enocean documents.
So if you want I could ask the (very good) NodOn support, if they could explain these messages? Maybe these are some manufacturer specific messages…

Best regards
Daniel

c214 · June 28, 2018, 6:34pm

Hi @fruggy83

I tried to install the openocean binding from the karaf console of my clean install of openhab 2.3.0 (raspbian-stretch) and got the same error message:

openhab> bundle:install org.openhab.binding.openocean
Bundle IDs:
Error executing command: Error installing bundles:
Unable to install bundle org.openhab.binding.openocean: org.osgi.framework.BundleException: Error reading bundle content.

Is there any misstake from my side? Thx in advance for your help.

Best regards
Christian

fruggy83 · June 28, 2018, 9:20pm

Hi Christian (@c214),

did you installed the serial feature before you tried to install the openocean bundle? My bundle has a dependency against gnu.io, therefore this feature has to be installed. I am currently not aware how to automatically install this feature during the installation of my bundle.

You can install this feature manually with the following command in the karaf console

feature:install openhab-transport-serial

Afterwards you should hopefully be able to install the openocean bundle.

Best regards
Daniel

c214 · June 29, 2018, 5:00am

Hi Daniel (@fruggy83),

unfortunately I installed the openhab-transport-serial feature before your bundle. The feature is listed as installed and started in the karaf feature list.

And other suggestions?

Kind regards

Christian

Casshern · June 29, 2018, 4:13pm

Hi @c214,

how did you install / copy the binding ? I think the read-write permissions of the file are not set properly.

If you are using filezilla you can change this via right-click on the file.

Best regards,
Alex

raphael · July 2, 2018, 4:31pm

Hi

First of all thanks to Daniel to implement this binding.

I just started with OH and the fist actuator I try to control is the in wall module SIN-2-2-0x from nodon. I added a light to the in wall module channel 1 and a physical switch to the input 1 of the module. OH is running on a PI3.

I was able to add a USB310 as OpenOcean bridge and the in wall module as a D2-01 - Energy measurement switch. To control the in wall module I added the following items.

Switch Switch_Test1_A "Test1_A" <switch> (gSwitch) {channel="openocean:measurementSwitch:0c42edb0:0509D103:generalSwitchA"}
Switch Switch_Test1_B "Test1_B" <switch> (gSwitch) {channel="openocean:measurementSwitch:0c42edb0:0509D103:generalSwitchB"}
String Switch_Test1_Status "Test1 Status [%s]" (gSwitch) {channel="openocean:measurementSwitch:0c42edb0:0509D103:receivingState"}

I am able to control the light from OH. I am also able to toggle the light by pressing the physical switch connected to the in wall module. But there is no feedback to OH if a change the state by the physical switch.

So my questions how do I setup the bidirectional communication?

Best regards Raphael

c214 · July 2, 2018, 6:51pm

Hi @Casshern,

I did the following steps according the readme:

Download precompiled binding into your openhab2-addons folder and adjust permissions

cd /usr/share/openhab2/addons/
sudo wget https://github.com/fruggy83/openocean/raw/master/precompiled/org.openhab.binding.openocean-2.4.0-SNAPSHOT.jar
sudo chown openhab:openhab org.openhab.binding.openocean-2.4.0-SNAPSHOT.jar
sudo chmod 644 org.openhab.binding.openocean-2.4.0-SNAPSHOT.jar

Open karaf shell (ssh -p 8101 openhab@localhost, std psw habopen)

install gnu.io (feature:install openhab-transport-serial)
install openocean (bundle:install org.openhab.binding.openocean)

I think permissions are set properly:
-rw-r–r-- 1 openhab openhab 197140 Jul 2 20:36 org.openhab.binding.openocean-2.4.0-SNAPSHOT.jar

In my karaf console I can see that openhab-transport-serial is started:

*      openhab-transport-serial                    | 2.3.0            | x        | Started     | distro-2.3.0            | Serial Transport*

In the logs I found the following error messages:

*20:37:55.932 [ERROR] [org.openhab.binding.openocean        ] - FrameworkEvent ERROR - org.openhab.binding.openocean* *      org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.openocean [222]* *Unresolved requirement: Import-Package: gnu.io*  *      at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]* *      at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634) [?:?]* *      at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613) [?:?]* *      at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585) [?:?]* *      at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528) [?:?]* *      at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [?:?]* *      at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]* *      at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]*  *      20:38:13.652 [WARN ] [org.apache.felix.fileinstall         ] - Error while starting bundle:*  *      org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.openocean [222]* *Unresolved requirement: Import-Package: gnu.io*  *      at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]* *      at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]* *      20:38:23.669 [WARN ] [org.apache.felix.fileinstall         ] - Error while starting bundle:*  *      org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.openocean [222]* *Unresolved requirement: Import-Package: gnu.io*  *      at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]* *      at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]* *      at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]*

Looks like gnu.io isn’t installed properly?

Thx for your help.

Best regards,
Christian

fruggy83 · July 3, 2018, 7:14am

Hi Raphael (@raphael),

welcome to the openhab community. I am glad that this binding works for your (at least in most cases).

Openhab gets inform in two ways about the current state of your in wall module. First of all, your module should send a message when you toggle the light by pressing the physical switch. As I do not own such a module, I cannot confirm that this message is really send by your module. I will check this with my Nodon smart plug, it uses nearly the same EEP. Meanwhile you could look into you openhab log viewer when you press your switch (set log level of my binding to debug). If your module sends a message you should find it here.

Second I implemented a polling mechanism. You can set the polling interval in your thing. A value of zero deactivates the polling. After the polling interval the binding queries the current state of your module and upodates the item states. Could you check if you enabled the polling?

@Matt77
As you also own such a in wall module, can you confirm this behaviour?

Best regards
Daniel

fruggy83 · July 3, 2018, 7:23am

Hi Christian (@c214),

thanks a lot for this information. Your setup seems to be correct. Maybe they updated the gnu.io lib in openhab and my binding tries to use a specific (older) version of this lib ? My last update of openhab is two weeks ago. I will check this.

Best regards
Daniel

raphael · July 3, 2018, 4:42pm

Hi Daniel (@fruggy83)

Thanks for the feedback. I activated trace for the gateway as described here https://community.openhab.org/t/new-openhab2-enocean-binding/39917/12?u=raphael.

The logger entries of activate channel 1 of the in wall module by its physical switch is:

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

2018-07-03 18:34:28.257 [vent.ItemStateChangedEvent] - Switch_Test1_Status changed from Rssi 48, repeated 0 to Rssi 49, repeated 0

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

2018-07-03 18:34:33.239 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-07-03 18:34:33.342 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 9 optional length 7 packet type 1

2018-07-03 18:34:33.691 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 0509D103

2018-07-03 18:34:33.697 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D20460E40509D1030001FFFFFFFF3000

2018-07-03 18:34:33.707 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D20460E40509D10300 for 0509D103 received

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

2018-07-03 18:34:33.729 [vent.ItemStateChangedEvent] - Switch_Test1_Status changed from Rssi 49, repeated 0 to Rssi 48, repeated 0

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

2018-07-03 18:34:33.737 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-07-03 18:34:33.840 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1

2018-07-03 18:34:34.148 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 0509D103

2018-07-03 18:34:34.151 [TRACE] [nal.transceiver.OpenOceanTransceiver] - F6100509D1033001FFFFFFFF3100

2018-07-03 18:34:34.155 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet F6100509D10330 for 0509D103 received

2018-07-03 18:34:34.169 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

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

2018-07-03 18:34:34.171 [vent.ItemStateChangedEvent] - Switch_Test1_Status changed from Rssi 48, repeated 0 to Rssi 49, repeated 0

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

2018-07-03 18:34:34.272 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 7 optional length 7 packet type 1

2018-07-03 18:34:34.580 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 0509D103

2018-07-03 18:34:34.585 [TRACE] [nal.transceiver.OpenOceanTransceiver] - F6000509D1032001FFFFFFFF3000

2018-07-03 18:34:34.590 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet F6000509D10320 for 0509D103 received

And deactivating by OH:

2018-07-03 18:39:18.952 [ome.event.ItemCommandEvent] - Item 'Switch_Test1_A' received command OFF

2018-07-03 18:39:18.960 [vent.ItemStateChangedEvent] - Switch_Test1_A changed from ON to OFF

2018-07-03 18:39:18.965 [GroupItemStateChangedEvent] - gSwitch changed from ON to OFF through Switch_Test1_A

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

2018-07-03 18:39:18.968 [TRACE] [nal.transceiver.OpenOceanTransceiver] - sending request

2018-07-03 18:39:18.976 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - 550009070156D2010000FF97A9810001FFFFFFFFFF00F1

2018-07-03 18:39:18.997 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-07-03 18:39:19.108 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 1 optional length 0 packet type 2

2018-07-03 18:39:19.143 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish response

2018-07-03 18:39:19.148 [TRACE] [nal.transceiver.OpenOceanTransceiver] - request without listener

2018-07-03 18:39:19.164 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-07-03 18:39:19.267 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 9 optional length 7 packet type 1

2018-07-03 18:39:19.616 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 0509D103

2018-07-03 18:39:19.618 [TRACE] [nal.transceiver.OpenOceanTransceiver] - D20460800509D1030001FFFFFFFF3000

2018-07-03 18:39:19.622 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet D20460800509D10300 for 0509D103 received

For me it looks like, that some data will be received by the bridge.

Polling is also active and set to the default value of 300s.

Best regards Raphael

raphael · July 3, 2018, 5:10pm

Hi Daniel (@fruggy83)

I created the in wall module things by auto detection. The detected EEP is:

NodON SIN-2-1-0x (EEP: D2_01_12)

The reference of the in wall module I use based on the user manual is different:

SIN-2-2-0x

and the EEP is identically

EEP: D2-01-12

If I open the drop down list in the Paper UI of the related thing, I’ve got the following possible EEP’s

grafik

Its seems that the reference and EEP are mixed for the nodon in wall modules.

Best regards

Raphael

fruggy83 · July 4, 2018, 4:31am

Good morning Raphael (@raphael),

thanks a lot for this trace log. I could find the error and will fix the bug today. Another interesting fact from the log is that whenever you press your physical switch the in wall module emulates an enocean rocker switch press/release. Therefore you could link another wireless enocean actuators to you wired switch (for example switch on light and activate an smart plug). Very nice feature
These in wall modules getting more and more interesting for me.

Best regards
Daniel

fruggy83 · July 4, 2018, 4:32am

Hi Raphael (@raphael),

thanks a lot for this hint, too. I will also fix this.

Best regards
Daniel