I think his issue is that Alexa can dim the two lights just fine together, but when using the ST app he will have to dim the two lights separately. I don’t have this issue as my lights are LIFX and I use my LIFX Group of Groups DH for that.
If you use the sdk to create a custom device type, and select the rf9500 template, the built-in fimming logic does work. At least on the wall powered version of the dimmer remote it works. I have issues with the stock driver, in that it does not implement all the features I require, but in between my testing of my own driver, i go back to the stock (unsupported) driver. As it reads and sets level correctly… there just wasnt anyway back in the day to use this to remotely set the lights without custom rule engine, but now there are. I will be playing more, and once i get my fully supported device type working, i will share it. These really are just standard z-wave dimmers. It is smartthings that doesnt know how to do remote controlled dimming. They only do load controlled dimming.
This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382&mt=8&ct=how_i_email) is how I Email now
@whoismoses - Did you use the RF9500 device template when you created Cooper RF9500 Beast handler? I’m curious if it’s hard to get the dimming to work in ST smart app when the device is accessed.
To be clear about my setup:
- I have (2) Kitchen lights – both are Osram Lightify light strips.
- The light strips can be dimmed and turned on/off in ST smart app.
- The light strips are linked to Amazon Echo under a group called “Kitchen Cabinets”.
- Anyone can request to have the lights dimmed or turned on/off with Alexa.
- Cooper RF9500 switch is mounted on the wall and controls these lights
- Toggimmer v2 is used to link the dimmer (Cooper RF9500) to the (2) light strips.
- Device Handler: Cooper RF9500 Beast
As you can see, any activity performed by Alexa will not update the Cooper switch state and level. Since Cooper switch dimming level cannot be set in the ST smart app that’s where the setup gets messy. I can make the setup cleaner but the Cooper switch dimming level would need to be adjustable in ST smart app directly.
I did not. It was my first DH I had ever written.
You might be more productive if you create a smart app that keeps your lightify strips in sync.
Not that either is these fits your use case, both are specific to the lightify light strips and might get you on your way…
SmartApp
Device Handler
Thanks. Will give it a try.
Below is a link to a DH for the Cooper scene controller.
My RF9500 won’t perform any commands when set up with the Cooper RF9500 Beast device type handler. If I set it as the Cooper RF9500 the main rocker acts as a single toggle and the small button only responds to presses on the bottom.
I have a Cooper RF9542-Z, which is the line powered, non-load controlling remote dimmer wall switch. I have used every device handler I could find, and wrote my own. Currently I am using the generic dimmer switch handler. It is not perfect, but it works well enough. One of these days I hope to understand the dev environment well enough to create a proper device handler, because they are all wrong.
1 Like
What do you use the RF9542 to do?
My RF9500 is controlling Sengled LEP bulbs in lamps. Right now all it can do is toggle but I’ll be trying different handlers and apps to see if I can get it do adjust the brightness as well.
Next up is the RFWC5 wall station / keypad for me to try out.
Almost the exact same thing. I control two GE+Link zigbee bulbs. Thw best solution I found was one that turns the dimmer buttons into two more buttons, and I used a rule engine. Eqch time I pressed the up/down dummer buttons, the brightness would go up/down 10%. My custom handler allows for integral brightness control, so most of the dimming is handled in the lower 20%. This makes the dimmer behave in a more human way. Single the rule engine was deprecated, and since I dont want to use core, I am just limping along with the generic dimmer. Dimming works, and on/off work, but i dont have a feedback to control the LEDs on the switch.
Can you capture the logs and send them to me? Every now and then I come across a device that sends slightly different commands.
Press all the buttons. The main one 3-4 times and then the dim up and down a few more.
This is using the Cooper RF9500 Beast DTH:
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:43:09 PM: debug description === zw device: 30, command: 2002, payload:
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:42:45 PM: debug description === zw device: 30, command: 2002, payload:
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:42:43 PM: debug description === zw device: 30, command: 2002, payload:
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:42:24 PM: debug description === zw device: 30, command: 2002, payload:
The dimmer button doesn’t seem to send any commands regardless of the DTH I assign to the device.
This is the log after assigning the stock Cooper RF9500 DTH:
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:45:42 PM: debug Parsed 'zw device: 30, command: 2002, payload: ' to [[name:button, value:pushed, data:[buttonNumber:1], descriptionText:Aaaaa button 1 was pushed, isStateChange:true, displayed:true, linkText:Aaaaa]]
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:45:42 PM: trace Button 1 pressed
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:45:35 PM: debug Parsed 'zw device: 30, command: 2002, payload: ' to [[name:button, value:pushed, data:[buttonNumber:1], descriptionText:Aaaaa button 1 was pushed, isStateChange:true, displayed:true, linkText:Aaaaa]]
78a715e3-3702-445e-b9dd-b650f65bd7cb 9:45:35 PM: trace Button 1 pressed
When the device is first added it’s discovered as a “Z-Wave Remote” device type which has no controls associated with it.
Out of intrigue, I downloaded the device handler. I see some really interesting coding in it, so I tried it. I too experience the same thing, so back to my dimmer device handler. Actually, not the factory generic one, but my work in progress one. I got some ideas to try on my handler from this beast handler, but it didnt work for me either.
@xraycat - So when you use the Beast DTH handler and you press the toggle button (not the dimmer) you get the follow?
9:43:09 PM: debug description === zw device: 30, command: 2002, payload:
9:42:45 PM: debug description === zw device: 30, command: 2002, payload:
9:42:43 PM: debug description === zw device: 30, command: 2002, payload:
9:42:24 PM: debug description === zw device: 30, command: 2002, payload:
This is weird. Mine always send a payload. For example mine send…
9:43:09 PM: debug description === zw device: 30, command: 2002, payload: FF
9:42:45 PM: debug description === zw device: 30, command: 2002, payload: 00
9:42:43 PM: debug description === zw device: 30, command: 2002, payload: FF
9:42:24 PM: debug description === zw device: 30, command: 2002, payload: 00
Can you post the raw description of the device in question?
Also, I’m curious. If you modify line 79, change it from…
if(description?.trim()?.endsWith("payload: FF") || description?.trim()?.endsWith("payload: 00") || description?.trim()?.endsWith("payload: 01")) { // On / Off Toggle
to
if(description?.trim()?.endsWith("payload: FF") || description?.trim()?.endsWith("payload: 00") || description?.trim()?.endsWith("payload: 01") || description?.trim()?.endsWith("payload:")) { // On / Off Toggle
Does that at least fix the on/off?
Raw Description zw:L type:0100 mfr:001A prod:4243 model:0000 cc:72,77,86,85 ccOut:26Well, they are definitely different.
Did you try changing line 79 in the DH?
I made the change to line 79 and this is the live logging now after pressing the main toggle and the dimmer:
the main button acts as a toggle (not top=on & bottom=off) and the dimmer doesn’t produce a command.
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:03 PM: debug CRF9500 -- parse -- returned AAA switch is off.
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:03 PM: debug CRF9500 -- parse -- returned AAA switch is off.
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:03 PM: debug CRF9500 -- parse -- Button Pressed
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:03 PM: debug description === zw device: 30, command: 2002, payload:
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:01 PM: debug CRF9500 -- parse -- returned AAA switch is on.
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:01 PM: debug CRF9500 -- parse -- returned AAA switch is on.
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:01 PM: debug CRF9500 -- parse -- Button Pressed
c2d984e8-ae3c-43f4-957d-35b25571f5f6 7:13:01 PM: debug description === zw device: 30, command: 2002, payload:The cooper aspire RF9500 series of switches and dimmers (this includes the battery operated model) dont have an off button. The bottom of the on/off switch is a rocker and the top is a momentary contact switch that toggles between on/off. Pressing the bottom of the button should prove very difficult, and yield the same results as pressing the top, as when you press the bottom, if pressed hard enough, you are actually using the bottom to press the top button.
Ah, good info. Makes sense.
The bottom of button 1 (main button) does in fact have its own tactile click that’s separate from the top.
Is this the product?
If so, that is interetsting to learn it has an off button contrary to the documentation… I only own the wall powered remote switch. But this would be good information to have for my device handlers should Inchoose to add a battery operated model