Zwave remote connection rfc2217 vs tcp (raw). running zwave-js-ui with zwave binding

If anyone has run the zwave binding concurrently with zwave-js-ui against remote ser2net I would be interested to know the configuration. The preferred way to run remote OH zwave binding seems to use rfc2217 which requires a ser2net like this:

10002:telnet:0:/dev/zstick:115200 8DATABITS NONE 1STOPBIT max-connections=3 remctl

Unfortunately zwave-js-ui operates on raw socket so the configuration is like:

10001:raw:600:/dev/zstick:115200 8DATABITS NONE 1STOPBIT max-connections=3

If anyone has figured out the edge case to get both running reliably I am all ears. For the moment I switched the zwave binding back to using a local device created by socat so that I can use the raw setting for both. This is OK for reads but writes from zwave-js-ui seem to fail when I use the same listener. I’m also expecting OH to crash at some point (as I recall this was a problem when using socat to represent the remote device).