Caseta Smart Bridge (L-BDG2)

Driver will not automatically import the file.  Use the command builder to import the file you put in the data folder.  It should import the devices and scenes you've defined. If it misses anything email me the export file.

Importing the file is the key step, missing from the documentation.

All the devices were added automatically.  I change the names to make them globally unique.  The type was correctly assigned.  Since I didn't use the same room names in the Lutron app and in myServer, I needed to assign some devices to the correct room.

Looking at the Integration Report, it looks like Scenes are assigned as buttons directly on the hub.

I can control any dimmer in any room with the Level command.  But I can't find a command that activates a Scene.

In general, now that the driver is working, how do I get it onto the remote?  Do I need to create a non-AV Source?  Ideally, I would like to swipe left or right from any device in the room and get to a page that controls the lighting in that room, including selecting a Scene.

davep wrote:

Driver will not automatically import the file.  Use the command builder to import the file you put in the data folder.  It should import the devices and scenes you've defined. If it misses anything email me the export file.
 

What driver command is used to activate a Scene?

I have attached my export file if that helps.

The driver did not know how to import scenes. I just modified it do do that. (Thanks for attaching the imports file)

Update the driver.
Remove and re-import the text file.
You should now see devices of type scene.
To activate a scene the command is Lighting|<device id>~Scene

It simulates a button press on a keypad which I believe what triggers the scene. Let me know it works.

Don't forget there is an architecture question of which system is managing the lighting scenes - ie: in the lighting controller - or in myServer.
If you already have lighting scenes pre-programmed in the lighting controller - then you should be able to trigger those.
But, in a more powerful multi sub-system control system like what myServer is typically used in - you can define the lighting scene (along with Video, HVAC, irrigation, Audio, etc) in myServer and save those as PreSets that can be launched either by automation events or a button push or scheduled.

davep wrote:

The driver did not know how to import scenes. I just modified it do do that. (Thanks for attaching the imports file)

Update the driver.
Remove and re-import the text file.
You should now see devices of type scene.
To activate a scene the command is Lighting|<device id>~Scene

It simulates a button press on a keypad which I believe what triggers the scene. Let me know it works.
 

I successfully imported the Scenes as devices.  An unexpected side-effect is that every button on the Pico Remote also imported as a Scene.

Unfortunately, the scene command does not work.

Looking at the imports file, I expected the scenes to trigger as a button press on the hub itself.  I wasn't expecting to need an additional device for each scene.

I need to experiment further, but the Press and Release commands for the Pico remote don't seem to be doing anything either.  Perhaps if we get that working, scenes will just work.