![]() There are some obvious (and some not so obvious pros and cons to this set up. See, not cumbersome at all! Finally I mounted the RM Pro upside down on the suspended ceiling in roughly the middle of the room where I had an outlet. I inserted these in a CURL request that I typed up into a one line batch file for each TV, then created an HS event that triggers when the virtual device's status is changed, running an immediate script that calls the batch file, which makes the HTTP request to the RM plugin on the tablet, which in turn communicates with the econtrol app to send the right IR signal from the RM Pro. ![]() I enabled HTTP bridge in the plugin, and browsed the code list provided there to find the "codeId" for each TV's power button. Next I got the Broadlink RM Plugin running (standalone, not using Tasker) on an infrequently used bartop tablet that's left plugged in at the bar all the time. ![]() ![]() I started by training the IR remote buttons for the two TVs in the basement using the eControl app provided by Broadlink, then created virtual devices for them in HS. Here is the not-at-all-cumbersome process i followed to make it happen. I've got this working reliably in HS3, controllable by Alexa, Google Home HSTouch, etc.
0 Comments
Leave a Reply. |