Caseta driver

On the Caseta driver when you import the, file the grid doesn't get populate and the target device dropdown is empty.

Exactly- Not sure if I did it correct or not, but used the import command and manually typed in the file name caseta1.txt and sent that. Then went back and hit add device. Used the same name as in the integration report, selected my type (dimmer), manually put in the device address (from the integration report) and what room it was controlling from the drop down box. Controller ID is what hub it is running off of.

Ran a test and was able to finally turn off my theater lights and back on again running a command test.

I had to do this in the Lutron driver- had no luck at all in the lutron caseta driver.

So my command ended up being:
Lutron|AddDevice~Basementstairs~Dimmer~9~1~Theater

9 being the ID number from the integration report. That added the device and then had to click on the pencil icon beside it and add the IP address associated with the hub (aka controller) it was on. Not sure if it is needed or not, but I went ahead and added the login and password on each one when I added the IP address. I also updated the name in there to read now as Basement Stairs instead of it being one word.

Not sure if this is correct or not, but happy that I have finally got something to work. Ive read the documentation sections over and over on this and havent come across anything that actually tells you how to get the lights to finally get recognized. So not sure if this is correct, but working for me. I dont plan on setting commands on the pico remote I have, so just going to use this driver and consider it a minor win.

I am experiencing two issues with the Caseta driver. The first issue is that adding my Smart Bridge Pro there is no auto-population of devices from the Lutron integration file (/home/allonis/applications/myServer/data/caseta1.txt). If all devices have to be added manually, I don't see a need for the integration file in the data directory. 

The second issue is that adding devices from my testing the web template for AddDevice is not working correctly. The generated command which I have changed "name" to "test" and ID to "14" (for the dimmer I want to control) is as follows "Caseta|AddDevice~test~14~1~Den" returns an error that the room name is not in a correct format. What appears to be missing is device type. If I alter the above command to "Caseta|AddDevice~test~Dimmer~14~1~Den", that command is accepted and the word "Dimmer" in the Device Properties display show up in the Type Field. "Dimmer" is just a guess on my part as to what should be in the Type field. With this entry I am then able to successfully turn on and off the specified dimmer via Driver Command Testing. Screen captures of the above screens are in the attached file.

To summarize the issues I would like to see addressed:
1) The AddDevice command seems to require a type field that is not input which results in the syntax error on Room Name.
2) The Device Name pull down selection of "Controller Name" is confusing. It either should reference unique name or make it clear that "Controller" in this case is the name of the device attached to the Smart Bridge Pro.
3) In the devices I was able to add the "ID" and the "Device Address" were set to the same value. I don't think the ID should be being set to the value of the "Device Address".
4) Can the "Type" field be populated from the integration report? If not, how do I know what acceptable types are, such as via a drop-down menu?
5) The Caseta instructions state: 
"If you have switches, fans or Lutron shades, open the Integration Report in your config directory using a text editor and find their Integration IDs and edit your myServer 6 configuration as described in the instructions below to tell it which devices are switches or shades."

I cannot find the "instructions below" that is mentioned in the above sentence. Am I supposed to make changes to the integration file or change the "type" field of the device?

If AddDevice was working, I can add the 30+ dimmer and switches individually, but it would really be helpful for some type of auto-populate to minimize errors.




 

I was having the same issue where the Caseta Driver didn't seem to work at all but the Lutron driver did.

I noticed my bridge in the Caseta Driver was showing up with an ID of -1. I changed that to +1, which agreed with the ID in the caseta1.txt file, and reran the import command. This populated all of my devices. I will need to go through and update the names and rooms, but everything seems to work.

Kyle

Gentlemen please email me your Caseta import files. Send them to dave @ allonis.com. Thanks.
 

I just sent you my Caseta file. Please let me know if you need anything else.

Kyle