node-zwave-js: Merten FunkTaster CONNECT; Merten 5071xx no trigger options for basic command set 0 and 255
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist
-
I have checked the troubleshooting section and my problem is not described there.
-
I have read the changelog and my problem was not mentioned there.
Describe the bug
What causes the bug? The Merten wireless Z-wave switch sent only basic command values. These values are not selectable in the screen; automations -->trigger type: Device --> name device eg. “Merten wall controller” --> trigger drop down list
I expect a value like; ‘subtype: 54-32-0 (currentValue)’
Or a read only entity under this z-wave device that detect the 0 and 255 basic value
s
Device information
Manufacturer: Merten Model name: 5071xx and 506219
Device info 506219 by Merten Firmware: 1.8 Z-Wave Info Source: Z-Wave JS Device ID: 54 Device Status: Asleep Device Ready: Yes Secure: No
How are you using node-zwave-js
?
-
zwavejs2mqtt
Docker image (latest) -
zwavejs2mqtt
Docker image (dev) -
zwavejs2mqtt
Docker manually built (please specify branches) -
ioBroker.zwave2
adapter (please specify version) -
HomeAssistant zwave_js
integration (please specify version) -
pkg
-
node-red-contrib-zwave-js
(please specify version, double click node to find out) - Manually built from GitHub (please specify branch)
- Other (please describe)
Which branches or versions?
version:
node-zwave-js
branch:
Z-Wave JS
Current version: 0.1.45 (Changelog)
Home Assistant 2021.10.6 Frontend version: 20211007.1 - latest System Health Version core-2021.10.6 Installation Type Home Assistant OS Development false Supervisor true Docker true User root Virtual Environment false Python Version 3.9.7 Operating System Family Linux Operating System Version 5.10.70 CPU Architecture x86_64 Timezone Europe/Amsterdam
Did you change anything?
yes (please describe)
If yes, what did you change?
I upgrade form Z-Wave (deprecated) version to z-wave JS
Did this work before?
Yes (please describe)
If yes, where did it work?
In the Z-Wave (deprecated) I used the switch to fire events/scipts in home assistent with the automation: Here I used the event type below:
trigger type: event
entity_id: zwave.merten_transmitter_2_gang_switch basic_level: 255
action: a bunch of devices to turn on
and automation:
trigger type: event
entity_id: zwave.merten_transmitter_2_gang_switch basic_level: 0
action: a bunch of devices to turn off
Attach Driver Logfile
dump of the debug log when I press the buttons: On command:
2021-10-24T21:02:17.990Z SERIAL « 0x01090004003b032001ff14 (11 bytes)
2021-10-24T21:02:17.993Z SERIAL » [ACK] (0x06)
2021-10-24T21:02:17.995Z DRIVER « [Node 054] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 255
2021-10-24T21:02:17.998Z CNTRLR [Node 054] treating BasicCC::Set as a report
2021-10-24T21:02:18.000Z CNTRLR [Node 054] [~] [Basic] currentValue: 0 => 255 [Endpoint 0]
Off command:
2021-10-24T21:02:20.965Z SERIAL « 0x01090004003b03200100eb (11 bytes)
2021-10-24T21:02:20.967Z SERIAL » [ACK] (0x06)
2021-10-24T21:02:20.969Z DRIVER « [Node 054] [REQ] [ApplicationCommand]
└─[BasicCCSet]
target value: 0
2021-10-24T21:02:20.972Z CNTRLR [Node 054] treating BasicCC::Set as a report
2021-10-24T21:02:20.974Z CNTRLR [Node 054] [~] [Basic] currentValue: 255 => 0 [Endpoint 0]
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 25 (15 by maintainers)
@zwave-js-bot add compat flag to 0x007a:0x0001:0x0002
@zwave-js-bot add compat flag to 0x007a:0x0001:0x0004