fruggy83 / openocean Goto Github PK

View Code? Open in Web Editor NEW

27.0 27.0 12.0 2.91 MB

Java 99.75% HTML 0.25%

openocean's People

Contributors

Stargazers

Watchers

Forkers

wiss911 casshern81 bodiroga sepp99 dominikkv rebuild82 nimric tboesch iot-openhab efdeb thehendla

openocean's Issues

Switching state of D2_01 EEP is not correctly parsed

Switching state of D2_01 EEP is not correctly parsed. Condition checks for STATUS_SWITCHING_ON instead of STATUS_SWITCHING_OFF.

STM 330 temperature sensor formatting error

Premise: I am new to openhab2 and to enocean protocol, but I was able to get the EnoceanPi gateway recognized and working following your instructions (using the 2.4.0-snapshot release on openhabian). It might be that the issue is not related to this addon, but it's the first sensor I am adding to openhab.

I managed to get an STM 330 temperature sensor automatically recognized with the "teach in" message. It has been added as A5-02-05, with a temperature range of 0-40 degrees C, which matches the datasheet.

Everything looks fine, except I am getting the following warnings in openhab.log:

2018-10-05 16:28:53.299 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '22.431372549019606' of item openocean_temperatureSensor_IDIDXX_IDIDYY_temperature with format '%.1f %unit%': Conversion = 'u'

And in paper UI the values are displayed as follows:

I am unsure whether this issue is in the addon or if there is something wrong with my openhab setup, so please apologize if this issue is creating unnecessary noise.

USB Auto discovery detects every FTDI device as an USB300 gateway

The USB dicovery just checks the vendor and product id => each FTDI device is detected as an USB300 gateway. The manufacturer should be added to this check.

support for 2 Channel Actor

Hi
I just digged into home automation with openHAB and some eltako devices that I was using decentralised. I was very impressed how much was already working out of the box. Thanks for that.
The one thing that I didn't get completely working is the FSR71-2x which is more or less an FSR61 but with two channels. The first channel is working normally. Is there an easy way (not using an generic device) to get the second channel working?

Support discovery of USB dongles

Hi Daniel (@fruggy83)!

