It’s out of sync, although I am able to use the app to adjust them, something I wasn’t able to do when I paired the remote directly to the bulbs.
I have no clue how the Iris Button handler is allowing the commands to turn on and of, change color or brightness without a smart app in the middle, but that’s the status of things at the moment.
EDIT: So I used the Device Handler for the Lightify Button Dimming Switch as well as the Handler for the Swann Key fob, and with all three handlers the commands to turn on and off all bulbs as well as change color and brightness pass through the Hub, the other buttons on the bottom of the remote don’t do anything either physycally or through the logs in the IDE.
There is likely a smart app in the middle for the iris button. That button itself is not in any way controlling the other devices. All it is doing is telling the hub that its button was pressed.
Then something has been set up to subscribe to that button press event, and that something is sending a command to the bulb to change its state.
It could be a routine, it could be smart lighting, it could be rule machine, it could be custom code.
There’s also a small possibility that there has been a direct binding between the iris button and another zigbee device. That works like direct association in zwave. If two devices of the same protocol belong to the same network, and they are within one hop of each other, They can be set up to talk to each other directly without going through the hub. But we don’t usually do that in a SmartThings set up because it has a lot of limitations and the app will be out of sync
Then the Bulbs are likely bound to The remote. Try turning off the hub (take it off power and take out the batteries). If the remote can still control the bulbs, then they are independently bound and the remote is not actually being used as a SmartThings button controller.
I don’t think you’ll be able to use the following device handler, but if you read through the thread, I think you’ll see that they are having the same issues with that device that you are having with yours, and it might give you some ideas.
Weird thing is I did bind each of my 4 bulbs to one of the on and of sets on the bottom of the remote, they paired and the bulbs were no longer available on my ST hub, I reset the bulbs and unpaired the remote with each bulb, then repaired them with the ST hub and all was working well, with the added bonus of partial control while the remote is paired to the hub.
Now that I think about it, I’ll unpair from the hub and see if the lights still obey the remote.
If you could post the fingerprint/raw description from the IDE and some logs with notes as to which catchall messages correspond to the various actions… I might be able to take a stab at it before I get mine.
The raw description should be listed in the Devices entry for that device. Otherwise you can dig through the location events to find the initial join event which should also list it. It will look something like this in that case:
Since the raw description isn’t showing in the Device entry, you’ll need to find it in the Location event list. Head to the Location link in the top nav bar, then click on “events” next to your location. You’ll probably need to change the filter to “all”.
This should be enough for a start at least. It won’t fingerprint correctly, but changing the device type manually should still work.
Do the lower, numbered buttons produce any output?
Ok. So what we should be able to do with this remote is this:
You should be able to pair the bottom buttons to the bulbs after pairing the remote and bulbs to the hub, similar to the way the Lutron remote works as a parallel controller. These are likely using the group/scene commands and aren’t supported by the ST hub, so we can’t use them as generic buttons.
The top on/off button could be used as two discrete buttons. This could be built as either a generic button controller, or we could set this up to look like a no-load light switch which could then be mirrored by one of the various smart apps, similar to some of the z-wave companion switches. (This might already work if you try the Zigbee Dimmer DTH)
The color (temp?) control and dimming control in the center could probably be used as a control for color/dimmable lights in a similar fashion by setting this up as a virtual Zigbee RGBW bulb which could then be mirrored using other smart apps.
I’m not sure if I’m way out of base here, but I think the remote might be useful for things other than just lights, even if the lower buttons don’t communicate to the hub, a 6 button remote for US$12 seems like a steal, I do agree that its original intended use of controlling lights seems obvious, but who’s to say this remote can’t be used for other purposes.
In any case, I believe the first step is having a basic handler, and working up from there, correct?
EDIT: So I have both the remote and the bulbs paired with the hub, and tried pairing the lower buttons with individual bulbs. So far 2 buttons turn individual bulbs and 2 turn all the bulbs on, this is kind of weird.
This is true. As a generic button controller you could control pretty much anything. It would be less intuitive to use the 4-way for buttons, but it would be doable. The problem is in the way the remote handles those presses.
The color control (left/right) sends a hue and saturation along a sliding scale from 0x0000 to 0xFFFF (or whatever the sane limits are). So we’d have to determine which direction the remote is moving and determine which button is being pressed from that. This would rely on a reliable “last state” value, which has proven to be a very unreliable thing to get from the platform lately. This could result in unexpected behavior.
The level control (up/down) sends repeated move level commands while held and a stop move command when released. The stop move command is probably what we’d want to trigger the action on (just using the move command would likely result in a lot of repeated button presses and would require some debouncing) Again, this depends on reliable “last state” and reliable message sequencing to know what button was just released and could be… unreliable.
So this is not really the ideal remote to use as a button controller, but it is doable. I’d be willing to help either way, just wanted to put that out there for the community in case anyone else had some input.
I’m now leaning toward the virtual dimmer/hue concept for my own uses. Would be good for the non-techies in the family to control Hues/Gardenspots/Lightstrips
Oh it has the potential to be useful, I just see it being problematic as a generic controller. Likely to be a bit finicky. I’ll see if I can bang out a DTH for it. Hope the simulator is behaving this week…