PLUGIN: Broadlink RM Interface

The Local Vera Concierge Server is under development and will provide Broadlink integration with Vera.
I do not have any RF devices to test with.
Actually I do, but the Broadlink APP will not learn from it … Neither does the Local Concierge Server.
I am looking for a tester that has a Broadlink Pro, an RF device that can be learned by the Broadlink APP and has … or is willing to install the Local Concierge Server.
I would like to Verify the RF learning process.

Shortly I will provide the Plugin to control these from your Scenes, LUA, PLEG, or Google Home devices or Assistant.

RF or IR?
Not that it matters to me yet as I’m waiting on the mail delivery.

The IR works fine … I have tested with multiple IR devices in my house (RM Mini and RM Pro)
I am looking to test with an RF remote … My Dish box has an RF remote … It won’t learn from it. But neither does the Broadlink APP.
My Dish box also supports IR … So I think I am OK … just have to put a Mini in my AV closet.

Having just read the Manual, it appears (to me) that RF devices are discovered by the Pro App and no learning is possible (Unless there is a RF Remote available). Without either a Pro or compatible RF device, I’m really grasping at straws and am hating China Post for their tardiness in deliveries…
In the meantime, I’m all ears as to what others have added to the Pro, the Pro App and this Plugin and of course what they would like to add to your PlugIn

Hi Guys.

I’m so happy to find this plugin.

I’m a Vera Edge user and I just find this Broadlink RM interface in the App store. I have a old Broadlink RM PRO, about 4 years old and according to e-Control app on my phone running on Firmware version v20.
My Vera Edge on a latest firmware 1.7.3231.

I installed the Broadlink Plugin, in Devices → Broadlink RM Interface → Devices and I hit ReScen but ’ No Discovered Devices ’

Did I miss something or why my RM PRO not discovered?

Thank You

If that is accurate, it is an ancient firmware… The current version is v20025. Use e-Control to update the firmware version, and try aagain.

If that is accurate, it is an ancient firmware… The current version is v20025. Use e-Control to update the firmware version, and try aagain.[/quote]

I know it is an old Firmware. I have already try to upgrade it a couple of years ago with no luck. Always got the same message ’ Internet connection is poor.’ but I have no problem with my internet. Even contacted with the factory, they gave me URL to upgrade my RM PRO and still the same. It won’t upgrade.
Anyway if I unable to use this plugin without upgrade or no one have an idea how to ‘fix’ my problem, then I have to buy a new one RM PRO.

My rm pro is with v20028. Still not recognizes devices. Do not know how to proceed.

Sent from my iPhone using Tapatalk

[quote=“cybrmage, post:1, topic:197515”]**** 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).[/quote]

Hello, I’m new here. I have a You Tube channel that talks about the schedules and functions of various models of Broadlink, but in Portuguese. But you can use Google translator. I am also user VeraPlus and Edge.

I’m sorry, but I did not understand how to integrate the two devices, Vera and Broadlink, could you pass me the step by step? I am also testing the IFTTT for Mios …
Tks

[quote=“cybrmage, post:1, topic:197515”]Broadlink RM2 Interface

Learn and send IR 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.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:

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 with the IP Address of your Vera, and 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:

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

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)
  1. 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.

**** 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).[/quote]

Hi all, I have installed Broadlink Plugin, but:

  1. In Devices there is nothing Broadlink related appeared.
  2. In app list to install for Broadlink there is still not checkbox, that I have installed it, but when I am trying to install it again, then I see a popup - application is installed… I am confused and finally this app is not visible in my apps…

I am running the latest version 1.7.3231…

What to do?

Auto-discovery does not work. I have Vera Edge and Broadlink with the latest updates. For Broadlink plugin I tried the versions: 1.4, 1.8 and 1.10. If I force my Vera to update to a specific release the version is changed but the same effect does not work. I get the following message:

[tt]This page contains the following errors:
error on line 2 at column 50: xmlns:u: ‘Unknown Service’ is not a valid URI
Below is a rendering of the page up to the first error.[/tt]

OK

If I press DEBUG button I get the following message:
ERROR: Device not ready

Has the App been released in the store?