It would be great if we could add support for automatic discovery of Enocean USB dongles using the new USB discovery API (more information: eclipse-archived/smarthome#5153). I will try to provide a PR to include the Enocean USB300 controller. Device information:

idProduct = "6001"
idVendor = "0403"
manufacturer = "EnOcean GmbH"
product = "EnOcean USB 300 DB"
serial = "FT3MXEB" (Can you confirm that your device has a different serial number?)

Data taken executing the command: "udevadm info -a -n /dev/ttyUSB0"

Many many thanks for your work with the binding, I'm playing with it and it looks really really good! 👍

Best regards,

Aitor

Sender Id and options for spoofing

Hi,

I installed the addon, and configured a rocker switch via the discovery. I can see the state of the buttons are being picked up nicely, and everything seems to work.

Currently the rocker switch is controlling a light-bulb, and clicking the switch turns it on or off (Channel A). Changing the state in the web-interface does nothing.

I believe that I am supposed to configure the sender_id on the rocker switch, such that a unique device id can be generated, and then program this ID into my receiver / actuator, which actually controls the light bulb.

Is my understanding on this correct? - This is the intended way to configure the system?

The reason I'm asking, is that I (perhaps wrongly) assumed that it would just work out of the box. That the USB300 would spoof / send the device id from the rocker switch, and send an identical message to the one generated by toggling the switch.

Is there a reason why this is not the case? - Is it not technically feasible / impossible to do?

I would argue, that spoofing would be a reasonable feature (assuming it's possible), as it would remove the burden of reconfiguring / reprogramming receivers to accept the new device id.

Analyse Transceiver startup

Sometime thes Transceiver does not start up the first time. Whenever this occures the time between setting up the receiving thread and requesting the base Id is very short. Maybe following actions should wait a bit until the threads are running.

I am working on this.

Fix channel comparison in D5_00_01

Comparison is made by reference. Change to String.equals().

Add PTM200 messages to rollershutter

I am working on this.

Analyse percentage value messages for rollershutter A5-38

I am working on this.

Richtige Nutzung

Hallo Daniel,

ich teste jetzt schon ein paar Tage verschiedenes mit meinem Enocean Setup und verfolge dein Binding hier. Habe jetzt auch die neueste Version von dir installiert, aber mir ist gerade mit dem neuesten nicht ganz klar wie ich vorgehen muss um das richtig einzusetzen. BTW: Hast du zufällig ein Weberhaus? Kommt mir wegen der Komponenten so vor, ist gleich wie bei mir :-)

Also ich möchte für meine Lichtschalter und Rolloschalter ( FSR14, FSB14 ) jeweils einen Schalter/Steuerungsschalter in meiner Oberfläche abbilden. Wenn der physische Schalter gedrückt wird, soll der Status davon upgedated werden und ich möchte auch über den virtuellen Schalter die Rollos und Lichter schalten. Habe dazu einen USB Stick ( USB300 ) . Habe das auch schon einigermaßen hinbekommen aber mit deiner neuesten Änderung muss ich nochmal generell nach der einfachsten und besten Vorgehensweise fragen um das zu bewerkstelligen. Ich möchte nicht mehrere Switches haben, einen zum an und ausschalten und einen anderen der den Status anzeigt.

Das ich die virtuellen Schalter im Aktor anlernen muss ist mir auch klar und habe ich mit der vorhergehenden Version auch erfolgreich mit 2 Schaltern hinbekommen.
Habe jetzt mit deiner neuesten Version und deinem Beispiel hier aus den Issues so einen Schalter ( siehe unten ) in den Items angelegt. Aber damit wird ja nicht gesendet.

Switch vLight "vLight" {channel="openocean:virtualRockerSwitch:ee492843:virtualRockerswitch", profile="openocean:rockerswitch-to-on-off",switchMode="rockerSwitch", duration="250", channel="openocean:rockerSwitch:xxxxxxxx:yyyyyyyyy2:rockerswitchB"[profile="openocean:rockerswitch-to-on-off"]}
String VRS_CMD "CMD" {channel="openocean:virtualRockerSwitch:ee492843:virtualRockerswitch"}

Am liebsten wärs mir noch die Beispieleinträge für die Config files ( Items, Things ) zu haben oder die Schritte für ein Item ( Licht oder Rollo ) um oben genanntes zu erreichen.

Vielen Dank

Selecting USB device doesn't show my device.

Hi,
I have a bit more complex setup where I pass a USB EnOcean USB300 stick from a raspberry pi to my server via ethernet. When I look at which devices I have present on the server, I get this:

ls -lah /dev/tty*
crw-rw---- 1 root uucp 188, 0 May 20 20:44 /dev/ttyUSB0
lrwxrwxrwx 1 root uucp 10 May 23 11:18 /dev/ttyUSB2 -> /dev/pts/6

As you can see I have one local EnOcean USB 300 (ttyUSB0) and one linked virtual USB device (ttyUSB2).

Since I use docker, I pass this virtual device into my container via:
--device=/dev/ttyUSB2

This is the same way that I link the other.

Inside the container, when I once again do

ls -lah /dev/tty*
crw-rw---- 1 root    uucp2 188, 0 May 23 11:55 /dev/ttyUSB0
crwxrwxrwx 1 root   uucp2   136, 6 May 23 11:55 /dev/ttyUSB2

You can see that the device was provided to the container as well.
But when trying to add a new bridge to the OpenOcean binding, It doesnt let me choose the ttyUSB2 device. It simply doesn't show up in the dropdown.
Any idea how to solve this?

edit:
I also added the usb devices to the Java parameters with the following environment variable:

EXTRA_JAVA_OPTS=-Dgnu.io.rxtx.SerialPorts=/dev/ttyACM0:/dev/ttyUSB0:/dev/ttyUSB2

State not updated for F6-02 - Rocker Switch

Hi @fruggy83,

first of all thanks for taking up the task to provide an Enocean binding for OH2.

When i add my Eltako switches as thing and bind the actor channel generalSwitchB
to a Switch Item i can control the actor and switch the light. Unfortunately when i switch
the actor state by other means (for example with FT55 rocker switches) the state of the
Item is not updated in OH2. When i use the rockerswitchB channel i get a proper state
of the Item when the switch state changes but cannot switch the state from OH2 anymore.

I also tried the A5-38 - Central command profile but with this the actor is neither switching nor
can i see the state in OH2.

I am very grateful for any hints on how to get my switches to work.

Thanks

MArtin

Use default profile for rocker switches.

Currently when assigning an item to a rocker switch thing, there is no proper default conversion of trigger events to thing commands.

The appropriate system profiles for dimmers and switches should be used, so that the user does not always have to define a profile.

Implementation of EEP A5-07-01 EOSWA-W-EO occupancy sensors

Hey @fruggy83,

your official version has a lot of nice improvements, great work.
I wanted to use the occupancy sensors with your binding. The sensor use the EEP A5-07-01.
I tried the generic approach but stuck with the MAP transformation because of the data format from the sensor. It sends additionally to the occupancy value the super-cap voltage and solar panel current which i don't need but not fixed values.

For example four times the data from two different sensors (Wall and Overhead mounted)
DB_3 DB_2 DB_1 DB0
95 7D FF 0B
9D 7D FF 0B
96 7C FF 09
99 7B FF 09

DB_3 = Voltage Super-Cap 0-255 (% von 0-5V)
DB_2 = Solar Panel current 0-127uA (Wrong with battery)
DB_1 = 0xff occupied or 0x00 unoccupied
DB_0 = 0x09 Wall or 0x0b overhead mounted

I tried JS transformation but it didn't get triggered. And the MAP transformation fails because of dynamic values.

Do you know a way to transform such dynamic values from a generic device to string or something?

PushButton message validation to strict

The current message validation for PushButtons (EEP F6_01) is to strict.

FUD71-230V

i recently needed to replace a broken Dimmer with a new FUD71-230V.
It is working fine with the wall switches i have but unfortunately i am not
able to get it into openhab. I started scanning and than pressed a wall
switch to turn on the dimmer but nothing turned up in openhab.

I also tried to add it manually as A5-38 Central Command with the device address
as thingid and dimmer as profile but nothing happens when i use the dimmer
from wall switches and also i dont see a teach-in channel on the manually created
device so i can start the teach in process.

The trace logs show:

==> /var/log/openhab2/openhab.log <==
2018-12-11 20:27:51.204 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte
2018-12-11 20:27:51.307 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received header, data length 10 optional length 7 packet type 1
2018-12-11 20:27:51.678 [TRACE] [nal.transceiver.OpenOceanTransceiver] - publish event for: 050A7B7D
2018-12-11 20:27:51.688 [TRACE] [nal.transceiver.OpenOceanTransceiver] - A502000008050A7B7D0001FFFFFFFF5300
2018-12-11 20:27:51.694 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - ESP Packet A502000008050A7B7D00 for 050a7b7d received

Any help would be greatly appreciated.

Martin

Implement EEP A5-07-03 (NodOn PIR)

Should not be a big problem as all neccessary channels are already implemented.

I am working on it.

Warning during start of openhab

I am getting the following messageduring boot of openhab:


java.lang.IllegalArgumentException: The XmlConfigDescriptionProvider must not be null!
        at org.eclipse.smarthome.core.binding.xml.internal.BindingInfoXmlProvider.<init>(BindingInfoXmlProvider.java:59) [101:org.eclipse.smarthome.core.binding.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.core.binding.xml.internal.XmlBindingInfoProvider.createDocumentProvider(XmlBindingInfoProvider.java:141) [101:org.eclipse.smarthome.core.binding.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.acquireXmlDocumentProvider(XmlDocumentBundleTracker.java:174) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.addingObject(XmlDocumentBundleTracker.java:199) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.parseDocuments(XmlDocumentBundleTracker.java:343) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.processBundle(XmlDocumentBundleTracker.java:329) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker.access$3(XmlDocumentBundleTracker.java:324) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at org.eclipse.smarthome.config.xml.osgi.XmlDocumentBundleTracker$2.run(XmlDocumentBundleTracker.java:300) [97:org.eclipse.smarthome.config.xml:0.10.0.201803191037]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]

ClassicDevice Toggle SwitchMode is not handled correctly

The Toggle SwitchMode of ClassicDevices is not handled correctly. DIR1 result is overridden by DIR2 result.

TCM310 Stick not working

Hi,

I can't get the following Enocean-USB-Stick to work with openHAB and the openocean binding:
https://www.amazon.de/dp/B01DRO7B2U/ref=cm_sw_em_r_mt_dp_U_9PMHBbHX0HSN7
Is it documented that it should work? Than I would dig into this problem...
It is running out of the box with FHEM, so I can assure the Stick is not broken ;-)

Best regards

Bekomme Enoceanpi nicht zum laufen

Hallo,

Ich bekomme einen enoceanpi nicht zum laufen. Wenn ich ihn in Openhab2 hinzufügen wird er erkannt aber mit der falschen ttyUSB0 verbindung und er ist offline. Wenn ich ihn dann auf ttyS0 umstelle geht er online, will ich dann aber ein sensor oder switch hinzufügen geht er beim scan wieder offline.

ich hoffe ich habe mich verständlich ausgedrückt, anbei noch ein auszum aus dem log.

Vielleicht kann mir einer von euch einen Tip geben.

Danke

21:42:16.086 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
21:42:16.106 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:42:16.121 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:42:16.135 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id... to ONLINE
21:42:16.592 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:42:16.657 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:42:16.677 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:42:16.704 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:43:15.789 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'yamahareceiver:zone:5f9ec1b3_ed59_1900_4530_00a0dea3212d:Main_Zone' has been updated.
21:43:27.495 [INFO ] [ransceiver.OpenOceanSerialTransceiver] - Transceiver shutdown
21:43:27.511 [INFO ] [ransceiver.OpenOceanSerialTransceiver] - Transceiver shutdown
21:43:27.515 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from ONLINE to OFFLINE (CONFIGURATION_PENDING): trying to connect to gateway...
21:43:27.512 [INFO ] [overy.OpenOceanDeviceDiscoveryService] - Stopping EnOcean discovery scan
21:43:27.547 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'openocean:serialbridge:AI05HDEQ' has been updated.
21:43:27.535 [INFO ] [ransceiver.OpenOceanSerialTransceiver] - OpenOceanSerialTransceiver initialized
21:43:27.574 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): trying to connect to gateway... to OFFLINE (CONFIGURATION_PENDING): opening serial port...
21:43:27.560 [INFO ] [overy.OpenOceanDeviceDiscoveryService] - Starting EnOcean discovery and accepting teach in requests
21:43:27.610 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
21:43:27.651 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
21:43:41.008 [INFO ] [smarthome.event.ItemStateChangedEvent] - ITSchrank_Gesamtverbrauch changed from 1168.65 kWh to 1168.651 kWh
21:43:41.033 [INFO ] [smarthome.event.ItemStateChangedEvent] - ITSchrank_Leistung changed from 29.460 W to 29.110 W
21:43:44.812 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'samsungtv📺94d34678_84f0_92c9_2ea2_9e2751666d35' changed from ONLINE to OFFLINE
21:44:15.818 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'yamahareceiver:zone:5f9ec1b3_ed59_1900_4530_00a0dea3212d:Main_Zone' has been updated.
21:44:27.561 [INFO ] [overy.OpenOceanDeviceDiscoveryService] - Stopping EnOcean discovery scan
21:44:27.646 [INFO ] [ransceiver.OpenOceanSerialTransceiver] - Transceiver shutdown
21:44:27.681 [INFO ] [ransceiver.OpenOceanSerialTransceiver] - OpenOceanSerialTransceiver initialized
21:44:27.683 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id... to OFFLINE (CONFIGURATION_PENDING): opening serial port...
21:44:27.752 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
21:44:27.788 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:serialbridge:AI05HDEQ' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
21:44:30.287 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:virtualRockerSwitch:e4d07369' changed from UNINITIALIZED to INITIALIZING
21:44:30.321 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'openocean:virtualRockerSwitch:e4d07369' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)

