This project contains Node-RED nodes that allow you to build Smart Home scenarios with your Zigbee devices connected to ZigBee2MQTT.
Many nodes are available right now, and there are still new node ideas that will be added in the near future. Here is a list of the currently available ones:
- generic-lamp
- send-messages
- override-nodes
- button-switch
- scene-in
- scene-selector
- ota-node
- bridge-log
- And many more for sensors and remotes...
Have a look at the getting started guide.. All you need are some already paired Zigbee lamps and an installed Node-RED. What are you waiting for? Find out now how easy it is to get started.
The documentation for the project is located in the docs
folder.
Join the Discord server for a more in depth support or problems that aren't metioned anywhere :)
That's easy! Feel free to post suggestions, adding documentation or add new features. Every support is welcome!
If you feel very generous and want to contribute with coffee, you sure can:
- Add support for Ikea Styrbar (E2001) remote control
- Setting brightnes to 0 did not turn it off. Now it will override the state to "OFF"
- Fixed Scenic Friend of Hue switch. Property names has changed between versions
- Bridge did not connect in newer z2m versions because z2m changed the format of 'bridge/state' from string to JSON.
- Shelly 2.5 did not connect to the broker, because it used an old configuration node.
- Shelly 2.5 node did not unsubscribe from the old channel with no full redeploy.
- Add mocha and first-unit test examples
- Add integration tests to test with a real MQTT broker
- Hosting the Node-RED UI under a different root path than
http://localhost:1880/
resulted in failing web requests to load the device list. For example, when the UI was set tohttp://localhost:1880/admin
or Node-RED was running as a Home Assistant plugin. - Fixed a bug where the configured device name gets deleted, when the device list couldn't be loaded. Further details in #105 and #119
Happy new year to all!
- @itupsk fixed the issue #114, where we forgot a null check on the ikea bugfix in the last release. Thanks a lot!
- Also fixed the same issue in hue, scenic and sonoff devices
- Documented additional settings for upgrading to mosquitto 2.0 in the getting started guide.
- Documented Mirek scale.
- Not set property on Ikea Remote device caused a complete Node-Red restart
- Not set property on Hue Remote device caused a complete Node-Red restart
- Preventive measure: Check action for empty string in scenic remote and sonnoff buttons
- Local node-red installation with nodejs 12 had a problem to load the node-red dependency. Removed it for now as it is only used for logging.
- Better handling for invalid MQTT messages from z2m. Sometimes a required/expected property is missing or empty which caused an error.
- Hue Dimmer switch crashed NodeRED because the power status with no action came with no action.
- Removed some unnecessary files from the package, reducing the size from 324 kB to 229 kB
- Removed vulnerable dependencies
- Updated and thinned out dependencies so the installation will be faster
- Dev feature: Cleaned up npm build scripts so there are no warnings, and they behave the same on Windows, Linux, and macOS.
- Two new example flows, from the getting started guide
- Documentation overview page
- Documented examples
- Show switch to manual button if the device-list request failed.
- Added
deviceName
to the ouput of the climate-sensor. Resolves #75 - Added
separateOuputs
option the the climate sensor. Resolves #75
You can find all the release notes at the Release-Page