Are you giving them your own network IDs in the old Groovy IDE? If so, that won’t work. They’re assigned a node ID by the hub’s z-wave radio, and that’s the only one that matters. That’s the one you’ll find in the CLI.
1 Like
Ok, much appreciated on all the help, I have it working now. Multiple issues here. Network Ids have to be gotten from the CLI now, and I had a lingering device handler associated with the switch type I was able to comment out. Then exclude and include and boom they work. Thank you for the advice, really appreciate it!
4 Likes
I have another variant of the GE/Jasco 14284 “Plug-In Outdoor Smart Switch”. Here are the full details:
deviceId: ********-****-****-****-************
name: Switch
label: Sparkle
deviceManufacturerCode: 0063-6363-3130
manufacturerName: SmartThings
deviceModel: 6363-3130
presentationId: SmartThings-smartthings-Z-Wave_Switch_Generic
locationId: ********-****-****-****-************
roomId: ********-****-****-****-************
sharedLocations: []
components:
- id: main
label: Sparkle
capabilities:
- id: switch
version: 1
- id: polling
version: 1
- id: refresh
version: 1
- id: sensor
version: 1
- id: actuator
version: 1
- id: healthCheck
version: 1
- id: light
version: 1
categories:
- name: Switch
categoryType: manufacturer
- name: Light
categoryType: user
icon: oneui/oic.d.light
createTime: '2022-08-31T23:34:52.856Z'
parentDeviceId: ********-****-****-****-************
dth:
completedSetup: true
deviceNetworkType: ZWAVE
deviceTypeId: d22d3280-a358-4ab3-b6cd-710da4d068d0
deviceTypeName: Z-Wave Switch Generic
executingLocally: true
hubId: ********-****-****-****-************
networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE
type: DTH
vid: SmartThings-smartthings-Z-Wave_Switch_Generic
mnmn: SmartThings
ocfDeviceType: oic.d.switch
restrictionTier: 0
allowed: []
Thanks very much for your terrific Edge drivers - I have been able to move all my other Jasco devices to the new system without any trouble. I am grateful to you.
Thank you, thank you, thank you, @philh30, this is excellent! I’ve been able to move my Jasco/GE switches and dimmers over to Edge drivers now. I did pick up a new one this week with a fingerprint you don’t list: 0063-4944-3132. It’s just the latest almond color dimmer. Please let me know if you need any more information! Thanks again for contributing to the community!
1 Like
How about GE Smart Outdoor Plug In Switch (ZW4201) 0063/6363/3130
Thanks
Appreciate the work you have done! I need some basic help in using your driver.
I have an old groovey DTH that will be non-functional with the end of the groovey environment. I have enrolled and installed your driver (GE Z-Wave Switch/Dimmer/Fan/Outlet) on my home hub. Now how do I connect it to my GE/Jasco 14292 switch?
Now: “If your device is currently using a Groovy DTH, you will need to exclude and then add it back to SmartThings to pick up this driver.”
ok - I can do that.
But - where do I then see this edge driver attached to the re-added dimmer switch? Within the Smartthing mobile app?
And…“If you have any custom Groovy DTHs installed that have the device’s fingerprint, either delete the DTH or comment out the fingerprint before attempting to re-join the device.” Well? I have several more GE Jasco dimmer switches that use the same groovey DTH (which I will have to convert over…to a new driver). Do I need to delete and re-add all the switches - just to test one switch? These dimmer switches only use the one groovey DTH.
Thanks in advance for your help to this novice!
Dave
Appreciate the work you have done! I need some basic help in using your driver.
I have an old DTH that will be non-functional with the end of the groovey environment. I have enrolled and installed your driver (GE Z-Wave Switch/Dimmer/Fan/Outlet) on my home hub. Now how do I connect it to my GE/Jasco 14292 switch?
If a device joins with an Edge driver, you should see a “Driver” option in the app when you tap on that 3-dot menu in the top right corner (beneath Edit and Settings but above Information). If you tap on that menu too quickly after navigating to the device it may not immediately show. You should also see the device listed as “Placeholder” device type and “Cloud” execution in the Groovy IDE. Ignore what it says about cloud execution - the Groovy IDE hasn’t been updated to understand that Edge is local.
You’ll need to comment out any fingerprints in your custom DTH. The fingerprint in the DTH is only used when the device is being included, and doing this won’t hurt your existing devices. Near the top of the DTH, in the metadata section, you might have lines that look like this:
fingerprint mfr:"0084", prod:"0053", model:"0216", deviceJoinName: "FortrezZ Temperature and Leak Sensor"
Just add // to the beginning of each of those lines like this:
// fingerprint mfr:"0084", prod:"0053", model:"0216", deviceJoinName: "FortrezZ Temperature and Leak Sensor"
Save and publish the DTH. After you’ve paired the one switch to Edge, you could go back and remove the //, but it’s not necessary for your other devices to continue functioning.
1 Like
ok - so here is where I am at:
Yes, I see the "driver: option in the mobile app. That is good news. I see a “settings” option. That is good news. Yes, I see in the Groovey IDE has changed from the custom DTH to the “PlaceHolder” and “Cloud” comments. That is good.
No:
fingergerprint mfr:“0084”, prod:“0053”, model:“0216”, deviceJoinName: “FortrezZ Temperature and Leak Sensor”
in the custom DTH.
Also, if I change the “numbers” in the settings 1 to 255 or 1 to 9 or 9 to 1 or 255 to 1 (in all the settings as appropriate) there is no change in how the light reacts. It dims or brightens t the same speed. I am looking for “on” or “off”. (Yes I should have just installed a on/off switch…but years ago - that was not the thought.)
Update: There is a fingerprint line as shown here:
Blockquotemetadata {
definition (name: “Enhanced Dimmer Switch”, namespace: “desertblade”, author: “Ben W.”) {
capability “Switch Level”
capability “Actuator”
capability “Indicator”
capability “Switch”
capability “Polling”
capability “Refresh”
capability “Sensor”
command "updateSettings"
fingerprint inClusters: "0x26"
}
standing by…
Good! That means your device is using a driver. No need to worry about fingerprints in the DTH then.
I assume with your old DTH you saw a real change in the dimming speed from changing these parameters? All of my dimmers are either newer or the motion variety, so I don’t have a similar model to yours to compare.
All good feedback! Thanks!
Yes - under the old DTH, when I set the values I could get a near instant on / off reaction.
But, here the values have no effect.
Hmmm? So my, some of my GE/Jasco dimmer switches are 3 or maybe even 4 years old. So I either need to replace my dimmer switches (that would be like 15 or so - ugh!) with newer models (?) or ? do I dare say, investigate another option?
No before I do anything, what should I set the various values to, in order to get a more instant on / off reaction?
THanks!
Let me look into things. I’m seeing a discrepancy in the byte length shown for those parameters in the DTH you were using (1 byte) versus other DTHs and documentation I’ve seen (2 bytes). If the command to set those parameters uses the wrong byte length, the command is ignored. I’m guessing that’s what happening here, and that’s it’s just an inconsistency between different models (or even firmware versions of individual models). I’m throwing something together that will let us verify what your device expects.
Don’t worry - this shouldn’t be a complicated issue to solve!
1 Like
Most excellent ! Standing by ! 
1 Like
Any thoughts on adding Param16 for dimmers version 5.26 or higher for switch mode?
Sorry if it’s been explained already l but searching wasn’t finding it.
In order to take advantage of double abs triple tap control, how do I find the Hex ID for devices once’s I’ve transitioned them to edge drivers?
That one and Param20 have been requested and are on my list to add. For simplicity’s sake I probably won’t tie them to firmware version, they’ll just be available to any device in that generation even if the device has older firmware and won’t support it.
Here are two options:
- The Command Line Interface (CLI) is the new way to view device information, but it requires a computer and a bit of technical skill. It’s worth setting up if you’re able since it’s the only way to view logs. Download the most recent release from the Assets section here, open a command prompt window and run
smartthings devices, then find the number next to the device you’re interested in (let’s say it’s 5) and runsmartthings devices 5. You should seeNetwork Idin the output with the hex node ID. - For an easier, though unofficial, way that works even from a tablet or phone, @lmullineux has put together a web interface to view device info pulled from the API. Follow his instructions here. You’ll need to create a token, but can give it minimal permissions (list and see devices; see locations) and can delete it afterwards. Just click on the Info button next to your device and look for the Network Id in the list.
2 Likes
Philh30 – following up to our discussion on Sept 26:
BlockquoteLet me look into things. I’m seeing a discrepancy in the byte length shown for those parameters in the DTH you were using (1 byte) versus other DTHs and documentation I’ve seen (2 bytes). If the command to set those parameters uses the wrong byte length, the command is ignored. I’m guessing that’s what happening here, and that’s it’s just an inconsistency between different models (or even firmware versions of individual models). I’m throwing something together that will let us verify what your device expects.
Don’t worry - this shouldn’t be a complicated issue to solve!
Something has changed in the system (Thank you?). When I turn on the bedroom light at the wall switch – either on or off, the reaction is immediate – which is great!
I am looking for this same behavior from the app or motion sensor – instant on/off.
When I turn on/off the same bedroom light via the SmartThings app or a motion sensor, the light slowly comes on or goes off.
The settings in the app are:
It does not matter what the numbers are for the Zwave – the on/off diming speed of the light does not change.
The “manual” numbers allow the instant on/off function which is great.
I am not sure what the “All-On/Off” setting is.
What am I doing wrong?
What do I need to change?
Your help is appreciated.
There’s a setting to set the dimmer to switch mode (for physical control only) that can be enabled with a switch tap sequence. I haven’t pushed a driver update yet, so you’ve managed to enable it. Or it could be the manual steps/timing settings taking hold if you have them set to 99 and 1 as in your screen shot.
I’ve got this figured out. What’s happening is that the default commands that are sent for on/off include a “duration” parameter set to 1 second, and that overrides any of the settings on the device. I have one switch (my motion dimmer) that has the same dimming steps/timing settings as yours, and I now have it obeying the device settings, including flipping on/off immediately. I just need to do a bit more testing before I can push out the update to the driver.
Funny, @krlaframboise just identified the same issue in troubleshooting ramp rates on one of his drivers…
I am having an issue and am unsure if others are experiencing the same. The problem happens with both the stock drivers and these custom drivers. Here is the scenario:
- In my living room, I have two motion sensors (Fibaro, ZW5)
- Two sets of lights, two switches (6 ceiling cans and two spotlights). Both are on Honeywell dimmers.
- A single routine is set that when ST senses motion (any condition), it sets only the cans to 50% brightness for five minutes.
Here’s the experience:
- The lights turn on to 50%, then drops by ~5%
- When the motion sensors exit the blind period, the routine resets the lights to 50%, then they immediately drop another ~5%
- This cycle continues as long as there is motion in the room.
- I have tried this routine with one motion sensor, but I still had the same experience.
I thought I would be able to catch the 5% drop in the app, but when looking at the device in the ST app, the brightness level does not show any shift from the set of 50%. The rest of my house is GE Enbrighten dimmers and switches, and I do not experience this issue.
Any thoughts on why this would be happening?