Vera - Smarter Home Control Forum

Advanced => Programming => Plugins & Plugin Development => Topic started by: cybrmage on October 28, 2017, 06:08:31 am

Title: PLUGIN: Broadlink RM Interface
Post by: cybrmage on October 28, 2017, 06:08:31 am
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).
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on October 28, 2017, 10:24:39 am
Great ... you beat me to be to it ...  I will still probably release mine as well ... integrated with voice control.

Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on October 28, 2017, 04:43:34 pm
mmm, I'm waiting on my two to arrive (Pro & Mini) so I can test. Now I can't wait!
I had been wanting to buy a Goggle Home so having voice available would be a plus, so I'm still waiting on your your version richard!
Thanks guy's ( both of you), making devices compatible with Vera is really state of art, just need to get Vera to sort out it's own bugs and the world will be a better place.



Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 28, 2017, 07:36:46 pm
weird, it does not show up in the available apps...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on October 28, 2017, 07:43:54 pm
Did you notice:

Quote

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>

Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 28, 2017, 07:59:48 pm
Did you notice:

Quote

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>


yup, just don't know what to put in for the version...  any entry gets me this error:

Code: [Select]
ERROR: Failed to retrieve plugins
EDIT: never mind, i'm a dumbass...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 29, 2017, 09:58:35 am
Auto-discovery does not seem to work.  I've installed the plugin and it shows "no selected device" on the devices list.  I uninstalled and re-installed the UPnP proxy and verified it is running by going to http://<IP OF VERA>:2529/version.   that returns the running version.  Not sure what else to try.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on October 29, 2017, 12:26:56 pm
Auto-discovery does not seem to work.

My fault... Fixed in latest version...


weird, it does not show up in the available apps...

With the rate that Vera/Mios reviews and approves plugins, It should be available on the app store in 3 to 6 weeks. (ok... A little exagerated... but not much... I have seen approvals take over two weeks at some points... Some of my plugins have had 6 or seven updates pending approval at one time...)


Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 29, 2017, 08:09:30 pm
Thank you!!! this is awesome... I really wish there was a way to import all the codes i have already learned on the iphone app.   Guess i'll spend some time churning through the 'motes.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on October 30, 2017, 01:48:56 am
I really wish there was a way to import all the codes i have already learned on the iphone app.

I depends on which app you are refering to... there are Two... e-control and IHC...

If you are using e-control, i have figured out how to retrieve the IR Codes from an Android or IOS device... The tricky part is parsing the data and adding it... which will take a little time...

Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 30, 2017, 09:14:31 am
If you are using e-control, i have figured out how to retrieve the IR Codes from an Android or IOS device... The tricky part is parsing the data and adding it... which will take a little time...

I am using e-control.  If there is anyway i can help, let me know...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana on October 30, 2017, 02:50:13 pm
Guys. could you tell how did you succeed to download the plugin. The command for forcing the Vera to retrieve it did not work for me. Maybe I?m doing something wrong .  Any tip you can share ?? 


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 30, 2017, 02:59:43 pm
Guys. could you tell how did you succeed to download the plugin. The command for forcing the Vera to retrieve it did not work for me. Maybe I?m doing something wrong .  Any tip you can share ?? 


Sent from my iPhone using Tapatalk

Did you try this?  replace <your ip> with the ip of your vera...

Code: [Select]
http://<your ip>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8996&Version=34871
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana on October 30, 2017, 03:24:59 pm
 Worked !!! Thanks


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 30, 2017, 03:40:30 pm
I really wish there was a way to import all the codes i have already learned on the iphone app.

I depends on which app you are refering to... there are Two... e-control and IHC...

If you are using e-control, i have figured out how to retrieve the IR Codes from an Android or IOS device... The tricky part is parsing the data and adding it... which will take a little time...

