16 hours ago16 hr I have a Pico PJ2-3BRL which is programmed to operate multiple Lutron shades simultaneously. I am using a Lutron L-BDFPRO2 hub. After installing the Caseta nodeserver, the IoX AC shows two pico devices, a pico-main and a pico-fav (each shade is also present as a separate device). The pico-main has no available commands or status. The pico-fav has six available settings for "send command": On Off Brighten Dim FastOn FastOff. How in IoX can I perform the equivalent of, for example, pressing the Open button on the physical Pico remote?
15 hours ago15 hr 29 minutes ago, wmcneil said:How in IoX can I perform the equivalent of, for example, pressing the Open button on the physical Pico remote?The short answer is, you can't.Lutron's protocols don't provide that capability. The plugin can't send commands as if they came from a specific device.Pico's simply send button press commands to the hub and then the hub sends command to the device(s) linked to that. The plugin should also see that button press and you can use that in a program to trigger other events -- if control pico-main is on then do something. The top button of the 3BRL is the on button (regardless of what engraved on the remote).You can also have a program that sends open/close commands to the shades, but you'd need something to trigger that. I believe you can also put the shades in a group and have some other device trigger commands (be the controller) for that group.But you can't send commands to the Pico and Pico's have no status. They are very simple, when the button is pressed, the button press command is sent to the hub. The hub programming determines what happens when it gets that button press event. The node would have to know the topology of the hub to know what the Pico on/open button was linked to and then have a button/command to send the on/open command directly to those devices. I don't believe the hub will share that topology info and if it can, it hasn't been reverse engineered to know how it would work.The -Favorite node is tied to the favorite button on the Pico and you can set how you want the plugin to treat that. The "Sends Command" setting is what the plugin will translate the Pico's favorite button into something that IoX can understand. Again, this would be used in programs. If set the button to "ON" then in a program you can use "if control pico-fav is on" do something.
14 hours ago14 hr Author 5 minutes ago, bpwwer said:Pico's simply send button press commands to the hub and then the hub sends command to the device(s) linked to that. The plugin should also see that button press and you can use that in a program to trigger other events -- if control pico-main is on then do something. In my eisy, the pico-main device has no available status that a program could use. The pico-fav device does have available status. It is certainly possible to have an IoX program control multiple shade devices at the same time. I have tried this, and it works. The shades do not move together in nearly perfect synchronization as they do when the physical pico remote is controlling them, but they do arrive at the requested setting. I tried using an IoX scene to group the shades. That did not work well. Not all the shades moved properly, and the status of shades became confused in IoX
13 hours ago13 hr Correct, Pico devices have no status. They only send commands (button presses). The -Favorite node is special. I tried to make that somewhat useful in groups/scenes.The screen shot shows the if clause for my Pico that is controlling 2 shades. But, if I understand what you want to do, that doesn't really help. It's saying that when the open button is pressed, do something. I believe you want to trigger the shades without physically pressing the pico's button, correct? Something like what's in the second screenshot. And as you noticed, the two command are executed sequentially by the IoX, it doesn't have the ability to simultaneously send two commands.The other option is use the Lutron app and create a scene with both shades in that scene. The plugin will create node for the scene and you can trigger the Lutron scene to activate. You'd need different scenes for different shade positions/settings, but the shades should then be in sync.IoX was originally developed to work with the Insteon protocol so for most other protocols, there are compromises. The different companies also patent parts of their protocols so other companies can't do things exactly the same way.
11 hours ago11 hr Author 1 hour ago, bpwwer said:I believe you want to trigger the shades without physically pressing the pico's button, correct? Something like what's in the second screenshot. And as you noticed, the two command are executed sequentially by the IoX, it doesn't have the ability to simultaneously send two commands.Yes, using multiple device commands in an IoX program results in them being executed sequentially, so the multiple shades are not synchronized.1 hour ago, bpwwer said:The other option is use the Lutron app and create a scene with both shades in that scene. The plugin will create node for the scene and you can trigger the Lutron scene to activate. You'd need different scenes for different shade positions/settings, but the shades should then be in sync.Yes, I tried creating Lutron scenes and that works to keep the multiple shades in sync.
Create an account or sign in to comment