Author Topic: PLUGIN: Broadlink RM Interface  (Read 2179 times)

Offline Guimaraes

  • Sr. Newbie
  • *
  • Posts: 35
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #60 on: November 14, 2017, 12:41:25 pm »
That's what a Mexican soap opera says ... there's no end to it.

Offline nirgal

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #61 on: November 14, 2017, 01:52:14 pm »
Any chance to add support for SP modules ?
Or to explain how this can be done?

Offline zedrally

  • Hero Member
  • *****
  • Posts: 862
  • Karma: +2/-0
  • Black Cat Controllers & Control Systems
    • Black Cat Control Systems
Re: PLUGIN: Broadlink RM Interface
« Reply #62 on: November 14, 2017, 04:53:14 pm »
Actually... You *DID* state that it was not working...


Still no, do you still need the log?

What do you mean tommorrow??? You're in Oz... It is Tommorrow...


Actually Today now.
Next problem/question.
Is there a new device that should be created when the IP address of e-Control is added?,
No log supplied as I have no idea what to expect other than I see no way to control the device.

Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, then some  Black Cat Cat's Eye PIR's & Door-Window Sensors plus a Z-UNO or 2.

Offline zedrally

  • Hero Member
  • *****
  • Posts: 862
  • Karma: +2/-0
  • Black Cat Controllers & Control Systems
    • Black Cat Control Systems
Re: PLUGIN: Broadlink RM Interface
« Reply #63 on: November 14, 2017, 10:45:54 pm »
You are going to ask for the log.
Adding the IP Address has no effect and doesn't retrieve e-Control codes

08   11/15/17 14:39:41.773   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=477 <0x73202520>
08   11/15/17 14:39:41.773   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Broadlink1 <0x73202520>
08   11/15/17 14:39:41.774   JobHandler_LuaUPnP::HandleActionRequest argument eControl_ip=192.168.0.22 <0x73202520>
02   11/15/17 14:39:41.775   luup_log:477: (BroadLink::UPNP::AddEcontrol) Called. <0x73202520>
01   11/15/17 14:39:41.775   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd1 [wget "http://192.168.0.22:48815" -O /etc/cmh-ludl/eControl-data.zip]. <0x73202520>
01   11/15/17 14:39:41.776   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd2 [unzip /etc/cmh-ludl/eControl-data.zip -d /etc/cmh-ludl/]. <0x73202520>
01   11/15/17 14:39:41.776   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd3 [rm -rf /etc/cmh-ludl/SharedData; rm -f /etc/cmh-ludl/eControl-data.zip]. <0x73202520>
01   11/15/17 14:39:41.800   luup_log:477: (BroadLink::UPNP::AddEcontrol) Error - No e-Control data retrieved. <0x73202520>
01   11/15/17 14:39:41.826   LuaInterface::CallFunction_Job2 device 477 function SBroadlink_Broadlink1_AddEcontrol_run failed (null) with return false <0x73202520>
02   11/15/17 14:39:41.827   JobHandler_LuaUPnP::RunAction device 477 action urn:micasaverde-com:serviceId:Broadlink1/AddEcontrol failed with 501/Action failed <0x73202520>
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, then some  Black Cat Cat's Eye PIR's & Door-Window Sensors plus a Z-UNO or 2.

Offline hvazana

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #64 on: November 15, 2017, 11:44:14 am »
 Guys. I tried something that actually solved the device detection problems. I just uninstalled the plugin , changed the browser to explorer (edge) , and that?s it. Response of the plugin was immediately different. Devices detected. When trying to select a device there were problems again so I changed back to chrome. Bam.. worked again.  Codes were transferred as well.  Slowly slowly it is starting to work. Codes are now working . This worked for me . Good luck for those who faced the same issue.


Sent from my iPhone using Tapatalk

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +105/-5
Re: PLUGIN: Broadlink RM Interface
« Reply #65 on: November 15, 2017, 01:26:08 pm »
Any chance to add support for SP modules ?

No. The SP modules do not have IR/RF capabilities


Or to explain how this can be done?

Use the correct plugin -> HERE.
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - Broadlink RM - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +105/-5
Re: PLUGIN: Broadlink RM Interface
« Reply #66 on: November 15, 2017, 01:28:01 pm »
Adding the IP Address has no effect and doesn't retrieve e-Control codes

Nope. Logs not needed (but did confirm)...

You did not follow the instructions (given in the first post in the thread), and the plugin could not retrieve the e-Control data.
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - Broadlink RM - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +105/-5
Re: PLUGIN: Broadlink RM Interface
« Reply #67 on: November 15, 2017, 01:48:47 pm »
I originally loaded V1.10

Not the latest version. Latest version is always listed in the first post of the thread.

Forced the plugin update to V1.4

Not an upgrade... actually a downgrade...

Then forced the plugin to V1.8 and still no go.

Still not an upgrade...

I have the correct IP address in the advanced ip address.

Did you read the instructions (in the first post of the thread)??? No. The "ip" parameter in the advanced tab is not used. Follow the instructions to select the device.
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - Broadlink RM - MyQGateway

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +105/-5
Re: PLUGIN: Broadlink RM Interface
« Reply #68 on: November 15, 2017, 01:55:34 pm »
changed the browser

The Vera UI web interface has been horribly broken for the past 4 or 5 firmware releases... As I (and others) have said, If it doesn't work, try a different browser.

I take ABSOLUTELY no responsibility for recurrent issue with the MIOS firmware.

That being said, I do most of the development and testing of my plugin using Firefox. It has been stable and working despite issues with other browsers.
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - Broadlink RM - MyQGateway

Offline zedrally

  • Hero Member
  • *****
  • Posts: 862
  • Karma: +2/-0
  • Black Cat Controllers & Control Systems
    • Black Cat Control Systems
Re: PLUGIN: Broadlink RM Interface
« Reply #69 on: November 15, 2017, 05:30:34 pm »

Import IR/RF codes or Devices from e-Control
==============================

  1) Determine the IP Address of the IOS/Android device running e-Control.    Check
  2) have the e-Control application running and select the "more functions" page (stacked bars icon in upper left corner of the "Control" page  Check
  3) Select "share", then select "Share to other phones in WLAN"  Check
  4) On the plugin code management page, in the "Add code from network connected device running e-Control." box, enter the IP address of the phone and click "Add"  Check After eControl says it has compressed files.
Processing eControl Data
No devices found.

Code: [Select]
02   11/16/17 9:28:22.266   Finished rotate logs <0x77e38000>
08   11/16/17 9:28:23.372   JobHandler_LuaUPnP::HandleActionRequest device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 action: AddEcontrol <0x731ae520>
08   11/16/17 9:28:23.373   JobHandler_LuaUPnP::HandleActionRequest argument action=AddEcontrol <0x731ae520>
08   11/16/17 9:28:23.373   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=477 <0x731ae520>
08   11/16/17 9:28:23.373   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Broadlink1 <0x731ae520>
08   11/16/17 9:28:23.374   JobHandler_LuaUPnP::HandleActionRequest argument eControl_ip=192.168.0.22 <0x731ae520>
02   11/16/17 9:28:23.375   luup_log:477: (BroadLink::UPNP::AddEcontrol) Called. <0x731ae520>
01   11/16/17 9:28:23.375   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd1 [wget "http://192.168.0.22:48815" -O /etc/cmh-ludl/eControl-data.zip]. <0x731ae520>
01   11/16/17 9:28:23.376   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd2 [unzip /etc/cmh-ludl/eControl-data.zip -d /etc/cmh-ludl/]. <0x731ae520>
01   11/16/17 9:28:23.377   luup_log:477: (BroadLink::UPNP::AddEcontrol) cmd3 [rm -rf /etc/cmh-ludl/SharedData; rm -f /etc/cmh-ludl/eControl-data.zip]. <0x731ae520>
01   11/16/17 9:28:24.805   luup_log:477: (BroadLink::UPNP::AddEcontrol) Error - No e-Control data retrieved. <0x731ae520>
01   11/16/17 9:28:24.832   LuaInterface::CallFunction_Job2 device 477 function SBroadlink_Broadlink1_AddEcontrol_run failed (null) with return false <0x731ae520>
02   11/16/17 9:28:24.833   JobHandler_LuaUPnP::RunAction device 477 action urn:micasaverde-com:serviceId:Broadlink1/AddEcontrol failed with 501/Action failed <0x731ae520>
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, then some  Black Cat Cat's Eye PIR's & Door-Window Sensors plus a Z-UNO or 2.

Offline nirgal

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #70 on: November 16, 2017, 10:57:26 am »
@cybrmage