Import worked like a charm,but it seems the codes do not work when triggered from the vera.    I was watching the logs when i sent the command via a web request (http://my.vera.ip.addr:3480/data_request?id=action&DeviceNum=178&serviceId=urn:micasaverde-com:serviceId:Broadlink1&action=SendCode&CodeData=1509390321) and this is what showed:

Code: [Select]
08 10/30/17 16:06:42.893 JobHandler_LuaUPnP::HandleActionRequest device: 178 service: urn:micasaverde-com:serviceId:Broadlink1 action: SendCode <0x715c7520>
08 10/30/17 16:06:42.893 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=178 <0x715c7520>
08 10/30/17 16:06:42.893 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Broadlink1 <0x715c7520>
08 10/30/17 16:06:42.893 JobHandler_LuaUPnP::HandleActionRequest argument action=SendCode <0x715c7520>
08 10/30/17 16:06:42.893 JobHandler_LuaUPnP::HandleActionRequest argument CodeData=1509390321 <0x715c7520>
02 10/30/17 16:06:42.894 luup_log:178: (BroadLink::UPNP::SendCode) Called. <0x715c7520>
01 10/30/17 16:06:42.895 LuaInterface::CallFunction_Job device 178 function SBroadlink_Broadlink1_SendCode_run failed [string "VERSION = "v1.4"..."]:1596: attempt to index local 'sCommand' (a number value) <0x715c7520>


If i send the code from the send button on the codes page in the plugin i get the following, but still no response from the TV:

Code: [Select]
08 10/30/17 16:30:02.955 JobHandler_LuaUPnP::HandleActionRequest device: 178 service: urn:micasaverde-com:serviceId:Broadlink1 action: SendCode <0x713c7520>
08 10/30/17 16:30:02.956 JobHandler_LuaUPnP::HandleActionRequest argument action=SendCode <0x713c7520>
08 10/30/17 16:30:02.956 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=178 <0x713c7520>
08 10/30/17 16:30:02.956 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Broadlink1 <0x713c7520>
08 10/30/17 16:30:02.956 JobHandler_LuaUPnP::HandleActionRequest argument CodeData={"Name":"TV_BTN_34","Timestamp":1509390321,"Source":"e-Control","Code":"32363030353830303030303132363934313431313131313431323337313231343132313231313134313131333133313231323338313233373132313331343336313133383132333731643264313233383133313131313134313231333133333631333132313131343133313231323133313133383131333831323338313531303131333831323338313333363134333631323030303464353030303132373462313230303063353230303031323634623132303030643035"} <0x713c7520>
02 10/30/17 16:30:02.957 luup_log:178: (BroadLink::UPNP::SendCode) Called. <0x713c7520>
02 10/30/17 16:30:03.446 luup_log:178: (BroadLink::UPNP::SendCode) Sent code data. <0x713c7520>

ALSO: One suggestion for a future version (as if you hadn't done enough), it would be nice to add the ability to give the imported codes a friendly name.  I can prpbably edit them in the advanced variable tab,but it would be nice to be able to do it from the UI.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on October 30, 2017, 11:33:48 pm
Import worked like a charm,but it seems the codes do not work when triggered from the vera.

Somehow, I missed that the imported codes were being corrupted when saved... (The codes were hex encoded when imported, then hex encoded again when being saved)

The latest version will detect and fix the corrupted codes, and the import function has been fixed... Once the codes are fixed, they can be sent...

The SendCode action is also fixed... so everything should work now.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: sebby on October 31, 2017, 08:15:39 am
Yup, this version works great!  thanks for adding the name change button!!
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana on October 31, 2017, 01:10:57 pm
Any suggestion for ?no discovered devices? status ? . Rescanned several times . 


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on October 31, 2017, 04:23:04 pm
Any suggestion for ?no discovered devices? status ? . Rescanned several times . 


Sent from my iPhone using Tapatalk

reboot you broadlink device. reboot your vera. Turn on debug mode in the plugin and post the LuaUPnP log showing the plugin startup.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana on October 31, 2017, 04:43:43 pm
Did both a reboot. the plugin debug mode does not work. status stays disabled.  both broadlink devices are not detected ( RM pro and RM mini) .
I am using version 1.6 .

Sometimes when pressing rescan he following error appear :" Error executing function selectDevicePage(): "
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on November 03, 2017, 11:31:51 pm
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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 03, 2017, 11:48:04 pm
RF or IR?
Not that it matters to me yet as I'm waiting on the mail delivery.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on November 04, 2017, 12:38:22 am
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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 04, 2017, 12:44:16 am
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
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Ben007 on November 07, 2017, 04:55:30 am
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
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 07, 2017, 11:14:25 am
according to e-Control app on my phone running on Firmware version v20.

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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Ben007 on November 07, 2017, 12:06:32 pm
according to e-Control app on my phone running on Firmware version v20.

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.

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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana on November 07, 2017, 02:00:55 pm
My rm pro is with v20028. Still not recognizes devices. Do not know how to proceed.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 07, 2017, 02:05:06 pm
My rm pro is with v20028. Still not recognizes devices. Do not know how to proceed.

**** 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).
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Guimaraes on November 08, 2017, 12:12:45 pm
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

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:
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.



**** 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).
Title: Re: PLUGIN: Broadlink RM Interface
Post by: s83569 on November 08, 2017, 06:38:43 pm
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?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: TMC on November 09, 2017, 09:06:36 am
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:

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.


