Author Topic: PLUGIN: Caseta Connect  (Read 31813 times)

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
PLUGIN: Caseta Connect
« on: January 03, 2016, 05:53:15 am »
Caseta Connect Plugin
-----------------------------

Note: This plugin only works with Vera Lite (UI5 or UI7), Vera 3 (UI5 or UI7), Vera Edge (UI7) or VeraPlus (UI7).

Supported Controllers:
-----------------------------
Lutron Caseta SmartBridge Controller (Model ID: L-BDG)
Lutron Caseta SmartBridge 2 Controller (Model ID: L-BDG2)
Lutron Caseta SmartBridge Pro Controller (Model ID: L-BDGPRO)
Lutron Caseta SmartBridge Pro 2 Controller (Model ID: L-BDGPRO2)

*NOTE 1: Smartbridge devices are normally referred to by the ordering code. The only ordering codes currently add "-WH" to the end of the model id.
*NOTE 2: All currently available kits contain either a L-BDG2 or L-BDGPRO2.


Supported Devices:
------------------------
Lutron Plug-In Lamp Dimmer
Lutron In-Wall Dimmer
Lutron In-Wall Dimmer Pro
Lutron In-Wall Switch
Lutron In-Wall Switch Pro
Serena/Sivoia QS/Triathalon shades
Pico Remote Control (Pro/Pro 2 only)


Features:
------------
Automatic detection and configuration of devices installed on the SmartBridge controller
Local control of devices connected to the controller
Near Real-time status updates from controller
Pico Remote Control operates as a Scene Controller (Pro/Pro 2 Only)
Programmable Ramp Rate for dimmers
Relative dim (up and down) for dimmers

Version History:
---------------------

v1.76     (Version ID: 34514) September 12, 2017
-- fixed - code regression prevented plugin operation when configured with a pro hub

v1.75     (Version ID: WITHDRAWN) September 12, 2017
-- added - LEAP service monitor to provide real-time status updates to smartbridge (non-pro) in place of MQTT
-- changed - removed obsolete embedded MQTT client (Lutron move the MQTT data to a secure server - The Vera IO model is not compatible with the requirements for TLS encapsulation)
** NOTE ** - The Lutron account credentials that were required to use MQTT are no longer required. There credentials are now only used for bridge discovery.

v1.65     (Version ID: 34376) September 4, 2017
-- added - better recovery from corrupted or incomplete configuration data
-- added - various minor bugfixes

v1.63     (Version ID: 32948) January 16, 2017
-- added - support for ToggleState UPnP Action for switches, dimmers and blinds
-- added - various minor bugfixes to device actions

v1.61     (Version ID: 32198) September 24, 2016
-- fixed - lutron account signin changes - caused plugin crash if account credentials are entered
-- fixed - lutron mqtt broker signin changes

v1.59     (Version ID: 32102) September 6, 2016
-- fixed configuration rejected unless at least 7 configuration sections are returned by the bridge (condition is not satisfied if pico remote(s) are not configured on the bridge)

v1.0.58     (Version ID: 31040) April 4, 2016 (Not available in App Marketplace)
-- fixed mDNS discover causes failure if no response received on VeraPlus

v1.0.56     (Version ID: 30998) March 31, 2016 (Not available in App Marketplace)
-- fixed mDNS discover response not processed
-- fixed silent failure on openLuup platforms without socat preinstalled
-- force logging of device discovery regardless of debug mode
-- device discovery not working on VeraPlus

v1.0.52     (Version ID: 30770) March 10, 2016 (Not available in App Marketplace)
-- added UPnP SetStepDelta, StepUp and StepDown commands
-- extended UPnP DimUpDown, SetStepDelta, StepUp and StepDown commands to work on blinds

v1.0.51     (Version ID: 30756) March 9, 2016 (Not available in App Marketplace)
-- added - UPnP actions DimUp and DimDown

v1.0.50     (Version ID: 30596) February 28, 2016 (Not available in App Marketplace)
-- fixed device summary generated invalid html
-- fixed configuration retrieval retry mechanism did not retry on LIP integration report failure
-- fixed plugin did not automatically fall back to using LEAP server when LIP configuration was not retrieved

