Hello everyone,
as discussed in the topic « Gladys 4 Beta est disponible ! 🚀 - #281 par pierre-gilles », I am opening a dedicated topic for Zwave in v4. The idea is to share your feedback, bugs, and ideas to improve the service, for example:
etc.
At the graphical interface level, sometimes the On/Off does not work (it remains stuck in the same position). I encounter the problem with different connected Z-Wave outlets. Switching to another tab or refreshing the page allows to fix the problem. In the logs, I have this:
2020-04-16T21:23:18+0200 <debug> scene.executeSingleAction.js:15 (SceneManager.executeSingleAction) Executing action of type device.set-value
2020-04-16T21:23:18+0200 <debug> zwave.setValue.js:13 (ZwaveManager.setValue) Zwave: Setting value
2020-04-16T21:23:18+0200 <debug> zwave.valueChanged.js:14 (ZwaveManager.valueChanged) Zwave: Value Changed, nodeId = 20, comClass = 37, value = {"value_id":"20-37-1-0","node_id":20,"class_id":37,"type":"bool","genre":"user","instance":1,"index":0,"label":"Switch","units":"","help":"Turn On/Off Device","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"value":true}
2020-04-16T21:23:18+0200 <debug> zwave.valueChanged.js:16 (ZwaveManager.valueChanged) node20: changed: 37:Switch:false->true
2020-04-16T21:23:18+0200 <debug> device.saveState.js:16 (DeviceManager.saveState) device.saveState of deviceFeature zwave-switch-nas-wr01ze-power-plug-12a-node-20
2020-04-16T21:23:18+0200 <debug> zwave.valueChanged.js:14 (ZwaveManager.valueChanged) Zwave: Value Changed, nodeId = 20, comClass = 37, value = {"value_id":"20-37-1-0","node_id":20,"class_id":37,"type":"bool","genre":"user","instance":1,"index":0,"label":"Switch","units":"","help":"Turn On/Off Device","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"value":true}
2020-04-16T21:23:18+0200 <debug> zwave.valueChanged.js:16 (ZwaveManager.valueChanged) node20: changed: 37:Switch:true->true
2020-04-16T21:23:18+0200 <debug> device.saveState.js:16 (DeviceManager.saveState) device.saveState of deviceFeature zwave-switch-nas-wr01ze-power-plug-12a-node-20
The bug is visible on the second to last line.
Connected plug Neo Coolcam. Not all information is being reported.
I just mapped the missing commandsClass, and this fixes the issue. Here is the result:
Electric - KWh is negative. Maybe an issue with my plug, otherwise it’s an issue at the openZwave level. In any case, it’s the value reported by the latter that is displayed. The problem is not
on Gladys’s side.
I will make a PR for the added comClass.
Bug:
When you click on the « Setup » page and the key scan is not complete, a loading button appears. However, once the scan is complete, it does not change state; you need to refresh the page or switch tabs to see the information update in the « Setup » section.
Great idea!
When the bugs mentioned here are recognized, don’t hesitate to create an issue per bug on GitHub, otherwise these bugs will be overlooked 
I’m working on my dev environment. So sometimes I wonder if it’s related to that or not. That’s why I’d like other users to confirm the bugs I find before opening bugs on GitHub.
I invested in Z-Wave to control a motorized shutter
My key is well recognized by Gladys.
The module I used is a Qubino ZMNHCD1.
I just integrated the node into Gladys, the problem is that I can only lower my shutter (fortunately I kept the physical buttons 
)
There must be something missing because it’s a bit more than an on/off switch
Pierre-Gilles is already aware of my problem, but since there is a special Zwave topic, I take advantage of it to centralize.
I bought two Qubino ZMNHJD1 modules to control my radiators. I managed to add them to Gladys, but like VonOx, I only have the possibility to make a switch on/off, whereas normally I should be able to send 6 different instructions.
Same issue with my Fibaro roller shutter. For the roller shutters, a UI-side modification is planned. The « roller shutter » feature needs to be modified to display 3 buttons in the UI: up / stop / down.
The zwave service also needs to be modified. As it stands, it detects a single « switch » instance. All modules with multiple switches only see a single instance of the switch and not the others. Modules like « roller shutter » and « double relay » that have multiple switch instances therefore only work partially for now. I spent last night trying to modify the code, to no avail. I’ll get back to it tonight, otherwise I’ll need some help from @pierre-gilles.
More information feedback (well, consumption is not very useful) and positioning in %
I’ve retrieved consumption information and mapped the comClass, this should also work for your equipment.
Ah yes, the positioning, good catch, I’ll need to map that too!
Okay, I’ll take a look at your PR, I’m discovering Z-Wave
Hello Aldo,
Could you send me your ozwcache_something.xml file located in: server/services/zwave/node_modules/openzwave-shared/. I would like to check if the fact that you only have one switch is also related to the instance issues.
Thank you
Hello everyone
I’m back for my zwave problem
The key used is: an everspring key compatible zwave and zwave plus
But the problem is that no data comes back then only the door module battery comes back only the first time during the first sync then nothing
I did various tests with firefox and chromium and waited several days (you never know) but nothing
Here, thank you for looking at the problem
Hi @Will9,
could you give me the models/brands of your opening detector and the trisensor?
I confirm, zwave modules with multiple instances only have one instance recognized. Thanks to zwave and its crappy indexing system…
My lack of knowledge in node doesn’t allow me to fix the issue even though I can visualize it well. @pierre-gilles, I’m available if you want me to explain/show you the problem on my dev environment. This correction will affect many modules at once!
Hello link39,
Sorry for the delay, here is my ozwcache file: https://pastebin.com/dhGng83i
I just looked at the file. I imagine you only have an On/Off button in Gladys, and that’s normal.
The values you would like to send are probably these:
According to Openzwave, these are configuration elements of the module. Just like a connected switch for which you would choose whether it should be of the « single switch » or « toggle switch » type.
The configuration part is not yet coded in the zwave service. I imagine that for each zwave device, we will be able to click on it to edit its configuration from the « devices » tab. You will thus be able to change the values in this way.
Hello @VonOx,
what model of roller shutter module do you have? If it’s not Fibaro, can you send me the file ozwcache_something.xml that is in: server/services/zwave/node_modules/openzwave-shared/?
Ok, I see.
Actually, I find it a « shame » to have to configure the device and only have 2 options available.
In normal use, I would like to be able to set « On/Off » => « Comfort/STOP », but in scenarios, I would like to be able to say « As I am absent today, set Comfort -2 » or « I am going on vacation so Frost Protection ».
After that, if the module does not allow this operation, it’s not a big deal, but it’s true that it is less practical in use.
