Zwave2mqtt: [question] Multisensor not discovering all values

[chilicheech]

I have 2 different multisensors that have temperature, humidity, luminance, and motion sensing. All values are identified properly and I can see them in the UI. However, the hass devices section only shows:

• binary_sensor_contact
• sensor_battery
• sensor_humidity
• sensor_illuminance
• sensor_temperature

The devices that are missing in hass devices are:

• sensor_home_security/sensor_security/sensor_burglar
• sensor_alarm_type
• sensor_alarm_level

The missing sensors are the ones used for motion and tamper detection.

I see that the configurations exist here: https://github.com/OpenZWave/Zwave2Mqtt/blob/v2.1.1/hass/configurations.js#L135-L158

I also see some definition/discovery here: https://github.com/OpenZWave/Zwave2Mqtt/blob/v2.1.1/lib/Gateway.js#L785-L802

I don't understand why the hass devices are not being created. Here are some screenshots:

Sensor 1 - ZSE40 4-in-1 sensor (Zooz)

Sensor 2 - ZP3111 Multisensor 4in1 (Vision Security)

My question is, how can I get the other values to show up as hass devices?

Cheers,

[robertsLando]

@chilicheech Fixed now, check latest commit :)

[chilicheech]

Thank you so much for the quick fix :)

[chilicheech]

@robertsLando quick question. I want to build the docker image so i can test the new change locally so I'm looking at this: https://github.com/robertsLando/Zwave2Mqtt-docker#custom-builds
So, looking at the Dockerfile, i see this: https://github.com/robertsLando/Zwave2Mqtt-docker/blob/master/Dockerfile#L9 and it says: # Latest stable 1.4
Is that still the case? I thought we were defaulting to 1.6 now? If it's still defaulting to 1.4, what sha should I use for 1.6?

Or should I use this file instead to build the image? https://github.com/robertsLando/Zwave2Mqtt-docker/blob/master/Dockerfile.cross

[robertsLando]

I suggest you to build it also by replacing the openzwave sha with latest ozw commit so you are also using latest ozw in your docker.

So copy and paste there the ozw and the z2m latest commit sha and your image will be ready

Daniel

On 3 Feb 2020, at 22:36, Thiago Oliveira [e-mail] wrote:


@robertsLando quick question. I want to build the docker image so i can test the new change locally so I'm looking at this: https://github.com/robertsLando/Zwave2Mqtt-docker#custom-builds
So, looking at the Dockerfile, i see this: https://github.com/robertsLando/Zwave2Mqtt-docker/blob/master/Dockerfile#L9 and it says: # Latest stable 1.4
Is that still the case? I thought we were defaulting to 1.6 now? If it's still defaulting to 1.4, what sha should I use for 1.6?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[chilicheech]

Just reporting back that it's working great. Thanks again:

[chilicheech]

@robertsLando another question, since in openzwave the value is called home security do you think it would make sense to label this home_security instead of alarm_burglar? Or maybe alarm_home_security? I found a reference doc here: https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/ValueIDIndexesDefines.def#L1076 and here: https://github.com/OpenZWave/open-zwave/blob/master/cpp/src/ValueIDIndexesDefines.h#L9
If so, I'll be happy to send you a PR to relabel it..

[Dinth]

The next release is gonna be soo great :)

[robertsLando]

@chilicheech I have follow this file specs: https://github.com/OpenZWave/open-zwave/blob/master/config/Localization.xml

Anyway there are 18 different types of alarms (index < 256) would you mind to create a configuration for each one of them? Every configuration need also to be added to /hass/configurations.js

[chilicheech]

Sounds good. I'll work on that today.