@Mariano_Colmenarejo thanks , now is working perfect again. Quick question, there is a way to stick to a driver version? So if something change with a new version you can stay in an old working one? Thanks in advance.
You can continue to use that driver as long as you have it installed on your hub, but no further changes or fingerprints will be updated to that driver.
That version uses LAN type child devices instead of EDGE type, which are what the default libraries handle now.
It was left so that they could use it with smart wifi hub, but it is no longer necessary with its latest firmware version.
It would be advisable to switch to the Mc driver whenever you want.
When you change it, you must delete the child device, if you have created it, and recreate it with the new driver. They are incompatible.
Perhaps this already exists. I’m looking for an edge driver for this stand alone switch (controller). I previously used the z-wave tweaker to set the association group. It directly controls other z-wave devices with the same association group. I preferred this method as there is lower latency than having the hub process the commands. The switch was branded by several manufacturers. One being NuTone NWD500Z, Linear/GoControls.
Just a note: @Mariano_Colmenarejo has an edge driver called the Z wave configuration tool that works in a very similar way to the old groovy Z wave Tweaker. Regardless of the edge driver you use for everyday use, you can temporarily assign any Z wave device to the Z wave configuration tool, then set the associations, then switch back to your everyday driver.
So if the edge driver you end up with for every day use does not itself expose the association groups, you can use the configuration tool to do that step:
Also, This won’t apply to the device you’re currently discussing, which is mains powered, but be aware that any batterypowered zwave device may only update its configuration parameters once or twice a day. So you won’t necessarily see an instant update. See the following community FAQ for more information about this issue if you are interested.
Added to this driver version.
You could create in settings preferences a virtual device to configure association groups and parameters.
When configuration was done then you can delete de virtual configuration device
Name Z-Wave Switch and Child Mc
- id: 014F/5457/3033
deviceLabel: GoControl Switch
In these data are not the necessary data.
From the “deviceProfileName”: “switch-binary” it seems that it is already paired with an edge driver and parede zwave.
If so, please install Z-wave Thing Mc on your hub and do a driver change to see all device data