Ok, so I selected this instead:
Generic Component Button Controller
Hopefully this will be a button on the dashboard that I can push to mute the TV. I will place it on a dashboard, then create a rule according to your instructions.
Tks, AB
Hi, I still cannot make it work. I checked the log and I get this:
2021-01-29 12:47:48.281 pm errorjava.lang.NullPointerException: Cannot invoke method push() on null object on line 589 (dashboardCmd)
Tks, AB
Hi @Royski, yes, it is button 1.
I did a bit more work on it, but I'm still getting this error:
java.lang.IllegalArgumentException: Command 'push' is not supported by device. on line 589 (dashboardCmd)
At some point I actually got the yellow transmission light to flash on the RM Pro, but it did not mute the TV.
Tks, AB
That error is for the Broadlink device or app?
Hi @snell, hmm, I was thinking it was more about the button, 'push' being one of the actions you can undertake, but I'm really not sure.
I was hoping I could put together a set of instructions that would allow the Broadlink to function normally, so that I could write a 'how to' article on my website, but now I'm not sure I can do this.
I had also sent an email to Hubitat before I found this forum, but I never heard back, so maybe it's not possible. I was hoping they could access my unit to see what was wrong, but perhaps it is not possible.
Tks, AB
@tech, you shared a screenshot earlier of a device named 'Den' with codes stored. That is the device that you want to use in the Dashboard.
Create a new tile in the Dashboard. Select that device. Select the button template. Then for the button number, enter the name of the stored command (like power_audio in your screenshot).
Hi @tomw, I did what you asked, but I still have the same error in the logs:
Command 'push' is not supported by device
Tks, AB
What is the specific log message? And will you please share a screenshot of the Rule Machine config page for the tile as well as a screenshot of the device that you are using?
Hi @tomw, thanks for your help with this. I included the final picture to show that the Broadlink app learns and tests commands just fine.
There should be 8 pictures below.
Tks, AB
Your "Den-mute-button" device should not be a Generic Component Button Controller. Instead, you should have the Type "Virtual Button". The type you have selected now does not have commands for pushing a button. Thus the error.
That is true, @snell
Also, you don't need Den-mute-button or rule. Just select Den RM2 Pro Plus as the device in dashboard and enter the name of the stored code as the button number.
Hi, thank you both for this feedback!
I was wondering if I was over-complicating things, so I will give it another go tomorrow. Most of my problems are probably due to being a noob, but I'm learning fast, thanks to your help.
Cheers, AB
SUCCESS!!
Thank you for all the great help!
I authorized the RM Pro to be used in the dashboard, then set up a button for mute (not virtual). I have put the final screen capture below, just in case someone else needs it. It turned out to be remarkably simple as I did not need the rule or the virtual button.
I still need to create a similar structure to switch the channel to CNN, which is ch 17 here, so I'm wondering how I can send 2 commands in sequence (1 followed by 7). I think I saw something in the rule I had created that might allow me to do this, but since I no longer need the rule, I'm wondering how this might be done?
Cheers, AB
You can do it a couple of different ways.
You can add another button and use it to send another command, like "channel_up". Then you push each of the buttons as needed.
Or, you can return to the Virtual button that @snell suggested and have it represent a sequence of button pushes on the RM2. If you want to do that, create the virtual button to represent the set of actions (maybe something like "Power On AV"). Then add back the rule and have the rule trigger be a button press on "Power On AV". Then have the rule actions be the sequence of individual button presses on the RM2 device, plus adding delays or turning on lights or whatever else to set up the scene how you want.
Hi @snell & @tomw, thanks again for all your help with making the Broadlink code work. I'm wondering if you happen to know why the original developer withdrew his beta code for the Broadlink devices?
We have several of the original RM Pro devices (3 sided), and his code is working perfectly, as far as we can tell, but we recently purchased the newer 4 sided replacement (RM4 Pro), and it does not work with his code.
I'm wondering if a slight adjustment to his code might make the newer RM4 Pro work?
Regards, AB
It was mentioned originally that the RM4 would not work, which is a bummer because I have one also. I never heard any reason for why they left. Unfortunate, also that they decided not to leave the code to share or for someone else to take over.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
