Home Assistant Community Add-on: Z-Wave to MQTT

[wrkn]

Thanks! I’ll wait for that fix.

Also, I just noticed when playing around with it I couldn’t get my dongle’s USB by-id path working, it would only take the tty path. I don’t want to rely on that because sometimes after reboots or upgrades my device tty paths change and it’s a pain to manage.

[frenck (Franck Nijhof)]

Release v0.2.0

Full Changelog

This release is a maintenance release, upgrading all parts of the add-on to the latest and greatest.

Changes

• Upgrades base image to v3.1.2
• Updated zwave2mqtt to version 1.1.2 (#4)
• Maintaince -> Maintenance
• Adds FUNDING.yml
• Upgrades add-on base image to v4.0.1
• Upgrades git to 2.22.0-r0
• Upgrades linux-headers to 4.19.36-r0
• Upgrades npm to 10.16.0-r0
• Upgrades yarn to 1.16.0-r0
• Upgrades nodejs to 10.16.0-r0
• Upgrades eudev to 3.2.8-r0
• Upgrades nginx to 1.16.0-r2
• Upgrades openssl to 1.1.1c-r0
• Adds links to upstream project

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

[Quexser]

Thank you! I have been struggling trying to figure out how to get this set up.

[gzeel]

I’ve configured zwave2mqtt to make a connection to my MQTT broker. However, when I want to switch on a (neo coolcam) zwave plug at the topic zwave/neo_plug/switch/set (Where the Switch value is mapped to a switch topic) nothing is happening.

With mosquitto_sub I can see that zwave/neo_plug/switch topic is changed to true/false when I flip the Switch value at the zwave2mqtt node settings.
When I publish a ‘true’ message at zwave/neo_plug/switch/set nothing is changed in the topic…
I do have to use /set at a topic to write to it right?

[selfhostedhome (Zack)]

I wrote up my process of moving devices over to ZWave2MQTT on my blog if anyone finds it useful.

I think there are still a few warts but overall I was able to get my devices moved over. Looking forward to where this project goes.

[silfa718]

Try the solution here to add MQTT Dimmers correctly: Mqtt value template

[frenck (Franck Nijhof)]

Release v0.3.0

Full Changelog

This release ships with Zwave2Mqtt v2.0.1, which brings Home Assistant auto-discovery via MQTT!

Changes

• Upgrades add-on base image to v4.0.2
• Upgrades Zwave2Mqtt to v2.0.1

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

[frenck (Franck Nijhof)]

Release v0.3.1

Full Changelog

This is a general maintenance release.

Changes

• Upgrades Zwave2Mqtt to v2.0.2

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

[Jtarche]

Hi,

Does this add-on replace OpenZwave? Can I use Z-Wave S2 functionality with it?

[frenck (Franck Nijhof)]

@Jtarche

Does this add-on replace OpenZwave?

This add-on runs ZWave2MQTT which is an project by OpenZwave…

[finity]

That actually brings up another good question…

Which version of OZW does it use? v1.4 or v1.6?

[frenck (Franck Nijhof)]

1.4, the 1.6 bindings for other languages are not all done yet.

[frenck (Franck Nijhof)]

Release v0.3.2

Full Changelog

This is a general maintenance release.

Changes

• Upgrades add-on base image to v4.0.3

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

[thundergreen]

unfortunately latest version can’t upload xml anymore… i cannot get my lock working it shows binary sensor only

EDIT:

#Strangely when I open the user menue of the node i have the locked thing and can control the lock … weird why hass wonÄt have this lock thing then … ?

[lingvo]

Hi all,

Can someone explain, how autodiscovery should work now? E.g. I have Z-wave to MQTT installed and running and it discovered my items. I can change the switch state there. Now I see following json for auto-discovery tab for my selected Node.

{
  "type": "switch",
  "object_id": "switch",
  "discovery_payload": {
    "payload_off": false,
    "payload_on": true,
    "value_template": "{{ value_json.value }}",
    "command_topic": "home/nodeID_5/37/1/0/set",
    "state_topic": "home/nodeID_5/37/1/0",
    "device": {
      "identifiers": [
        "zwave2mqtt_nodeID_5"
      ],
      "manufacturer": "FIBARO System",
      "model": "0x1002",
      "name": "FGS222 Double Relay Switch 2x1.5kW",
      "sw_version": "Unknown"
    },
    "name": "nodeID_5_switch",
    "unique_id": "zwave2mqtt_nodeID_5_5-37-1-0"
  },
  "discoveryTopic": "switch/nodeID_5/switch/config",
  "values": [
    "37-1-0"
  ],
  "persistent": false,
  "id": "switch_switch"
}

When I click Rediscover it is published on MQTT Broker, but nothing happens. Should I copy-paste it somewhere?

[silfa718]

Today I am unable to login into webui. It refuses my login and password giving me “401 access denied”. My zwave network is working, my devices and automatons are working.

Ive rebooted HA, the addon, and even restored the addon from a couple days ago.

I do see this in my logs:

19-08-18 14:20:24 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_zwave2mqtt
19-08-18 14:20:24 WARNING (MainThread) [hassio.api.security] No API token provided for /api/config

Edit: Updating supervisor to 181 fixed my issue.

[iblis]

Same here. Gives me “401 access denied”

[silfa718]

Did it work before for you?

Mine use to work before, not sure what changed.

[silfa718]

Updating supervisor to 181 fixed my issue.

[frenck (Franck Nijhof)]

Release v0.3.3

Full Changelog

This is a general maintenance release.

Changes

• Upgrades nginx to 1.16.1-r0
• Upgrades add-on base image to v4.1.1
• Fixes path handling for SSL certificates
• Updates HA Auth URL in NGinx LUA script
• Use Hass.io DNS as NGinx resolver
• Upgrades Zwave2Mqtt to v2.0.3

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck