Thank you! I have been struggling trying to figure out how to get this set up.
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?
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.
1 Like
Release v0.3.0
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
2 Likes
Release v0.3.1
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
Hi,
Does this add-on replace OpenZwave? Can I use Z-Wave S2 functionality with it?
This add-on runs ZWave2MQTT which is an project by OpenZwaveâŚ
That actually brings up another good questionâŚ
Which version of OZW does it use? v1.4 or v1.6?
1.4, the 1.6 bindings for other languages are not all done yet.
2 Likes
Release v0.3.2
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
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 ⌠?
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?
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.
Same here. Gives me â401 access deniedâ
Did it work before for you?
Mine use to work before, not sure what changed.
Updating supervisor to 181 fixed my issue.
Release v0.3.3
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
Decided to try this and got it working with powered nodes, but all battery nodes are showing âdeadâ. I see issues concerning that but they seem related to 1.6. Does this have 1.6 OZW yet, and are there issues with battery nodes?
Iâve tried âassume awakeâ on and off. The stick is nortek on a Pi 3. Five powered nodes look OK (including on the remote HA end through the MQT broker) but nothing on the others but the node number and âDEADâ.
If I manually wake a node, or cause activity (e.g. motion), in the debug I see detail coming from that node number, but it remains âDEADâ on the control panel, so it doesnât seem to be a loss of communication but rather something in how the messages are processed.
1 Like
At this point should a fibaro RGBW Zwave conroller be able to change colors? In OZW it comes int as a regular dimmer switch. (Normal (Dimmer) - BASIC SET/SWITCH_MULTILEVEL_START/STOP)
I tried changing it to Normal (RGBW) - COLOR_CONTROL_SET but it made no difference. To get it out of HA, I had to remove the mqtt integration reboot and re-add.
So I guess I have 2 questions. 1. If it is possible for the RGBW to work, what settings do I need to change? 2. Whatâs the easiest way to get the integration to update its settings once you make a change in zwave2mqtt?
Thanks for taking the time to make an add-on like this. Once I get it up and running, it is going to make my life so much easier.