From e2877fac8324eb745e6b01ea0723a4fd73c9523f Mon Sep 17 00:00:00 2001 From: David Date: Sat, 3 Apr 2021 19:44:18 +0200 Subject: [PATCH] [enocean] Update README.md (#10443) --- bundles/org.openhab.binding.enocean/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bundles/org.openhab.binding.enocean/README.md b/bundles/org.openhab.binding.enocean/README.md index 38600c86d2..54c77c8ad7 100644 --- a/bundles/org.openhab.binding.enocean/README.md +++ b/bundles/org.openhab.binding.enocean/README.md @@ -14,7 +14,7 @@ First of all you have to configure an EnOcean transceiver (gateway). A directly connected USB300 can be auto discovered, an EnOceanPi has to be added manually to openHAB. Both gateways are represented by an _EnOcean gateway_ in openHAB. If you want to place the gateway for better reception apart from your openHAB server, you can forward its serial messages over TCP/IP (_ser2net_). -In this case you have to define the path to the gateway like this rfc2217://x.x.x.x:3001. +In this case you have to define the path to the gateway like this rfc2217://x.x.x.x:3001. When using _ser2net_ make sure to use _telnet_ instead of _raw_ in the _set2net_ config file. If everything is running fine you should see the _base id_ of your gateway in the properties of your bridge. Another way to improve sending and reception reliability is to setup a wired connection. -- 2.47.3