<root Using_2G="0" LoadTime="1510474247" DataVersion="474248555" UserData_DataVersion="474247075" TimeStamp="1510477639" lights_on="1" lights_off="7" doors_locked="0" doors_unlocked="0" sensors_tripped="0" sensors_not_tripped="8" failed_devices="0" visible_devices="84" partitions_active="0" partitions_notactive="0" ZWaveStatus="1" Mode="1" LocalTime="2017-11-12 11:07:19 D"> <Device_Num_510 PendingJobs="0" status="-1"> <states> <state id="95" service="urn:micasaverde-com:serviceId:Broadlink1" variable="PLUGIN_VERSION" value="v1.8"/> <state id="96" service="urn:micasaverde-com:serviceId:Broadlink1" variable="DebugMode" value="DISABLED"/> <state id="97" service="urn:micasaverde-com:serviceId:Broadlink1" variable="SelectedDevice" value=""/> <state id="98" service="urn:micasaverde-com:serviceId:Broadlink1" variable="DISCOVERED_DEVICES" value=""/> <state id="99" service="urn:micasaverde-com:serviceId:Broadlink1" variable="CommandCodes" value=""/> <state id="100" service="urn:micasaverde-com:serviceId:HaDevice1" variable="Configured" value="0"/> <state id="101" service="urn:micasaverde-com:serviceId:HaDevice1" variable="CommFailure" value="0"/> <state id="102" service="urn:micasaverde-com:serviceId:HaDevice1" variable="ID" value="Broadlink RM Interface"/> </states> <Jobs/> <tooltip display="0"/> </Device_Num_510> <alerts> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13077094871" LocalDate="2017-11-11 23:30:11" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510435811" Code="DL_ARMEDTRIPPED" NewValue="1" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13077127311" LocalDate="2017-11-11 23:32:31" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510435951" Code="DL_ARMEDTRIPPED" NewValue="0" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13078813501" LocalDate="2017-11-12 01:29:11" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510442951" Code="DL_ARMEDTRIPPED" NewValue="1" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13078886351" LocalDate="2017-11-12 01:34:31" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510443271" Code="DL_ARMEDTRIPPED" NewValue="0" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13081939021" LocalDate="2017-11-12 05:38:41" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510457921" Code="DL_ARMEDTRIPPED" NewValue="1" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13081963841" LocalDate="2017-11-12 05:41:01" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510458061" Code="DL_ARMEDTRIPPED" NewValue="0" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13082594141" LocalDate="2017-11-12 06:42:11" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510461731" Code="DL_ARMEDTRIPPED" NewValue="1" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13082615981" LocalDate="2017-11-12 06:44:31" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510461871" Code="DL_ARMEDTRIPPED" NewValue="0" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13083217801" LocalDate="2017-11-12 07:45:11" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510465511" Code="DL_ARMEDTRIPPED" NewValue="1" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> <alert PK_Device="495" Room="12" DeviceName="Ping Sensor" DeviceType="urn:schemas-demo-ted-striker:device:PingSensor:1" PK_Alert="13083246701" LocalDate="2017-11-12 07:47:31" EventType="4" SourceType="4" Argument="0" Filesize="0" Severity="1" LocalTimestamp="1510465651" Code="DL_ARMEDTRIPPED" NewValue="0" Description="Ping Sensor" Users="" Server_Storage="" Key="" Icon="" PK_Store="0"/> </alerts> </root>

I’m stuck.

V1.8
error message: Broadlink RM Interface[474] : Running Lua Startup

Does not initalise.

Unable to enable DEBUG with a error message Device not ready (not surprised by that).
Have deleted and re-installed with the same results.
Logging not possible so I don’t know where to go from here.

The log exceeds the permitted length, I’m really not familiar with providing these, but read up on in it in wiki and used the following which probably hasn’t got the right filter?

http://192.168.0.21/cgi-bin/cmh/log.sh?Device=LuaUPnP

Attached a pdf of it.

and for good measure.

[quote=“TMC, post:32, topic:197515”]Auto-discovery does not work. I have Vera Edge and Broadlink with the latest updates. For Broadlink plugin I tried the versions: 1.4, 1.8 and 1.10. If I force my Vera to update to a specific release the version is changed but the same effect does not work. I get the following message:

[tt]This page contains the following errors:
error on line 2 at column 50: xmlns:u: ‘Unknown Service’ is not a valid URI
Below is a rendering of the page up to the first error.[/tt]

OK

If I press DEBUG button I get the following message:
ERROR: Device not ready[/quote]

First of all, thanks for your effort making a plugin! I also get the exact same error as this. Would love to have this plugin working.

Did any of you try to see if the “Local Concierge Server” sees your RM devices ?