Thanks for the "PLUGIN: Wifi/UDP Switch Controller " I will try it.

Offline cybrmage

  • Hero Member
  • *****
  • Posts: 1056
  • Karma: +105/-5
Re: PLUGIN: Broadlink RM Interface
« Reply #71 on: November 16, 2017, 11:08:54 pm »
Code: [Select]
01   11/16/17 9:28:24.805   luup_log:477: (BroadLink::UPNP::AddEcontrol) Error - No e-Control data retrieved. <0x731ae520>

That line indicates that the plugin could not retrieve the eControl zip file from your device.

This is entirely out of the control of the plugin.

It means that the wget command issue using os,execute() did not generate the zip file.

So... That means that the eControl device is
1) not accessible to the Vera
2) is not sharing the data (The "share to device on WLan" function sets up a web server on the device... there are many possible reasons for this to fail on the eControl device).

Make sure that the IP address is correct, and that it IS accessible to the Vera device (ie: not on a remote network segment, etc).

Force close the e-Control app. Reboot the device and try running e-Control again after a fresh reboot.
« Last Edit: November 16, 2017, 11:10:44 pm by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - Broadlink RM - MyQGateway

Offline glendale2008

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #72 on: November 17, 2017, 10:53:28 am »
Hi, so far I could not see the devices, so first thing first a basic question: do I need to have the RMs connected to the wifi network created by Vera or they can be connected to a separate wifi going into the same router? Thank you in advance

Offline elton

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: PLUGIN: Broadlink RM Interface
« Reply #73 on: November 17, 2017, 05:54:53 pm »
Broadlink RM2 Interface
------------------------

Learn (IR only) and send (IR/RF codes) remote codes using your Vera.

No RM-Bridge required!!


Supported Devices
-------------------

All Broadlink RM/RM2/RM3 devices.


Features:
------------
Automatic detection of Broadlink devices
Management of IR codes from the code management page.
Manual send of codes from the code management page.
Send code using UPNP action, lua call_action or from a scene

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

v1.13   (Version ID: 35006) November 14, 2017
-- fixed - timestamp issue caused plugin crash on certain firmware versions
-- fixed - unsupported devices appear in discovered device list

v1.10   (Version ID: 34952) November 7, 2017
-- added - device discovery through device probing when discovery mechanism fails to discover devices
-- added - device discovery via import of e-Control configuration
-- changed - prevent re-import of IR/RF codes when processing additional e-Control imports
-- changed - plugin excessively chatty when debug mode is disabled

v1.8     (Version ID: 34906) November 3, 2017
-- fixed - json handling caused configuration page to fail to load under certain circumstances
-- added - better device determination - support for more device variants

v1.6     (Version ID: 34892) October 30, 2017
-- fixed - UPnP SendCode action causes plugin crash

v1.5     (Version ID: 34886) October 30, 2017
-- fixed - code corruption when importing Pronto/e-Control codes
-- fixed - code verification regected valid code under certain conditions
-- added - update code name from code management page

v1.4     (Version ID: 34871) October 29, 2017
-- added - Ability to manually import a code in the code management page
-- added - Ability to manually import a PRONTO format code in the code management page
-- added - Ability to import IR Code configuration from the Broadlink e-Controll mobile app (Android or IOS)
NOTE* - To import code from e-Control, you must
  1) know the IP Address of your device
  2) have the e-Control application running and select the "more functions" page (stacked bars icon in upper left corner of the "Control" page
  3) Select "share", then select "Share to other phones in WLAN"
  4) On the plugin code management page, in the "Add code from network connected device running e-Control." box, enter the IP address of the phone and click "Add"

v1.3     (Version ID: 34862) October 29, 2017
-- fixed - typo prevented sending non-RF codes to non-pro devices

v1.2     (Version ID: 34856) October 29, 2017
-- fixed - Broadlink device initial discovery did not occur
-- added - option on device page to rescan for devices

v1.1     (Version ID: 34846) October 28, 2017
-- Initial release.
-- NOTE: This version will display in the UI as "v1.0"




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=8996&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.



Configuration
--------------

Once the plugin is installed, allow the LuaUPnP engine to finish loading and REFRESH YOUR BROWSER.

Open the device setup page, and click on the "Device" tab. The plugin will list all the Broadlink devices found on the network. Click on the "select" button next to the device you want to use for sending/learning IR codes.

