WT00Z5-1 Switch Control Missing

prairieit commented 2 years ago

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

[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug? Including the device

What do you observe? Once including, the device does not have a light. or a switch. service to control its on/off state. It has a diagnostic Node Status only.

What did you expect to happen? The device should have a light. service to control its on/off state

Steps to reproduce the behavior:

Include device
Controllable light does not exist.
Re-interview
Controllable light still does not exist.

Device information

Manufacturer: Linear (Nortek Security Control LLC) Model name: WT00Z5-1 Node ID in your network: 48

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)
[X] 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?

Driver Version: 8.10.2 Server Version: 1.14.1

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Yes (please describe)

If yes, where did it work?

The device previously worked flawlessly on a Vera (non HA) device.

Attach Driver Logfile

zwave_js.log

AlCalzone commented 2 years ago

Attach Driver Logfile

log here

We ask for the log for a reason. Please make a driver log, loglevel debug or silly. Re-interview the device and when done, attach the log here as a file.

prairieit commented 2 years ago

I dont use zwavejs2mqtt, just the Z-Wave JS HA add-on.... are these the same logs? zwave_js.log

prairieit commented 2 years ago

@AlCalzone was that the proper log file?

AlCalzone commented 2 years ago

Yes. But from the information there, the device is a wall controller (controlling other devices) and not a switch:

[Node 048] received response for protocol info:
basic device class:    Routing Slave
generic device class:  Wall Controller
specific device class: Basic Wall Controller
node type:             Routing End Node

...

supported CCs:
· Z-Wave Plus Info
· Central Scene
· Version
· Manufacturer Specific
· Powerlevel
· Device Reset Locally
· Association
· Association Group Information
· Configuration
· Firmware Update Meta Data
controlled CCs:
· Central Scene

It also doesn't have any endpoints or Manufacturer Proprietary CC, which could expose additional functionality.

The OpenZWave config file also doesn't add any CCs to the list, so maybe the device isn't telling everything.

Try excluding, factory resetting and then including again.

zwave-js-assistant[bot] commented 2 years ago

This issue has not seen any recent activity and was marked as "stale 💤". Closing for housekeeping purposes... 🧹

Feel free to reopen if the issue persists.

zwave-js / node-zwave-js