diff --git a/static/pages/Transform-a-RaspberryPi-into-a-universal-Zigbee-and-Z-Wave-bridge.md b/static/pages/Transform-a-RaspberryPi-into-a-universal-Zigbee-and-Z-Wave-bridge.md
index e06ecb6..a129ea2 100644
--- a/static/pages/Transform-a-RaspberryPi-into-a-universal-Zigbee-and-Z-Wave-bridge.md
+++ b/static/pages/Transform-a-RaspberryPi-into-a-universal-Zigbee-and-Z-Wave-bridge.md
@@ -370,3 +370,25 @@ def on_white_bulb_on(event, **context):
 ```
 
 You should now have all the ingredients to build your custom IoT networks and ditch those bridges for good!
+
+### April 2021 note
+
+The native Z-Wave integration provided by Platypush will slowly get phased out in favour of the new `zwave.mqtt`
+integration (see [issue #186](https://git.platypush.tech/platypush/platypush/-/issues/186)).
+
+The reason is that the library used by the native Z-Wave integration (`python-openzwave`) is currently
+[unmaintained](https://github.com/OpenZWave/python-openzwave/issues/198) and its last commit was around the
+beginning of 2019. Many bugs keep stashing up on the library because of progress made on the OpenZWave framework
+while the library doesn't get updated, and some Platypush methods may be broken as of now.
+
+Instead, it is now advised to set up a [`zwavejs2mqtt`](https://github.com/zwave-js/zwavejs2mqtt) gateway to
+that uses an MQTT broker to dispatch events and messages (follow the installation instructions
+[here](https://zwave-js.github.io/zwavejs2mqtt/#/getting-started/quick-start)).
+
+After installing the gateway, you can configure the `zwave.mqtt`
+[plugin](https://docs.platypush.tech/platypush/plugins/zwave.mqtt.html) and
+[backend](https://docs.platypush.tech/platypush/backend/zwave.mqtt.html) on Platypush side to enable the integration.
+The format of the requests and responses is the same and the UI is also cross-compatible, although zwavejs2mqtt 
+doesn't implement some advanced features provided by OpenZWave (such as low-level controller commands or e.g. rename
+values and scenes).
+