I’m not able to get the additional button features to work in the newest Samsung update (May or June 2021?). They worked prior to that point. Is there another update to the code needed, DarwinsDen?
]]>I wasn’t sure what to do with those instructions either but the pull request spelled things out more clearly. The lines in red are the ones being changed or removed, and the green lines are the ones being added/replacing them. I found that while Automations still don’t work properly in the new app (I don’t think this device handler was designed to do that), the Smart Lighting app DOES work, since double/triple taps are mapped to button 3, 4, etc. Button 3, 4, etc are selectable within the Smart Lighting app. So, I’m able to get my scenes working again.
]]>Hi! Thanks so much for writing this DTH! It has worked great for the two years I have been using it. I switched over to the new Smartthings App yesterday and I can’t get the double, triple tap, etc to work anymore. Looks like Mike Rossman figured out the code issues? I am not a programmer, where do I find the code with those changes in it? Also, I am having the same problem with my wd200+ dimmer switches. But I was using the HomeSeer DTH for those. Haven’t checked their site to see if they posted an update to work with the new app yet. Is there a better DTH I should be using for those switches with the new app? Thanks again! -Brian
]]>Thank you! I’ve merged in your Github pull request for the WS100+ Device Handler Very much appreciated.
]]>Here’s the fixes:
1. Remove the unicode triangle characters from descriptions.
2. Add this function:
private getSupportedButtonValues() {
def values = [“pushed”, “held”]
log.debug (“getSupportedButtonValues() called”)
return values
}
3. Update the configure function adding:
sendEvent(name: “supportedButtonValues”, value: supportedButtonValues.encodeAsJSON(), displayed: false)
Sorry about that. I had a git pull/merge issue. Please grab the code again from the repository.
]]>Org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: script_dth_metadata_65cc1e47_a8b3_46e8_b9ab_c0df9a8c06f5: 300: The method public java.lang.Object setLevel(java.lang.Object value, java.lang.Object duration) { … } duplicates another method of the same signature . At [300:1] @ line 300, column 1. def setLevel(value, duration) { ^ script_dth_metadata_65cc1e47_a8b3_46e8_b9ab_c0df9a8c06f5: 280: Repetitive method name/signature for method ‘java.lang.Object setLevel(java.lang.Object, java.lang.Object)’ in class ‘script_dth_metadata_65cc1e47_a8b3_46e8_b9ab_c0df9a8c06f5’. @ line 280, column 1. def setLevel (value, rate=null) { ^ script_dth_metadata_65cc1e47_a8b3_46e8_b9ab_c0df9a8c06f5: 300: Repetitive method name/signature for method ‘java.lang.Object setLevel(java.lang.Object, java.lang.Object)’ in class ‘script_dth_metadata_65cc1e47_a8b3_46e8_b9ab_c0df9a8c06f5’. @ line 300, column 1. def setLevel(value, duration) { ^ 3 errors
Thanks!
]]>When you get ready to try out the upgraded speed and reliability found in standalone local control a Hubitat system provides and want to port over this excellent ST device handler to a Hubitat driver make sure to post up in the Hubitat forums and I would love to help beta test the driver for you.
]]>Hi David. The WD100 device handler has a capability Actuator show this should show up when you add devices under WebCore->Settings->Available devices->Which actuators. I can’t say I’ve seen this issue before. The WD100+ should also show up as an option in WebCore under “Which dimmers and dimmable lights”. Are you able to add the device to WebCore using that option?
]]>Any insight would be appreciated!
Thanks!
Any ideas as to why this might be?
]]>I’ve been keeping an eye on Hubitat, but haven’t yet pulled the trigger on giving it a trial review. Despite the occasional hiccup, I’ve been fairly content with SmartThings reliability for my basic home operation needs and the HomeSeer controller works well for me for mission-critical, near real-time operations.
That said, as I delve into electric utility demand management, I am moving into an arena where even a short half hour internet or SmartThings server outage could end up costing several hundred dollars in utility demand charges. Porting my demand management smart App to Hubitat may be the perfect solution. I’ll certainly post here if I end up getting a Hubitat and delve into operations with the HomeSeer 100+ and 200+ lines.
]]>Hi Kyle. Great news! I was contacted by HomeSeer and informed that they have already created a SmartThings device handler based on my code for the WD100+. Their commitment to the SmartThings platform is impressive. Since its based on the previous handler code, existing SmartApp rules should work as-is if the device is swapped in place for a WD100+.
The new WD200+ device handler can be found here: http://helpdesk.homeseer.com/article/177-smartthings-handler-wd200. I plan on reviewing this switch at some point, and will be happy to make any suggested tweaks to their device handler if anyone has suggestions.
]]>It worked! Thank you for the quick response. Now to confirm the taps!
]]>Hi Rolis. It appears the code being selected may be incomplete for some reason. Try hitting the “Raw” button to the upper right of the code block on GitHub and then select edit->select-all and copy that before pasting into the SmarthThings IDE. Hope this helps. Let me know it goes.
]]>Thanks for the info! I’m having trouble copying your code. This is the error I keep getting, any help would be greatly appreciated. Thanks
Org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: script_dth_metadata_c3e4955a_44f5_43ef_b22c_341d3a70039d: 72: expecting ‘}’, found ‘:’ @ line 72, column 32. 72 fingerprint deviceId: “0x1101”, inClusters: “0x5E, 0x86, 0x72, 0x5A, 0x85, 0x59, 0x73, 0x26, 0x27, 0x70, 0x2C, 0x2B, 0x5B, 0x7A”, ^ 1 error