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

I haven’t done it, but I’d start here: https://www.home-assistant.io/hassio/installation/

With the virtual appliance ones, then once up install the zwave2mqtt (only).

I have home assitant running as avm (appliance) already. But I would rather not have zwave to be a container in that vm. I wouod like to have a dedicated vm with a zwave stick (usb) only serving zwave2mqtt…

Yes, but as I understand it this add on needs a HA instance to run within/beside. So what I think is intended is for you to install another HA instance that does nothing essentially except provide the hooks to install this add-on. Again, caveat: I’m not using it myself right now.

Linwood appreciate your response. But I prefer a more simple setup… having solely zwave2mqtt in an esxi vm with usb passthrouh for a zwave dongle and not combined with HA and all … Anyone one else, would that be easily possible?

This topic is about the add-on. I you are looking for just running zwave2mqtt on a separate system, I suggest on looking at the upstream project.

Let’s keep it on topic in here, thanks :+1:

Frenck, I was looking for pros and cons. But I did not receive any remark on that… so I thought running separate was better. Can you shine a light there?


I have a problem with the sound_switch command

OpenZWave Info, Node031, Value::Set - COMMAND_CLASS_SOUND_SWITCH - Volume - 2 - 1 - 10
OpenZWave Detail, Node031, Queuing (Send) MultiChannel Encapsulated (instance=1): SoundSwitchCmd_Tones_Config_Set (Node=31): 0x01, 0x0f, 0x00, 0x13, 0x1f, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x79, 0x05, 0x64, 0x06, 0x25, 0x53, 0xf1
OpenZWave Detail,
OpenZWave Info, Node031, Sending (Send) message (Callback ID=0x53, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SoundSwitchCmd_Tones_Config_Set (Node=31): 0x01, 0x0f, 0x00, 0x13, 0x1f, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x79, 0x05, 0x64, 0x06, 0x25, 0x53, 0xf1
OpenZWave Info, Node031, Encrypted Flag is 0
OpenZWave Detail, Node031, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
OpenZWave Detail, Node031, ZW_SEND_DATA delivered to Z-Wave stack
OpenZWave Detail, Node031, Received: 0x01, 0x07, 0x00, 0x13, 0x53, 0x00, 0x00, 0x03, 0xbb
OpenZWave Detail, Node031, ZW_SEND_DATA Request with callback ID 0x53 received (expected 0x53)
OpenZWave Info, Node031, Request RTT 26 Average Request RTT 64
OpenZWave Detail, Node031, Expected callbackId was received
OpenZWave Error, Node031, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "MultiChannel Encapsulated (instance=1): SoundSwitchCmd_Tones_Config_Set (Node=31): 0x01, 0x0f, 0x00, 0x13, 0x1f, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x79, 0x05, 0x64, 0x06, 0x25, 0x53, 0xf1"
2020-02-29T13:27:41.634Z z2m:Zwave Notification from node 31: Notification - TimeOut (1)
OpenZWave Detail, Node031, Removing current message
OpenZWave Detail, Node031, Notification: Notification - TimeOut

I still can’t update the volume on Aeotec Doorbell 6.

I see here [https://github.com/OpenZWave/Zwave2Mqtt/issues/222] that it might be because of Open Zwave.

Anyone has the same problem ?

Your issue is not add-on related, but OpenZwave related: https://github.com/OpenZWave/open-zwave/issues/2085

yes you’re right.
I tried what they said including the doorbell insecure with no more success.

I’ll just wait (i don’t really know what I have to wait for).

I just a user with no knowledge on these programming stuff.

Anyway, thank you for the job done so far for making things possible for guys like me !

Frenck, can you answer this one as well? Is it the best way forward if running esxi to have a second instance of HA with your repo installed only? And then?

An add-on in HA is not the only way to install Z2M. You can install a containerized version of Z2M through docker on any other machine that supports it. You do not have to have 2 instances of HA running. In fact, that might complicate things.

What “uncomplicate” things?

Is there a way to restore the older zwave2mqtt addon?
Edit: restored older snapshot.

0.5.0 is quite broken for me.

I’m having random restarts of the container.
Also openzwave 1.6 seems to not be able to correctly detect switch changes in some switches.
I checked the product xml’s but can’t find the difference that blocks the switches
Will send a bug report to openzwave project.

For me was the same. After update to 0.5.0 all my battery devices were dead and the other devices was not able to detect corretly. I made a hard reset to my zwave stick and all zwave devices, removed the updated component, and installed a clean 0.5.0 version. And then configured and added back all my devices. The result is now good, no failures every device handled correctly.
I thing the change from openzwave 1.4 to 1.6 was a big step and this migration is not the best at the device database or something.

Fixing battery powered devices: a manual wakeup + maybe a nif request should do it.

When I think of it, the container crashes started happening after enabling a new setting in the config panel.

Will run a 0.5.0 container to retest, and ex/include one of those switches when I got some free time. Tnx for the hint :slight_smile:

hi all,

I still don’t understand how everything works but I have used another tool (homeseer) connecting my aeotec stick and I did change the volume of my aeotec doorbell.

I don’t know what lib they are using but if they are on open zwave too I don’t really know why it doesn’t work. Sorry if i’m maybe saying stupid things

Hope it helps someone

HomeSeer is basically like the Vera and HA merged into one, except they release hardware as well as software. There doesn’t seem to be an integration in HA for it (unless I missed something). What’s funny is you basically went the opposite direction (Well more of a lateral direction) from HA/Z2M. HomeSeer is like HA and has its own plugins and integrations and interface.

No no no !

i’m still on HA, I just install homeseer for a minute on my PC with the one month trial then I plugged the zwave stick keeping all the included nodes. I just updated the volume for the doorbell then I put it right back on my RPI/HA.
It was just a (succesful) test for updating the volume because it doesn’t work on HA even with the last Zwave2MQTT update

I’m having MAJOR issues with this plugin. I have 1 device that I’m trying to migrate. Just one, and it doesn’t work. It’s a GE 14294 dimmer switch. I have added it securly to Z2M, it shows up, I can control it through the control panel by clicking the dim and bright buttons. It even got discovered by HA. But, and this is the important part, when I click on or off in HA, it doesn’t do anything. If I change brightness, it occasionally does something, might not be what I want it to do, but it does something. Sometimes it does nothing.

If I do a debug in Z2M, I see the following when I try to change brightness.

2020-03-13T19:50:27.755Z z2m:App New connection 4jx4jDI78A8yhLW6AAAA
2020-03-13T19:50:41.113Z z2m:Mqtt Message received on homeassistant/Chandelier/38/1/0/set
2020-03-13T19:50:54.536Z z2m:App New connection 24ikfeVJin6Qq2I1AAAA
2020-03-13T19:50:57.353Z z2m:Mqtt Message received on homeassistant/Chandelier/38/1/0/set

I don’t see any value anywhere in there, but it looks like it’s sending a set command. When I turn the switch on or off, I get absolutely nothing in my debug. Any ideas?

Most of my Zwave devices work but 2 out of 3 smoke detectors don’t have all options available.
When starting the Zwave2Mqtt add on I see the messages below, does anyone know what is wrong?

2020-03-30T17:50:36.485Z z2m:Zwave Node added 44
2020-03-30 19:50:36.485 Info, Failed to load device_classes.xml
2020-03-30 19:50:36.485 Info, Check that the config path provided when creating the Manager points to the correct location.
2020-03-30T17:50:36.486Z z2m:Zwave node 44 AVAILABLE: Heiman Technology Co. Ltd - Smart Smoke Sensor HS1SA-Z (Unknown)
2020-03-30T17:50:36.486Z z2m:Zwave ValueAdded: 44-94-1-0 ZWave+ Version
2020-03-30T17:50:36.488Z z2m:Zwave ValueAdded: 44-94-1-1 InstallerIcon
2020-03-30T17:50:36.489Z z2m:Zwave ValueAdded: 44-94-1-2 UserIcon
2020-03-30T17:50:36.490Z z2m:Zwave ValueAdded: 44-113-1-1 Unknown
2020-03-30T17:50:36.491Z z2m:Zwave ValueAdded: 44-114-1-0 Loaded Config Revision
2020-03-30T17:50:36.492Z z2m:Zwave ValueAdded: 44-114-1-1 Config File Revision
2020-03-30T17:50:36.493Z z2m:Zwave ValueAdded: 44-114-1-2 Latest Available Config File Revision
2020-03-30T17:50:36.494Z z2m:Zwave ValueAdded: 44-114-1-3 Device ID
2020-03-30T17:50:36.495Z z2m:Zwave ValueAdded: 44-114-1-4 Serial Number
2020-03-30T17:50:36.497Z z2m:Zwave ValueAdded: 44-115-1-0 Powerlevel
2020-03-30T17:50:36.498Z z2m:Zwave ValueAdded: 44-115-1-1 Timeout
2020-03-30T17:50:36.500Z z2m:Zwave ValueAdded: 44-115-1-2 Set Powerlevel
2020-03-30T17:50:36.501Z z2m:Zwave ValueAdded: 44-115-1-3 Test Node
2020-03-30T17:50:36.503Z z2m:Zwave ValueAdded: 44-115-1-4 Test Powerlevel
2020-03-30T17:50:36.505Z z2m:Zwave ValueAdded: 44-115-1-5 Frame Count
2020-03-30T17:50:36.506Z z2m:Zwave ValueAdded: 44-115-1-6 Test
2020-03-30T17:50:36.508Z z2m:Zwave ValueAdded: 44-115-1-7 Report
2020-03-30T17:50:36.510Z z2m:Zwave ValueAdded: 44-115-1-8 Test Status
2020-03-30T17:50:36.511Z z2m:Zwave ValueAdded: 44-115-1-9 Acked Frames
2020-03-30T17:50:36.513Z z2m:Zwave ValueAdded: 44-128-1-0 Battery Level
2020-03-30T17:50:36.514Z z2m:Zwave ValueAdded: 44-132-1-1 Minimum Wake-up Interval
2020-03-30T17:50:36.515Z z2m:Zwave ValueAdded: 44-132-1-2 Maximum Wake-up Interval
2020-03-30T17:50:36.516Z z2m:Zwave ValueAdded: 44-132-1-3 Default Wake-up Interval
2020-03-30T17:50:36.517Z z2m:Zwave ValueAdded: 44-132-1-4 Wake-up Interval Step
2020-03-30T17:50:36.518Z z2m:Zwave ValueAdded: 44-132-1-0 Wake-up Interval
2020-03-30T17:50:36.520Z z2m:Zwave ValueAdded: 44-134-1-0 Library Version
2020-03-30T17:50:36.521Z z2m:Zwave ValueAdded: 44-134-1-1 Protocol Version
2020-03-30T17:50:36.522Z z2m:Zwave ValueAdded: 44-134-1-2 Application Version
2020-03-30 19:50:36.523 Info, Failed to load device_classes.xml
2020-03-30 19:50:36.523 Info, Check that the config path provided when creating the Manager points to the correct location.