Hi Daniel (@fruggy83), would it make sense to send you the whole events.log? If so, how can I transfer it to you?
If not I can extract the messages from today and post it here.
Thanks, Tino
Hi Frank (@fnu), not sure if this helps, but I am using openhab 2.4.0 stable + the enocean 2.5.0 snapshot from Daniel and this worked on my openhabian on my VMware.
To use the enocean 2.5.0 snapshot it make the serial connection to my raspi with enocean pi much easier. Just installed and confirured ser2net on the raspi and use the rdc2217 path in the config of the enocean bridge.
Thanks, Tino
Hi Tino (@flynux
you lucky one. I tried the same without success. What exact settngs do you use on raspi and openhab side? Which ser2net version do you use?
Kind regards,
Ralf
Hi Tino (@flynux), everything might help, thanks 
I’m running openhabian directly on the Raspberry Pi 2 (w/ EnoceanPi) I planned to use for OH2. Hardware works great, eno bridge does come up flawless on openhabian and also raspbian with OH2.
Actually I can install any other binding (feature) without hassle from OH2 repository, I don’t get these dependency errors. The 2.4.0 enocean binding can be configured easily, e.g. adding the bridge, albeit some things don’t work as they should, as we know.
The openocean 2.5.0-SNAPSHOT is visible in PaperUI after installation, despite the dependency errors. But it doesn’t list any “Supported Things” in PaperUI … looks like a dummy package. (2.4.0 enocean binding has to be deinstalled …)
Since I did setup a pristine openhabian some hours ago, everything should be at it’s place, I’m a bit perplexed …
Thanks & cheers.
Hi Tino (@flynux),
as I wrote above, your “raw” link gave me the correct file in size 
good to go. 
Installing and deinstalling 2.4.0 enocean binding doesn’t solve my issue, but I guess I have it run now. I tried several bindings from repo I might use in the future, already, e.g. avm for my fritzbox, network & WOL for general purpose, nothing did help up to now.
But since I own a Yamaha RX-S600D, I gave that feature a last chance directly after the last post. To my surprise, “feature:install openhab-transport-serial” made it thru without that dependency errors after “feature:install openhab-binding-yamahareceiver”. Quickly set up my eno bridge w/o hassle, it was up and running within seconds.
Therefor I guess all of you had already running bindings before using 2.5.0-SNAPSHOT and maybe nobody has ever tried to install it on a pristine installation, w/o other running bindings … looks like there is a little flaw in that jar … ?
Thanks and cheers.
Indeed, I had some bindings installed before.
Gruss, Tino
Hi Ralf (@shotte),
my ser2net on the raspi is 2.10.1. My /etc/ser2net.conf has only one line:
3001:telnet:0:/dev/serial0:57600 8DATABITS NONE 1STOPBIT remctl
On the openHAb server (VMware) the path on the bridge looks like:
rfc2217://:3001
But as I noted somewhere else it works only with Daniels enocean 2.5.0 Snapshot.
Hope this helps.
Thanks, Tino
Hi all,
but to make it short, albeit I have openocean binding running, can setup my bridge, unfortunately it doesn’t solve my original issue, to switch a unidirectional Peha actuator. I have three of them in my installation (451 FU-BEP).
I added again a classic device, PaperUI / Configuration / Things / “+”, stopping discovery by “Add manually”, choosing “Classic Device”. There I did set a proper name, accepted given Thing ID, EPP=F6-02-01, also “EPP for receiving states” and let the SenderID set automatically by OH2.
Then adding an Item to the rocker switch of my new classic device, setting a proper name and “Enforce an auto update”.
Finally set one of the “451 FU-BEP” into teach in/learn mode and toggled the little software switch of my Item in PaperUI Control Panel.
But situation hasn’t changed, actuator doesn’t signal it has learned something new by the LEDs nor do I see any specific in the openhab log, again just status changes:
...
2018-12-23 17:07:44.438 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command ON
2018-12-23 17:07:44.503 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitchLicht_RockerSwitch changed from NULL to ON
2018-12-23 17:07:45.096 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command OFF
2018-12-23 17:07:45.111 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitchLicht_RockerSwitch changed from ON to OFF
2018-12-23 17:07:45.777 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command ON
2018-12-23 17:07:45.791 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitchLicht_RockerSwitch changed from OFF to ON
2018-12-23 17:07:46.432 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command OFF
2018-12-23 17:07:46.461 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitchLicht_RockerSwitch changed from ON to OFF
2018-12-23 17:07:47.056 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command ON
2018-12-23 17:07:47.079 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitchLicht_RockerSwitch changed from OFF to ON
2018-12-23 17:07:47.684 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitchLicht_RockerSwitch' received command OFF
...
Thanks so far.
Cheers.
Hi Daniel (@fruggy83),
I have reinstalled openHAB. After this your binding is running.
Just one point: in your documentation you have examples where
enoceanID
is written with a capital D. First I copied this in my config files and did not realize that in the table it is in lower case.
Thorsten
1 Like
Hi Daniel (@fruggy83),
I am now going through my devices checking if they are working with my definitions. There seems to be a problem in my setup moving from virtualRockerSwitch to classicDevise. The virtual switch defined with
Thing enocean:classicDevice:37182ce4:FFC75D31 "Aktor - Hobby" (enocean:bridge:37182ce4) @ "Hobby" [sendingEEPId="F6_02_02",senderIdOffset=49, broadcastMessages=true]{Channels: Type virtualSwitchA:virtualSwitchA[duration=250, switchMode="rockerSwitch"]}
Switch iHobby "Entfeuchter - Hobby" <poweroutlet> (gDryer) {channel="enocean:classicDevice:37182ce4:FFC75D31:virtualSwitchA",autoupdate="true"}
only sends x00. Have I done something wrong in the definition?
Thorsten
Hi Frank (@fnu),
could you please activate the debug level log of the binding. log:set debug org.openhab.binding.enocean. I just want to see, what messages my binding sends when you switch the item.
Best regards
Daniel
Hi Thorsten (@ThAO),
I have just copy and paste your definition into my config files. And this is what I get, when I switch the iHobby item:
2018-12-23 21:26:31.783 [ome.event.ItemCommandEvent] - Item 'iHobby' received command ON
2018-12-23 21:26:31.799 [vent.ItemStateChangedEvent] - iHobby changed from NULL to ON
==> /var/log/openhab2/openhab.log <==
2018-12-23 21:26:31.817 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 21:26:31.822 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F610FFBCF5793001FFFFFFFFFF00
2018-12-23 21:26:31.835 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 21:26:31.860 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFBCF579 payload F610FFBCF5793101FFFFFFFF4700 received
2018-12-23 21:26:32.110 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 21:26:32.113 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F600FFBCF5792001FFFFFFFFFF00
2018-12-23 21:26:32.124 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 21:26:32.145 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFBCF579 payload F600FFBCF5792101FFFFFFFF4700 received
As you can see the messages are send, they are even received as I have to use a repeater, which sends my outgoing messages back to me
So could you please post the debug log here? I just want to see what happens when you switch your iHobby.
Best regards
Daniel
Hi Tino (@flynux),
you could send me the log by mail. You can find my adress in every commit in my openocean repo 
Best regards
Daniel
Hi Daniel (@fruggy83),
here it is:
018-12-23 22:42:18.812 [ome.event.ItemCommandEvent] - Item 'iHobby' received command ON
2018-12-23 22:42:18.839 [vent.ItemStateChangedEvent] - iHobby changed from OFF to ON
==> /var/log/openhab2/openhab.log <==
2018-12-23 22:42:19.075 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:42:19.080 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F600FFC75D312001FFFFFFFFFF00
2018-12-23 22:42:19.090 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-23 22:42:19.094 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2
2018-12-23 22:42:19.097 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:42:19.099 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response without listener
2018-12-23 22:42:19.108 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-23 22:42:19.112 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2018-12-23 22:42:19.116 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFC75D31 payload F600FFC75D312101FFFFFFFF4900 received
==> /var/log/openhab2/events.log <==
2018-12-23 22:42:22.105 [ome.event.ItemCommandEvent] - Item 'iHobby' received command OFF
2018-12-23 22:42:22.123 [vent.ItemStateChangedEvent] - iHobby changed from ON to OFF
==> /var/log/openhab2/openhab.log <==
2018-12-23 22:42:22.367 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:42:22.370 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F600FFC75D312001FFFFFFFFFF00
2018-12-23 22:42:22.381 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-23 22:42:22.385 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2
2018-12-23 22:42:22.389 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:42:22.393 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response without listener
2018-12-23 22:42:22.401 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-23 22:42:22.405 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2018-12-23 22:42:22.423 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFC75D31 payload F600FFC75D312101FFFFFFFF4700 received
I havn’t checked if this is what I expected.
Thorsten
Hi Daniel (@fruggy83),
very interessting behavior, after my last try that afternoon, I deleted the defined Classic Device and corrosponding switch Item and restartet Openhab2 Service. Items don’t dissappear completely when deleted thru PaperUI, but cleanup thru a openhab2 restart …
A minute ago I did set the requested Debug Level and redefined everything, so a Classic Device with a proper Switch Item. I did not even put the actuator into teach in mode. Well what should I say, actuator does work now … 
To things, I haven’t restarted openhab2 after feature:install openhab-transport-serial, but the most important mistake I made, I obviously didn’t even try to switch the actuator after I took it out of teach in at my last test.
Since I haven’t seen the changed blink frequency on the actuator in teach in mode, I thought it didn’t work. But trying to switch it, is only possible after leaving teach in and there I just deleted everything … my bad, sorry.
So, but some Debug output for you:
2018-12-23 22:27:55.125 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitch_RockerSwitch' received command ON
2018-12-23 22:27:55.146 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitch_RockerSwitch changed from OFF to ON
2018-12-23 22:27:55.159 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:27:55.179 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F610FF9567013001FFFFFFFFFF00
2018-12-23 22:27:55.194 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:27:55.460 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:27:55.464 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F600FF9567012001FFFFFFFFFF00
2018-12-23 22:27:55.478 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:27:55.971 [ome.event.ItemCommandEvent] - Item 'Flur1OGVirtualSwitch_RockerSwitch' received command OFF
2018-12-23 22:27:55.986 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:27:55.988 [vent.ItemStateChangedEvent] - Flur1OGVirtualSwitch_RockerSwitch changed from ON to OFF
2018-12-23 22:27:55.990 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F630FF9567013001FFFFFFFFFF00
2018-12-23 22:27:56.003 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:27:56.270 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2018-12-23 22:27:56.275 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload F600FF9567012001FFFFFFFFFF00
2018-12-23 22:27:56.287 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2018-12-23 22:31:43.243 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for FFFA4100 payload A500009348FFFA41000001FFFFFFFF5800 received
2018-12-23 22:40:43.424 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for FFB44900 payload A50003E048FFB449000001FFFFFFFF4A00 received
2018-12-23 22:41:27.070 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for FFB44902 payload A5FF072649FFB449020001FFFFFFFF4A00 received
2018-12-23 22:42:04.819 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for FFB44902 payload A5FF072749FFB449020001FFFFFFFF4A00 received
Looks like I receive some polling from the only bi-directional Peha actuator (2-channel), which is already installed … I still have one 2-channel from Peha to install and also 2 Nodon dual channel.
And like with the only physical rocker I discovered 2 days ago and deleted already again, I need to define EPP:F6-02-02 for that Peha 451.
Thanks so far. Merry christmas and some quiet & peaceful days for all of you 
I will now go one with my OH2 experience the next days and may report some things here.
Cheers
And for the last, toggling the software switch while the actuator is in teach in, is a stupid idea. Just one ping … not more … 
What is the correct way for the bi-directional actuators? Define them also via classic device or put them into teach in and do a discover with OH2?
Cheers
Hi Thorsten (@ThAO),
thanks for your log. I think you have not installed my snapshot 2.5 binding, have not you? The 2.4 binding has a bug in the virtualSwitchA channel. It does not send the PRESSED message. If you compare my log with your, you will see, that in my log two messages are send. One PRESSED message 0x10 and one released message 0x00. The first one is missing in your log.
Best regards
Daniel
Hi Frank (@fnu),
I am glad that it works now. Sometimes you better do not ask why… 
So, but some Debug output for you
Looks good to me!
Looks like I receive some polling
Yes you receive 4BS messages from three different actuators FFFA4100, FFB44900 and FFB44902. These messages could be energy measurement messages or anything else. Without knowing the EEP it is almost impossible to interpret the message content.
What is the correct way for the bi-directional actuators?
In most cases the bi-directional actuators support a teach in method called UTE. In this case they send a teach in messages which contains the EEP to control them. This should work at least for the NodOns as these are definitely not too old. Just do the following. Start discovery for the enocean binding and start the teach in process of you actuators afterwards. Shortly after you should find an item in your inbox which is completely configured sending/receiving EEP, enocean Id, senderId and so on. You just need to give it a name. However be sure to use the snapshot version, otherwise you are not able to switch these actuators 
Best regards and merry christmas
Daniel
Hi all,
I wish you all a merry christmas and some peaceful days. As I am on a family round trip the next days, I will be a little more quiet.
Sorry for the troubles with this binding, I hope the next release will be more stable. Have a good time 
Best regards
Daniel
2 Likes