OK

If I press DEBUG button I get the following message:
ERROR: Device not ready
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 12, 2017, 01:57:14 am
Has the App been released in the store?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: TMC on November 12, 2017, 04:14:31 am
Code: [Select]
<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>
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 12, 2017, 08:35:11 pm
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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 13, 2017, 12:41:21 am
Logging not possible so I don't know where to go from here.

you MUST post LuaUPnP logs
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 13, 2017, 01:35:40 am
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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 13, 2017, 01:38:06 am
and for good measure.



Title: Re: PLUGIN: Broadlink RM Interface
Post by: Bananfluen on November 13, 2017, 03:14:48 am
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:

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.


OK

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

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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on November 13, 2017, 05:52:08 am
Did any of you try to see if the "Local Concierge Server" sees your RM devices ?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Guimaraes on November 13, 2017, 11:25:21 am
Mine looks this way, but I can not write the codes ...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: nirgal on November 13, 2017, 01:01:31 pm
Hello,

Does the plugin can also be used with Broadlink SP (SmartPlug) devices - IP based plugs ?
I don't have any central Broadlink device beside the e-control app.

Thanks,
Nir
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 13, 2017, 02:44:38 pm
Attached a pdf of it.

which is quite useless... It shows 4 seconds of the Vera Z-Wave initialization, and not anything else...



Mine looks this way, but I can not write the codes ...

Which shows that you have some devices, and have selected a device... You don't show the "Codes" tab, which is where the codes are managed and manually sent... So far, I don't see a problem... If you can't send codes, show a screenshot of the codes page and the LuaUPnP log showing a send attempt....


Does the plugin can also be used with Broadlink SP (SmartPlug) devices - IP based plugs ?

No. This plugin is exclusively for the Broadlink RM (remote control) devices.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: TMC on November 13, 2017, 03:24:59 pm
Hi cybrmage.
How can I post LuaUPnP logs showing the operation of the plugin?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: TMC on November 13, 2017, 03:27:34 pm
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:

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.


OK

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

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.

I'm not the person who developed the plugin.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 13, 2017, 05:06:13 pm
Attached a pdf of it.

which is quite useless... It shows 4 seconds of the Vera Z-Wave initialization, and not anything else...



I thought as much but have no idea of how to get the log info you need. When it comes to this it looks like I'm not alone and need some hand holding to get the log info you need.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 13, 2017, 10:33:17 pm
Take 2.
The attachment covers deleting, reloading and installing V1.8



