node-zwave-js
node-zwave-js copied to clipboard
zwave-js
Command Class Wishlist
All users of this library: here's your chance to influence which CCs I will implement next.
The rules are simple:
- Pick one of the un-implemented CCs
- Vote for it: a. Search this issue. If there's a comment for your CC, vote for it using the thumbs up button. b. If there's no comment yet, please add one.
Unrelated comments and comments that don't follow the rules will be ignored and deleted.
These CCs are next:
- this could be your CC!
Already requested:
- ~~Application Status~~ - Won't be supported. Supervision is better in every regard and we can't match the Application Status commands to the requests they belong to.
- Association Command Configuration
- Meter Table Monitor
- Schedule
- Screen Meta Data
Color (0x33)
I would like to try implementing it, but so far I have been unable to find the spec docs.
That's the Color Switch CC, to be found in https://github.com/AlCalzone/node-zwave-js/blob/master/specs/SDS13781-Z-Wave-Application-Command-Class-Specification.pdf on page 148ff. If you would like to make a PR, go ahead.
"Alarm Sensor CC" for Fibargroup FGSS001
16:08:05.075 CNTRLR « [Node 013] TODO: no handler for application command 16:09:17.290 DRIVER Dropping message because it could not be deserialized: The command class Alarm Sensor is not implemented
Thank you!
I am interested in Schedule one, to be used with new devices supporting scheduling Schedule Comman Class. I am also happy help implementing it
I'd love to finally be able to move my scene controller, an Enerwave ZWN-SC7, off of the Vera controller that it resides on. This device does not support the Central Scene Command class (91 or 0x5B). Instead, it uses Z-Wave Group Associations along with the Scene Controller Configuration Command Class (45 or 0x2D). This is described in the user manual. You use this command class to a map an association group, which is mapped to a physical button, to a scene ID. For example, for this device it looks like Group 1 is mapped to “Button 1”. The scene ID can be any number 1-255. I'm certain to be moving to zwavejs as I use Zwave2mqtt and it's moving to zwavejs.
@MYeager1967 please upvote https://github.com/zwave-js/node-zwave-js/issues/729#issuecomment-730310951 to vote for Scene Controller Configuration
Entry Control, literally no DIY keypad solution on the market at the moment!
Application Status
I'm seeing some reports of it being dropped due to not being supported. Has something to do with "device being busy". Sounds simple :)
~~Sound Switch, please. I have a couple of the Zooz MultiSirens that I use with the legacy HA Zwave implementation that use parameter 3 via a service call, Sound Switch would make life easier!~~ Nevermind, its implemented, just need to figure out how to use it in HA/Node Red.
I'm currently working on Scene Controller Configuration and will do Scene Actuator Configuration afterwards.
Reminder:
Unrelated comments and comments that don't follow the rules will be ignored and deleted.
Powerlevel CC would be very useful to debug networks and would integrate nicely with the new node graph.
Started implementing Entry Control in https://github.com/WizKid/node-zwave-js/commit/7648f2de5669df450976023870a529d71e6cd8ac . Still more to do which I'm planning to do. But thought I post in case someone else is working on it.
Especially handling the notifications and doing something useful with them. But I'm testing it with Ring Keypad and overall it seems to work. Pushing in a code and clicking Arm or any of the other buttons works. In the sense that the messages are parsed and I can see in the log that we get the right data.
Powerlevel CC would be very useful to debug networks and would integrate nicely with the new node graph.
I'm implementing PowerlevelCC now.
I’m voting for MultiCommandCCCommandEncapsulation since I have three Philio PST02-1A that are ignored when they send motion and door-open data... (temperature and illuminance are OK):
14:38:55.358 DRIVER « [Node 024] [REQ] [ApplicationCommand]
└─[MultiCommandCCCommandEncapsulation]
14:38:55.365 DRIVER Received a command that contains multiple CommandClasses.
This is not supported yet! Discarding the message...
14:38:55.367 CNTRLR « [Node 024] TODO: no handler for application command
https://github.com/zwave-js/node-zwave-js/blob/09d5ab6f2289bbf6e8a13d2f5ce8347353c82494/packages/zwave-js/src/lib/driver/Driver.ts#L2270
Hi,
Thanks for asking the masses what we need.
I'm voting for Transport Service as I've loads of messages on my log stating "Dropping message because it could not be deserialized: The command class Transport Service is not implemented".
I think they are being generated while trying to communicate with my Aeotec Water Sensor 7 Pro, so maybe this will also help pushing for that device to be supported soon. ;)
Meter Table Monitor
I've an "Eneco - Meteradapter" by "Prodrive B.V." PN: 6599-1500-0201 that sends this command. It is connected to the P1 port of my electricity meter.
https://products.z-wavealliance.org/products/1281
Z-Wave JS logs show two of these every 10 seconds:
SERIAL « 0x0122000400081c600d06003d0d000111000007e601090d1d0060006fbc9d67000 (36 bytes)
0013b0c
DRIVER Dropping message because it could not be deserialized: The command class Meter
Table Monitor is not implemented (ZW0303)
SERIAL » [ACK]
I expect that this contains the kWh counter(s) of the meter. The node currently shows as <unknown> Manufacturer and Model in HA. However it identifies itself as:
"manufacturerId": 304,
"productId": 0,
"productType": 2,
