Honestly I don’t know with OH3. I tested it some time ago with OH2.5 and there it did not work (as PaperUI only offered the physical COM-Ports and would not allow any alternative entry for the Port). As it worked fine with a textual .things-file I kept this solution.
Unfortunately I am not happy with that. After a network interruption I have to restart the Z-Wave binding. Otherwise it won’t recover by itself.
The revocery was better with the previous solution I had with ser2net on a RPI (serving as “antenna”) and hub4com on my Windows OH server.
But now I anyhow changed again the setup and also run OH3 on the “Antenna”-RPI and connect to the items via the new Remote-OH-Binding (and no longer user RFC2217). The advantage with this new setup is that my Z-Wave networks can run through when I update the main OH instance and are immediately available after upgrade (no discovery, no initialization of devices etc.)
Yes, absolutely. That was also exactly my reason to use it. Especially as I need 3 ZWave antennas within my installation.
Many thanks Rafal,
happy to hear that. Even though I started this thread, I still have my remote serial
adaptors on a socat/ser2net combination after of some initial issues with rfc2217.
Because of the promising posts here I currently reconsider moving to rfc2217 while migration to openHAB3 (of course )
That’s very similar to my setup and mainly for the same reasons
Just additional Zigbee and Bluegiga (unused currently) and as said yet - with socat instead of the built-in rfc2217. It has been very stable for years! Admittedly, I dealt with some scripts to solve the re-connect in case the tcp connection got lost.
So from the stability perspective I could stay with socat. But rfc2217 would help me getting rid of some aditional scripts and systemd services and therefore slim down the setup
Therefore:
May I ask You too about your re-connect experiences when using rfc2217 ?
Hmm, I guess I have not been “lucky” enough to experience enough disconnections over the 6 months to notice any issues. I blame my networking. On the other hand, clearly the rfc2217 experience @vossivossi had was much poorer than mine—I am sorry to hear. I suppose it all depends on other aspects of the set-up.
At least in the released version of OH3, yes, it does. I have just done that in the z-wave thing GUI.
For it to work, on the remote system where the z-wave interface is connected, just make sure you define everything correctly in the /etc/ser2net.conf file, as per post 31 above ([SOLVED] [Zwave, Zigbee, ...] RFC2217 remote serial port HowTo? - #31 by mvbergen)
Has anyone gotten this to work with Zigbee? I’m testing OH3 in a docker container in a VM on my server and while the ZWave binding works great connecting to rfc2217://192.168.0.5:3001, the Zigbee binding configured for rfc2217://192.168.0.5:3002 gives me this in the debug log. The box at 192.168.0.5 is a PC that currently has my OH2 installation (OH2 service stopped) and has ser2net running with this config and I have verified with netstat that both ports 3001 and 3002 are open and listening
I have just done a couple of restarts of my Pi, which runs the ZStick and RFXCOM antennas, to see if and how rfc2217 ZWave recovers. I am pleased to say that in the current version (OH2.5_11) both ZWave and RFXCOM have recovered well. RFXCOM has always been rock-solid, so this is more of a confidence vote for ZWave over rfc2217. Log does not show ZWave losing the connection, but it shows the restart. RFXCOM shows both:
2021-01-23 17:14:38.370 [ERROR] [internal.handler.RFXComBridgeHandler] - Error occurred: End of stream
2021-01-23 17:15:25.093 [INFO ] [nternal.connector.RFXComTcpConnector] - Connecting to RFXCOM at openhab-relay:2002 over TCP/IP
2021-01-23 17:15:31.036 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2021-01-23 17:15:31.036 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
Other than simulating the disconnections, I have not experienced any issues with RFC2217 for many months now.
Can someone summarize the situation regarding OH3?
I am quite sure that restarting either the openhab machine as well as the ser2net machine causes a loss of connection between OH3 and a zwave stick. Am I correct?
My setup is so far:
OH 3.0.1 ReleaseBuild on a rpi4 running buster
Z-Wave Serial Controller configured to “rfc2217://remoteusb:3001” through the UI
ser2net on a rpi1 (hostname “remoteusb”) running buster with “3001:telnet:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT remctl” in my /etc/ser2net.conf
Rebooting one of these machines leeds to a connection loss that I can only heal by clicking onto “Synchronize Network” in the OH3 UI.
Is there a workaround or did I mix some things up or miss a detail?
@FrankR , you decided to post your question in a very old thread … certainly to reach out to others which have contributed/posted here and therefore - for sure - are interested in RFC2217-related stuff.
So you got the intended audience - perfectly fine with me
But you should have noticed that my initial questions had nothing to do with openHAB3 - and were answered/solved meanwhile.
So: It’s absolutely o.k. for me to proceed here with RFC2217 questions.
But if you feel the topics headline is not matching your issue, then it might be better opening a new thread instead and hoping for enough attention there to get it solved too.
The tcp connection to the remote Pi with the Zigbee stick connected got established but it seems, that openHAB cannot “open” that remote serial port yet…
Has anybody yet a working setup with rfc2217-connected Zigbee coordinator? Preferably Ember based? If so, would you share your ser2net.yaml and openHAB thing configuration for it?
EDIT:
Just found this:
Some change in the Zigbee was needed to make it work with rfc2217:
Since this has been merged back in October, it’s not included in my 3.1.0-RELEASE setup…
So: Somebody out there who had tried it on 3.2 already?
On rasperry pis, I use ser2net and socat to bring a remote aeotech zwave stick serial to my rpi running openhab, I’ve been noticing that occasionally openhab crashes in the RTXPortMonitor thread from time to time. I think maybe socat is restarting occasionally and causing it. In reading through this thread I’m not clear if I should try RFC2217 to access a remote zwave stick or not?
Thanks! I converted over to that and so far it seems to be working.
I did have to manually define the thing even in the new UI (OH 3.1).
If anyone has Zwave security make sure to grab the security key first before you delete the old device in the UI (if switching to a text file)
I’ll see how it goes…
It all depends on what the USB device server supports. It looks like the particular model you’ve linked to does not. It seems to depend on its own proprietary drivers for creating virtual serial ports to access the remote serial ports.
When using virtual serial ports for accessing remote devices, you add a device mapping for that port to the Docker container (similar to socat/ser2net).
)