**************************************
************** STARTING **************
************************************** <0x7722f520>
02   11/14/17 14:18:29.598   luup_log:477: (BroadLink::getMiosVersion): vera_model [Sercomm NA301] mios_branch [1] mios_major [7] mios_minor [3014]. <0x7722f520>
02   11/14/17 14:18:29.599   luup_log:477: (BroadLink::getMiosVersion): MIOS_VERSION [UI7] openLuup [FALSE]. <0x7722f520>
06   11/14/17 14:18:29.600   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: PLUGIN_VERSION was: EMPTY now:  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.601   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: EMPTY now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.602   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: SelectedDevice was: EMPTY now:  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.602   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DISCOVERED_DEVICES was: EMPTY now:  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.603   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: CommandCodes was: EMPTY now:  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.604   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: EMPTY now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x8bad78/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.605   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:HaDevice1 variable: ID was: EMPTY now: Broadlink RM Interface #hooks: 0 upnp: 0 skip: 0 v:0xa489d8/NONE duplicate:0 <0x7722f520>
06   11/14/17 14:18:29.606   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: PLUGIN_VERSION was:  now: v1.8 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722f520>
50   11/14/17 14:18:29.606   luup_log:477: (BroadLink::Plugin_Init): Broadlink RM Interface - Plugin version [v1.8] - isDisabled 06   11/14/17 14:18:29.607   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7722f520>
06   11/14/17 14:18:29.608   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7722f520>
02   11/14/17 14:18:29.609   luup_log:477: (BroadLink::getDebugMode) DEBUG MODE [DISABLED] UnitID [NIL] DEV_SYS [FALSE]. <0x7722f520>
01   11/14/17 14:18:29.616   LuaInterface::CallFunction_Startup-1 device 477 function Plugin_Init failed [string "VERSION = "v1.8"..."]:800: bad argument #1 to 'char' (invalid value) <0x7722f520>
01   11/14/17 14:18:29.616   LuImplementation::StartLua running startup code for 477 I_Broadlink.xml failed <0x7722f520>
06   11/14/17 14:18:30.101   Device_Variable::m_szValue_set device: 196 service: urn:futzle-com:serviceId:AstronomicalPosition_Sun variable: RightAscensionRounded was: -130.5 now: -130.5 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x75e2f520>
06   11/14/17 14:18:30.102   Device_Variable::m_szValue_set device: 196 service: urn:futzle-com:serviceId:AstronomicalPosition_Sun variable: DeclinationRounded was: -18.3 now: -18.3 #hooks: 1 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x75e2f520>
06   11/14/17 14:18:30.103   Device_Variable::m_szValue_set device: 196 service: urn:futzle-com:serviceId:AstronomicalPosition_Sun variable: AzimuthRounded was: -44.4 now: -44.6 #hooks: 1 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x75e2f520>
50   11/14/17 14:18:30.112   luup_log:447: RFXtrx: Tree with number child devices: 3 <0x7542f520>
50   11/14/17 14:18:30.112   luup_log:447: RFXtrx:        door sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.113   luup_log:447: RFXtrx:      motion sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.113   luup_log:447: RFXtrx:       light sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.114   luup_log:447: RFXtrx:      light switches: 0 <0x7542f520>
50   11/14/17 14:18:30.114   luup_log:447: RFXtrx:  dim light switches: 0 <0x7542f520>
50   11/14/17 14:18:30.115   luup_log:447: RFXtrx:     window covering: 3 <0x7542f520>
50   11/14/17 14:18:30.115   luup_log:447: RFXtrx: temperature sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.116   luup_log:447: RFXtrx:    humidity sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.116   luup_log:447: RFXtrx:  barometric sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.116   luup_log:447: RFXtrx:        wind sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.117   luup_log:447: RFXtrx:        rain sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.117   luup_log:447: RFXtrx:          UV sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.118   luup_log:447: RFXtrx:      weight sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.118   luup_log:447: RFXtrx:       power sensors: 0 <0x7542f520>
50   11/14/17 14:18:30.119   luup_log:447: RFXtrx:    security remotes: 0 <0x7542f520>
50   11/14/17 14:18:30.119   luup_log:447: RFXtrx:     remote controls: 0 <0x7542f520>
03   11/14/17 14:18:30.123   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x7722f520>
03   11/14/17 14:18:30.124   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 0 <0x7722f520>
50   11/14/17 14:18:30.130   luup_log:447: RFXtrx:     heating devices: 0 <0x7542f520>
50   11/14/17 14:18:30.130   luup_log:447: RFXtrx:           RFXMeters: 0 <0x7542f520>
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 13, 2017, 11:22:35 pm
try this...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 13, 2017, 11:58:56 pm
Nup, I'm getting the hang of this now  :) Thanks.



