Merge zigbee.mqtt plugin/backend and zwave.mqtt plugin/backend #4

New Issue

Closed

opened 2022-07-05 01:38:38 +02:00 by blacklight · 1 comment

blacklight commented

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

Owner

Since this is no longer the case (Platypush now provides the RunnablePlugin object), it makes sense to simplify the configuration and the architecture and merge the plugin and the backend.

The Zigbee and Z-Wave integrations currently require two tightly coupled pieces (the plugin and the backend) in order to work properly, for historical reasons (traditionally, Platypush plugins were stateless, while backends were the only way to get a listener to run in the background). Since this is no longer the case (Platypush now provides the `RunnablePlugin` object), it makes sense to simplify the configuration and the architecture and merge the plugin and the backend.

blacklight added the

architecture

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

blacklight self-assigned this 2022-07-05 01:38:38 +02:00

blacklight added this to the core project 2022-07-13 10:34:23 +02:00

blacklight commented

2023-02-22 11:21:49 +01:00

Author

Owner

Implemented on the generic_entities_support branch (relevant commits for zigbee.mqtt and zwave.mqtt).

Implemented on the [`generic_entities_support`](https://git.platypush.tech/platypush/platypush/src/branch/29-generic-entities-support) branch (relevant commits for [`zigbee.mqtt`](https://git.platypush.tech/platypush/platypush/commit/341e749d23ce172e801f183ef0a28dbb489b0ef6) and [`zwave.mqtt`](https://git.platypush.tech/platypush/platypush/commit/8aff1819564a55bbf540f8f6286673c01294de8b)).

blacklight closed this issue

2023-02-22 11:21:52 +01:00