Well… this could be my problem ( I’m relieved that I’m not the only one who has a Com problem) as I’m not using the latest & greatest due to no RFXCom support or rather the new FW blocks the port needed.
edit: Vera Edge FW 1.7.3014
I was attempting to set up a new RMMini3 but couldn’t attach to my wifi network due to a stupid 32byte password limitation that also doesn’t allow spaces or other special chars. I’m not about to reconfigure all my devices to satisfy this limitation, so I will be returning this broadlink mini3.
Can anyone confirm if the RM2 Pro has the same limitation?
Thanks!
The RMPRO is the same. You will have the same problem.
I’ve been doing some investigating regarding the inability to discover devices and transfer e-Control data…
Apparently, in the e-Control app, there is an option to “lock” the configuration of a device to prevent accidental changes to the configuration. According to the documentation I could find, if you enable this option, it also has the (unintended??, but now documented) consequence of turning off discovery replies from the devices and preventing the sharing of device configuration on the WLAN.
So… Make sure that you do not “lock” the configuration in the e-Control app.
Check your router… Many have the ability to set up a secondary (or guest) SSID that can have a shorter/less convoluted password.
At me, in the new version 1.13, Mini began to be seen and managed from Windows.
Mobile applications do not see anything. In the scenarios, too, empty 
[quote=“cybrmage, post:84, topic:197515”]I’ve been doing some investigating regarding the inability to discover devices and transfer e-Control data…
Apparently, in the e-Control app, there is an option to “lock” the configuration of a device to prevent accidental changes to the configuration. According to the documentation I could find, if you enable this option, it also has the (unintended??, but now documented) consequence of turning off discovery replies from the devices and preventing the sharing of device configuration on the WLAN.
So… Make sure that you do not “lock” the configuration in the e-Control app.[/quote]
I don’t think that is it as I transferred the information to an old cell phone on the same network. That worked great, I think it has something to do with the Vera and the way it is setup.
Thanks zedrally & cybrmage for confirming the RM Pro has the same limitation. Yeah, I have a guest SSID already in use that also has a long pass-phrase (which is not “convoluted” and easy for guests to enter, BTW). However, I will change it to make it fit with the Broadlink limitations and require my guests to update their devices.
Thanks again - and looking forward to testing this device.
[quote=“cybrmage, post:1, topic:197515”]Broadlink RM2 Interface
Learn (IR only) and send (IR/RF codes) remote codes using your Vera.
No RM-Bridge required!!
Supported Devices
With the latest update (v 1.13 ) my ancient RM PRO working perfectly. THANK YOU!!!
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
- know the IP Address of your device
- have the e-Control application running and select the “more functions” page (stacked bars icon in upper left corner of the “Control” page
- Select “share”, then select “Share to other phones in WLAN”
- 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:
- 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)
- 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
- Determine the IP Address of the IOS/Android device running e-Control.
- have the e-Control application running and select the “more functions” page (stacked bars icon in upper left corner of the “Control” page
- Select “share”, then select “Share to other phones in WLAN”
- 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).[/quote]
I have just transferred the codes for two devices between two different phones with no access problem.
The download problem must be in Vera.
edit: This is on the same network as Vera.
Just out of interest I had a look at what HomeSeer had done and found a contributor who ran it through Tasker, what seems interesting is the http call.
hs.WriteLog "Starting!", 0
'replace the ip adress and port with your own(its the adress of your RM Tasker host)
const server_url = "http://192.168.100.165:9876/codes
Could be that it needs a subdirectory in the wget?
Reading back in this thread I thought I would try a different browser, just to rule out a problem.
So using Firefox, the same com problem is still there.
Undeterred, I downloaded the App into a VeraLite running UI5.
The RMPRO & Mini could not be discovered in a scan.
I then set up the Share in the App and ran a discovery in UI5, this had the effect of discovering the RMPRO but wouldn’t lock the devices or download the codes. Unfortunately, I wasn’t able to capture the discovery of the RMPro (I wasn’t able to lock the scroll). It returned a Key and confirmed the discovery, so I’m not sure if this info is of any use or not?
[code]
luup_log:167: (BroadLink::UPNP::AddEcontrol) Called. <0x2e1a8680>
01 11/25/17 15:35:32.187 luup_log:167: (BroadLink::UPNP::AddEcontrol) cmd1 [wget “http://192.168.0.22:48815” -O /etc/cmh-ludl/eControl-data.zip]. <0x2e1a8680>
01 11/25/17 15:35:32.188 luup_log:167: (BroadLink::UPNP::AddEcontrol) cmd2 [unzip /etc/cmh-ludl/eControl-data.zip -d /etc/cmh-ludl/]. <0x2e1a8680>
01 11/25/17 15:35:32.188 luup_log:167: (BroadLink::UPNP::AddEcontrol) cmd3 [rm -rf /etc/cmh-ludl/SharedData; rm -f /etc/cmh-ludl/eControl-data.zip]. <0x2e1a8680>
01 11/25/17 15:35:32.209 luup_log:167: (BroadLink::UPNP::AddEcontrol) Error - No e-Control data retrieved. <0x2e1a8680>
01 11/25/17 15:35:32.231 LuaInterface::CallFunction_Job2 device 167 function SBroadlink_Broadlink1_AddEcontrol_run failed (null) with return false <0x2e1a8680>[/code]
Hi there,
the plugin is working great stand alone however i want to create a scene however when i add a 2nd line under the scene advanced editor i add the 2nd send code and it says command already exists?
how should i do this?
thanks
Check your router… Many have the ability to set up a secondary (or guest) SSID that can have a shorter/less convoluted password.[/quote]
Just letting you know that this suggestion didn’t pan out. After changing the guest wifi pw to make it acceptable to Broadlink, it still never would connect to a strong 2.4G signal. The client device used to set up the Broadlink was on the same guest network and was connected fine.
Even if I solve this issue, I have another show-stopper in that the guest wifi network apparently requires a different subnet. My attempts to configure the guest network to be on the same subnet were not accepted by the router, which also does not provide VLAN capability that I can find.
TL;DR - Gave up on Broadlink RMMini due to connectivity issues and am now using Harmony Hub with Vera plugin and Google Assistant voice control.
Harmony with the plugin on Vera works well? Can you create scenes with it and appear in the app? That is, does it show all control functions in vera?
Check your router… Many have the ability to set up a secondary (or guest) SSID that can have a shorter/less convoluted password.[/quote]
Just letting you know that this suggestion didn’t pan out. After changing the guest wifi pw to make it acceptable to Broadlink, it still never would connect to a strong 2.4G signal. The client device used to set up the Broadlink was on the same guest network and was connected fine.
Even if I solve this issue, I have another show-stopper in that the guest wifi network apparently requires a different subnet. My attempts to configure the guest network to be on the same subnet were not accepted by the router, which also does not provide VLAN capability that I can find.
TL;DR - Gave up on Broadlink RMMini due to connectivity issues and am now using Harmony Hub with Vera plugin and Google Assistant voice control.[/quote]
Hi Guimares - it would be best to take further discussion of the Harmony/Vera plugin into the appropriate thread - [url=http://forum.micasaverde.com/index.php/board,83.0.html]http://forum.micasaverde.com/index.php/board,83.0.html[/url]
It is a mature plugin that works really well, and is actively supported by the author. Scenes can be set up, and what devices and buttons/labels that appear in the Vera interface are all configurable. Imperihome also integrates with the Harmony hub for triggering activities or scenes, and not to mention, the Harmony mobile app itself is very polished.
You can’t beat the Broadlink devices for their low cost, but unfortunately their WiFi limitations didn’t work out for me.
What ALL the other solution do is: use an android/other device to host bridge software that provides an API. The android device talks to the Broadlink device, the home automation system talks to the API on the android device.
This plugin eliminates the need for the android device, as it talks directly to the broadlink device.
No.
[quote=“zedrally, post:90, topic:197515”]I have just transferred the codes for two devices between two different phones with no access problem.
The download problem must be in Vera.[/quote]
[quote=“zedrally, post:93, topic:197515”]I then set up the Share in the App and ran a discovery in UI5, this had the effect of discovering the RMPRO but wouldn’t lock the devices or download the codes.
[code][/quote]
There should be absolutely NO connection between running the eControl app, and the devices being discoverable.
The two functions are seperate… Discovery scan does just that… discovers devices… once discovered, you select the one you want to use. (If you have multiple devices you need to use, you install multiple plugin instances)
The discovery process does NOT discover codes that were “learned” by the device.
The devices DO NOT store any codes.
All of your existing codes are stored in the eControl app.
Once a device is discovered, you can then use that device to learn codes… OR you can manually add codes… OR you can try to import the code from the eControl app.
When you run the eControl app on an android/ios device, and turn on WLAN sharing, the android/ios device runs a webserver that does ONLY one thing, it serves a ZIP file containing the eControl app configuration. That data includes discovered devices and learned IR/RF codes.
As I have NOT yet discovered the mechanism that the eControl app uses to discover other eControl instances on the LAN, the plugin requires the IP address of the device running the eControl app…
As you can see from the log, it is a simple process… Ask the Vera operating system to ask webserver on the eControl device for the zip file (cmd1 - the wget command). The vera OS will run the wget command and will try to download the zip file… If the operation succeeds, it creates the eControl-data.zip file, if it fails, the file is not created… If, after having the Vera OS try to retrieve the file, the file does not exist, then you get the “Error - No e-Control data retrieved” message. No data retreived, no data to process, nothing further to do.
There is NOTHING that the plugin is doing to retrieve the file… It is all done by the OS… There is NOTHING in the pluging that can be fixed.
So… You need to…
- Make sure that the device running eControl is on the same network segment as the Vera.
- Make sure that the IP address you are using is the address for the device running eControl, NOT the IP address of the broadlink device.
Also note, The plugin does both Broadcast discover and, if the broadcast discovery does not find any devices, ARP table discovery (sends a UDP packet to every address on the local network to force the ARP table to populate, then read all the addresses in the ARP table)… If this doesn’t find your devices, then they are probably not on the same network segment as your Vera.
[/code]
Homelink does have native discovery and command processing.
[quote=“Nfluester, post:94, topic:197515”]Hi there,
the plugin is working great stand alone however i want to create a scene however when i add a 2nd line under the scene advanced editor i add the 2nd send code and it says command already exists?
how should i do this?
thanks[/quote]
This I hadn’t noticed… But see how it could be a problem…
An immediate fix would be to add delayed actions to the scene… The scene editor will allow the same actions if they are delayed…
OR you could add as many call_action statements as needed to the scene luup code…
I will incorporate the ability to specify multiple codes in one command to the next version…