**************************************
************** STARTING **************
************************************** <0x778e7520>
02   11/14/17 15:52:54.761   luup_log:477: (BroadLink::getMiosVersion): vera_model [Sercomm NA301] mios_branch [1] mios_major [7] mios_minor [3014]. <0x778e7520>
02   11/14/17 15:52:54.761   luup_log:477: (BroadLink::getMiosVersion): MIOS_VERSION [UI7] openLuup [FALSE]. <0x778e7520>
06   11/14/17 15:52:54.762   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: PLUGIN_VERSION was: v1.10 now: v1.11 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x778e7520>
50   11/14/17 15:52:54.763   luup_log:477: (BroadLink::Plugin_Init): Broadlink RM Interface - Plugin version [v1.11] - isDisabled
06   11/14/17 15:52:54.764   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x778e7520>
06   11/14/17 15:52:54.764   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x778e7520>
02   11/14/17 15:52:54.765   luup_log:477: (BroadLink::getDebugMode) DEBUG MODE [DISABLED] UnitID [NIL] DEV_SYS [FALSE]. <0x778e7520>
01   11/14/17 15:52:54.772   LuaInterface::CallFunction_Startup-1 device 477 function Plugin_Init failed [string "VERSION = "v1.11"..."]:929: bad argument #1 to 'char' (invalid value) <0x778e7520>
01   11/14/17 15:52:54.773   LuImplementation::StartLua running startup code for 477 I_Broadlink.xml failed <0x778e7520>
03   11/14/17 15:52:54.774   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x778e7520>
03   11/14/17 15:52:54.774   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 0 <0x778e7520>
06   11/14/17 15:52:55.101   Device_Variable::m_szValue_set device: 196 service: urn:futzle-com:serviceId:AstronomicalPosition_Sun variable: RightAscensionRounded was: -130.4 now: -130.4 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x762e7520>
06   11/14/17 15:52:55.102   Device_Variable::m_szValue_set device: 196 service: urn:futzle-com:serviceId:AstronomicalPosition_Sun variable: DeclinationRounded was: -18.3 now: -18.3 #hooks: 1 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x762e7520>
50   11/14/17 15:52:55.107   luup_log:447: RFXtrx: Tree with number child devices: 3 <0x758e7520>
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 14, 2017, 12:29:11 am
once again...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 14, 2017, 12:34:40 am
Still no, do you still need the log?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 14, 2017, 12:37:52 am
Still no, do you still need the log?

Of course I do... I'm still NOT psychic...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 14, 2017, 12:50:06 am
I'd lend you my crystal ball except it has a Vera FW bug :)


02   11/14/17 16:46:15.757   luup_log:477: (BroadLink::Plugin_Init): Broadlink RM Interface v1.12 ************************************** ************** STARTING ************** ************************************** <0x778df520> 02   11/14/17 16:46:15.759   luup_log:477: (BroadLink::getMiosVersion): vera_model [Sercomm NA301] mios_branch [1] mios_major [7] mios_minor [3014]. <0x778df520> 02   11/14/17 16:46:15.760   luup_log:477: (BroadLink::getMiosVersion): MIOS_VERSION [UI7] openLuup [FALSE]. <0x778df520> 50   11/14/17 16:46:15.760   luup_log:477: (BroadLink::Plugin_Init): Broadlink RM Interface - Plugin version [v1.12] - isDisabled 
  • MIOS_VERSION [UI7] <0x778df520>[/color] 06   11/14/17 16:46:15.761   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x778df520> 06   11/14/17 16:46:15.762   Device_Variable::m_szValue_set device: 477 service: urn:micasaverde-com:serviceId:Broadlink1 variable: DebugMode was: DISABLED now: DISABLED #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x778df520> 02   11/14/17 16:46:15.762   luup_log:477: (BroadLink::getDebugMode) DEBUG MODE [DISABLED] UnitID [NIL] DEV_SYS [FALSE]. <0x778df520> 02   11/14/17 16:46:15.769   luup_log:477: (BroadLink::Plugin_Init): Loaded Devices [ 1: [   KEY: a37dd835d9f04e251064c51446d73b04   IP: 192.168.0.22   MAC: 34:ea:34:8e:fa:0b   internalID: 02000000   isPro: TRUE   Name:   sensors: [     temperature: 27.1   ]   hasAuth: TRUE   devType: 10119   devTypeName: RM2 Pro Plus2   hasTemp: TRUE   hasIR: TRUE ] 2: [   KEY: aad79912aad79912e14a100217be8671   MAC: 34:ea:34:40:99:8f   IP: 192.168.0.25   internalID: 02000000   devType: 10039   isPro: FALSE   Name:   hasAuth: TRUE   devTypeName: RM Mini   hasTemp: FALSE   hasIR: TRUE ]  ]. <0x778df520> 02   11/14/17 16:46:15.770   luup_log:477: (BroadLink::Plugin_Init): Loaded Commands [  ]. <0x778df520> 02   11/14/17 16:46:15.770   luup_log:477: (BroadLink::Plugin_Init): Selected Device [  ]. <0x778df520> 02   11/14/17 16:46:15.771   luup_log:477: (BroadLink::Plugin_Init): Broadlink RM Interface controller v1.12 ************************************** *********** INIT COMPLETED *********** ************************************** <0x778df520> 03   11/14/17 16:46:15.772   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 1 <0x778df520> 03   11/14/17 16:46:15.773   JobHandler_LuaUPnP::m_bReloadCriticalOnly_set now 0 <0x778df520> 50   11/14/17 16:46:16.105   luup_log:447: RFXtrx: Tree with number child devices: 3 <0x758df520> 50   11/14/17 16:46:16.106   lu[/pre]
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 14, 2017, 12:56:20 am
OK, hold on.
It's come good, not sure why it took so long.


