ZMNHDD does not report switch status to Zwave-JS

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.

https://www.home-assistant.io

Apache License 2.0

71.34k stars 29.88k forks source link

ZMNHDD does not report switch status to Zwave-JS #46695

Closed edgarvoorbraak closed 3 years ago

edgarvoorbraak commented 3 years ago

The problem

When pressing a button on the Qubino ZMNHDD dimmers, the status is not updated in the switch and/or light entity.

Removing and re-adding the device does not help, nor does removing the device and re-associating the device to the Reporting groups

The devices worked fine with zwave2mqtt, OZW and the old z-wave component.

What is version of Home Assistant Core has the issue?

2021.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave-JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line

marcelveldt commented 3 years ago

I believe this is one of those dimmers that need to be polled for status updates. Polling is by default not implemented in Z-Wave JS (like it was in OpenZwave) and you need to poll a value yourself. We're working on a service that allows you to poll the device/value.

Idcsl commented 3 years ago

Just noticed this and thought I would mention that I have one of these dimmers and just verified that when using the wall on/off switch, the status is indeed replicated in the dimmers card. I cannot though verify change of brightness replication as the wall switch is a simple on/off switch and not a retractive switch.

edgarvoorbraak commented 3 years ago

I believe this is one of those dimmers that need to be polled for status updates. Polling is by default not implemented in Z-Wave JS (like it was in OpenZwave) and you need to poll a value yourself. We're working on a service that allows you to poll the device/value.

I do not understand, The dimmer is reporting power consumption in Watts when I turn it on, so am I correct to assume that polling would not be needed for this ? Also strange that ldcsl reports that switch activity is indeed reported while for me this is not the case.
By the way I have another qubino device that is misbehaving, the ZMNHBD dual relay switch, which is connected to 2 switches, does report when a switch is on, but it does not report which swich is on. My regular qubino single relay switches work normally and report their state correctly.

baswieb commented 3 years ago

I believe this is one of those dimmers that need to be polled for status updates. Polling is by default not implemented in Z-Wave JS (like it was in OpenZwave) and you need to poll a value yourself. We're working on a service that allows you to poll the device/value.

I also own Qubino ZMNHDD dimmers. With the old Z-Wave integration no polling was needed for status updates. With the old Z-Wave integration all my Qubino ZMNHDD dimmers updated correctly in the UI after using the hardware switches connected to the dimmer. With the Z-Wave JS integration only one of my ZMNHDD dimmers updates the Home assistant UI correctly (the one with firmware version 3.5). The ZMNHDD dimmer with firmware version 1.1 does not.

marcelveldt commented 3 years ago

reporting the power consumption and the state are two separate things. It might happen for a device that it correctly reports sensor values but not the primary value (brightness or switch state). Like @baswieb also mentioned it can even differ between various firmware versions.

Whenever a device reports a new value, this event is transmitted by zwave-js to the HA integration, which will in-turn update the state in Home Assistant for the entity. If there is no event emitted, the state will not be updated, simple as that.

Some things to test/consider:

If you're using the Z-Wave JS 2 MQTT add-on / container you have the ability to update the firmware. Might be worth a shot if that fixes the issue without having to manually poll the device.
You could watch the logs of the Z-Wave JS Server (either the official add-on or zwavejs2mqtt) to see if there is a value update event coming in, that should be logged.

If there's no event and you're sure that your device should support the auto reporting of it's value natively, please report back here so we can create an issue upstream in zwave-js.

Idcsl commented 3 years ago

I looked at the information presented in devices for the dimmer and my dimmer is on firmware version 3.7. I can also confirm that it does reflect the power consumption as well as the state so it would seem that if edgarvoorbraak updates his firmware it should work as expected.

edgarvoorbraak commented 3 years ago

Sounds promising, however I have yet to find a firmware binary for these devices. Is it possible to dump this firmware, has someone found this firmware online, or should I contact Qubino ?

Idcsl commented 3 years ago

Unfortunately Qubino do not release firmware and only offer the option to send the units to them for updating. See this link for their info on this.https://support.qubino.com/support/solutions/articles/44001936790-do-qubino-devices-support-ota-can-i-update-the-firmware-ota-

edgarvoorbraak commented 3 years ago

Well the latest version of Z-Wave JS to MQTT (0.6.1) restored the functionality. The dimmer is now reporting its value again.. So luckily it is not needed to send the qubino for upgrade.