You can then click on the "Codes" tab. The Codes page will show a summary of the existing learned codes (which will initially be empty). You can the click on the "Learn IR" button. The plugin will ask for the name you wish to give to the learned code. Once you enter the name and click on "ok", the plugin will place the selected Broadlink device into learn mode (an amber led will light on the Broadlink device). You then have 30 seconds to point the remote at the broadlink device and press the button you wish to learn. Once the code is learned, the broadlink device will return to normal mode, and the code page will be updated with the new code. Once a code is learned, you can then test the code by clicking the "Send" button next to the code. Unneeded or unwanted codes can be removed by clicking on the "Remove" button.


To have the Broadlink device send an IR code, you can:

1) Use a UPNP action to cause a stored code to be sent.

ie:
Code: [Select]
http://vera.ip.add.ress:3480/data_request?id=action&DeviceNum=<DeviceNumber>&serviceId=urn:micasaverde-com:serviceId:Broadlink1&action=SendCode&CodeData=<stored code identifier>

Where:
    vera.ip.add.ress = The IP Address of your Vera
    <DeviceNumber> = The Vera Device ID of the Broadlink RM device
    <stored code identifier> = the unique identifier of the stored code (see below for details)

or

Code: [Select]
luup.call_action("urn:micasaverde-com:serviceId:Broadlink1", "SendCode", {CodeData = "<stored code identifier>"}, <DeviceNumber>)

Where:
    <DeviceNumber> = The Vera Device ID of the Broadlink RM device
    <stored code identifier> = the unique identifier of the stored code (see below for details)




2) Use the Vera Scene Advanced editor, to send a code from a Vera Scene.

In the Vera Scene Editor, to to the advanced editor and select "Add Action", select the Broadlink RM Interface device, Select the "SendCode" action, and enter the stored code identifier into the CodeData text box, and click on "Add".



Stored Code Identifiers
===============

Each learned code must be identified with a unique identifier. The unique identifier can be either the name of the stored code or the ID shown on the code management page.

Please note that, at this time, if you use more that a single word for the name of a code, you *MUST* use the ID to identify the code.

NOTE: Although the plugin identifies the IP address of the device that learned a code, the codes are *NOT* specific to individual Broadlink devices. You *CAN* learn code with one device and send them with another device.



Import IR/RF codes or Devices from e-Control
==============================

  1) Determine the IP Address of the IOS/Android device running e-Control.
  2) have the e-Control application running and select the "more functions" page (stacked bars icon in upper left corner of the "Control" page
  3) Select "share", then select "Share to other phones in WLAN"
  4) On the plugin code management page, in the "Add code from network connected device running e-Control." box, enter the IP address of the phone and click "Add"

Note: Devices included in the e-Control data are not directly imported into the plugin. The device identifier is used to locate the device, if the device is located, it is added to the discovered device list. The device(s) are NOT automatically selected.


**** PLEASE NOTE ****

If you have problems, and expect any support.... you MUST post LuaUPnP logs showing the operation of the plugin (with the plugin debug mode enabled).

###################################################################################################

Hi, I'm new here, I'm following your explanation, but I do not go from this part:
2) Use the Vera Scene Advanced editor to send a Vera Scene code.
No vera edge is not showing my Broadlink when I have to add it to the scene!
Is there any other way to do it? :-\ :-\

Offline zedrally

  • Hero Member
  • *****
  • Posts: 862
  • Karma: +2/-0
  • Black Cat Controllers & Control Systems
    • Black Cat Control Systems
Re: PLUGIN: Broadlink RM Interface
« Reply #74 on: November 17, 2017, 09:54:52 pm »
Unfortunately, I have followed your suggestion and none of this helps. (I do appreciate your help with this)
I haven't even able to "Learn" the codes directly.
The codes have been backed up and I have tried with the App running and not running, rebooted several times with no success.
I have even tried to access Broadlink directly and cannot, with the firewall turned either ON/Off.
I had expected a return message for a User name & Password, nup just an error page.
The only redeeming feature so far is that it works well Locally and Remotely just not with Vera.


If anyone has any suggestions, I'm all ears.....

edit: could it be a specific Port that is being blocked?


In the meantime 'm going to setup Vera Concierge and see what happens next.
« Last Edit: November 18, 2017, 01:01:17 am by zedrally »
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, then some  Black Cat Cat's Eye PIR's & Door-Window Sensors plus a Z-UNO or 2.