Author Topic: BroadLink Mark II plugin  (Read 9371 times)

Offline conchordian

  • Sr. Member
  • ****
  • Posts: 322
  • Karma: +4/-1
Re: BroadLink Mark II plugin
« Reply #30 on: March 05, 2018, 07:48:12 pm »
Thanks,
I can see the C Tick, has it a FCC number?

No idea, but Hunter Pacific have been around for years in Oz, so if that's a necessary safety standard thing, I'm sure they'll have it.  You could email them if you're curious.

Offline zedrally

  • Hero Member
  • *****
  • Posts: 1112
  • Karma: +9/-4
  • Black Cat Control Systems
Re: BroadLink Mark II plugin
« Reply #31 on: March 06, 2018, 04:16:13 pm »
It's just that you can google the FCC number and it will give you the frequency, that was all that I was interested in.
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, Fantem Tec and then some  Black Cat Cat's Eye PIR's & Door-Window Sensors, RFXComm, Broadlink RMPro & Mini plus a Z-UNO or 2.

Offline LibraSun

  • Hero Member
  • *****
  • Posts: 560
  • Karma: +2/-0
Re: BroadLink Mark II plugin
« Reply #32 on: March 09, 2018, 06:45:23 pm »
I want to join in, heaping praise upon our many plug-in coders, especially @a-lurker for the BroadLink Mark II effort. We've seen a lot of plug-in authors back away from the Vera platform (or, more tellingly, the MCV environment altogether) for various reasons, stated and unstated.

I never want one of those reasons to be, "I did not feel appreciated and my work valued." Because you are, and it is!

In a perfect world, device plug-ins would equate to (or at least have a chance at becoming) built-in "features" rather than "add-ons", and these authors remunerated somehow for their efforts. (Example: I was once given $100 off my first Vera unit as thanks for re-writing the MCV FAQ section, many years ago.) I do wish, in the meantime, that plug-in creators could benefit financially from their many hours of work, in the same way Google Play Store contributors can, or YouTube! content creators might via Patreon or PayPal.

What I sense has happened in the past is that a rift erupts between plug-in creators and the (silent, invisible) big decision-makers at MCV who rightly wish to maintain proprietary control over their ecosystem -- clearly, that's why the plug-in Apps Store came into being.

But having been involved in the Vera community for nearly 10 years, and hardly ever (ever?) heard from the company itself and only gotten a response from Tech Support once or twice during that time, I would encourage MCV staffers to become a little more active here (in the Forums) and far more transparent (dealing with contributors) so we can all know the lay of the land.

Finally, if any Public Relations folks are listening, it would be sweet if the Vera brand could somehow be pushed more broadly, as I have YET to meet a techie IRL who's ever heard of Vera, MiOS or MiCasaVerde, much less used one of their products. The highway of home automation products is littered with dead remnants of failed platforms, and a common refrain has always been, "If only they had maintained it!"

I look at brilliant, die-hard volunteers like @A-Lurker on the front lines of development and realize (as I hope MCV suits do, too), "These are the ones keeping our customers satisfied!" Yes, these timely plug-ins make that much difference.

So thanks again! ♥

 - Libra
Vera Model I running UI4 (Firmware 1.1.1338), died in 2015
Vera Plus running UI7 (Firmware 1.7.2935)

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 857
  • Karma: +63/-8
Re: BroadLink Mark II plugin
« Reply #33 on: March 21, 2018, 11:26:23 pm »
@LibraSun Thanks for the great words of encouragement :D

Years ago I decided to purchase Vera because of the SONOS plugin being available, plus an active forum, plus Z-Wave support. So here we are sometime later and the SONOS plugin appears to be problematic due to recent Vera firmware changes. Fortunately the forum is still very active.

I have also tried to improve the documentation but my English expression is lacking on occasions:

http://wiki.micasaverde.com/index.php/Special:Contributions/A-lurker

We should note that MCV may receive calls for support that are caused by 'errant' plugins and as such, probably see this as an on going cost that they may not feel responsible for. However they review the plugins that go into the store.
« Last Edit: March 21, 2018, 11:45:40 pm by a-lurker »

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 857
  • Karma: +63/-8
Re: BroadLink Mark II plugin
« Reply #34 on: March 21, 2018, 11:27:28 pm »
Version 0.54 released - see first post.

Offline PrincessCleavage

  • Full Member
  • ***
  • Posts: 228
  • Karma: +4/-1
Re: BroadLink Mark II plugin
« Reply #35 on: March 29, 2018, 04:00:22 am »
I want to join in, heaping praise upon our many plug-in coders, especially @a-lurker for the BroadLink Mark II effort. We've seen a lot of plug-in authors back away from the Vera platform (or, more tellingly, the MCV environment altogether) for various reasons, stated and unstated.

I never want one of those reasons to be, "I did not feel appreciated and my work valued." Because you are, and it is!

