PLUGIN: Caseta Connect

The plugin works now. I entered the ip address and the mac address. The only problem is that it doesn’t show up in “My Apps”. The version is the latest. That is not a problem, as long as it works.

A new version has been posted to address the issue of Bridge devices not being detected.

v1.0.18 (Version ID: 30380) February 10, 2016 (Not available in App Marketplace)
– added - device detection via Lutron account when credentials provided
– added - when bridge device can not be definitively detected, do network device scan and allow select from list of detected devices

** See updated instructions in post #2.

cybrmage,

With a pro or pro2 controller would I be able to use Pico remotes to control a group of z-wave dimmers? Are the pico remotes available as scene triggers?

A new version has been posted.

v1.0.19 (Version ID: 30391) February 10, 2016 (Not available in App Marketplace)
– added - device detection via Lutron account did not find target device

Is there a minimum limit on the polling interval? With the default of 30 seconds, I find that it’s pretty useless to try and use the Lutron switches as triggers, eventhough Lutron switches have instant status. Can I set the poll period down to 2 or 5 seconds? Do you think that would impact Vera performance?

I did the force update using the URL you posted. I was running v1.0.17. I did the update for v1.0.19. It created another plugin. Now I have two Caseta Plugins and they both say version 1.0.5 (Device ID# 75 and 78). I had created a scene using the first one (ID 75), and it still works. What should I do? Delete them both and create a new one manually with version 1.0.19 software, or delete the second one? I am including a screen shot of my device page for you to see.

Now I am confused! I added another switch to my bridge. I rebooted my Vera Edge, and now I have two (2) of everything ( 2 x Plugins, 2 x of each dimmer switch). The scene still works for the first switch.

No, you can not… With a SmartBridge, the status update command takes a minimum of 2-3 seconds to complete… If you set the polling interval that low, it will overload your vera.

Instead, enter your Lutron account credentials so that the plugin can receive status notifications from the Lutron MQTT servers.

You should be able to delete the second device (#78)… It should automatically remove the extra child devices.

I am not seeing this behavior on my development system (Vera Edge UI 7.0.13)… I am able to issue the update URL with various versions and no extra devices are created… May be an anomaly on the Edge…

Are there any errors displayed? Does your LuaUPnP.log show any errors… What Vera device are you using?? What UI version??

Hey whats the differance between this version and the RA2 plugin? I am able to use the RA2 plugin for my smartbridge pro just fine. Does this plugin function differently or add any benefits over the RA2 plugin?

I’m using Vera Edge, UI7, version: 1.7.1707.
This is how I did the upgrade: http://192.168.58.159:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8588&Version=v1.0.19

Just got my Caseta Smart Bridge Pro up and running, very excited to move Caseta control off Wink. I am having a few issues- Vera Plugin detects local smart bridge pro and it’s devices, but control and status of devices does not work at all. My Smart Bridge Pro has a static IP which I have verified is correct in the Vera dashboard. Any ideas? I’m so ready to get these devices off my Wink hub!

This version is specifically for the Caseta SmartBridge controllers - both pro and non-pro versions.

The RadioRA2 plugin only works with the pro version…

With the Caseta Connect plugin, you do not need to figure out the translation from the integration report to device numbers and types, and you do not need to manually set the device names in Vera… This is all detected and configured automatically.

If you already have the RadioRA2 plugin configured and working, the Caseta Connect plugin does not provide any additional functionality (at least, not until you add more devices).

[quote=“Mudd, post:50, topic:190407”]I’m using Vera Edge, UI7, version: 1.7.1707.
This is how I did the upgrade: http://192.168.58.159:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8588&Version=v1.0.19[/quote]

You are setting the “…&Version=” part of the URL incorrectly… You need to use the numeric version identifier, as provided in the release notes in the first post… The number listed in “(Version ID: XXXXX)”.

So, for version 1.0.19, you would use “…&Version=30391”

If your SmartBridge Pro is detected, and the devices are created in Vera, then the plugin is able to communicate with the Bridge… So control and status should work…

The first thing you need to do is enable debug mode in the plugin… then reload the LuaUPnP engine… Allow the vera to complete the reload, then try to control a device (ie: light switch) and then capture and post the LuaUPnP.log so we can see what exactly is happening… Also, provide details of you Vera… (Which model, which UI firmware)…

If your SmartBridge Pro is detected, and the devices are created in Vera, then the plugin is able to communicate with the Bridge… So control and status should work…

The first thing you need to do is enable debug mode in the plugin… then reload the LuaUPnP engine… Allow the vera to complete the reload, then try to control a device (ie: light switch) and then capture and post the LuaUPnP.log so we can see what exactly is happening… Also, provide details of you Vera… (Which model, which UI firmware)…[/quote]

I will try and grab a LuaUPnP.log tonight. I am on a Vera Plus, which I understand is not officially tested with this plugin. All other plugins do appear to be operating as intended, so i’m not sure if that is the issue. The devices will show up, but there is no status. If you try and control a light the dimming percent may change within UI7, but the on/off always states off. I did verify the telnet is enabled on the lutron app, and I did make a manual telnet session logging in with Lutron, Integration credentials. Bridge shows correct IP and mac address. I did try and manually load the latest update, that device didn’t detect a smart bridge.

EDIT: Got it working
I did a factory reset on the smart bridge pro (rear black button, 3 taps, hold 10 seconds on last tap, 3 more taps) and repaired, worked immediately on rebooting of vera

login as: root
root@192.168.1.237’s password:

BusyBox v1.19.4 (2015-12-22 16:26:34 EET) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.


| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|
_____|| |
||||___||| |____|
|
| W I R E L E S S F R E E D O M


  BARRIER BREAKER (Bleeding Edge, r39638)

*** MiOS LTD. ( www.mios.com ) ***


*** WARNING : ***
*** Any changes made to the system without ***
*** guidance from MiOS support will VOID ***
*** your future Support requests ***

root@MiOS_50001540:~# cd /var/log/cmh
root@MiOS_50001540:/tmp/log/cmh# tail -f LuaUPnP.log
50 02/18/16 18:16:59.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:16:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:16:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:16:59.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:16:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:16:59.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:16:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:16:59.205 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:17:29.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:17:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:17:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:17:29.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:17:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:17:29.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:17:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:17:29.205 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:17:59.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:17:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:17:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:17:59.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:18:29.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:18:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:18:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:18:29.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:18:29.206 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:18:59.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:18:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:18:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:18:59.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:18:59.204 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:18:59.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:18:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:18:59.205 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:19:29.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:19:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:19:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms
02 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:18:29.206 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:17:59.205 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:18:29.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:18:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:18:29.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:18:29.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:18:29.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:18:29.206 luup_log:41: (Caseta_Connect)::handleResponseLIP): ERROR 1 - Unknown or unhandled message received <0x7341e520>
50 02/18/16 18:18:59.100 luup_log:41: (Caseta_Connect::getStatusLIP): Checking Status <0x7581e520>
50 02/18/16 18:18:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Sending cmd = [?OUTPUT,4,1] <0x7581e520>
50 02/18/16 18:18:59.101 luup_log:41: (Caseta_Connect::CASETA_LIP::sendCommand) : Request returned in 0ms <0x7581e520>
50 02/18/16 18:18:59.202 luup_log:41: (Caseta_Connect::getStatusLIP): Status checked <0x7581e520>
02 02/18/16 18:18:59.204 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:‘GNET> ~ERROR,2
’ <0x7341e520>
50 02/18/16 18:18:59.205 luup_log:41: (Caseta_Connect::RESPONSES_HANDLERS:ERROR): Object does not exist <0x7341e520>
02 02/18/16 18:18:59.205 luup_log:41: (Caseta_Connect::handleResponseLIP): data received:’
’ <0x7341e520>
01 02/18/16 18:18:59.205 luup_log:41: (Caseta_Conne

Hello,

I am very new to Vera, but would love to get this working. I manually installed version 1.19 and after many attempts have it connected and my devices have been created (ended up specifying MAC and IP and I think that is what got it connected.)

I am unable to control the devices through vera, though.

I think I am getting messages like this in the log:

JobHandler_LuaUPnP::RunAction device 310 action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget failed with -911/Device not ready <0x735f9520>

Any help would be appreciated. Thanks!

[quote=“jwalsh, post:55, topic:190407”]I think I am getting messages like this in the log:

JobHandler_LuaUPnP::RunAction device 310 action urn:upnp-org:serviceId:Dimming1/SetLoadLevelTarget failed with -911/Device not ready <0x735f9520>[/quote]

You need to provide more of the LuaUPnP.log file… Turn on debug mode in the plugin if possible, then reload the LuaUPnP engine, and post the LuaUPnP log showing the plugin startup… Also, please specify model of Vera and firmware version…

Thanks you very much for looking at this for me, and thanks for developing this plugin!

If I did this right, the file is attached.

Device: Vera Edge Home Controller

Firmware Version: 1.7.1707

Yes, the file is attached… But you enabled verbose logging for the Vera (under settings/logs/verbose logging), not debug logging for the plugin (enabled in the setup page for the Caseta Connect device, under options)…

No matter… There is enough information to see that the plugin is operating normally… It is connecteding to your SmartBridge Pro, loading the configuration, configuring the vera devices (all 49 of them!!) and starting the monitoring loop…

Unfortunately, although you did try to control any devices, there is no logging of what is or is not happening when you try to control a device… debug mode needs to be enabled to see exactly what the plugin is doing…

Without debug mode enabled in the plugin, I can see that the plugin sends commands (status requests) and receiving the responses… But not how the plugin is processing them…

Please enable debug mode in the plugin… (this is dynamic… no need to reload the LuaUPnP engine)… and try to control a light… Then post the new logs.

BTW… You have Serena shades… I do not, and have not been able to test that the plugin can actually control them… Once we have the Lights working, we can work on the shades…

A more detailed look at the logs reveals a VERY obscure error…

It looks like the LuaUPnP engine is not setting up the child devices properly, do to a problem loading the implementation file…

Go to the Caseta Connect device settings, click on advanced, find the “impl_file” field… make sure it contants “I_CasetaConnect.xml”… without a space at the beginning of the line… Once you remove the space, reload the LuaUPnP engine…

[quote=“br636, post:43, topic:190407”]cybrmage,

With a pro or pro2 controller would I be able to use Pico remotes to control a group of z-wave dimmers? Are the pico remotes available as scene triggers?[/quote]

I’m trying to figure this out also. I had to manually put in the IP and MAC and reboot the Vera before my Pro2 bridge would be seen (on new Vera Plus, so that could be related).

It sees my Picos, but I have been unable to get them to act as triggers for scenes. This is my first Vera, so that could be part of the problem also :).

I have tried with the regular 5 button picos, and I have some of the 4 button “Pro” Picos, which use different activity ID’s for the buttons in the telnet interface than the normal Picos.

EDIT: More info, I know the overall plugin is working as I can see and control my Lutron devices in the Dashboard, and they reflect status properly. I also created a scene and it controls a Lutron dimmer without issue. Finally to test status updates as scene triggers I created a scene that uses one of the Lutron dimmers turning on to turn on another Lutron dimmer, and this also works. It is only the Pico’s I can’t figure out.

I’d really like to get this working as this plugin should allow much more flexibility than Lutron allows with the Picos.