Missed this on the first look. 800-series are supported in the OH zwave binding starting with 4.1.0. I tested the OH4.1 zwave binding with a Zooz zst39. The only caveat is that the LR mode is not supported, but the zst39 will work fine in “classic” zwave. FWIW this is the same situation with Zwave-js-ui at this moment. Something else I wrote;
Starting with OH4.1M4 700 and 800 chip Zsticks should work in the OH ZWave. The biggest beneficiary will be the new OH user as the 500 chip controllers are hard to find and cost more. For current OH users with 500 chip controllers, observed gains from 700/800 controllers may be modest. The top speed of 100KB/sec is the same. There may be a few more devices are in direct communication with the controller and the chip processes messages a bit faster. Your results may vary.
The 800 chip “Long Range” capability is misleading. Long Range Zsticks have dual frequency ranges. One set of frequencies are for “classic” Zwave and have the same range as 700 chip (and 500 chip) controllers. Long Range uses a separate set of frequencies with a spread spectrum technology that allows for higher power. I found this on the Silabs website and the summary below is extracted from my understanding. To achieve the higher power Long Range capability, the device must be included with the following requirements (these could change over time?):
1) Long Range nodes have 12 bit addresses (vs classic 8 bit) starting at 256. This would require a major refactoring on the binding.
2) Long Range inclusion requires Smart Start. This is not currently coded into the OH Zwave binding.
3) Long Range inclusion requires S2 security. The OH Zwave binding currently only supports S0 security.
4) Long Range is currently only permitted in North America.
5) Long Range nodes only ‘talk’ to the controller (no mesh) so the binding needs to relay messages to other nodes (No Association Group messages).
6) Without all the Long Range requirements nodes will automatically be included in classic mode.