v1.0.47     (Version ID: 30566) February 28, 2016 (Not available in App Marketplace)
-- icon fix for OpenLuup v7
-- fix for vera device renumbering when bridge does not return data during configuration

v1.0.45     (Version ID: 30560) February 28, 2016 (Not available in App Marketplace)
-- LEAP status not processed correctly when LIP server enabled

v1.0.44     (Version ID: 30556) February 28, 2016 (Not available in App Marketplace)
-- additional fixes to pico button mapping
-- LIP response handler optimization

v1.0.42     (Version ID: 30536) February 26, 2016 (Not available in App Marketplace)
-- fixed LIP input processing causes plugin crash

v1.0.41     (Version ID: 30486) February 23, 2016 (Not available in App Marketplace)
-- fixed unsolicited device update during configuration cause plugin crash

v1.0.40     (Version ID: 30481) February 22, 2016 (Not available in App Marketplace)
-- fixed initial device state not set correctly for devices on pro model bridges
-- fixed support for blinds
-- extend support for RampTime device variable to blinds

v1.0.37     (Version ID: 30471) February 22, 2016 (Not available in App Marketplace)
-- added retrieve LIP integration report and correlate IDs to LEAP devices
-- fixed detect lowest pico button ID from LIP integration report
-- added support for StartRampToLevel UPnP action
-- added support for RampTime dimmer device variable

v1.0.30     (Version ID: 30464) February 21, 2016 (Not available in App Marketplace)
-- added support for activating Lutron Caseta scenes

v1.0.25     (Version ID: 30452) February 20, 2016 (Not available in App Marketplace)
-- fixed processing of pico remote models with non standard component ids
-- changed debug output clarifications

v1.0.23     (Version ID: 30451) February 20, 2016 (Not available in App Marketplace)
-- fixed LIP status processing for non-dimmer devices
-- fixed plugin crash on unprocessed LIP status response
-- fixed number of buttons not set for pico devices
-- fixed LIP response last parameter not correctly decoded for certain devices

v1.0.19     (Version ID: 30391) February 12, 2016 (Not available in App Marketplace)
-- fixed - device detection via Lutron account not detecting target device

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 below for updated instructions.

v1.0.17     (Version ID: 30218) January 27, 2016 (Not available in App Marketplace)
-- fixed - enable LIP mode under openluup (openluup.io version 2016.1.26 or greater required)

v1.0.16     (Version ID: 30182) January 24, 2016 (Not available in App Marketplace)
-- fixed - setTarget action fails under certain circumstances
-- added - initial support for openluup
** NOTE: When running under openluup, due to limitations of the io implementation, LIP and MQTT support are not functional.

v1.0.14     (Version ID: 30164) January 22, 2016 (Not available in App Marketplace)
-- fixed - luup io routine does not process LIP responses

v1.0.12     (Version ID: 30161) January 22, 2016 (Not available in App Marketplace)
-- fixed - could not set Lutron Username or Password from options tab

v1.0.11     (Version ID: 30152) January 22, 2016 (Not available in App Marketplace)
-- fixed - expanded MAC address filter for ARP device discovery
-- changed - set device variables only if changed
-- fixed - initial child device status not set for devices connected to a SmartBridge (non-pro)
-- added - optional instant status mechanism for SmartBridge (non-pro)
-- fixed - MQTT connection lost after initial keep-alive-time

v1.0.8     (Version ID: 30106) January 19, 2016 (Not available in App Marketplace)
-- fixed - unable to set debug mode from option page
-- fixed - unable to set poll time from option page
-- fixed - excessive debug logging when debug mode not enabled
-- fixed - child device variables updated when values have not changed

v1.0.5     (Version ID: 30056) January 13, 2016 (Available in App Marketplace)
-- fixed issue with files being corrupted during install
-- fixed issue with plugin running under UI5

v1.0.0      January 3, 2016
-- Initial public release
« Last Edit: September 19, 2017, 03:12:14 am by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect - INSTALLATION
« Reply #1 on: January 03, 2016, 05:55:26 am »
Automatic installation:
----------------------------
You can install the plugin via the App Store from you Vera under the Apps/Install Apps menu.

You can update to the latest approved version in the App Store by going to Apps/My Apps, selecting the plugin and enabling "Auto Update"

