FYI I have it running in docker (as I do OH, MQTT, mySQL). All on RPI5 with 64-bit Debian OS. Use about 1.6G RAM out of 4G.
This is my ZST39 Zstick compose. Changed type for upload
docker-compose.yml.txt (1.2 KB)
I donât think docker works (correctly) on freebsd, last time I checked. The concept of docker is similar to freebsd jail. I have OH and postgresql (used by other things too) on the same host in different jails. There are many more jails on the host (rack server).
I figured your reference to âjailâ meant some sort of container, but am not familiar with it myself. Anyway just thought I should mention it.
It did one install of zui via npm or yarn but they issue new versions all the time, so that wasnât going to work for me either.
It is freebsd jail I was referring to. See the nice article:
https://freebsdfoundation.org/freebsd-project/resources/introduction-to-freebsd-jails/
I heard news of OCI container support was added to freebsd, with podman. Never tried it myself. Does it still use that user space proxy for networking?
Thatâs my thought exactly.
Beyond my knowledge.
- Here is the USB section of the OH docker documents. Docker | openHAB
- When I use Docker into a WSL environment (for OH testing only). I use usbipd to pass the Zstick in WSL.
- Here is a forum post on podman maybe some details there;
I finished porting zwave-js-ui, the request is in freebsd bugzilla. More runtime testing with Mosquitto, but it seems to work for now.
Interestingly, zwave-js-ui does not need ser2net workaround. It is most likely that S2 security is the cause for all the problems.
I have just come across this discussion
Ironically I did search in the forum, and saw this
before getting that same transceiver. The rest is history. Since zwave-js-ui
is mentioned in the discussion, is it sensible to add the reference to ZWave Binding?
I had a PR reviewed and approved by the OH ZW developer in Nov 2023 for the OH 4.1 release that allows supports for 700 and 800 chip controllers with the exception about Long Range noted by me 2 posts above the one you referenced. Before then (like the other thread you referenced) they werenât supported. (You were the first person to have a problem that couldnât be explained 
, but nothing in the logs pointed to the binding itself.) It could be security or some sort of ser2net error checking that sends part of the messages over.
I actually started using ZUI earlier in Apr 2023 because it had 700/800 chip support at that time. They recently added the 800 LR option, although I donât believe LR is permitted in Europe, only North America. I think with the guide, improvements in the OH HA config handling (by others) and the OH websocket development work (by others), most OH Zwave users will transition to ZUI over time.
ZUI and Zwave-js are supported financially by HA. The OH foundation has limits of what they can financially support. All OH development (and forum support 
) is volunteer. The ZW developer has a full-time job and lots of international travel. I originally started with OH because of the open-source ZW capability and nothing was comparable 5 years ago, but with the financial support ZUI is a better option now. In 5 more years with Matter, who knows?
Hence I was asking if ZUI should be mentioned in zwave binding doc. At least for me, ZUI works and the zwave binding had problems (breaking problems), even without enabling security. The band used by LR option is indeed unavailable in the EU version, but there is no hardware difference.
I had to use ser2net because inputing /dev/cuaU0 as serial port did not give me an online bridge. Not unlike whatâs described in
It is not permission. By adding the user to dialer group, the user should be able to⊠dial. Like ZUI did.
I will test the zigbee binding in the coming days and see if that works, now that with ZUI, zwave devices are functioning corrrctly. If not, zigbee2mqtt has been ported, so that is an option. I will try to fix up any problem along the way.
Thanks for all the hard work, OH community.
Update on zigbee. I can confirm serial port experienced similar issues. Only way is to use zigbee2mqtt like with zwave-ui-js. It is likely the serial library used by openhab being incompatible.
HA discovery with zigbee2mqtt is great, things showed up in inbox and it was possible to add things that way.
Only question I have is about density. Openhab uses SI units, which is great. Density is displayed in kg*m^-3, I changed state description to use ug*m^-3.
In graphs
Looks like the (very) small value is rounded to 0. Is there a way to multiply the value by, for example 10^9?
Maybe. However, I recently set up a remote Z-stick on an Rpi3 using usbipd since OH5 (64bit OS needed) wonât fit in a container on the Rpi3. It has worked so far but had an issue when I rebooted the RPi3 to move it across the house. Needed to restart my OH container on the client (Rpi4).
Anyway, before you restart OH, are you restarting ser2net? It might be needed to clear the old connection. On the OH side the lock is released when OH is stopped, but maybe something is left on the ser2net side of things. This could explain the scrambled messages. Just a thought