Add zwavejs2mqtt integration #34

New issue

Closed

opened 2022-07-05 01:38:41 +02:00 by blacklight · 0 comments

blacklight commented

2022-07-05 01:38:41 +02:00

Owner

python-openzwave is unmaintained and the codebase hasn't seen any new activity for the past two years.

This leaves many Z-Wave-related issues (e.g. #180, #182, #183) unaddressed, since the bugs are often caused by the underlying python-openzwave dependency.

zwave2mqtt is in a similar condition as python-openzwave, is currently unmaintained and its API is largely incomplete and mostly designed for the specific use case of HomeAssistant.

zwavejs2mqtt is probably the most mature project that implements a Z-Wave bridge and is still largely maintained.

Platypush should implement an integration with zwavejs2mqtt and decommission/deprecate the native python-openzwave integration once it's ready.

`python-openzwave` [is unmaintained](https://github.com/OpenZWave/python-openzwave/issues/198) and the codebase hasn't seen any new activity for the past two years. This leaves many Z-Wave-related issues (e.g. #180, #182, #183) unaddressed, since the bugs are often caused by the underlying `python-openzwave` dependency. [`zwave2mqtt`](https://github.com/OpenZWave/Zwave2Mqtt) is in a similar condition as python-openzwave, is currently unmaintained and its API is largely incomplete and mostly designed for the specific use case of HomeAssistant. [`zwavejs2mqtt`](https://github.com/zwave-js/zwavejs2mqtt) is probably the most mature project that implements a Z-Wave bridge and is still largely maintained. Platypush should implement an integration with `zwavejs2mqtt` and decommission/deprecate the native `python-openzwave` integration once it's ready.