In a perfect world, device plug-ins would equate to (or at least have a chance at becoming) built-in "features" rather than "add-ons", and these authors remunerated somehow for their efforts. (Example: I was once given $100 off my first Vera unit as thanks for re-writing the MCV FAQ section, many years ago.) I do wish, in the meantime, that plug-in creators could benefit financially from their many hours of work, in the same way Google Play Store contributors can, or YouTube! content creators might via Patreon or PayPal.

What I sense has happened in the past is that a rift erupts between plug-in creators and the (silent, invisible) big decision-makers at MCV who rightly wish to maintain proprietary control over their ecosystem -- clearly, that's why the plug-in Apps Store came into being.

But having been involved in the Vera community for nearly 10 years, and hardly ever (ever?) heard from the company itself and only gotten a response from Tech Support once or twice during that time, I would encourage MCV staffers to become a little more active here (in the Forums) and far more transparent (dealing with contributors) so we can all know the lay of the land.

Finally, if any Public Relations folks are listening, it would be sweet if the Vera brand could somehow be pushed more broadly, as I have YET to meet a techie IRL who's ever heard of Vera, MiOS or MiCasaVerde, much less used one of their products. The highway of home automation products is littered with dead remnants of failed platforms, and a common refrain has always been, "If only they had maintained it!"

I look at brilliant, die-hard volunteers like @A-Lurker on the front lines of development and realize (as I hope MCV suits do, too), "These are the ones keeping our customers satisfied!" Yes, these timely plug-ins make that much difference.

So thanks again! ♥

 - Libra
Well said!
A nice addition to the forums would be a ?like button? to show support for various statements/threads

Offline PrincessCleavage

  • Full Member
  • ***
  • Posts: 228
  • Karma: +4/-1
Re: BroadLink Mark II plugin
« Reply #36 on: March 29, 2018, 04:02:53 am »
Version 0.54 released - see first post.
Will your plugin allow control of the broad link black bean also?

Offline a-lurker

  • Hero Member
  • *****
  • Posts: 857
  • Karma: +63/-8
Re: BroadLink Mark II plugin
« Reply #37 on: March 29, 2018, 07:19:33 am »
Yes.

Offline PrincessCleavage

  • Full Member
  • ***
  • Posts: 228
  • Karma: +4/-1
Re: BroadLink Mark II plugin
« Reply #38 on: March 29, 2018, 07:59:15 am »
Yes.
Beauty, thanks! (which this forum had a like button:-/

Offline Don Phillips

  • Hero Member
  • *****
  • Posts: 1313
  • Karma: +34/-32
Re: BroadLink Mark II plugin
« Reply #39 on: March 29, 2018, 06:28:48 pm »
Give him a +1 karma boost.
Vera 3, 1.7.1030, CT101, Everspring motion sensor, GE/Jasco switch, Leviton outlet, AeonLabs sensor, NuTone garage door, Blue Iris, Sricam SP011, iPhone locator, APCUPSD, VeraMate, VeraAlerts, PLEG, House Modes, Countdown Timer, DVR, Virtual/Multi Switch, Weatherunderground, LB60Z-1 bulb, Hue, Alexa

Offline PrincessCleavage

  • Full Member
  • ***
  • Posts: 228
  • Karma: +4/-1
Re: BroadLink Mark II plugin
« Reply #40 on: March 30, 2018, 03:37:26 am »
Give him a +1 karma boost.
Can not seem to through the Tapatalk app:-(
Other forums using Tapatalk I can tho

Offline Don Phillips

  • Hero Member
  • *****
  • Posts: 1313
  • Karma: +34/-32
Re: BroadLink Mark II plugin
« Reply #41 on: March 30, 2018, 07:11:38 pm »
I gave him a +1 for you.
Vera 3, 1.7.1030, CT101, Everspring motion sensor, GE/Jasco switch, Leviton outlet, AeonLabs sensor, NuTone garage door, Blue Iris, Sricam SP011, iPhone locator, APCUPSD, VeraMate, VeraAlerts, PLEG, House Modes, Countdown Timer, DVR, Virtual/Multi Switch, Weatherunderground, LB60Z-1 bulb, Hue, Alexa

Offline rvendrame

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +1/-0
Re: BroadLink Mark II plugin
« Reply #42 on: April 02, 2018, 08:35:54 pm »
@a-lurker,

I tried to install (version 0.54) but can't get it to work.  The new vera device does show up, but with no tabs / controls on it, and no Broadlinks are being discovered.

I found the bellow in the log.  Maybe I did something wrong when creating the new device?  I just entered 'D_BroadLink_Mk2_1.xml' as device_file, and 'I_BroadLink_Mk2_1.xml' as impl_file,  both at 'Create Device' from ALTUI.

Code: [Select]
JobHandler_LuaUPnP::HandleActionRequest argument UpnpDevFilename=D_BroadLink_Mk2_1.xml <0x2ffa9680>
08 04/02/18 21:24:10.577 JobHandler_LuaUPnP::HandleActionRequest argument UpnpImplFilename=I_BroadLink_Mk2_1.xml <0x2ffa9680>
09 04/02/18 21:24:22.563 JobHandler_LuaUPnP::Run device 635 ptr 0xac1050 RM Pro2 room 0 type urn:schemas-a-lurker-com:device:BroadLink_Mk2:1 cat 11:-1 id  parent 0/0xb87060 upnp: 0 plugin:0 pnp:0 mac: ip: <0x2b694310>
50 04/02/18 21:24:36.253 luup_log:635: BroadLink_Mk2 debug: Initialising plugin: BroadLink_Mk2 <0x2c0d6680>
50 04/02/18 21:24:36.253 luup_log:635: BroadLink_Mk2 debug: Using: Lua 5.1 <0x2c0d6680>
50 04/02/18 21:24:36.254 luup_log:635: BroadLink_Mk2 debug: 0.54 --> PluginVersion <0x2c0d6680>
06 04/02/18 21:24:36.255 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: PluginVersion was: EMPTY now: 0.54 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
50 04/02/18 21:24:36.255 luup_log:635: BroadLink_Mk2 debug: 0 --> DebugEnabled <0x2c0d6680>
06 04/02/18 21:24:36.256 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: DebugEnabled was: EMPTY now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
06 04/02/18 21:24:36.257 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: PluginEnabled was: EMPTY now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
06 04/02/18 21:24:36.280 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: BroadLinkDevices was: EMPTY now: {} #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
06 04/02/18 21:24:36.281 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: PollEnable was: EMPTY now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
06 04/02/18 21:24:36.292 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: PollInterval was: EMPTY now: 300 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>
50 04/02/18 21:24:36.297 luup_log:635: BroadLink_Mk2 debug: Error: discovery msg - incorrect size <0x2c0d6680>
06 04/02/18 21:24:37.299 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: BroadLinkDevices was: {} now: [  ] #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2c0d6680>



Offline a-lurker

  • Hero Member
  • *****
  • Posts: 857
  • Karma: +63/-8
Re: BroadLink Mark II plugin
« Reply #43 on: April 02, 2018, 09:15:12 pm »
@rvendrame - looks OK so far but with no devices discovered.

In AltUI, under the 'Variables' for the device, set DebugEnabled to 1 and restart the Luup engine, then post the log here.

And a question: - have you also been using any BroadLink bridge apps with your device(s)?

Offline rvendrame

  • Sr. Newbie
  • *
  • Posts: 37
  • Karma: +1/-0
Re: BroadLink Mark II plugin
« Reply #44 on: April 03, 2018, 06:35:58 am »
@rvendrame - looks OK so far but with no devices discovered.

In AltUI, under the 'Variables' for the device, set DebugEnabled to 1 and restart the Luup engine, then post the log here.

And a question: - have you also been using any BroadLink bridge apps with your device(s)?

@a-lurker,

Yes, I had another Broadlink plugin in my Vera (which never worked as well).  The e-control app works fine in my Android, so for sure the broadlink is working.

Here's the log,  is that 'incorrect size'  message right?

Thanks for your support!

Code: [Select]
06 04/03/18 7:25:27.864 Device_Variable::m_szValue_set device: 635 service: urn:a-lurker-com:serviceId:BroadLink_Mk2_1 variable: DebugEnabled was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2f18f680>
09 04/03/18 7:25:57.910 JobHandler_LuaUPnP::Run device 635 ptr 0x11047a0 RM Pro2 room 1 type urn:schemas-a-lurker-com:device:BroadLink_Mk2:1 cat 11:-1 id  parent 0/0x11ca7a0 upnp: 0 plugin:0 pnp:0 mac: ip: <0x2aafe310>
50 04/03/18 7:26:14.077 luup_log:635: BroadLink_Mk2 debug: Initialising plugin: BroadLink_Mk2 <0x2b540680>
50 04/03/18 7:26:14.078 luup_log:635: BroadLink_Mk2 debug: Using: Lua 5.1 <0x2b540680>
50 04/03/18 7:26:14.078 luup_log:635: BroadLink_Mk2 debug: 0.54 --> PluginVersion <0x2b540680>
50 04/03/18 7:26:14.103 luup_log:635: BroadLink_Mk2 debug: Using: dkjson <0x2b540680>
50 04/03/18 7:26:14.114 luup_log:635: BroadLink_Mk2 debug: 300 --> PollInterval <0x2b540680>
50 04/03/18 7:26:14.117 luup_log:635: BroadLink_Mk2 debug: Broadcasting discovery message <0x2b540680>
50 04/03/18 7:26:14.118 luup_log:635: BroadLink_Mk2 debug: 192.168.81.1 <0x2b540680>
50 04/03/18 7:26:14.121 luup_log:635: BroadLink_Mk2 debug: Rx'ed a discovery response: rxMsg length = 48
50 04/03/18 7:26:14.122 luup_log:635: BroadLink_Mk2 debug: Error: discovery msg - incorrect size <0x2b540680>
50 04/03/18 7:26:15.124 luup_log:635: BroadLink_Mk2 debug: [  ] --> BroadLinkDevices <0x2b540680>