v0.3.0

What’s changed

Upgrade to the latest and greatest! Additionally, @raman325 added the possibility to open up the Z-Wave JS Server port for direct access. This can be useful when, for example, testing or using Z-Wave JS Server on a secondary system.

✨ New features

• Optionally expose WS port @raman325 (#15)

⬆️ Dependency updates

• ⬆️ Update OpenZWave database to 76408b1623f966815c98a4b5ce581 @frenck (#18)
• ⬆️ Upgrades ZwaveJS2Mqtt to v1.0.5 @frenck (#17)
• ⬆️ Bump actionshub/markdownlint from 2.0.0 to 2.0.2 @dependabot (#21)
• ⬆️ Bump actions/cache from v2.1.3 to v2.1.4 @dependabot (#20)

v0.2.3

What’s changed

⬆️ Dependency updates

• Bump frenck/action-yamllint from v1.0.2 to v1.1 @dependabot (#12)
• ⬆️ Upgrades ZwaveJS2Mqtt to v1.0.3 @frenck (#13)

v0.2.2

What’s changed

⬆️ Dependency updates

• ⬆️ Upgrades ZwaveJS2Mqtt to v1.0.2 @frenck (#9)
• ⬆️ Update ZwaveJS device database to b62505309ef31c4717d321a @frenck (#10)
• Upgrade add-on base image to 9.1.2 @frenck (#11)

v0.2.1

What’s changed

🐛 Bug fixes

• Ensure HA Discovery awaits for Z-Wave JS Server @frenck (#5)

⬆️ Dependency updates

• Upgrade zwavejs2mqtt to v1.0.1 @frenck (#6)
• Upgrade Z-Wave JS database to 93d505e97daa7649d0d4af16d0145b52cbdcc141 @frenck (#7)

v0.2.0

What’s changed

The add-on will now create a default configuration on the first run, pre-configured as much as possible for use with Home Assistant.
Additionally, if the Mosquitto add-on is found, it will configure that too.

✨ New features

• Initiate default configuration on first run @frenck (#3)

v0.1.0

What’s changed

The initial release of the Z-Wave JS to MQTT add-on 🎉

✨ New features

• Add initial add-on code @frenck (#1)

📚 Documentation

• Extend setup instructions @frenck (#2)