Support Status telegram from Eltako TF-FKB

The window contact TF-FKB sends, next to the sensor telegrams, every hour a status telegram. In this telegram, the battery voltage is given, which I want to use for maintenance.

The problem is that the EEP is not given, only the content of the telegram. The nearest EEP I could find is A5-14-01, so I would call the new EEP A5_14_01_ELTAKO (or is A5_14_01_TFFKB better?). Here the content like given in the manual:
ORG = 0x07
DB0 = 0x08
DB1 = 0x00
DB2 = 0x00..0xFF = 0..5V (Battery voltage)
DB3 = 0x00..0xFF = 0..5V (Battery storage)

Sample data received:

A5 8E A2 00 08 0580E268 0001FFFFFFFF5800
A5 8F A2 00 08 0580E268 0001FFFFFFFF5900

I don't know what the difference is between DB2 and DB3, so I would publish both values, adding a channel "batteryStorage". Is this OK?

Support wired Bridge Types

Implement support for:

~~TCP Bridges~~
FAM/FGW Bridges

Splitt receivingState into RSSI & repeater count

I think of splitting the channel "receivingState" into its parts RSSI & repeater count to log these values in database, to see anomalies. I think the best would be to remove "receivingState", because one can build this string on his own.

I'm open for discussion :-)

Required OpenHAB version

Hi,

this may sound like a stupid question, but can I Install this plugin also with the stable version 2.2 of OpenHAB? Or do I need to upgrade to nightly builds?

Thanks,
Leif

Implement retry-policy for missing answers

Discussion here

I will implement this

Commands for virtualSwitchA channel are not correctly converted

The On/Off commands from the switch item bound to the virtualSwitchA channel are not transfered correctly to the EEP. So only the release message is send correctly.

Support Eltako TF-AHDSB

The outdoor brightness sensor Eltako TF-AHDSB has two differnt modes:

FAH mode
Sends brightness data.
EEP A5-06-01
DB3 = 0x00..0x64 = 0-50 lux, linear (brightness, only if DB2 = 0x00)
DB2 = 0x00..0xFF = 300..30000 lux, linear (brightness)
DB1 = -
DB0 = 0x08
This seems to be odd, because the content does not match the given EEP. Further testing would be neccessary.
TF-Mode (additional to FAH mode)
Sends on / off telegrams when a given brightness is reached.
EEP A5-38-08
DB3 = 0x01 (-> CMD 1 "switching")
DB0 = (0x08 = off) || (0x09 = on) || (0x28 = unlock)

Eltako FLC61NP und FDB

Analyse exception on MSC messages

I am working on this.

Problem with Virtual Rocker Switch

Hi Daniel, (@fruggy83 )
thank you so much for the new Enocean binding.
At the moment I'm running into some issues using the "Virtual Rocker Switch" for my PEHA EasyClick 452 FU-EBIM JR UP Rollershutter device, as this device is not directly supported at the moment.
The system I use:
A Rasbperry 3B with openHabian, version openHAB 2.3.0-1, a TCM300 USB stick and the OpenOcean version I use is this one here: https://github.com/fruggy83/openocean/raw/master/precompiled/org.openhab.binding.openocean-2.4.0-SNAPSHOT.jar

It seems that the Openocean Binding is up and running. In the log file I get the following output:

2018-11-18 16:46:16.538 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte 2018-11-18 16:46:16.542 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 10 optional length 7 packet type 1 2018-11-18 16:46:16.548 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RADIO_ERP1 with RORG _4BS for FFEDB980 payload A500001108FFEDB9800001FFFFFFFF2E00

So then I tried to teach in the device using the "Virtual Rocker Switch".

I was reading the issue here #18 .
First of all I run into the same issue, that I couldn't select a profile during item linking.
So I tried the way of creating a manual configuration like in the issue but had the problem, that I couldn't activate the switch. After a little bit back and forth I suddenly could link an item to the thing over the PaperUI. Don't ask me why and what I exactly did.
So now I have switch in the UI which is toggeling in the UI, but I'm not able to pair OH2 with the PEHA. There are no log messages which would indicate that there are any messages send by OH2.

