Have you found a solution for this?
If I set a Location in ZWave panel, is that meant to carry through to an HA Area? It is not in my case, wondering if there is a config or process step to enable it.
no, location in zwave2mqtt is only meant to be used for the mqtt topic name, independent of home assistant locations. You still have to manually assign your devices to home assistant locations
I don’t understand. in my config panel everything is empty but in mqtt integration it all got:
nodeID_24 - FIBARO System - FGD212 Dimmer 2 (0x1000) - No area - MQTT
so here I can see that the device is a dimmer. how is that posible?
after an hour everything was populated and now it’s empty again…
Hi All,
Can someone tell me how to handle it.
Zwave2Mqtt in HA have a “Start on Boot” must this enabled or disabled after I start it manual?
Reason I ask,
when is restart HA, all my nodes are not available … When I push the buttons of de power plugs they come up, also for the motion sensors. I tought HA leave Z2M alone and start itself and Wave nodes are working again, because they not startup with HA.
So I got it running and installed… works but a LOT of questions… let’s start with the first 3:
-
Can I update this?
-
It seems I can set parameters as I am used in Vera
But where can I do this? I have a test device like this one:
I should be able to add/change parameters below configuration?
3.I have an issue… my device is unavailable in hass after restart of hass:
After pressing
REDISCOVER NODE
they are back:
What is causing this?
This holds me back MAJORLY because I am not sure what happens with 50 devices included… will I have to do this 50x after each hass reboot ?!
Hi!
I’ve installed Zwave2mqtt because so far… I wasn’t able to get OpenZwave-qt working because i’m using external mqtt broker (in docker image) and openzwave daemon seems to need the addon… . But i’m struggling to add a thermostat on Zwave2mqtt as well…
I have performed SRT-323 inclusion without any issues and in the Zwave2mqtt webpage, i have everything i need for the thermostat. I can even change the temperature set point on the interface which change the temperature on the thermostat after the wake-up interval.
But i can’t have the thermostat on the Hass webpage. I have read the github readme page regarding the thermostat but:
-
When i add any json configuration like this:
and then click sur Add, nothing happens… even after clicking on “rediscover node” -
On the other hand, reading the readme file tells that I can specify custom devices configuration inside "store/customDevices(.js|.json) which i can’t find on my homeassistant folder.
I am on Raspbian and Hass is installed via docker but i don’t think it changes much…
Thanks for the guide.
Almost there not there yet.
Got Ozwave in docker woriking on raspberry PI remote antenna.
Mqtt messages flowing to mqtt server on same server as homeassistant
ozw beta component installed.
But I have a notice that no openzwave running instance has been found.
My understading is that the docker contaitning openzwave can run anywhere on the network.
Gateway has een configured in openzwave as per the instructions (discovery on, homeassistant topic, retain true)
What can be wrong?
update . devices are discovered and I can find them in the devices tab. just the integration page says nothing could be found.
Hey guys.
Someone know how to start the calibration process in ZWAVE2MQTT addon? I want to calibrate my fibaro roller shutter 3, or I think I have to do this and find a screenshot in the normal Z-Wave Addon to do this.
Unfortunatly my roller shutter was detected correctly but I cant control it with HA.
Here is the json. I dont know why the roller shutter also has a metering for energy.
Couple questions,
-
In MQTT setting for Auth, am I putting in the username/pw that is auto populated in my MQTT broker add on?
-
How do I enter the config path correctly to get it to recognize that my switch is an innovelli? Heres all my config files…
-
Why do I not see any entity in my ENTITIES section, even though I succesfully added a switch to ZWAVE2MQTT?
Select “start calibration process” and hit “set config parameter” at the bottom.
Other methods are described in the manual.
https://manuals.fibaro.com/document/fgr-223-positioning-calibration/
Are you able to use cover.open or cover.close? I only get an error when I call the service. set_position is working fine.
But I’m also using the new integration which is currently available in the new HA beta.
Has anyone encountered any issued with Aeotec Multisensor 6’s? I’m banging my head against the wall with them. I have them all in Zwave2MQTT properly and properly in HA and the contacts are customized to motions. Everything was working perfectly and now the motions are not triggering events in HA for some of the units. The other sensors (temp, lux, etc) in those units are continuing to to function. Any suggestions or experience appreciated.
I had the same problem the motion was sometimes reported sometimes not. Because i have also Vera controller at home i moved the sensors to vera and they are working fine with vera integration in home assistant.
Ok, I have a Vera controller also and I have also found it works. I was hoping to migrate away from Vera as the legacy platform is becoming deprecated as they move to EZ-LO. Also, it sends the sensors as 6 devices. The Z-wave frustration is unending.
Try Play with this maybe it will change something
Parameter 5: Which command would be sent when the motion sensor triggered.
To set which command would be sent when the motion sensor is triggered.
Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 1 | Send Basic Set |
| 2 | Send Sensor Binary Report |
Honestly from the devices that i use vera had much better support so i was not able to migrate completely.
I have Fibaro, Aeotec and Qubino devices and only fibaro is working better on zvave2mqtt, aeotec is ok but sometimes it dos not sync the state, qubino dimer does not work at all when you manually chage the state of the switch, and qubino relay is responding very slow, aeotec dimmer also does not report state sometimes 
so i use zeave l2mqtt for fibaro modules and vera for the rest.
Has somebody got this working with the NodeRed addon?
I can’t seem to get information from this node.
Can someone tell me if it is better to switch from Z2MQTT > ZwaveJS2MQTT ?
If you are happy with your setup, then no need to switch. If you don’t mind tinkering a little, then the switch should be better.
2 Likes
So what you saying is ZwaveJS2MQTT is better then Zwave2MQTT but in need to some little changes to let it work, but after that its better?