In devices that do not support theWAKE_UP Command Class, a message will be displayed stating that this Command Class is not supported and will not execute anything.
If the Command Class WAKE_UPis supported you can read the current value of the WakeUp interval or set a new one within the range allowed by the Zwave and device specification.
As these devices are usually asleep, both Get and Set have to be woken up manually according to the documentation.
If we select the Get or Set values and the new interval in seconds, when we wake up the device the code to sending of the Get or Set command will be executed automatically.
Added help instructions with steps to follow in all profiles in the Device Info capability. These instructions are shown when the profile is initialized or a refresh is performed in the App
These improvements will be added to the device config subdrivers in the Z-Wave Sensor and Child Thermostat CONFIG driver and the steps help in the Z-Wave Switch and Child Mc driver since the wake Up interval is not needed here.
This is the new driver version
───────────────────────────────────────────────────
Name Z-Wave Device Config Mc
Version 2023-04-01T15:57:38.628606474
───────────────────────────────────────────────────
Hi Mariano - Does this driver have support for the Enbrighten Z-Wave Plus IN-Wall Smart Dimmer, No Neutral, LED-CFL 52252? I couldn’t find it in the fingerprint section, but just wanted to double check with you. Thanks
If you already have it paired with the stock driver you can install and change to Z-Wave Device Config Mc to configure device.
In order not to lose the routines and scenes you have made, you could also install and change to Z-Wave Switch and Child Mc, which has the option to create a configurator virtual device.
Once device configured, delete it and you can change back to the stock driver
Hi. Thanks for all the great edge drivers. I’m trying to use the Device Config Mc to associate two Inovelli switches together but when I change the driver of one to Device Config Mc and then exit and reenter the device screen instead of the expected interface I see a Device Info block of text starting with “Z-Wave Device:”. My iOS SmartThings app is v1.6.98.2. I tried iswitching the driver back and forth a couple times, restarting the app and rebooting the hub. Any idea what the issue might be ?
I have 2 shutters from fakro and 1 remote. All the three devices work with zwave. Can I add them to Smartthings with this driver?
The screenshot has the information i get from the remote.
The Z-Wave Device Config Mc driver is used to configure parameters of a Z-Wave device not exposed by stock or other custom Edge drivers. It can’t be used as the normal, operational device driver. If a stock Edge driver isn’t installed when you add the device(s), you’ll need to see if a developer has added the fingerprints for your device(s) to their custom window treatment Edge drivers.
I just migrated to Smartthings (Aeotec Smart Home Hub) and I’m trying to configure my Fibaro Switches (eg. FGS-221) to work with Smartthings.
Based on the existing discussion I managed to set the parameters as they should be (Momentary switch). When controlled from the smarthings app, everything works flawlessly.
However, when I manually flip the switch, Smartthings does not notice the state change (and thus fail to trigger scenes) until I manually refresh the device in the app (drag down on the device page). I have tried the Z-Wave Switch driver (default when adding the switch via scan) and Z-Wave Switch Child Mc driver (both via installing the driver from beta channel and by manually selecting Fibaro switch model when adding the device).
Is there any driver or way that would allow the hub to proactively notice the status updates sent by the switch and trigger scenes accordingly? Perhaps @Mariano_Colmenarejo would know, as you seem to be the author of the drivers?
When this device was added it worked correctly and I have not heard from other users that it did not work for them.
The stock drkver should not work for the 2 relays, only for one, since their fingerprints are not in the driver.
This device uses association group 3 to communicate with the hub.
If you didn’t pair it directly with my controller, that group 3 association with the hub may not have been set up.
You can create the configurator device and check and make the association of device group 3 with the hub (node id: 1)
I tried refreshing the device many times. I also opened and closed the window several times. Neither made any change.
I will leave it set to your driver until tomorrow to see if it eventually changes.
I don’t currently have access to my laptop, so I can’t run logs. In a couple days if it is not resolved, I will have access to my laptop and will run logs.
Thanks for replying.
Edit: I am able to switch to @philh30 's “z-wave explorer” without any issues.
Uninstall old version and install this new version
If it works, I’ll tell you what happened
───────────────────────────────────────────────────
Name Z-Wave Device Config Mc
Version 2023-08-28T16:32:51.012831031
───────────────────────────────────────────────────
I have tried with the old version and I get the same result as you.
I have tried with the new version and in a fibaro button I have to wake it up so that it responds and the data appears.
If I switch to parameters scan I have to wake it up to respond to the parameters scan.
The old version didn’t work because smartthings has changed the order of lifecycles when a driver change is made.
The normal cycle was init, added, driverSwitched and in driver in init first assigned the correct profile and then executed the added lifecycle, which depended on the device profile.
Now, it first performs added and is missing some profile data since the init cycle was not performed.
uninstall the old version and install the new one
Change to this driver first the mains powered device
───────────────────────────────────────────────────
Name Z-Wave Device Config Mc
Version 2023-08-28T18:01:27.884302431
───────────────────────────────────────────────────
