After waiting 4 or 5 hours I got the following a battery operated device:
Itâs still asleep, it hasnât responded to the firmware read.
Your screenshot profile is the one of fingerprints info, in settings you have to choose the profile you need for parameters or associations.
when you hit Get or send you have to wake it up to answer, if itâs battery.
Thanks. Now I get the driver change without waiting and I see the settings options.
1 Like
I am trying to use the config to set wake up on Monoprice Contact Sensor but instruction suggest using âSetâ command but I only see âGetâ,âSendâ,âSelectâ. When I use the âSendâ and then use âGetâ it doesnt show the updated setting.
Yes, you must use Send to send the value to the device.
Once sent, the value is automatically read.
You should wake it up, generating an event or if they have some external button to wake it up, at the time of sending the new value
Thanks for the work on this driver, Mariano. Very cool.
I may be seeing the same problem as pmjoen.
Setting the default dimming level (parameter=36, size=1, value=99) for HomeSeer dimmer HS-WX300 (mains power). The HomeSeer driver doesnât have this configuration in its driver ⌠yet.
Following these instructions:
Got to the part in the instructions where driver is selected on the device, then selected Zwave Device Action = Device Parameter Configuration.
Error: âThis device hasnât updated all its status information. Check back later.â
Waited about 20 minutes. Tried exiting device in SmartThings app and re-entering it. Same error.
Tried quitting the SmartThings app and re-running it. Same error.
Finally, switched back to HomeSeer driver. Quit SmartThings App. Run and switch driver back to Z-Wave Device Config MC driver.
Error no longer appears!
Was able to set the parameter on the first device (Kitchen Table) and it worked!
However, it doesnât work for any other of my devices.
When I try and set the exact same parameters on another HomeSeer HS-WX300 device (e.g. Island), select âSendâ and then press âExecuteâ, the value changes from the â99â that I entered to â0â and the action changes from âSendâ to âGetâ. The parameter is not changed. 
I tried uninstalling the driver from my SmartThings hub and reinstalling, but still have the same problem.
Really appreciate your work. What do you suggest that I try?
Hi @Stone
The truth is, it is a very well done tutorial on how to use the configuration driver step by step. 
When you change the function, profile, it is essential to close the app and reopen it for iOS. On Android, just close the device and open it again.
When you send the command with the new value, the driver sends it and after 2 sec it reads the modified parameter to check if the value has been changed or not.
If it continues to show the old value, it may be for several reasons:
Is the size value correct? It is essential that it be correct.
If it is an AC powered switch, I donât think it is asleep, but could it be far from the hub?
The device may be bad. Try changing a different parameter and see the result.
Is would to see the logs with the CLI to see if there are any errors detected by the device.
You can use the Device Parameter Scan function and read the device parameters.
The speed with which the device responds and whether parameter values are lost can give you an idea of how the hub-device connection works.
Hi I am using this driver and it works well but I have a question. I have one Fibaro Dimmer 2 with a momentary switch (on S1) in my hall controlling 4 downlights, and I have another Fibaro Dimmer 2 controlling 2 downlights with no switch.
I want the second dimmer to mirror the actions of the first dimmer whenever the momentary switch on the first dimmer is pressed. When I look to create a routine to do this in ST I see that there are a LOT of possible actions for button1 but I dont know what they mean so it will be a bit hit and miss to get this working.
We have eg button 1 (shortened list):
pressed
double pressed
held
pressed 2 times
pressed 3 times ...
toggled down
held down...
toggled up
held up
Can anyone explain the difference between these different variants of held and pressed. Does for example âheld downâ mean the button is pressed and it is dimming down? Is double pressed and pressed 2 times the same thing?
Documentation for the momentary switch functions which I want to mirror for the second dimmer:
Momentary switch (after releasing the switch a spring automatically
pushes back and disconnects the switch):
- Turning the light ON/OFF: change the position of switch no. 1. The Dimmer 2 will be activated always at previously set brightness level,
- Brightening/dimming the light: hold switch no. 1 down. When the switch is held down, the Dimmer 2 will always reach the extreme value of 1% or 99%,
- Turning the light ON completely: fast double-click switch no. 1. The Dimmer 2 will set the load at 99%.
Are there any of the actions that can be used for each of the situations described in the momentary switch description?
Hi,
For what you want to do, I think it is better that you use the direct association of the wired dimmer with the dimmer you want to control.
In the manual you have what groups you have to use.
Group 2 sends on/off commands from wired S1 to associated devices
Group 3 sends multilevel switch commands from wired S1 to associated devices
If you are using my Z-Wave Switch and Child Mc controller
-
In the preferences of the wired device, which will send the commands, create the configurator device and it will appear in the room where the hub is
-
Find the zwave network identifier (node id) of the non-wired device. You can see it at my.smartthings.com advanced users. example: 1F, in hexadecimal.
-
In the child device configurator preferences, choose the Device Association Groups Configure option.
-
Close the device and relaunch it for the new profile to appear.
-
The steps to follow will be shown
- Write group number 2
- Write the node Id in hex for no wired device
- Write the endpoint: 1
- For these devices choose Multi Channel Device Association and follow the steps
- Choose the Set option
- Click on execute action
Repeat steps for group 3, multilevel switch
1 Like
brilliant, thanks.
Thanks so much for your help!
If it continues to show the old value, it may be for several reasons:
Is the size value correct? It is essential that it be correct.
Yes. The size for all parameters = 1 byte
If it is an AC powered switch, I donât think it is asleep, but could it be far from the hub?
AC powered. This device is in the same room as the hub. 31 Z-Wave devices in the house and communication is speedy. No connection problems.
The device may be bad. Try changing a different parameter and see the result.
You can use the Device Parameter Scan function and read the device parameters.
There is something strange going on here.
When I set the Parameter Size = 1 Byte, the Parameter Value allows values from -2,147,483,648 ~ 2,147,483,647.
Also, when I see the specific settings in the native HomeSeer driver and then compare them to what shows on the Device Parameter Scan, they arenât the same. Something is off. I can set a lower number parameter and it appears to work, but the higher numbers appear to be off.
Is would to see the logs with the CLI to see if there are any errors detected by the device.
This sounds very promising. Where can I find the logs?
Have you tried using the official edge driver provided by the manufacturer for this model? It has a number of complex features that interact in complex ways and you might get better results.
Hereâs the information on the manufacturerâs channel:
https://docs.homeseer.com/products/other-docs/homeseer-edge-driver-for-smartthings
And hereâs the support documents. Note that they specifically say there can be compatibility issues with smartthings unless you are using their edge driver.
https://docs.homeseer.com/products/lighting/hs-wx300/hs-wx300-r2-user-guide
Just as one example, this device has a âpower restoreâ feature, which is designed to return the dimmer to the value It was at when there was a power cut. That can lead to some of the weird values that you are seeing. 
1 Like
Hi,
The range of 1 Byte is 0x00 to 0xFF, (0 to 255).
The range shown by the capability value is not limited to the size value, it is the maximum or size 7, because in smarttings the range cannot be varied dynamically. The profile would have to be changed for each size with a specific presentation. Crazy.
The values sent by the driver for size 1 Byte are always signed, values from -128 to + 127.
To send you donât have to worry, the driver does the conversion to 2 complement.
When you read a 1 Byte parameter and a value > 127, you will see a negative value (value -256). I think it is explained in the original post.
Most modern devices use a size of 2 Bytes for values from 1 to 255 and avoid this problem.
Tell me what parameter and value you want to change and Iâll look at it in the documentation
1 Like
The manufacturerâs application will show what the numerical value means for better user understanding.
In smatthings, when there is a specific profile of the device preferences, the value is not shown to the user, the meaning of the value is shown.
This is a generic driver and should be used with the device documentation to understand what each value means and what values and format are supported or not.
Here is a tutorial on how to view and capture the logs with the CLI
1 Like
Hi JDRoberts. Thanks for taking the time to help out.
Have you tried using the official edge driver provided by the manufacturer for this model?
Yes, I have been using the HomeSeer Edge driver soon after it was available. As you can see in the on-line manual, the HS-WX300 is a really nice Z-Wave switch and has lots of parameters (e.g. each of the power level LEDs can be set to any color). While about 75% of the parameters are settable in the HomeSeer Edge driver, the one my wife cares about (setting the default dim level to 99% when you hit the top paddle instead of the last dim level) is not.
I contacted HomeSeer about adding that parameter to the HomeSeer driver, and they are the ones that pointed me to this driver solution by Mariano.
Thanks for sending the URL for the user guide. For the record, the R2 version of this switch just came out. The user guide for my R1 switch is:
https://docs.homeseer.com/products/lighting/legacy-lighting/hs-wx300-r1-user-guide
1 Like
The range shown by the capability value is not limited to the size value, it is the maximum or size 7, because in smarttings the range cannot be varied dynamically. The profile would have to be changed for each size with a specific presentation. Crazy.
That is crazy that the number canât be dynamically generated. The label makes sense to me now.
I will play around with the CLI and logs to see what I can learn. You and JDRoberts have been super helpful and I donât want to waste your time if I can figure it out. I have been doing SmartThings for over a decade, but havenât had to dive into the driver world too deeply until now.
For software, sometimes doing a complete âuninstallâ, âclear cacheâ, and reinstall fixes the problem. Not sure if this concept makes sense in the Edge driver world, but it just seems like my problem may be related to an error where the driver got kind of half-installed.
Just to rule it out, is there a way to completely uninstall the association with this device/account, clear out the settings, and re-install in the Edge driver world?
1 Like
Hi @Stone
You can perform a zwave exclusion to unpair it from the driver and smartthings hub.
Then, according to the manual, you can do a factory reset that will restore all the values to the default ones.
And add it back to the driver that you have installed on your Hub
1 Like
I have modified the screen with the steps to configure parameters to show the ranges of sizes 1, 2 and 4, which are the most used
| Z-Wave Device Parameter GET: 1- Enter Parameter Number. 2- Select GET Command Option. * 3- If device is Asleep: Awake device manually. 4- Press Action Button. 5- Parameter Value & Size will be shown Negative Values can represent the 2's Complement of a positive value: Example, value -1 (Size 1) is positive value 255 (-1 + 256) Z-Wave Device Parameter SEND: |
1 Like
@Mariano_Colmenarejo, thanks for pointing me to the CLI. Lots of great info there. I spent a number of hours trying to solve the problem, but am still a bit stuck. The log files didnât show any issues that I could see, so I excluded the device, factory reset, and enrolled the device.
Using the SmartThings app, I then changed the driver on the device to Z-Wave Device Config Mc. Then Settings > Device Parameter Configure.
Then I started streaming the logs from the driver using the CLI:
smartthings edge:drivers:logcat 7ca45ba9-7cfe-4547-b752-fe41a0efb848
On the SmartThings app, I set the parameters:
Device Parameter Number = 36
Parameter Size = 1 Byte
Parameter Value = 99
Select Config Parameter Action = Send
At this point, the SmartThings app gave me the error:
A network or server error occurred. Try again later. OK
(I have a screenshot of this error if desired)
I then tried Execute Selected Action. The parameter is not set.
Below are the logs that were running when this error occurred. I could see no mention of the error in the logs.
2023-09-18T03:03:57.374987560+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:03:57.378347227+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"setDeviceParameter","capability":"legendabsolute60149.deviceParameter","positional_args":[36],"component":"main","args":{"value":36}}
2023-09-18T03:03:57.386300352+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:03:57.387002477+00:00 PRINT Z-Wave Device Config Mc <<< device_Parameter: 36
2023-09-18T03:03:57.387620852+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":36},"component_id":"main","capability_id":"legendabsolute60149.deviceParameter","attribute_id":"deviceParameter"}
2023-09-18T03:03:57.396337518+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:04:45.192135590+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:04:45.195521632+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"setDeviceParameter","capability":"legendabsolute60149.deviceParameter","positional_args":[36],"component":"main","args":{"value":36}}
2023-09-18T03:04:45.206295924+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:04:45.206983090+00:00 PRINT Z-Wave Device Config Mc <<< device_Parameter: 36
2023-09-18T03:04:45.207602174+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":36},"component_id":"main","capability_id":"legendabsolute60149.deviceParameter","attribute_id":"deviceParameter"}
2023-09-18T03:04:45.209765382+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:04:54.987837171+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:04:55.015814588+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"setParameterSize","capability":"legendabsolute60149.parameterSize","positional_args":[1],"component":"main","args":{"value":1}}
2023-09-18T03:04:55.019757088+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:04:55.020409838+00:00 PRINT Z-Wave Device Config Mc <<< parameter_Size: 1
2023-09-18T03:04:55.021023713+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":1},"component_id":"main","capability_id":"legendabsolute60149.parameterSize","attribute_id":"parameterSize"}
2023-09-18T03:04:55.026847963+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:05:04.007754586+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:05:04.024144503+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"setParameterValue","capability":"legendabsolute60149.parameterValue","positional_args":[99],"component":"main","args":{"value":99}}
2023-09-18T03:05:04.024925128+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:05:04.025637128+00:00 PRINT Z-Wave Device Config Mc <<< parameter_Value: 99
2023-09-18T03:05:04.026272836+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":99},"component_id":"main","capability_id":"legendabsolute60149.parameterValue","attribute_id":"parameterValue"}
2023-09-18T03:05:04.027845127+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:05:09.632720584+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:05:09.642461668+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"setCommandConfig","capability":"legendabsolute60149.commandConfig1","positional_args":["Send"],"component":"main","args":{"value":"Send"}}
2023-09-18T03:05:09.644701626+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:05:09.645400126+00:00 PRINT Z-Wave Device Config Mc <<< Config Command: Send
2023-09-18T03:05:09.646104584+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":"Send"},"component_id":"main","capability_id":"legendabsolute60149.commandConfig1","attribute_id":"commandConfig"}
2023-09-18T03:05:09.655872084+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
A network or server error occurred. Try again later. OK
2023-09-18T03:06:07.031205071+00:00 TRACE Z-Wave Device Config Mc Received event with handler capability
2023-09-18T03:06:07.045771779+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(a290a0f8) queued for radio transmission: CC:Configuration, CID:0x04
2023-09-18T03:06:07.047622779+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received command: {"command":"push","capability":"legendabsolute60149.actionbutton2","positional_args":{},"component":"main","args":{}}
2023-09-18T03:06:07.048400237+00:00 TRACE Z-Wave Device Config Mc Found CapabilityCommandDispatcher handler in zwave_thing
2023-09-18T03:06:07.049052237+00:00 PRINT Z-Wave Device Config Mc <<< Action_button: nil
2023-09-18T03:06:07.049667529+00:00 PRINT Z-Wave Device Config Mc new_parameter_value Sent >>>> 99
2023-09-18T03:06:07.050282404+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> sending Z-Wave command: {args={configuration_value=99, default=false, format=0, parameter_number=36, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x24\x01\x63", src_channel=0, version=3}
2023-09-18T03:06:07.058792821+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(b772642b) queued for radio transmission: CC:Configuration, CID:0x05
2023-09-18T03:06:07.059289321+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> sending Z-Wave command: {args={parameter_number=36}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="$", src_channel=0, version=1}
2023-09-18T03:06:07.107963112+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:06:07.110996612+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:06:07.164119154+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(a290a0f8) transmit status: TRANSMIT_COMPLETE_OK
2023-09-18T03:06:07.321314987+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(b772642b) transmit status: TRANSMIT_COMPLETE_OK
2023-09-18T03:06:07.331177946+00:00 TRACE Z-Wave Device Config Mc Received event with handler unnamed
2023-09-18T03:06:07.331630112+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> received Z-Wave command: {args={configuration_value=0, parameter_number=36, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\x24\x01\x00", src_channel=0, version=1}
2023-09-18T03:06:07.338527696+00:00 TRACE Z-Wave Device Config Mc Found ZwaveDispatcher handler in zwave_thing
2023-09-18T03:06:07.343548196+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":36},"component_id":"main","capability_id":"legendabsolute60149.deviceParameter","attribute_id":"deviceParameter"}
2023-09-18T03:06:07.348131112+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":0},"component_id":"main","capability_id":"legendabsolute60149.parameterValue","attribute_id":"parameterValue"}
2023-09-18T03:06:07.358065779+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":1},"component_id":"main","capability_id":"legendabsolute60149.parameterSize","attribute_id":"parameterSize"}
2023-09-18T03:06:07.408672196+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
2023-09-18T03:06:09.083005445+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: e70bc385-a3a8-4fa7-87be-db0ebfab5f14 [2F] (Dining Room)> emitting event: {"visibility":{"displayed":false},"state":{"value":"Get"},"component_id":"main","capability_id":"legendabsolute60149.commandConfig1","attribute_id":"commandConfig"}
2023-09-18T03:06:09.089370654+00:00 DEBUG Z-Wave Device Config Mc Dining Room device thread event handled
Trying to set the parameter again doesnât result in the Network Error, but also doesnât work.
I also tried setting the same parameter on another identical device. Didnât get the network error, but also didnât get the parameter set.
It just seems like there is some kind of miscommunication between the driver and hub that isnât being logged.
What would you suggest that I try next?
Hi @Stone
That network error is not important for this.
The value is sent correctly and read correctly, the only thing is that the 2 sec delay is not executed between sending the parameter and reading it.
I have made a new version of the driver ensuring that the delay is executed.
With the CLI command smartthings edge:drivers:install you can install the new version dated today, September 18.
The CLI is not working well for me today and I cannot get the date and time of the new version.
You can also try changing a different parameter or with another value less than 99.
1 Like