Do you have any suggestions? Is this a bug or is it a user problem?

Thanks,

Christian

Installation von openocean in Openhab 2

Hallo,
Ich versuche mich schon den ganzen Abend daran openocean in meiner Openhab2 installation zu integrieren. Ich habe einen Raspberry 3 mit installiertem raspbian und darauf habe ich openhab installiert.
Als erstes habe ich versucht das komplette git in /ust/share/openhab2/addons zu packen. Aber habe das Addon dann nicht gefunden.
Auch im Ordner /opt/openhab2/addons gab es kein Erfolg.
Evtl kannst du ja hier eine kurze Anleitung schreiben wie man das Addon am schnellsten in openhab2 installieren kann

Support for Eltako TippFunk EnOcean devices

Does OpenOcean also support the Eltako TippFunk devices. I currently have many of these installed and would like to switch from FHEM to OpenOcean

TF61L Light Actuator (uses EEP N5-38-08)
TF61D Dimmer Actuator (uses EEP H5-38-08)
TF61J Rollershutter Actuator (uses EEP H5-3F-7F)

Remote FAM4PI not working

Hi,

I played around with Openhab2 over the weekend and tried connecting the Enocean binding to the FAM4PI (TCM-310) on a remote RPI. So I made /dev/ttyAMA0 accessible to my local network via ser2net. Unfortunately, the URL rfc2217://pi-enocean:22100 can't connect. But in a Telnet session I see incoming telegrams.

However, the next attempt was to connect to my remote RPI tty via socat, like this tutorial. I created a local device named /dev/tty.enocean. Et voila! The binding attempts to retrieve the base ID. But it never succeeds.

The following output is the Openhab log with DEBUG loglevel and filtered by grep enocean. (I removed my base ID and chip ID)

2019-01-19 23:12:00.456 [DEBUG] [transceiver.EnOceanSerialTransceiver] - shutting down transceiver
2019-01-19 23:12:00.464 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Interrupt rx Thread
2019-01-19 23:12:00.470 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closing serial output stream
2019-01-19 23:12:00.477 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closeing serial input stream
2019-01-19 23:12:00.480 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closing serial port
2019-01-19 23:12:00.503 [INFO ] [transceiver.EnOceanSerialTransceiver] - Transceiver shutdown
2019-01-19 23:12:00.537 [INFO ] [transceiver.EnOceanSerialTransceiver] - EnOceanSerialTransceiver initialized
2019-01-19 23:12:00.561 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - request base id
2019-01-19 23:12:00.583 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2019-01-19 23:12:00.591 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 08
2019-01-19 23:12:00.606 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2019-01-19 23:12:00.646 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00FF [<BASE-ID>] received
2019-01-19 23:12:00.654 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - received response for base id
2019-01-19 23:12:00.864 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 03
2019-01-19 23:12:00.909 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00020A000002050000[<CHIP-ID>]454F0103474154455741594354524C0000000000 received

Can someone confirm that the rfc2217:// connection works?
Have you seeing something like this before?

Help Wanted: Cannot connect to USB300

Hi,
I'm running the latest docker openhab version on a QNAP TS453. Unfortunately I can't connect to my USB300.

I tried the following:
Install Enocean Binding
Add Thing -> Enocean Gateway with Path = /dev/ttyUSB0

OH gives me the Status:OFFLINE - CONFIGURATION_ERROR Port could not be found.

I tried Openhab with a virtual machine running ubuntu server on my notebook which works perfect so the hardware might not be the problem.

Is it possible that i don't have the proper permissions to access the stick? Running "ls -l /dev/ttyUSB0" only shows
"crw------- 1 root root 188, 0 Jan 5 21:01 /dev/ttyUSB0"

but i already added user openhab to dialout and tty group

any help would be appreciated as i'm not very into Linux and Docker ;)

Cheers,

Lars

[Qnap] OpenHAB crasht sobald bridge hinzugefügt wird

Hallo @fruggy83
die letzten Jahre lief auf meinem Qnap NAS 219p II immer FHEM, da es leider kein gutes Bindung für OpenHAB 2 gab. Jetzt bin ich letzte Woche über dei Binding gestolpert und wollte es gleich mal testen. Nach vielen Anstrengungen

erst nur QPKG für openHAB 2.2 gefunden - - > mit älteren openocean Versionen versucht
nach vielen Fehlversuchen eine QPKG mit 2.3.0 gebastelt und installiert bekommen und am Ende auch 2.4.0-M5 und auch 2.4.0-SNAPSHOT

habe ich dein aktuelles Binding mit openHAB 2.4.0 soweit zum laufen gebracht, dass es in der karaf console als Active angezeigt wurde und ich es auch in der Paperui gefunden habe. In der Inbox findet er auch brav den USB300 Adapter. Aber jedesmal wenn ich dann auf "add to Things" drücke stürzt der openHAB ab. Ich habe schon verschiedene openhab Versionen getestet und auch verschiedene Stände von openocean. Auf meinem anderen Qnap NAS 109P passiert genau das selbe. Hast du eine Idee woran das liegen könnte?
Ich komme leider nicht mehr weiter und meine Frau hatte gerne wieder das die Jalousien von selber auf und zu gehen ;)

