Z-Way built-in MQTT dependencies and sensor filtering

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
A&A
Posts: 4
Joined: 27 Aug 2018 08:40

Z-Way built-in MQTT dependencies and sensor filtering

Post by A&A »

Dependencies for z-way-server deb for Ubuntu 20.04 x64 are incorrect. For MQTT feature to work it requires manual install of libmosquitto1 package. I'm using https://repo.z-wave.me/z-way/ (found via https://github.com/Z-Wave-Me/docker-z-w ... Dockerfile).

If libmosquitto dependency is something that is intentionally excluded from z-way-server deb I'd suggest adding message to MQTT setup that it must be installed manually. Cause of MQTT failing was obvious after manually launching z-way-server executable (says libmosquitto1.so missing), but couldn't find anything telling what's wrong via GUI or z-way-server log files.


There's also issue with MQTT "Devices that should not be published in MQTT" filtering and sensors set "Deactivated" via Smarthome UI > Devices > Z-Wave > Manage > pick device > Configuration.

Sensors set deactivated in device settings are not shown on list of devices that can be excluded from MQTT publishing. When unsolicited sensor data is received from one of such sensor (for example Fibaro Dimmer 2 power consumption data) it is processed by Z-Way built-in MQTT and causes extra entries in MQTT. I know, it's mostly cosmetic and in no way major issue.

I suggest that either MQTT device list should also show deactivated devices (so they can be filtered away) or alternatively treat deactivated devices like those with "mqtt-skip" tag applied (preferred for my use case).
User avatar
PoltoS
Posts: 7562
Joined: 26 Jan 2011 19:36

Re: Z-Way built-in MQTT dependencies and sensor filtering

Post by PoltoS »

You need to add the repo.mosquitto.org to repositories in your Ubuntu. This will solve the issue.

Thanks for the report about desactivated sensors, we will check it.
Post Reply