1 Member and 2 Guests are viewing this topic.
It's pretty easy to get the codes learnt through either the official broadlink app, or within the rm tasker plugin. You just create a device, learn (single), swap frequency (then press the remote button & it figures out the frequency, it then says its ready) then you give your remote button another press. You give it a name.. Done! You can subsequently create a tasker task with that button as an action. They world is your oyster after that. You do need to import your configured codes into the tasker plugin. It's really simple to do that too, you just share from the official app, and suddenly all your codes are in the plugin. The Alexa Bridge is working fine. Once you have created your codes, you enable the alexa bridge, create a 'device' and define what virtual button press you want to action when the 'device' is triggered (you define what button you want to send when you command it to on/off). Once you have your devices all set, you do a discover devices on your echo, and your device appears on your alexa app. (they appear as wemo devices as far as alexa is concerned). You can command them on or off subsequently, and the RM2 will dutifully turn on or off any infrared or rf device you have configured.
Yes. RM Tasker is the important one because it needs to be running in the background on a dedicated Android device connected to your network. Initially you need eControl just learn all of the remote codes.
Items needed:-Broadlink RM Device-Broadlink e-Control app (free - Google Play Store)-Broadlink RM Tasker Plugin ($5.49 - Google Play store) or the Trial version (to test it out)Follow these instructions until you get to "Set up your Android Bridge": https://goo.gl/Z4IBA6The reason why you stop at "Set up your Android Bridge" is because these instructions were created before an Alexa Bridge was added to the RM Tasker Plugin.Start RM Tasker Plugin & click on "Import new data from eControl app" and follow the instructions to import the codes from the eControl app into the RM Tasker Plugin.Once you have imported all of your codes into Tasker, enable "Alexa Bridge" and follow Maff's instructions.
Another thing I have experienced is that the alexa bridge seems to become unresponsive after a few hours (alexa can't find the devices). This is solved by briefly loading the app,and it comes back to life. If it isn't something peculiar to my setup, I imagine the developer will sort this soon. As a temporary work around I have set a tasker task to wake up the screen and load the app on an hourly basis.
Yeah, that was the first thing I thought as I have a bunch of stuff I use on my marshmallow devices which need background services and I'm used to configuring it all. The devices I have had the bridge on are both lollipop so Doze not applicable. One device had Samsung smart manager which I made sure was not touching tasker or the plugin /bridge etc. Now I have the tasker scheduled wake up of the app it has worked flawlessly for a couple days now. Fine for the moment, but if I get to the bottom of it I'll report it here.
So I got everything working well with my Alexa, new RM2, a samsung galaxy S3 and a few etekcity modules. However, I am experiencing the same thing as above where after being dormant for the night, Alexa says 'device is not responding' when I try to use it it in the morning. Everything works again when I 'wake' up the Samsung galaxy S3.Could you please outline the steps for creating the tasker scheduled wake up of the bridge app as you have described above?Thanks