Unter Userdata wird dabei ein Error Logfile angelegt. Hier die ersten Zeilen:
A fatal error has been detected by the Java Runtime Environment: SIGILL (0x4) at pc=0xab512d10, pid=10350, tid=0xa61bf490 Problematic frame: C [libNRJavaSerial.so+0x98e4] JNI_OnLoad+0x28 . . . Event: 485.558 Thread 0x00f9b400 Exception <a 'java/lang/UnsatisfiedLinkError': unsupported JNI version 0x00000002 required by /share/MD0_DATA/openHAB/userdata/tmp/libNRJavaSerial_HF_admin_0/libNRJavaSerial_HF.so> (0xacb9f568) thrown at [/HUDSON/workspace/8-2-build-elinux-arm-sflt/jdk8u1

Schon mal vielen Dank im Voraus

rebuild

Dimmer not updated after openhab restart

Hi @fruggy83

as mentioned in the community the is something problematic going on in the serial
transceiver on openhab startup:

I recently switched to the 2.4 release and found the issue to be present release as well as
at least m8, m7, m6 and the issue-10 version i am currently running.

On a clean openhabian installation i can create the bridge , dimmer thing and dimmer item
and everything works fine whenever the dimmer sends a status message the value is
reflected immediately. This is working until i restart the openhab process after which
the dimmer is still working in a sense that i can dimm it but if the dimmer is sending an
updated telegramm after manual dimming the new value is not updated in the item/thing.

I can solve the issue by removing the bridge and dimmer thing and adding it again afterward,
which makes it work until restart.

In the broken state i can still see the packet recieved for the thing in question but nothing is
published afterwards. As far as i can tell this behaviour is specific for the dimmer / command.

The other devices i have (classicDevices) are still reflecting the state via telegramms from associated
enocean id's. I have this behaviour consistently.

Below is a full startup log but i found the folowing:

2018-12-20 17:15:22.553 [WARN ] [erial.internal.SerialPortManagerImpl] - No SerialPortProvider found for: /dev/ttyUSB.Enocean
2018-12-20 17:15:22.557 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=383, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.681 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01840526' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.610 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - error during bridge init occured
java.io.IOException: Could not find a gateway on given path '/dev/ttyUSB.Enocean', 0 ports available.
	at org.openhab.binding.enocean.internal.transceiver.EnOceanSerialTransceiver.Initialize(EnOceanSerialTransceiver.java:54) ~[227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler.initTransceiver(EnOceanBridgeHandler.java:197) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler.access$2(EnOceanBridgeHandler.java:184) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler$4.run(EnOceanBridgeHandler.java:176) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

after a few minutes the bridge is reinitilized, which is working without a porblem:

2018-12-20 17:16:22.698 [DEBUG] [transceiver.EnOceanSerialTransceiver] - shutting down transceiver
2018-12-20 17:16:22.702 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Interrupt rx Thread
2018-12-20 17:16:22.705 [INFO ] [transceiver.EnOceanSerialTransceiver] - Transceiver shutdown
2018-12-20 17:16:22.712 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_ERROR): Port could not be found to OFFLINE (CONFIGURATION_PENDING): opening serial port...
2018-12-20 17:16:22.744 [INFO ] [transceiver.EnOceanSerialTransceiver] - EnOceanSerialTransceiver initialized
2018-12-20 17:16:22.751 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
2018-12-20 17:16:22.755 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - request base id
2018-12-20 17:16:22.758 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
2018-12-20 17:16:22.774 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:16:22.790 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 08
2018-12-20 17:16:22.823 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:16:23.074 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 03

After which all things go into online state but at least dimmers are not updated.

I am a bit lost on how to debug this problem further, I assume there is some problem
in teh startup sequence or the sequence of loading things. The above error does
not appear when adding the bridge after startup.

As always very much gratefull for any advise how to debug further?

Thanks

Martin

2018-12-20 17:14:26.428 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=120, service.bundleid=227, service.scope=bundle, component.name=org.openhab.binding.enocean.internal.discovery.EnOceanUsbSerialDiscoveryParticipant, component.id=13} - org.openhab.binding.openocean
2018-12-20 17:14:26.474 [DEBUG] [org.openhab.binding.openocean       ] - BundleEvent [unknown:512] - org.openhab.binding.openocean
2018-12-20 17:14:28.945 [DEBUG] [org.openhab.binding.openocean       ] - BundleEvent STARTING - org.openhab.binding.openocean
2018-12-20 17:14:28.952 [DEBUG] [org.openhab.binding.openocean       ] - BundleEvent STARTED - org.openhab.binding.openocean
2018-12-20 17:14:30.883 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2018-12-20 17:14:31.003 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2018-12-20 17:14:49.860 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'kz.items'
2018-12-20 17:14:50.352 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'wz.items'
2018-12-20 17:14:50.484 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ka.items'
2018-12-20 17:14:50.601 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ba.items'
2018-12-20 17:14:50.738 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'fl.items'
2018-12-20 17:14:50.845 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.items'
2018-12-20 17:14:50.953 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ku.items'
2018-12-20 17:14:51.104 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'az.items'
2018-12-20 17:14:51.215 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'sz.items'
2018-12-20 17:14:52.576 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'mapdb.persist'
2018-12-20 17:14:57.463 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2018-12-20 17:15:02.803 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ba.rules'
2018-12-20 17:15:03.698 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ku.rules'
2018-12-20 17:15:05.050 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.sitemap'

2018-12-20 17:15:08.670 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM.zwave'
2018-12-20 17:15:08.805 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized

2018-12-20 17:15:08.912 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2018-12-20 17:15:08.916 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.

2018-12-20 17:15:19.449 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://10.0.3.37:8080
2018-12-20 17:15:19.468 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://10.0.3.37:8443
2018-12-20 17:15:20.338 [INFO ] [.cc2531.network.ZigBeeNetworkManager] - Initialized ZigBee network with existing network state.
2018-12-20 17:15:20.546 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 7CB03EAA00ACE98E: Starting ZigBee device discovery

2018-12-20 17:15:20.556 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 7CB03EAA00ACB3CF: Starting ZigBee device discovery

2018-12-20 17:15:21.144 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui

2018-12-20 17:15:22.197 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0183E856' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-20 17:15:22.211 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BFE' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-20 17:15:22.229 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:018614C7' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-20 17:15:22.233 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01860CD3' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-20 17:15:22.238 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BB7' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2018-12-20 17:15:22.252 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0082254F' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)

2018-12-20 17:15:22.253 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=381, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.327 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=382, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean

2018-12-20 17:15:22.433 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.468 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from INITIALIZING to OFFLINE (CONFIGURATION_PENDING): trying to connect to gateway...
2018-12-20 17:15:22.536 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): trying to connect to gateway... to OFFLINE (CONFIGURATION_PENDING): opening serial port...
2018-12-20 17:15:22.553 [WARN ] [erial.internal.SerialPortManagerImpl] - No SerialPortProvider found for: /dev/ttyUSB.Enocean
2018-12-20 17:15:22.557 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=383, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.681 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01840526' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.610 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - error during bridge init occured
java.io.IOException: Could not find a gateway on given path '/dev/ttyUSB.Enocean', 0 ports available.
	at org.openhab.binding.enocean.internal.transceiver.EnOceanSerialTransceiver.Initialize(EnOceanSerialTransceiver.java:54) ~[227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler.initTransceiver(EnOceanBridgeHandler.java:197) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler.access$2(EnOceanBridgeHandler.java:184) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at org.openhab.binding.enocean.internal.handler.EnOceanBridgeHandler$4.run(EnOceanBridgeHandler.java:176) [227:org.openhab.binding.openocean:2.4.0.201812142103]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2018-12-20 17:15:22.680 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:22.700 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:01840526 bridge status OFFLINE
2018-12-20 17:15:22.702 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_ERROR): Port could not be found
2018-12-20 17:15:22.714 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01840526' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:22.726 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=384, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.752 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25429286
2018-12-20 17:15:22.805 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:22.805 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:00877367' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.807 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:00877367 bridge status OFFLINE
2018-12-20 17:15:22.814 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:00877367' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:22.820 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=385, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.855 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:22.856 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:0185F65C' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.859 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:0185F65C bridge status OFFLINE
2018-12-20 17:15:22.873 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25556572
2018-12-20 17:15:22.877 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:0185F65C' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:22.875 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=386, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.907 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:22.909 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:050A7B7D bridge status OFFLINE
2018-12-20 17:15:22.908 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:050A7B7D' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.916 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:050A7B7D' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:22.922 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=387, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:22.963 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:018614C7' changed from UNINITIALIZED to INITIALIZING
2018-12-20 17:15:22.962 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:22.969 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:018614C7 bridge status OFFLINE
2018-12-20 17:15:22.980 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:018614C7' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.009 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=388, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.012 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=392, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.015 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=391, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.020 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=390, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.013 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=389, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.087 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=380, service.bundleid=227, service.scope=bundle, component.name=org.openhab.binding.enocean.internal.EnOceanHandlerFactory, component.id=12} - org.openhab.binding.openocean
2018-12-20 17:15:23.103 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.102 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BFE' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-12-20 17:15:23.105 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:FEFF4BB7 bridge status OFFLINE
2018-12-20 17:15:23.102 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.117 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.119 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:018614C7 bridge status OFFLINE
2018-12-20 17:15:23.129 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.132 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0082254F' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-12-20 17:15:23.131 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.130 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:FEFF4BFE bridge status OFFLINE
2018-12-20 17:15:23.127 [DEBUG] [org.openhab.binding.openocean       ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=393, service.bundleid=227, service.scope=singleton} - org.openhab.binding.openocean
2018-12-20 17:15:23.142 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:0082254F bridge status OFFLINE
2018-12-20 17:15:23.140 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BB7' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.136 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:01860CD3 bridge status OFFLINE
2018-12-20 17:15:23.149 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:018614C7' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-12-20 17:15:23.155 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:018614C7' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.171 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25564359
2018-12-20 17:15:23.178 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01860CD3' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-12-20 17:15:23.187 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BFE' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.195 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01860CD3' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.196 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25562323
2018-12-20 17:15:23.219 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0082254F' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:23.231 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - Initializing enocean base thing handler.
2018-12-20 17:15:23.233 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0183E856' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2018-12-20 17:15:23.234 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:0183E856 bridge status OFFLINE
2018-12-20 17:15:23.247 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0183E856' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-12-20 17:15:30.774 [vent.ItemStateChangedEvent] - kuSchrank changed from NULL to OFF
2018-12-20 17:15:30.794 [vent.ItemStateChangedEvent] - kuHaube changed from NULL to OFF
2018-12-20 17:15:30.813 [vent.ItemStateChangedEvent] - baSpiegel changed from NULL to OFF
2018-12-20 17:15:30.823 [vent.ItemStateChangedEvent] - kuDecke changed from NULL to OFF
2018-12-20 17:15:34.162 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:445d9f4d' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-12-20 17:15:34.253 [hingStatusInfoChangedEvent] - 'zwave:device:445d9f4d:node2' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-12-20 17:15:34.311 [me.event.ThingUpdatedEvent] - Thing 'zwave:serial_zstick:445d9f4d' has been updated.
2018-12-20 17:15:35.503 [hingStatusInfoChangedEvent] - 'zwave:device:445d9f4d:node2' changed from ONLINE to ONLINE: Node initialising: PING
ONLINE
2018-12-20 17:16:22.698 [DEBUG] [transceiver.EnOceanSerialTransceiver] - shutting down transceiver
2018-12-20 17:16:22.702 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Interrupt rx Thread
2018-12-20 17:16:22.705 [INFO ] [transceiver.EnOceanSerialTransceiver] - Transceiver shutdown
2018-12-20 17:16:22.712 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_ERROR): Port could not be found to OFFLINE (CONFIGURATION_PENDING): opening serial port...
2018-12-20 17:16:22.744 [INFO ] [transceiver.EnOceanSerialTransceiver] - EnOceanSerialTransceiver initialized
2018-12-20 17:16:22.751 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
2018-12-20 17:16:22.755 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - request base id
2018-12-20 17:16:22.758 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
2018-12-20 17:16:22.774 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:16:22.790 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 08
2018-12-20 17:16:22.823 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:16:23.074 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 03
2018-12-20 17:16:33.045 [hingStatusInfoChangedEvent] - 'zigbee:device:805460d3:7cb03eaa00acb3cf' changed from UNKNOWN to ONLINE
2018-12-20 17:16:33.057 [hingStatusInfoChangedEvent] - 'zigbee:device:805460d3:7cb03eaa00ace98e' changed from UNKNOWN to ONLINE
2018-12-20 17:16:33.108 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:805460d3:7cb03eaa00acb3cf changed to UNKNOWN.
2018-12-20 17:16:33.114 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:805460d3:7cb03eaa00ace98e changed to UNKNOWN.
2018-12-20 17:16:49.442 [vent.ItemStateChangedEvent] - kz_td_inside_temperature changed from 19.2 to 19.1
2018-12-20 17:16:49.463 [vent.ItemStateChangedEvent] - kz_td_humidity changed from 50.10 to 50.30
2018-12-20 17:17:22.826 [DEBUG] [transceiver.EnOceanSerialTransceiver] - shutting down transceiver
2018-12-20 17:17:22.829 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Interrupt rx Thread
2018-12-20 17:17:22.833 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closing serial output stream
2018-12-20 17:17:22.837 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closeing serial input stream
2018-12-20 17:17:22.840 [DEBUG] [transceiver.EnOceanSerialTransceiver] - Closing serial port
2018-12-20 17:17:22.882 [INFO ] [transceiver.EnOceanSerialTransceiver] - Transceiver shutdown
2018-12-20 17:17:22.894 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id... to OFFLINE (CONFIGURATION_PENDING): opening serial port...
2018-12-20 17:17:22.903 [INFO ] [transceiver.EnOceanSerialTransceiver] - EnOceanSerialTransceiver initialized
2018-12-20 17:17:22.911 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
2018-12-20 17:17:22.913 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - request base id
2018-12-20 17:17:22.916 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:17:22.917 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
2018-12-20 17:17:22.920 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 08
2018-12-20 17:17:22.938 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type COMMON_COMMAND with callback
2018-12-20 17:17:22.942 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-20 17:17:22.948 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 5 optional length 1 packet type 2
2018-12-20 17:17:22.958 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00FF826D000A received
2018-12-20 17:17:22.962 [DEBUG] [nternal.handler.EnOceanBridgeHandler] - received response for base id
2018-12-20 17:17:22.967 [hingStatusInfoChangedEvent] - 'enocean:bridge:cd2c57b1' changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id... to ONLINE
2018-12-20 17:17:22.966 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:0185F65C bridge status ONLINE
2018-12-20 17:17:22.973 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:018614C7 bridge status ONLINE
2018-12-20 17:17:22.973 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:018614C7 bridge status ONLINE
2018-12-20 17:17:22.973 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:01860CD3 bridge status ONLINE
2018-12-20 17:17:22.973 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:0082254F bridge status ONLINE
2018-12-20 17:17:22.974 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response handled
2018-12-20 17:17:23.193 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type COMMON_COMMAND, payload 03
2018-12-20 17:17:23.233 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25564359
2018-12-20 17:17:23.238 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:050A7B7D bridge status ONLINE
2018-12-20 17:17:23.238 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:018614C7' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.224 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2018-12-20 17:17:23.246 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:FEFF4BFE bridge status ONLINE
2018-12-20 17:17:23.250 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 8529231
2018-12-20 17:17:23.250 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 33 optional length 0 packet type 2
2018-12-20 17:17:23.236 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:classicDevice:01840526 bridge status ONLINE
2018-12-20 17:17:23.264 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:rockerSwitch:cd2c57b1:FEFF4BB7 bridge status ONLINE
2018-12-20 17:17:23.264 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:018614C7' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.272 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:0183E856 bridge status ONLINE
2018-12-20 17:17:23.277 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 4278143927
2018-12-20 17:17:23.279 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 000207010002040201018404DA454F0103474154455741594354524C0000000000 received
2018-12-20 17:17:23.309 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 84573053
2018-12-20 17:17:23.274 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 4278143998
2018-12-20 17:17:23.317 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:0185F65C' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.319 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 25421910
2018-12-20 17:17:23.284 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - initializeThing thing enocean:centralCommand:00877367 bridge status ONLINE
2018-12-20 17:17:23.332 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response handled
2018-12-20 17:17:23.341 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01840526' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.354 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Listener added: 8876903
2018-12-20 17:17:23.346 [hingStatusInfoChangedEvent] - 'enocean:classicDevice:01860CD3' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.359 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0082254F' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.366 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BB7' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.371 [hingStatusInfoChangedEvent] - 'enocean:rockerSwitch:cd2c57b1:FEFF4BFE' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.376 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:050A7B7D' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.381 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:0183E856' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-12-20 17:17:23.385 [hingStatusInfoChangedEvent] - 'enocean:centralCommand:00877367' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE

Confusing result when discovering things with multiple bridges

When the user has more than one bridge and discovers a thing it is showing multiple times, once for each bridge.
These things all look the same and the user does not know to which bridge the things belong.

A new method that asks the user for which bridge he wants to discover items should be implemented.

Eltako Funktelegramme Stand 2012

Hallo, anbei die Definition der Funktelegramme für FSR12, FUD12, ...

Eltako Funktelegramme Stand 2012.pdf

How to setup a Virtual Rocker Switch?

Hi Daniel,

I am on day 3 of learning OpenHab2 and I am trying to grasp the setup process of the "F6-02 - Virtual Rocker Switch" but I am not having any success.

List of EnOcean devices I have
EnOcean Pi (connected to a Pi3)
EnOcean STM 330 (Temperature Sensor)
EnOcean PTM215 (Switch)
EnOcean RCM250 (old unidirectional actuator)

I have gotten all the above EnOcean devices to work with your binding with the exception of the RCM250 actuator.

I am under the impression that need to use the Virtual Rocker Switch (as this is a really old actuator), but I am not so sure what things, item, rules and configuration files I need to create and configure (to place in "/etc/openhab2").

Could you please create a bullet list of requirements in order to setup a actuator with Virtual Rocker Switch and getting it working. Also could pleas provide some examples of what to put in the files.

Better still a short tutorial (I know this is a big ask but if you have time I would appreciate it!).

I am impressed with your work and I want to thank you for it!

Yoggi

Enocean USB300 Dongle does not show any event

After standard install of openocean (Bridge + SingleContact - both green "ONLINE", D5-00-01)
looking up openhab.log or events.log. No event has been thrown open or closing the switch

Testet with DolphinView Advanced (works fine) - Windows - getting Signals (ON/OFF)
Switched to UBUNTU, did a cat </dev/ttyUSB0 - works fine
reboot an installed Dongle and Switch - both green in paperUI - no reaction in events.log nor openhab.log
added openhab to group dialout, /dev/ttyUSB0, crw-rw----
For Testing, changed to RockerSwitch - does not help
added EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0" to /etc/defaults/openhab2 - does not help
After all - reinstalled enocean (Standard openhab) - and the devices - does not help either.
Set KARAF (enocean binding) to DEBUG/TRACE - no reaction

USB:
stty -F /dev/ttyUSB0 shows
speed 57600 baud; line = 0;
min = 1; time = 1;
-brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

JAVA:
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)

UBUNTU:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

Improve support for Peha bi-directional actuators.

Hi Daniel @fruggy83,

you may remember I have some issues with my Peha EBI actuators, "451 FU-EBI o.T." & "452 FU-EBI o.T.". They are discovered by openhab2 @ openocean, using EEP D2-01-08 afterwards, but don't do anything then. Means, I cannot switch my lights from OH2, but I get correct status of the switch channel.

I called Peha product support and got some helpful information:

The "Easyclick Gateway Application Note" is only applicable from Firmware Version 3.x and further. This will enable UTE using EEP A5-38-08 resp. -09 for these actuators. I guess two different EEP for 1- resp. 2-channel devices.
=> Here I'm now waiting for additional information, howto find out the FW version for the own actuators ...
If the actuator doesn't provide UTE, so, below FW 3.x, like mine, the teach in method is similar to the Eltako TF61L. Means, enable "normal" teach in mode and send a specific teach in telegram from gateway using EEP A5-39-08 and I also guess -09.
=> Here I'm now waiting for additional information, howto distinguish between 1- and 2-channel devices.
=> I got a screenshot showing these telegrams for A5-39-08:

Teach-In as a gateway controller (4BS): E0 40 00 83
Switch off (4BS): 01 00 00 08
Switch on (4BS): 01 00 00 09
Statusabfrage (4BS): 00 00 00 0A

Any chance to get my Peha actuators supported with openocean?

Cheers
Frank

Thing IDs are all caps

Contrary to all other bindings the OpenOcean binding generates Thing IDs that are all caps.
Clarify if the usage of the new hex conversion function that outputs caps is the way to go from now on and if not, fix it to have lower case thing IDs.

Add ramping time to central command (dimming)

EEP A5-38-08 CMD 0x02 has a ramping time, which defines the speed how fast a dimmer is going to the desired value. Add this as config for the channel.

Enocean discovery process makes Ember Zigbee dongle go offline

