@rendgeor
Hi,
my openhab runs on Linux and the WMS stick is attached to a raspberry (via TCP/IP). A special driver for this WMS stick is not necessary.
edit:
btw - now, the network key will be determined and stored as a property
Hi, I connected the wms stick (1002775) to my raspberry 3 with a openhab instance (2.4.0). I copied the jar from https://github.com/zeezee300/openwms to /usr/share/openhab2/addons (owner openhab:openhabian).
feature:install openhab-transport-serial is installed.
I get the following error in the log
2019-07-21 20:29:17.230 [ERROR] [org.openhab.binding.openwms ] - bundle org.openhab.binding.openwms:2.4.0.201905131030 (212)[org.openhab.binding.openwms.discovery(12)] : Constructor with 0 argume$ 2019-07-21 20:29:17.250 [ERROR] [org.openhab.binding.openwms ] - bundle org.openhab.binding.openwms:2.4.0.201905131030 (212)[org.openhab.binding.openwms.discovery(12)] : Error during instantiati$ 2019-07-21 20:29:20.459 [ERROR] [org.openhab.binding.openwms ] - bundle org.openhab.binding.openwms:2.4.0.201905131030 (212)[org.openhab.binding.openwms.discovery(12)] : Error during instantiati$ 2019-07-21 20:29:20.484 [WARN ] [org.openhab.binding.openwms ] - FrameworkEvent WARNING - org.openhab.binding.openwms org.osgi.framework.ServiceException: org.apache.felix.scr.impl.manager.SingleComponentManager.getService() returned a null service object at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:232) ~[?:?] at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111) ~[?:?]
The remote control is trained with the actor.
Can anybody help me why I canât scan the new thing? Thanks
I try it again today to connect with the WMS USB Stick. Iâm using openHAB 2.4.0-1 on a Raspberry 3 with Linux openHABianPi 4.19.57. The stick is connected on the same machine with openhabian and I run the command
sudo socat tcp-listen:4001,fork,keepalive,nodelay,reuseaddr /dev/ttyUSB0,nonblock,raw
I get the info in log:
[INFO ] [penwms.connector.OpenWMSTcpConnector] - Connecting to OpenWMS USB at 127.0.0.1:4001 over TCP/IP
No error occurs.
The library of openwms is in this location:
256029 4 drwxrwxr-x+ 2 openhab openhabian 4096 Jul 21 20:10 .
256022 4 drwxr-xr-x 4 openhab openhab 4096 Jul 21 19:05 ..
258634 177744 -rw-rw-r-- 1 openhab openhabian 182006216 Dez 17 2018 openhab-addons-2.4.0.kar
258705 48 -rwxrwxrwx 1 openhab openhabian 49120 Jul 21 20:10 org.openhab.binding.openwms_2.4.0.201905131030.jar
256030 4 -rw-rw-r-- 1 openhab openhabian 70 Dez 17 2018 README
[22:16:52] openhabian@openHABianPi:/usr/share/openhab2/addons$
But PaperUI show me the status OFFLINE. No scan with remote control (Warema Basic, 1002953) is possible.
I try it with a direct connection via USB with the same problem (OFFLINE). The stick works with Warema Studio or toolkit.@rainer300 can you support me plz? thanks
Hi hj8i5,
if the stick is directly connected to the Raspberry on which openhab runs, no bridge over TCP/IP (socat) is needed.
Please try to use the thing âOpenWMS WAREMA WMS-Stick Transceiverâ and enter the port directly (e.g. /dev/ttyS0).
Hi @rainer300,
I try both variants with the same problem. I create new Thing âOpenWMS WAREMA WMS-Stick Transceiverâ and select the correct port /dev/ttyUSB0 which I a found in the /var/log/messages.
Jul 31 13:26:40 openHABianPi kernel: [ 5.221609] usbserial: USB Serial support registered for FTDI USB Serial Device
Jul 31 13:26:40 openHABianPi kernel: [ 5.222161] usb 1-1.3: Detected FT232RL
Jul 31 13:26:40 openHABianPi kernel: [ 5.223117] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
In Paper UI the device is marked as OFFLINE and I have the following log entry.
2019-07-31 14:11:39.595 [ERROR] [openwms.handler.OpenWMSBridgeHandler] - Connection to OpenWMS transceiver failed
gnu.io.UnsupportedCommOperationException: Invalid Parameter
at gnu.io.RXTXPort.setSerialPortParams(RXTXPort.java:212) ~[?:?]
at org.openhab.binding.openwms.connector.OpenWMSSerialConnector.connect(OpenWMSSerialConnector.java:46) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.connect(OpenWMSBridgeHandler.java:110) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.lambda$0(OpenWMSBridgeHandler.java:87) ~[?:?]
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) [?:?]
I try to run openhabian-config -> âApply Improvementsâ -> âFix Permissionsâ but without success. I thought that might be the problem.
Do you have further ideas what I can do?
Thanks 
Hi hj8i5
maybe you can try the following:
Go to karaf and type
feature:install openhab-transport-serial
Hi,
Iâm trying to install https://github.com/zeezee300/openwms
System: openhabian, openhab 2.5.0 final.
I copied org.openhab.binding.openwms-2.5.0-SNAPSHOT.jar into /usr/share/openhab2/addons, but the binding is not found.
I have another binding (somfycul, 2.4.0) in this directory which works without problems. Same permissions on both.
Nothing at all in log:tail. It seems the addon is simply not loaded.
Any idea why the binding is not found?
Update: I tried the 2.4 binding, but it fails during initialization.
Constructor with 0 arguments not found. Component will fail.
Error during instantiation of the implementation object: Constructor not found.
The 2.5 binding is much larger than the 2.4 (845909 vs 16447bytes).
Any reason for this?
Update 2: it finally appeared and I tried to add the OpenWMS WAREMA WMS-Stick Transceiver (port /dev/ttyUSB0). But it is âuninitializedâ.
Log says:
Exception during HTTP PUT request for update config at âthings/openwms:bridge:66e6dfdb/configâ
java.lang.IllegalStateException: Thing with UID openwms:bridge:66e6dfdb has no handler attached.
at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:95) ~[?:?]
at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:438) [bundleFile:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_222]
tx,
Jean-Marc
Still the same problem.
Iâm running Openhab 2.5 and the org.openhab.binding.openwms-2.5.0-SNAPSHOT.jar
When I try to add the Warema WMS-Stick Transceiver and configure the port (/dev/ttyUSB2 in my case) I get the same error than @hj8i5 above: UnsupportedCommOperationException: Invalid Parameter
2020-01-09 22:56:35.318 [ERROR] [openwms.handler.OpenWMSBridgeHandler] - Connection to OpenWMS transceiver failed
gnu.io.UnsupportedCommOperationException: Invalid Parameter
at gnu.io.RXTXPort.setSerialPortParams(RXTXPort.java:212) ~[?:?]
at org.openhab.binding.openwms.connector.OpenWMSSerialConnector.connect(OpenWMSSerialConnector.java:46) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.connect(OpenWMSBridgeHandler.java:110) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.lambda$0(OpenWMSBridgeHandler.java:87) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_222]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]
Looking at the code, this seems to be the line with the error:
serialPort.setSerialPortParams(128000, SerialPort.DATABITS_8, SerialPort.STOPBITS_1, SerialPort.PARITY_NONE);
I have a WAREMA 1002775 WMS Stick (WAREMA WMS Stick (Transreceiver mit USB-Schnittstelle)).
Is this the correct stick? Or is there another one?
@rainer300 any idea?
Hi,
the WMS-Stick should be correkct - i have the same and it works as it should work.
maybe you can try the following:
(1) Go to karaf and type
feature:install openhab-transport-serial
(2) install the new compiled version (https://github.com/zeezee300/openwms/blob/master/org.openhab.binding.openwms-2.5.0.jar)
Hi rainer300,
first of all, let my say thanks for your hard work on this binding. I am really interested in to get this working.
Unfortunately, I have the same issue as described. I am using openHab 2.5 on a Pi and your latest binding (org.openhab.binding.openwms-2.5.0.jar). The serial driver is installed
( feature:install openhab-transport-serial ) and I have also removed other USB devices to avoid influences. The WMS stick is connected and working:
Jan 11 14:13:41 openhab kernel: [ 5.135413] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
Jan 11 14:13:41 openhab kernel: [ 5.135585] usb 1-1.4: Detected FT232RL
Jan 11 14:13:41 openhab kernel: [ 5.136802] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
I am getting the same error message:
2020-01-11 14:26:09.873 [ERROR] [openwms.handler.OpenWMSBridgeHandler] - Connection to OpenWMS transceiver failed - Exception
gnu.io.UnsupportedCommOperationException: Invalid Parameter
at gnu.io.RXTXPort.setSerialPortParams(RXTXPort.java:212) ~[?:?]
at org.openhab.binding.openwms.connector.OpenWMSSerialConnector.connect(OpenWMSSerialConnector.java:46) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.connect(OpenWMSBridgeHandler.java:121) ~[?:?]
at org.openhab.binding.openwms.handler.OpenWMSBridgeHandler.lambda$0(OpenWMSBridgeHandler.java:87) ~[?:?]
It looks like a problem with the serial communication. Did this work on your system or did you always communicate over TCP? Did you have a hint for us to get it working?
Thanks
I have made some improvements; the new version can be downloaded at github.
Hi Rainer,
i´ve tried this binding again on OH2.5. Now I get no Errors anymore but it shows
2020-02-09 23:21:08.430 [INFO ] [wms.connector.OpenWMSSerialConnector] - Connecting to OpenWMS USB at /dev/ttyUSB0 every minute and OpenWMS WAREMA WMS-Stick Transceiver still stays offline.
I´ve tried feature:install openhab-transport-serial in karaf and fix permissions without any change.
Do you have any idea what i can do else?
thx
`
Hello folks,
i have today install a new version from openhab 2.5.2 with Binding for Warema WMS Stick.
dmesg say:
1775.225750] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 1775.225771] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1775.225781] usb 1-1.4: Product: FT232R USB UART
[ 1775.225790] usb 1-1.4: Manufacturer: FTDI
[ 1775.225800] usb 1-1.4: SerialNumber: A908E018
[ 1936.305829] usb 1-1.4: USB disconnect, device number 5
[ 1945.817951] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 1945.975457] usb 1-1.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 1945.975471] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1945.975481] usb 1-1.3: Product: FT232R USB UART
[ 1945.975490] usb 1-1.3: Manufacturer: FTDI
[ 1945.975499] usb 1-1.3: SerialNumber: A908E018
[ 2527.921702] usb 1-1.3: USB disconnect, device number 6
[ 5363.929394] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[ 5364.086962] usb 1-1.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 5364.086976] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5364.086986] usb 1-1.3: Product: FT232R USB UART
[ 5364.086995] usb 1-1.3: Manufacturer: FTDI
[ 5364.087004] usb 1-1.3: SerialNumber: A908E018
Step1:
I have configure the OpenWMS Binding over
OpenWMS WAREMA WMS-Stick Transceiver
or
OpenWMS WAREMA WMS-Stick Transceiver over TCP/IP
Openhab has no connect with USB Stick.
Step 2:
I enter
sudo socat tcp-listen:4001,fork,keepalive,nodelay,reuseaddr /dev/ttyAMA0,nonblock,raw
open a telnet session:
telnet localhost 4001
enter in the console: {G} for get any answer from USB Stick.
No answer
Enter M%174DE4 in the console. No answer from Stick.
In WAREMA WMS Studio PRO has connect to USB Stick.
Iâm confused 
Can somebody help me.
2020-03-01 12:53:56.851 [INFO ] [penwms.connector.OpenWMSTcpConnector] - Connecting to OpenWMS USB at 127.0.0.1:4001 over TCP/IP
==> /var/log/openhab2/events.log <==
2020-03-01 12:53:56.810 [hingStatusInfoChangedEvent] - âopenwms:tcpbridge:996bd085â changed from UNINITIALIZED to INITIALIZING
2020-03-01 12:53:56.859 [hingStatusInfoChangedEvent] - âopenwms:tcpbridge:996bd085â changed from INITIALIZING to OFFLINE
I have the same problem as @Sascha_Jostock and @klausharald.
The USB stick is brand new, article number 1002775 Rev. D
Tried sending the â{G}â command via minicom, to no avail. Will soon check with WMS Studio to make sure the stick works fine.
The stick works with WMS Studio and with the javascript plugin for IoBroker.
port opened
sending {G} debug
received message: gWMS USB-Stick debug
{"type":"stickType","payload":{"name":"WMS USB-Stick"}} debug
received expected answer: gWMS USB-Stick debug
sending {V} debug
received message: v37605107 debug
{"type":"stickVersion","payload":{"version":"37605107"}} debug
received expected answer: v debug
Stick Version: v37605107
sending {K4010E99EB48AB0AEDBB5682857D933D294D} debug
received message: a debug
{"type":"ack"} debug
received expected answer: a debug
sending {M%17F228} debug
received expected answer: a debug
sending {R04FFFFFF7020F22802} debug
received expected answer: a debug
sending {R04FFFFFF7020F22802} debug
received message: r4FE70C50600F96021100 debug
{"type":"message","payload":{"src":"4FE70C","type":"switchChannelRequest","messagePayload":{"panId":"0F96","deviceType":"02","channel":17}}} debug
received switchChannelRequest, switching channel to 17 debug
sending {M%17F228} debug
received message: a debug
Trying to manually interact with the stick using Minicom or any other serial console emulator, I canât find any configuration that allows me to send commands to the stick.
However, using the serialport javascript package available via NPM (and the serialport-terminal emulator), I can access the stick:
$ ./node_modules/.bin/serialport-terminal -p /dev/ttyUSB0 -b 125000
Opening serial port: /dev/ttyUSB0 echo: true
{G}{gWMS USB-Stick}
{V}{v37605107 }
The latest version of the OpenHAB binding, as downloaded from GitHub, canât properly initialize the usb stick. Relevant debug logs:
2020-03-24 16:21:05.167 [INFO ] [wms.connector.OpenWMSSerialConnector] - Connecting to OpenWMS USB at /dev/ttyUSB0
2020-03-24 16:21:05.171 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Serial port #### Jetzt gehts los
2020-03-24 16:21:05.190 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Serial port event listener started
2020-03-24 16:21:05.194 [DEBUG] [penwms.connector.OpenWMSStreamReader] - Data listener started
2020-03-24 16:21:05.497 [DEBUG] [openwms.handler.OpenWMSBridgeHandler] - Try to send to controller
2020-03-24 16:22:06.504 [DEBUG] [openwms.handler.OpenWMSBridgeHandler] - Checking OpenWMS transceiver connection, thing status should be = OFFLINE
2020-03-24 16:22:06.509 [DEBUG] [openwms.handler.OpenWMSBridgeHandler] - Connecting to OpenWMS transceiver
2020-03-24 16:22:06.514 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Disconnecting
2020-03-24 16:22:06.548 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Serial port event listener stopped
2020-03-24 16:22:06.552 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Interrupt serial listener
2020-03-24 16:22:06.556 [DEBUG] [penwms.connector.OpenWMSStreamReader] - Data listener stopped
2020-03-24 16:22:06.561 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Close serial out stream
2020-03-24 16:22:06.565 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Close serial in stream
2020-03-24 16:22:06.570 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Close serial port
2020-03-24 16:22:06.578 [DEBUG] [wms.connector.OpenWMSSerialConnector] - Closed
2020-03-24 16:22:06.582 [INFO ] [wms.connector.OpenWMSSerialConnector] - Connecting to OpenWMS USB at /dev/ttyUSB0
@rainer300: does the latest JAR reflects the latest published code, or are there unpublished changes?
1 Like
I have the same problem as @Sascha_Jostock and klausharald and giuseppeiannello
This is what I have done:
Raspberry openHAB 2 Stable 2.5.3 Image from https://www.openhab.org/download/
flashed with BaleaEtcher under Windows 10 on 8GB SD card.
SD card inserted, WMS stick plugged in, LAN, router and power connected and waited for 17 hours until the installation and subsequent update were safely completed.
Afterwards logged in with Putty:
User and PW: openhabian
Latest stable version 2.5.3-1 is on and running.
From "https://github.com/zeezee300/openwms"
âorg.openhab.binding.openwms-2.5.0 SNAPSHOT.jarâ and uploaded it to the directory
/usr/share/openhab2/addons
copied with Filezilla.
Raspberry restarted with âsudo rebootâ
After the restart with Putty logged in on openhab and
openhab-cli console
(PW habopen)
feature:install openhab-transport serial
(takes a half minute)
logout
sudo reboot
executed.
For the first time on "http://openhab:8080/start/index"
logged in and selected Standard Recommended Setup.
Waited until Paper UI is selectable.
See picture here: "https://abload.de/img/wmsbindingeojp9.jpg" (only 2 Pictures for new forum-users allowed)
The stick has been successfully tested with the network under Windows 10 with WMS-Studio-Pro. It controls the external blind perfectly.
My Warema hardware:
WMS Wandsender basic
WMS Stick
WMS Zwischenstecker fĂźr Raffstore
WMS Wetterstation Plus
"First of all you have to configure an Warema USB-Stick. This device has to be added manually to OpenHab and is represented by an OpenWMS bridge.
You just have to set the right serial port. If everything is running fine you should see the Current firmware version: of your USB-Stick in the properties of your bridge."
In the inbox âSearch for thingsâ, OpenWMS Binding, WMS Stick Transceiver USB selected and â/dev/ttyUSB0â selected and confirmed with a click on the blue tick.
The result is as depressing as the first time I tried it. The stick has the status âOFFLINEâ.
The PANID is unknown to me, so I cannot configure it manually.
Automatic configuration according to these instructions:
"Discovery (search for new devices with the remote control)
(Rainer Tested with: WAREMA WMS Handsender basis (ArtNr. 1002953))
In my opinion technically identical with my WMS wall transmitter basic (ArtNr. 1002881)
The devices could be automatically discovered by pressing the scan-button of your warema remote control and put in the Inbox (PAPER UI) or may be configured manually.
Note: However, it is a prerequisite that the devices have already been trained in the warema network and are known.
After the bridge is configured in openhab, wake up the remote control (simply press any button on the remote control). Then press the âLearnâ button in the battery compartment for about 5 seconds until the green control lamp lights up.
You have to wait a few seconds until the green light (the right one on the front of the remote control) stops blinking and turns into red or orange. During the first scan the WMS network ID is determined and the LED light turns red. Then the red stop button must be pressed (this is the round button between the high and low buttons).
The USB-Stick should receives scan response messages from any sensor or actuator. You can find the new devices put in the Inbox (openhab PAPER UI). You can also find the current WMS network key as a property of the WMS-Stick transceiver"
âLâ button on the rear panel pressed for more than 5 seconds. âLâ lamp lights up.
Transmit LED on front:
2 x short green, short pause, 7 x green flashes, green 2 sec, 3 x green flashes, green 2 sec, 3 x green flashes, orange remains on
No red lamp as in Rainerâs description, but still âStopâ pressed in the middle of the remote control. No reaction. Exit the search mode by pressing the âLâ button again.
Paper UI Inbox remains empty. WMS Stick remains âOFFLINEâ.
The LOG viewer shows for the stick:
2020-03-27 15:18:11.533 [hingStatusInfoChangedEvent] - âopenwms:bridge:039b8524â changed from UNINITIALIZED to INITIALIZING
2020-03-27 15:18:11.589 [hingStatusInfoChangedEvent] - âopenwms:bridge:039b8524â changed from INITIALIZING to OFFLINE
2020-03-27 15:18:11.678 [INFO ] [wms.connector.OpenWMSSerialConnector] - Connecting to OpenWMS USB at /dev/ttyUSB0
I donât know what else to do. This was my second attempt at a complete fresh installation.
Unfortunately again without success.
First problem: Status of the stick âOFFLINEâ. Reason? No idea.
2nd problem: When searching with the wall transmitter no new device with âREDâ is found. Possible cause:
The wall transmitter has already become familar with the stick by WMS Studio Pro under Windows.
What is our fault?
Without @rainer300 nothing works here anymore!
Just to add more details: Iâve managed to make the binding work by configuring it, then launching the program available at https://www.npmjs.com/package/warema-wms-venetian-blinds#example-getting-wms-network-parameters
Looks like the serial port is not properly opened by the binding, but once that JS thingy opens the port, everything works as expected.
Auto-detection of the devices works even with a wall remote (wake it with any button, long-press the learn button, new devices land in the inbox).
@pet2001 I donât know why but sometimes the serial port is not initialized correctly. For testing purposes I have provided a small java program to fix this problem as a workaround:
1.) download serialport.jar
2.) copy it where you want (f.e. /opt/warema) and make it excecutable
3.) excecute it with your device as an argument (f.e./dev/ttyUSB2):
java -jar /opt/warema/serialport.jar /dev/ttyUSB2
This script should open the port and everything should work as expected until the wms-stick is unpluged 
@rainer300 Great work! My Stick ist ttyUSB0 so I used
java -jar /opt/warema/serialport.jar /dev/ttyUSB0
and the stick gets ONLINE Tschakka!!
Thatâs a big success. The serialport.jar has to be executed after every reboot to get the stick ONLINE again after reboot. No big problem.
But I get stucked in finding the WMS-stick and reading the PANID/KEY from the wall remote.
When pushing the L-Button on the wall remote it ends in orange and not red.
After manually adding the things âweather sensorâ and âblind actuatorâ with the correct PANID and DEVICEID in Hex (read with iobroker and pman script) they are OFFLINE and not connected with the WMS-Stick.
I do not know where to enter the Network Key.
Any idea?