MCO home MH-C421 multilevel switch is not good

S1M8N commented 3 years ago

Checklist:

[x] I am using HomeAssistant.
[x] I am using ZWaveJS2MQTT.
[x] I have checked the troubleshooting section and my problem is not described there. Yes and No
[x] I have read the changelog and my problem was not mentioned there. Yes and No...

Describe the bug

Hello,

I use home assistant OS without any add-on except zwavejs2mqtt which is in the latest version and the z-wave js integration that goes with it. However my C421 home MCO switches are not considered a multilevel switch (I think). I can still move them up and down I don't really know how but it works. On the other hand, it is impossible for me to do the STOP / PAUSE action ...

If you need a log please let me know where they are so I can send them to you. If I need an additional add on to retrieve these logs let me know

This is an issue that had already been addressed and corrected by adding a force multilevel switch for my device. When I did not yet have the add-on version it was good the force multievel switch worked but there it does not seem to work or badly ... I noticed that if the module was in an unknown state everything was working in the management of the multilevel switch however when it is added correctly this is no longer the case and the stop button no longer works ...

I won't go into details because I don't really know how it works.

Hope we can solve this problem.

Thank you in advance

Device information

MCO home C421 What are the node IDs? 6 and 8

Did you change anything?

[ ] No

Did this use to work before?

[ ] Don't know

How are you using node-zwave-js

[ ] HomeAssistant version 0.13.0

To Reproduce

Steps to reproduce the behavior:

Go to 'Zwave js Integration'
Click on 'Stop button'
See error (doesn't work) zwave_js_dump.zip

blhoward2 commented 3 years ago

What do you mean the stop/pause action? Can you go into the zwavejs2mqtt UI, go to that node, and see if everything works when controlling it under the Multilevel sub-tab?

AlCalzone commented 3 years ago

Also, I'm probably going to need a zwave-js logfile where you control the device.

S1M8N commented 3 years ago

Also, I'm probably going to need a zwave-js logfile where you control the device.

faf58650.zip

blhoward2 commented 3 years ago

The log is helpful but can you also answer my questions? We need to understand the issue.

AlCalzone commented 3 years ago

@S1M8N that's no logfile :(

S1M8N commented 3 years ago

Yes sorry... I have that : Log and printscreen.zip

AlCalzone commented 3 years ago

Thanks, but we still need a bit of explanation what the problem is. In your log I see that you control the device using Multilevel Switch CC and it changes the value.

S1M8N commented 3 years ago

Yes, however the pause button does not work :

AlCalzone commented 3 years ago

That's in Home Assistant though. I'd need to see a log where you push that, but I don't know how to get a log out of HA.

S1M8N commented 3 years ago

I understand but if I do not go through HA I do not have the pause button that appears in the add on zwavejs2mqtt. Moreover if I do not understand but I only have the possibility of doing UP / DOWN from HA in the add on I can only manage the position

AlCalzone commented 3 years ago

@S1M8N your cache file above contains version: 0 for Multilevel Switch on both nodes. Either the node didn't respond during the interview, or your cache file got corrupted. Please re-interview both nodes in zwavejs2mqtt (under the "advanced" node options) and post a log of that. Maybe that fixes the problem - if not, I'll at least know why.

S1M8N commented 3 years ago

it doesn't seem to have helped. Even worse ... However once I added the module and I had an unknown state and everything worked ... But when I have everything correct at Device ID level the problem is the one mentioned above .... Re-interview_log.zip

AlCalzone commented 3 years ago

Okay, the node is contradicting itself. First it lists Multilevel Switch as supported, then it claims it does not support Multilevel Switch:

2021-04-27T20:24:05.603Z CNTRLR « [Node 006] node info received
                                  supported CCs:
                                  · [...]
                                  · Multilevel Switch
...
2021-04-27T20:24:05.967Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[VersionCCCommandClassReport]
                                      CC:      Multilevel Switch
                                      version: 0
2021-04-27T20:24:05.974Z CNTRLR   [Node 006]   does NOT support CC Multilevel Switch (0x26)

We can force-override this information via the config files, but I'm not sure which version it actually supports. Going with 1 probably doesn't hurt.

AlCalzone commented 3 years ago

Ok, it turns out we already forced it to support Multilevel Switch, but that was not enough.

S1M8N commented 3 years ago

@AlCalzone,

Your changes had no effect

I have included the module again and check that the config file has been changed... logs.zip

AlCalzone commented 3 years ago

@S1M8N you have to re-interview it for the changes to be applied.

S1M8N commented 3 years ago

@S1M8N you have to re-interview it for the changes to be applied.

@AlCalzone, Yes I have make that...

S1M8N commented 3 years ago

Hello @AlCalzone,

I'm sorry but I don't have an answer, were you able to find something or do you need something more ??

thank you for your work

AlCalzone commented 3 years ago

Please re-interview the device and share the zwave-js log and the cache files <homeid>.json and <homeid>.values.json afterwards.

S1M8N commented 3 years ago

Please re-interview the device and share the zwave-js log and the cache files <homeid>.json and <homeid>.values.json afterwards.

Ok, I have re-interview the devices. It's the node 10

S1M8N commented 3 years ago

@AlCalzone,

The logs is ok for you ? Logs (1).zip

AlCalzone commented 3 years ago

Ok I think I found it. The change does get applied and you can even see in the cache now that the version is forced to be 1:

                "0x26": {
                    "name": "Multilevel Switch",
                    "endpoints": {
                        "0": {
                            "isSupported": true,
                            "isControlled": false,
                            "secure": false,
                            "version": 1
                        }
                    }
                },

However, the interview for that CC is still not done, which is why you're not seeing those values.

S1M8N commented 3 years ago

ok can you do something about it?

AlCalzone commented 3 years ago

Yeah

AlCalzone commented 3 years ago

Duplicate of #2273

Please follow that issue for an update

S1M8N commented 3 years ago

@AlCalzone Hello, I still cannot use the stop button on my shutter. I have version 7.7.0 of z-wavejs and the latest version of the plugin. I re included the device. Its node is now 12. Log 28.02.2021.zip

AlCalzone commented 3 years ago

The issue I linked to isn't done yet.

S1M8N commented 3 years ago

The issue I linked to isn't done yet.

@AlCalzone Ok when are you planning to do this?

AlCalzone commented 3 years ago

I can't make any promises right now. Will do it soon, but that's about as concrete as I can be at the moment.

S1M8N commented 3 years ago

I can't make any promises right now. Will do it soon, but that's about as concrete as I can be at the moment.

I hope you will have time before the end of June it would be super cool

zwave-js / node-zwave-js

MCO home MH-C421 multilevel switch is not good #2454