I'll have a good look at it tomorrow and report back.

Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 14, 2017, 01:00:31 am
ok... So... Where's the problem???

Logs show that it found a device, and that you have not added any commands or selected the device.

How do you figure it's not working?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 14, 2017, 01:04:33 am
I didn't say it wasn't working, just that I'll look further into the Plug In tomorrow and report if I run into any problems.
Thanks for all your help and the time you have taken to develop and de-bug, it's an enormous effort.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage on November 14, 2017, 01:07:40 am
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...
Title: Re: PLUGIN: Broadlink RM Interface
Post by: TMC on November 14, 2017, 03:07:00 am
Hi cybrmage.
I used the L_Broadlink.lua file and it works.
Great work.
Thanks.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Guimaraes on November 14, 2017, 04:22:46 am
Yes, it picks up all the devices, S1, SC1, MP1 SP, SP3, SP mini ...

Hello,

Does the plugin can also be used with Broadlink SP (SmartPlug) devices - IP based plugs ?
I don't have any central Broadlink device beside the e-control app.

Thanks,
Nir
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Newzwaver on November 14, 2017, 12:38:25 pm
HI

First of all I like to say a big thanks for when I get this working. 

I am trying to set up the plugin, I originally loaded V1.10, didn't work followed the following instructions;
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"
 Forced the plugin update to V1.4
http://<your ip>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8996&Version=<Version ID>
  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"
Then forced the plugin to V1.8 and still no go.

I have also reset the Broadlink Pro and rebooted vera a number of times.  I have the correct IP address in the advanced ip address.  When I press debug I get the following error.
Device not ready.

I have tried the
Add code from network connected device running e-Control.

When trying to obtain the log I get the following error;
ERROR: Invalid service/action/device
I could be doing that wrong.
Thanks
Title: Re: PLUGIN: Broadlink RM Interface
Post by: Guimaraes on November 14, 2017, 12:41:25 pm
That's what a Mexican soap opera says ... there's no end to it.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: nirgal on November 14, 2017, 01:52:14 pm
Any chance to add support for SP modules ?
Or to explain how this can be done?
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally 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.

Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally 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 (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>
Title: Re: PLUGIN: Broadlink RM Interface
Post by: hvazana 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
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage 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 (http://forum.micasaverde.com/index.php/topic,50722.0.html).
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage 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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage 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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage 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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally 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>
Title: Re: PLUGIN: Broadlink RM Interface
Post by: nirgal on November 16, 2017, 10:57:26 am
@cybrmage

Thanks for the "PLUGIN: Wifi/UDP Switch Controller " I will try it.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: cybrmage 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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: glendale2008 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
Title: Re: PLUGIN: Broadlink RM Interface
Post by: elton 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? :-\ :-\
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally 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.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: RichardTSchaefer on November 18, 2017, 10:59:37 am
It uses UDP  for communicating.
You might want to make sure you do not  have an ethernet "SWITCH" between your Vera and your RM and Android device.

A "ROUTER" is fine, but some older "SWITCH"es do not handle the UDP broadcast.
 
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 18, 2017, 03:23:42 pm
Thanks Richard, you may have the solution. I have a Vera Edge plugged into a Almond+ which I use as a downstairs access point and for 5G wifi. I checked the ADSL (upstairs) Router Firewall yesterday but forgot about the AP which is something I'll do tomorrow. It may be a case of moving Vera to a new home upstairs.


By the way I noticed that in eControl when configuring a Device there are 2 settings one for AP, then another setting (I can't remember the name), could I be using the wrong setting? The Help FAQ appears to be silent on this setting.
Title: Re: PLUGIN: Broadlink RM Interface
Post by: zedrally on November 19, 2017, 09:44:01 pm
Update: This is what I have tried so far.
I have also deleted the PlugIn and reinstalled it, although I don't see how it could be a PlugIn issue.
There is little point in posting new logs as they are all similar to the first.

What have I overlooked?