I can’t seem to remove this device handler. (For testing some stuff with homeassistant)
I remove the switch from smartthings, go to the IDE and delete the device handler, go back into the app and add the device back…and it still shows the screen with the buttons for double and triple taps.
How do I get rid of this thing?
Impossible to believe that these don’t yet have a native devicehandler and local execution. Samsung too busy destroying the mobile app to get serious about this platform, I guess.
After an unfortunate incident as a result of the terrible new SmartThings app (it just decided to delete my hub and perform a hard reset while doing nothing but adding an automation), I have had to start all over from scratch, setting up everything like it’s all brand new.
I have two WS100+ switches that worked without a single error or disconnect in the last year or so. Adding them back to SmartThings (with the manual reset process) has been fine, and it discovers them as generic Z-Wave Switches. They toggle on and off and work great… until I switch the DH to this one (which was the same one I was using before without fail). The first remote push works fine, but each subsequent on/off push gets more and more delayed over time to the point where the switch no longer responds to remote inputs. If I manually push the button, it resets the delay and instantly reflects the change in the app, as long as it hasn’t gotten to the point of no response. This is the case with both switches, in opposite ends of the house. They both exhibit the same behavior. Switching back to a generic Z-Wave Switch DH does nothing after they’ve become unresponsive - they have to be reset and re-added in order to work properly again.
I have tried a Z-Wave repair without success. I have also not installed ABC or added the switches to any automations or apps, so there are no apps interacting with the switch. I am also only dealing with single presses at the moment (no double/triple/hold actions).
I’ve read through this thread at least a dozen times and searched for hours on end. Anyone experienced the same issues? I need to get these back up and running!
@dougc84 - I’m also scratching my head on this one, but happy to take a look. If you haven’t already, can you hit configure in the mobile UI after switching over to the WS100 device handler? I don’t necessarily believe that will fix the problem, but for some reason, the old device fingerprint is no longer being recognized when the switch is being added to the hub, so the configure operation is no longer happening automatically. I just received a report on that and will update the code shortly.
Would you be able to PM me grabs from the live logging tab in the IDE while it is experiencing the issue with the switch toggling? Thanks.
@Darwin I don’t understand - which “configure” option are you talking about? I can hit the gear/settings page in the top right of the screen, but there’s nothing here to really do.
I don’t have a lot of time to deal with it until early next week, but I’ll happily do the live logging thing then and send it over.
Sorry - I should have said “refresh” instead of configure. That will trigger a configure call. Only the dimmer GUI has the configure button.
I tried this last night but… it seems everything is humming along ok at the moment. I’ll keep an eye on it over the next couple days but it might have just been some weird and incredibly coincidental Z-Wave issue. I’ll post logs next week if it continues.
Weird issue with my ws-100s. When I hold down (long hold) on the down button the switch turns off. Isn’t it only supposed to do that when I short tap down? I set long hold to do something through smartthings but I didn’t want the light going off as well.
Is this supposed to be how it works?
I recently received two more WD100+ to add to my hub, but they came with a weird firmware version v50.3. On/off locally and remotely works just like all of my other WD100+ with v5.17 on them but I cannot change any of the device handler properties. For example, I tried to speed up the ramp rate, saved, and pressed ‘configure’ but the switch stays on it’s default slow ramp. Anyone else seeing this issue?
That’s how all mine work also, I only use the long press to turn off/on other light along with the wired light, and use the taps to control other lights/devices.
I would like to know if any new firmware has fixed this issue though.
You might be seeing an issue related to this bug: Bug in ST Android Mobile App - invalid input in preferences in DTH
Are you on an Android mobile device and if so, can you view live logging while you are saving preferences to see if you are getting an exception? If there’s still an issue with SmartThings, I can workaround this in the device handler.
I am using the android app, but I don’t see an exception in the logging when I change a preference and save:
dfd66d90-16c0-483a-b52a-3631db286580 12:49:02 AM: debug zw device: 1B, command: 2603, payload: 63 63 00
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug Parse returned [descriptionText:Firmware V50.3, isStateChange:false, displayed:false, linkText:Basement Lights]
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zWaveProtocolSubVersion: 1
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zWaveProtocolVersion: 6
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zWaveLibraryType: 3
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug applicationSubVersion: 3
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug applicationVersion: 50
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug received Version Report
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zw device: 1B, command: 8612, payload: 03 06 01 32 03 FF 00
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug Parse returned [[name:switch, value:off, isStateChange:false, displayed:false, linkText:Basement Pool Table Lights, descriptionText:Basement Lights switch is off]]
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zw device: 1B, command: 2603, payload: 00 00 00
dfd66d90-16c0-483a-b52a-3631db286580 12:48:46 AM: debug zw device: 1B, command: 2603, payload: 00 00 00
dfd66d90-16c0-483a-b52a-3631db286580 12:48:44 AM: debug set prefs
dfd66d90-16c0-483a-b52a-3631db286580 12:48:44 AM: debug configure() called
dfd66d90-16c0-483a-b52a-3631db286580 12:48:44 AM: debug refresh() called
dfd66d90-16c0-483a-b52a-3631db286580 12:48:44 AM: debug refresh() called
I am having a problem getting this Dimmer paired. I just purchased one of the new SmartThings Hubs (v3 / 2018) and it’s unable to detect my HomeSeer WD100+ Dimmer – there is no option under “Switch/Dimmer” for HomeSeer.
From what I can tell, the latest version of the App doesn’t really have a button to force it to look for generic devices. When I go to “Add a Device” it spins and says it’s looking for devices (no matter how many times I hit the up/down paddles to try to trigger a connection), and the green light on the front of my Hub v3 doesn’t blink like it does when I’ve selected a specific device to look for. Further, because I can’t select to “look for a HomeSeer Dimmer” I can’t get it to blink/attempt to look.
I have already tried doing the manual reset on the HomeSeer switch (on // 3 up // 3 down // off) but that hasn’t worked. I’ve also added the WD100+ Device Handler listed here to my web console (however, oddly, my Hub does not show up in the Web Console…)
I’m feeling like I’m going crazy here – these are the first dimmers I’ve found that don’t make my lights flicker, and now I can’t get them paired with my Hub!! Is this an issue with the Hub v3? Latest version of the App? any help would be greatly appreciated…
I had a weird issue while adding my most recent WD100+ too. I went to ‘Add a Device’, pulled the airgap pin on the WD100+, pushed it back in, then did the manual reset sequence (make sure that the light goes off or flashes). They never showed up in the ‘Add a Device’ dialog like all of my other ones, but did get added to the ‘Things’ tab as a ‘Z-Wave Dimmer Switch’ device. I had to go into the IDE and manually set them to the WD100+ device handler and rename them before they would work correctly. Hope that helps.
Thanks @bisrael8191 – I will give that full process a try, I haven’t played with the air-gap switch at all. Also, I don’t recall seeing the lights flash when I did the manual reset, maybe my timing is bad…
Question: where is the “Things” Tab in the App? do you mean “Devices”? When you say they “got added” to that Tab, they just showed up by themselves?
In the Android smartthings app, under My Home, there is a tab called Things that lists out every device regardless of what room it’s in. And yes, they just showed up by themselves without going through the normal add process.
I had to try the reset taps a few times to get it to work. The dimmers turn off when done correctly and is pretty obvious when it works.
From what I’ve been reading on these forums and the ST Facebook group, any custom DTH may only work in the SmartThings Classic app…you might do some digging in that.
Thanks for the info - I think the mismatch here is that I’m using the App “SmartThings (Samsung Connect)” and not the App “SmartThings Classic”. I tried to use the Classic App, but I can’t get past the initial “Hello! Enter Code Here” page because my Gen3 Hub doesn’t come with a code, and there’s no way to bypass that screen in the Connect App without entering a code first…
So, in the SmartThings Samsung Connect app, I don’t have the same tabs that you’re describing, and even after following all the steps to reset my HomeSeer Dimmer multiple times (light went off and back on, as described) and place it into pairing mode, it’s not getting picked up during the generic ‘Looking for Devices…’ cycle.
Anyone had any luck using this Samsung Connect App? (or for that matter, bypassing the “Enter Code here” screen on the Classic App without having a code?)
Got this working finally!! Answering my own issue here:
Unfortunately, this means that for any user new to the ecosystem (and purchasing the latest version of Hub hardware + HomeSeer devices), the out-of-box setup process requires two different Apps plus the web console, used in the exact right order. This is… not intuitive. Hopefully Samsung / SmartThings get’s their new/old Apps playing a bit friendlier with their latest Hub soon!
Not sure what happened, but my WD100+ v50.3 devices are able to set their ramp rates and configure correctly now. I don’t think my classic android app or the device handler changed versions (I did update my phone’s android version to Pie). Hopefully all the magic stays working and I can move on to other automation. Thanks @Darwin!