You can force your Vera to update to a specific release before it is approved in the App Store by entering the following URL into your browser:
Code: [Select]
http://<your ip>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8588&Version=<Version ID>
Make sure to replace <your ip> with the IP Address of your Vera, and <Version ID> with the Version ID provided in the release post/ revision history.

Manual Installation:
-------------------------

1) Download the release archive from the first post in the thread. Extract all files to a temporary directory.
2) Upload all files to your Vera controller
    UI5: Go to Apps/Develop Apps/Luup Files. Select "Browse" and add each file, then click on "Go". NOTE: The "Restart Luup after upload" does not need to be selected.
    UI7: Go to Apps/Develop Apps/Luup Files. Click on "Upload". Select all the files from the archive and click "open". The "Restart Luup after upload" does not need to be selected.
3) Create the Vera device for the Caseta Connect plugin.
    UI5: Go to Apps/Develop Apps/Create Device. Enter the required device data (detailed below), then click on "Create device"
    UI7: Go to Apps/Develop Apps/Create Device. Enter the required device data (detailed below), then click on "Create device"

  Device Type: urn:schemas-micasaverde-com:device:CasetaConnect:1
  Internal ID: Caseta Connect
  Description: Caseta Connect
  Upnp device filename: D_CasetaConnect.xml
  Upnp implimentation filename: I_CasetaConnect.xml
  Ip Address: <LEAVE BLANK>
  MAC: <LEAVE BLANK>
4) Once the Vera controller creates the device, Allow the LuaUPnP engine to reload.

BRIDGE DETECTION
-----------------------

If you provide Lutron Account credentials (username and password), the Lutron Account will be queried for the ID of device that it is paired with, and the plugin will attempt to locate only that device.

If you do not provide Lutron account credentials, then plugin will search for Bridge devices using mDNS... If the mDNS search fails to detect a Bridge device, the plugin will use ARP table loading to try to find a Bridge device.

If a single SmartBridge controller is found on your network, the plugin will automatically select the Bridge, load its configuration and create the appropriate devices on your Vera.

If MORE than one SmartBridge controller is found on your network, the plugin will indicate "User Intervention required". You must then go to the plugin Settings page and select the "Bridge" tab, and select the controller you wish to use.

If the plugin can not definitively detect a Bridge on your network, the plugin will indicate "User Intervention required". You must then go to the plugin Settings page and select the "Bridge" tab, and select the controller you wish to use.

On the "Bridge" tab, the plugin will show a list of detected Bridge controllers or, if no controller could be definitively located, a list of all network devices on your network. Click on the "Select" button beside the controller you wish to use (The MAC address of the controller is printed on the product label attached to the bottom of the controller).

Once you select the desired controller, the plugin will restart the LuaUPnP engine, and will automatically detect its configuration and create the appropriate devices on your Vera.

Once a Bridge is selected, the plugin will no longer attempt device detection.

** FOR RELIABLE OPERATION, YOU SHOULD CONFIGURE YOUR ROUTER TO PROVIDE A STATIC IP ADDRESS TO THE BRIDGE!

« Last Edit: February 10, 2016, 10:33:46 pm by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect - Details and Limitations
« Reply #2 on: January 03, 2016, 06:01:14 am »
Technical details and limitations:
-----------------------------------------

The primary interface to the Lutron SmartBridge series controllers is a Secure Channel interface that implements a JSON encoded command/status server. The Secure Channel is part of the SSH specification, however the command/status server does not operate in the same way as a SSH login shell. The interface only implements the EXEC channel, so the standard dropbear SSH client installed on Vera devices does not interact well with interface. The controller refers to this interface as the "LEAP" server.

A secondary interface, only implemented on the SmartBridge Pro controllers, is the Lutron Integration Protocol. The is the same Telnet based interface used by the Radio RA2 devices (and the Radio RA 2 plugin). The controller refers to this interface as the "LIP" server.

The "LIP" server (on Pro/Pro 2 controllers) is NOT normally enabled on the controller, and must (normally) be manually enabled using the Lutron app. The Caseta Connect plugin will automatically enable the "LIP" server if it is available on the controller. This interface provides (near) real-time status updates for ALL devices connected to the controller.

The "LEAP" server also provides (near) real-time status for devices connected to the controller, but does NOT report status for PICO remotes.

Because the "LEAP" server does not implement the "shell" channel that is required for a persistant SSH connection (from the vera controller), status of the SmartBridge (non-pro) controllers is achieved by polling the controller for device status. Control of devices connected to the SmartBridge (non-pro) controller is achieved by creating a connection to the controller as needed. This on-demand connection introduces an ~2 second overhead per command.

** NOTE: As of version 1.0.11, the plugin is able to use the Lutron notification servers to obtain near-real time device status updates from non-pro bridges. To enable this option, enter the same username and password that you use in the Lutron app into the plugin on the options page. This remote login is used ONLY for device state notificatios.


The "LIP" server is used when the plugin detects a SmartBridge Pro controller.

Configuration of the devices connected to the SmartBridge controller is done using the Lutron app.



PICO BUTTONS
==========
Pico buttons are mapped as follows: (for a Pico3buttonRaiseLower)
Vera Button #1 : Pico "ON" button (square button at top of remote) short press
Vera Button #2 : Pico "ON" button (square button at top of remote) long press
Vera Button #3 : Pico "FAVORITE" button (round button in center of remote) short press
Vera Button #4 : Pico "FAVORITE" button (round button in center of remote) long press
Vera Button #5 : Pico "OFF" button (square button at bottom of remote) short press
Vera Button #6 : Pico "OFF" button (square button at bottom of remote) long press
Vera Button #7 : Pico "DIM UP" button (triangular button at center left of remote) short press
Vera Button #8 : Pico "DIM UP" button (triangular button at center left of remote) long press
Vera Button #9 : Pico "DIM DOWN" button (triangular button at center right of remote) short press
Vera Button #10: Pico "DIM DOWN" button (triangular button at center right of remote) long press

** NOTE **: long button presses are generated by the plugin. The can only be triggered by pressing a button on the pico remote and holding it for more that 2 seconds. long button presses can NOT be triggered from the Lutron app.



DIMMERS - RAMP (fade in/fade out) SUPPORT
---------------------------------------------------

** NOTE: Ramping is currently only supported on SmartBridge Pro models.

Ramping allows you to turn a light on or off over a period of time.

You may set the RampTime variable for a device, and that device will use that ramp time for all ON/OFF/DIM operations. The ramp time is expressed in number of seconds.

Note that setting the ramp time in a Vera device does NOT affect the ramp time when the dimmer is activated from the physical device or from a Lutron scene.

You may also use the "StartRampToLevel" UPnP action via HTTP or from a Vera Scene.

The UPnP action HTTP command is:
Code: [Select]
http://<Vera_IP_Address>:3480/data_request?id=action&DeviceNum=<Dimmer Device Vera ID>&serviceId=urn:upnp-org:serviceId:Dimming1&action=StartRampToLevel&newLoadLevelTarget=<brightness level>&newRampTime=<ramp time in seconds>

To use the Action in a scene, you need to add the action and parameters using the advanced scene editor.


DIMMERS - RELATIVE LEVEL CONTROL SUPPORT
------------------------------------------------------

Relative dimming allows you to change the light level of a dimmer relative to the current level.

The dim level can be changed using custom UPnP actions or standard UPnP actions. Both methods achieve the same result.


UPnP DimUp and DimDown Actions (NOTE: These are not standard UPnP actions)
---------------------------------------

To increase the light level of a dimmer device, use the "DimUp" command.
To increase the light level of a dimmer device, use the "DimDown" command.
The DimPercent parameter is the percentage of dim to change from the current level.

You may use the "DimUp" or "DimDown" UPnP action via HTTP or from a Vera Scene via lua code.
The DimPercent should be specified with the commands. If a DimPercent is not specified, a default of 10 is used.

The UPnP DimUp action is:
http -
Code: [Select]
http://<IP Address of Vera>:3480/data_request?id=action&DeviceNum=<Vera ID of Dimmer>&serviceId=urn:micasaverde-com:serviceId:CasetaConnect1&action=DimUp&DimPercent=<The amount of change desired>
Lua -
Code: [Select]
luup.call_action("urn:micasaverde-com:serviceId:CasetaConnect1","DimUp", {DimPercent = <The amount of change desired>},<Vera ID of Dimmer>)