Im running Openhab2 installed with Openhabian on a Raspberry Pi 3 B+ with both an Ember Zigbee and USB300 Enocean dongle attached. There is Symlinks for both.
When I start the Enocean discovery Process the Zigbee dongle (Bitron Video ember) goes offline with a communication error and the only way to get it back online is to reboot the Raspberry Pi. This happens every time. Maybe this is an issue of the Zigbee Binding too.

Update readme regarding the new TF-FGB device

Hi @dominikkv, kannst du vielleicht noch die readme zum Binding um ein paar Worte bzgl. TF-FGB erweitern? Vielen Dank im Voraus.

Gruß
Daniel

Einbinden in ein Windows System

Hallo @fruggy83,
ich habe gelesen das du auch ein WeberHaus gebaut hast.
Wir sind nun auch seit Juni stolze Besitzer.
Nun zu meiner Frage, ich habe OpenHab auf einem kleinen Windows on a stick am laufen.
Kann ich dein Binding auch unter Windows betreiben?
Ich würde bei uns gerne den Wibutler ablösen und komplett über OpenHab steuern.
Danke

virtualRockerSwitch stop sending after restart

Hey,

great work @fruggy83 i was waiting for a long time on this binding!

Now i have found a problem with the virtualRockerSwitch.
It stop sending when i restart openhab. But when i change the channel on thing and item live in the textfiles from virtualRockerswitchA to virtualRockerswitchB and also from virtualRockerswitchB to virtualRockerswitchA it starts working again.

Log:
After restart and switch item on the sitemap:

2018-11-01 11:59:05.589 [ome.event.ItemCommandEvent] - Item 'v1' received command ON

2018-11-01 11:59:05.608 [nt.ItemStatePredictedEvent] - v1 predicted to become ON

2018-11-01 11:59:05.621 [vent.ItemStateChangedEvent] - v1 changed from NULL to ON

After changed channel from B to A (update process and afterwards trigger via sitemap):

2018-11-01 12:01:03.856 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'enocean.things'

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

2018-11-01 12:01:04.371 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - Initializing open ocean base thing handler.

2018-11-01 12:01:04.375 [DEBUG] [an.handler.OpenOceanBaseThingHandler] - initializeThing thing openocean:virtualRockerSwitch:usb:AABBDD09 bridge status ONLINE

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

2018-11-01 12:01:04.391 [me.event.ThingUpdatedEvent] - Thing 'openocean:virtualRockerSwitch:usb:AABBDD09' has been updated.

2018-11-01 12:01:04.404 [me.event.ThingUpdatedEvent] - Thing 'openocean:virtualRockerSwitch:usb:AABBDD09' has been updated.

2018-11-01 12:01:04.407 [me.event.ThingUpdatedEvent] - Thing 'openocean:virtualRockerSwitch:usb:AABBDD09' has been updated.

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

2018-11-01 12:01:05.288 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'enocean.items'

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

2018-11-01 12:01:05.598 [.ItemChannelLinkAddedEvent] - Link 'v1-openocean:virtualRockerSwitch:usb:AABBDD09:virtualRockerswitchA' has been added.

2018-11-01 12:01:12.679 [ome.event.ItemCommandEvent] - Item 'v1' received command OFF

2018-11-01 12:01:12.693 [nt.ItemStatePredictedEvent] - v1 predicted to become OFF

2018-11-01 12:01:12.709 [vent.ItemStateChangedEvent] - v1 changed from ON to OFF

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

2018-11-01 12:01:12.788 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback

2018-11-01 12:01:12.792 [TRACE] [nal.transceiver.OpenOceanTransceiver] - << Sending data, type RADIO_ERP1, payload 55000707017AF650FFF13FB03001FFFFFFFFFF0034

2018-11-01 12:01:12.807 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-11-01 12:01:12.814 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2

2018-11-01 12:01:12.817 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RESPONSE with code RET_OK payload 00

2018-11-01 12:01:12.820 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Response without listener

2018-11-01 12:01:12.838 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-11-01 12:01:12.841 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1

2018-11-01 12:01:12.845 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFF13FB0 payload F650FFF13FB03101FFFFFFFF3D00

2018-11-01 12:01:13.071 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback

2018-11-01 12:01:13.317 [TRACE] [nal.transceiver.OpenOceanTransceiver] - << Sending data, type RADIO_ERP1, payload 55000707017AF600FFF13FB02001FFFFFFFFFF0087

2018-11-01 12:01:13.333 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-11-01 12:01:13.336 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2

2018-11-01 12:01:13.339 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RESPONSE with code RET_OK payload 00

2018-11-01 12:01:13.341 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Response without listener

2018-11-01 12:01:13.349 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-11-01 12:01:13.352 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1

2018-11-01 12:01:13.357 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RADIO_ERP1 with RORG RPS for FFF13FB0 payload F600FFF13FB02101FFFFFFFF4000

2018-11-01 12:01:15.411 [TRACE] [nal.transceiver.OpenOceanTransceiver] - Received Sync Byte

2018-11-01 12:01:15.415 [TRACE] [nal.transceiver.OpenOceanTransceiver] - >> Received header, data length 10 optional length 7 packet type 1

2018-11-01 12:01:15.423 [DEBUG] [nal.transceiver.OpenOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 01851D03 payload A59C7B000901851D038101FFFFFFFF4000

My config is:

raspberry Pi 3 B with openhabian
Actual Snapshot build openHAB 2.4.0~20181101034247-1 (Build #1408)
Openocean über Marketplace Binding installiert

Thing:

Bridge openocean:serialbridge:usb "OpenOcean Gateway" [ port="/dev/ttyUSB0" ] 
{
	Thing virtualRockerSwitch AABBDD09 "V1" @ "Kueche" senderIdOffset=48, sendingEEPId="F6_02_01_Virtual", broadcastMessages=true, suppressRepeating=false ] {Channels: Type virtualRockerswitch:virtualRockerswitchA [duration=300, switchMode="rockerSwitch"]} 
}

Item:

Switch v1 "v1" { channel="openocean:virtualRockerSwitch:usb:AABBDD09:virtualRockerswitchA" [profile="openocean:rockerswitch-from-on-off"]}

Sitemap:

sitemap Test_Enocean label="Test_Enocean"
{
	Frame label="Rolladen/Markisen Aktoren - Enocean"
	{
		Switch item=v1 			         
	}
}

Serial connection over rfc2217 does not support enableReceiveThreshold

As discussed here the rfc2217 connection does not support enableReceiveThreshold. Therefore the call to it should be handled silently in a try/catch block.

fruggy83 / openocean Goto Github PK

openocean's People

Contributors

Stargazers

Watchers

Forkers

openocean's Issues

Recommend Projects

Recommend Topics

Recommend Org