Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ZMNHDA Qubino Flush Dimmer multilevel switch current value not propagating from zwavejs to zwavejs2mqtt

See original GitHub issue

Version

Build/Run method

Docker -> running a Home Assistant supervised add-on

zwavejs2mqtt version: 1.1.0 zwavejs version: 6.1.3

Describe the bug

For my Qubino (GOAP) ZMNHDA dimmers, I see multilevel switch (“current value”) updates sent to Endpoints 0 and 1, but only Endpoint 1 is received in zwavejs2mqtt, this when manually toggling the light switch.

From zwavejs log:

15:34:46.396 SERIAL « 0x0109000400400326030094                                            (11 bytes)
15:34:46.398 CNTRLR   [Node 064] [~] [Multilevel Switch] currentValue: 63 => 0          [Endpoint 0]
15:34:46.399 SERIAL » [ACK]                                                                   (0x06)
15:34:46.402 DRIVER « [Node 064] [REQ] [ApplicationCommand]
                      └─[MultilevelSwitchCCReport]
                          current value: 0
15:34:46.407 CNTRLR   [Node 064] [~] [Multilevel Switch] currentValue: 63 => 0          [Endpoint 1]
15:34:47.336 SERIAL « 0x0110000400400a320221340000023b0000bd                              (18 bytes)

However in zwavejs2mqtt log, only 38-1 value is updated, which does not get picked up by the “Current Value” entity in HA (there is only one for the light): 2021-02-10 15:34:46.411 INFO ZWAVE: Node 64: value updated: 38-1-currentValue 63 => 0

To Reproduce

Steps to reproduce the behavior:

toggle lights
observe only endpoint 1 coming through to zwavejs2mqtt in the logs

Expected behavior

Also expect 64-38-0-currentValue to be updated

Additional context

Logs attached zwavejs2mqtt.log zwavejs_578.log

Issue Analytics

State:
Created 3 years ago
Comments:59 (32 by maintainers)

Top GitHub Comments

1reaction

AlCalzonecommented, Oct 19, 2021

@fbietlot please select your logs after pasting and click this button: grafik That will make it easier to digest.

1reaction

blhoward2commented, Oct 18, 2021

The only way to use a built docker image is by installing the Portainer addon, or you may be able to install the ssh addon and manually run docker (I’m not sure on that one). Otherwise he’s limited to the zwavejs addon or the zwavejs2mqtt addon.

https://community.home-assistant.io/t/home-assistant-community-add-on-portainer/68836

Top Results From Across the Web

ZMNHDA Qubino Flush Dimmer multilevel switch current value not ...

Steps to reproduce the behavior: toggle lights; observe only endpoint 1 coming through to zwavejs2mqtt in the logs. Expected behavior. Also expect 64-38-0- ......

ZwaveJS2MQTT and Qubino Flush dimmer - Z-Wave

So far, it appears the ZMNHDA device advertises “currentValue” on Endpoint 0 when it is interviewed, but when the values are updated it...

USER MANUAL EN. QUBINO FLUSH DIMMER

The Qubino Flush Dimmer is a MOSFET-switching light device that also supports control of low-voltage halogen lamps with electronic transformers, dimmable ...

Flush Dimmer - Technical specifications - Qubino

NOTE: The minimum level may not be higher than the maximum level! 1% min. dimming value is defined by the Z-Wave multilevel device...

Qubino Flush Module not updating Status - Z-Wave.Me forum

My Problem is: If I switch the Dimmer Module (or the Relay) with the normal Wall Switch (bi-stable Switch) thats wired to the...