The UPnP DimDown action is:
HTTP -
Code: [Select]
http://<IP Address of Vera>:3480/data_request?id=action&DeviceNum=<Vera ID of Dimmer>&serviceId=urn:micasaverde-com:serviceId:CasetaConnect1&action=DimDown&DimPercent=<The amount of change desired>

Lua -
Code: [Select]
luup.call_action("urn:micasaverde-com:serviceId:CasetaConnect1","DimDown", {DimPercent = <The amount of change desired>},<Vera ID of Dimmer>)

To use the Action in a scenes, you can add the actions and parameters using the lua code section of the scene editor.


UPnP SetStepDelta, StepUp and StepDown Actions (NOTE: These are standard UPnP actions)
--------------------------------------------------------

To increase the light level of a dimmer device, use the "StepUp" command.
To increase the light level of a dimmer device, use the "StepDown" command.
To set the StepDelta, use the "SetStepDelta" command.

The "StepDelta" parameter is the percentage of dim to change from the current level.
Before the StepUp or StepDown command is used, the SetStepDelta should be used to set the percentage of change desired.

The "StepDelta" is saved as a device variable, and is independent between devices.
If the "StepDelta" variable has not been set for a device when the "StepUp" or "StepDown" commands are executed, the "StepDelta" is set to a default value of 10.

The UPnP SetStepDelta action is:
http -
Code: [Select]
http://<IP Address of Vera>:3480/data_request?id=action&DeviceNum=<Vera ID of Dimmer>&serviceId=urn:upnp-org:serviceId:Dimming1&action=SetStepDelta&newStepDelta=<The amount of change desired>
Lua -
Code: [Select]
luup.call_action("urn:upnp-org:serviceId:Dimming1","SetStepDelta", {newStepDelta = <The amount of change desired>},<Vera ID of Dimmer>)

The UPnP StepUp action is:
http -
Code: [Select]
http://<IP Address of Vera>:3480/data_request?id=action&DeviceNum=<Vera ID of Dimmer>&serviceId=urn:upnp-org:serviceId:Dimming1&action=StepUp
Lua -
Code: [Select]
luup.call_action("urn:upnp-org:serviceId:Dimming1","StepUp", {},<Vera ID of Dimmer>)

The UPnP StepDown action is:
http -
Code: [Select]
http://<IP Address of Vera>:3480/data_request?id=action&DeviceNum=<Vera ID of Dimmer>&serviceId=urn:upnp-org:serviceId:Dimming1&action=StepDown
Lua -
Code: [Select]
luup.call_action("urn:upnp-org:serviceId:Dimming1","StepDown", {},<Vera ID of Dimmer>)

To use the Actions in a scene, you can add the actions and parameters using the advanced scene editor, or via lua code.

« Last Edit: March 10, 2016, 09:15:57 pm by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #3 on: January 03, 2016, 06:50:36 am »

** reserved **
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #4 on: January 13, 2016, 02:15:48 pm »
Caseta Connect Version 1.0.5 (Version ID: 30056) released to fix bugs in initial release.
« Last Edit: January 13, 2016, 02:32:31 pm by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline kyb2012

  • Full Member
  • ***
  • Posts: 118
  • Karma: +4/-0
Re: PLUGIN: Caseta Connect
« Reply #5 on: January 17, 2016, 07:55:59 pm »
Just bought the Lutron starter pack and was bummed to see that the RA plugin only supported the Pro version of the controller.  Happy to see your plugin.  Will try ASAP

Offline jquincy

  • Full Member
  • ***
  • Posts: 135
  • Karma: +0/-0
Re: PLUGIN: Caseta Connect
« Reply #6 on: January 18, 2016, 04:03:07 pm »
I was unable to find the Plugin in the app store. I downloaded the files and followed you detailed (very good ) directions. The Plugin was created but it did not create any devices for the Caseta switches I have. I still have the Radio Ra2 plugin installed and the smart pro bridge.  Any suggestions on what I should check?

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #7 on: January 18, 2016, 06:24:18 pm »
I was unable to find the Plugin in the app store.

It is still pending approval in the Mios Marketplace... (15 days and counting...)

I still have the Radio Ra2 plugin installed and the smart pro bridge.  Any suggestions on what I should check?

The SmartBridge and SmartBridge Pro both allow multiple connections to the integration server(s). So having the RadioRa2 plugin still installed should not interfere with the Caseta plugin.

To make sure you have the latest status of the plugin, refresh your browser (F5 or CTRL-F5)

Then check the status of the plugin on the device tile.

Then check the settings of the plugin. Check that the "Bridge" tab shows the selected bridge, then check the "Summary" tab.. It should show the list of discovered devices.

If the devices appear in the summary, but not in Vera, you may need to reload the LuaUPnP engine and refresh your browser.

If the devices still do not appear, you will need to check the LuaUPnP log... You can post it here and I will try to figure out what is going wrong.
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #8 on: January 19, 2016, 06:27:09 am »
new version (v1.0.8) available in the first post of the thread...

v1.0.8     (Version ID: 30106) January 19, 2016 (Not available in App Marketplace)
-- fixed - unable to set debug mode from option page
-- fixed - unable to set poll time from option page
-- fixed - excessive debug logging when debug mode not enabled
-- fixed - child device variables updated when values have not changed
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline Neilyboy

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
Re: PLUGIN: Caseta Connect
« Reply #9 on: January 19, 2016, 09:01:17 am »
I can not wait to give this a go. Thank you so much for your work on this plug-in. I just purchased a used Pro Hub to go along with my VeraEdge. Thank you so much! Keep up the great work. Will provide feedback once everything is installed. Should be within the next month or so.

Neil

Offline jquincy

  • Full Member
  • ***
  • Posts: 135
  • Karma: +0/-0
Re: PLUGIN: Caseta Connect
« Reply #10 on: January 19, 2016, 01:11:14 pm »
I have logged out and logged back in to be sure the browser is refreshed. As far as the rest of the questions I am not exactly sure how to answer them. I have taken a snipit of what I am guessing I should be looking at ?

Offline jquincy

  • Full Member
  • ***
  • Posts: 135
  • Karma: +0/-0
Re: PLUGIN: Caseta Connect
« Reply #11 on: January 19, 2016, 01:12:40 pm »
And...

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #12 on: January 19, 2016, 07:02:24 pm »
I have taken a snipit of what I am guessing I should be looking at ?

Your issue is that you did not create the device correctly (you made a typo)...

Your device file is: D_CasetaConnect.cml

It should be: D_CasetaConnect.xml

With the device file being incorrectly specified, the plugin is not loaded.

Go to the Advanced page and correct the device file name, then close the device settings popup... then click on the red "Save" button in the upper right hand corner of the page... Allow the LuaUPnP engine to reload... then press F5 to refresh your browser...

You should then have the plugin running with a blue square icon that says "Caseta Lutron"...
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline jquincy

  • Full Member
  • ***
  • Posts: 135
  • Karma: +0/-0
Re: PLUGIN: Caseta Connect
« Reply #13 on: January 19, 2016, 08:50:44 pm »
Silly error on my part and I looked it over so many times.  So I changed the file to  be: D_CasetaConnect.xml

Now I get the message Caseta_Connect  No Smart Bridge Device Found

Status:No Bridge FoundVersion:1.0.5

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1002
  • Karma: +96/-5
Re: PLUGIN: Caseta Connect
« Reply #14 on: January 20, 2016, 12:15:32 am »
Now I get the message Caseta_Connect  No Smart Bridge Device Found

Status:No Bridge FoundVersion:1.0.5

First, upgrade to v1.0.8

Then, go to the options tab, enable debugging and post the LuaUPnP.log so I can see what's happening.

The discovery routine uses mDNS discovery to find the bridge, and if that fails to find a device it then uses arp table loading... One of those should find the bridge... But I only have a SmartBridge v2 and SmartBridge Pro v2 to test... If you are using the original version, they may have different responses to the mDNS query or may use a different MAC address range...

If you know the IP address that the bridge has, you can enter it manually and bypass the discovery process... Go to the Advance tab and you will find the variables "BRIDGE_IP" and "BRIDGE_MAC"... and set them to the IP address and MAC address (using the format aa:bb:cc:dd:ee:ff) of the bridge.

EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway