Broadlink IR/RF remotes integration (RM3 Mini, RM Pro, RM4 Mini/Pro)

@tomw, I am having a problem with my RM4. I have a TV I turn on and off, and a fireplace which I turn on and off. I notice that if Iturn on the TV commands sent to the fireplace don't seem to make it. If I turn on the TV with the TV's remote the fire place commands work fine. Is there a problem with controlling these two devices from the same RM4? Do I need to refresh between devices? I have tried inserting a delay as long as 30 seconds between commands. Thanks for your help.

Curious if anyone has seen this...

I have a RM3 that is only used for one command to simulate the power button (on/off) for a Sony TV. That is the only command it has learned. It has been working well for several months.

Recently, I've noticed that sometimes it acts as though it is sending the command twice, e.g., if the TV is on, it turns off then turns on again a second later. Looking at the events and log for the device, it is only sending the command once.

The device is about 15' from the TV and pointed directly at it. Any idea what can cause this? It doesn't happen if I use the TV's remote to turn the TV on/off.

Kindly post how the command is being issued. Dashboard, rule machine, etc.

I use a virtual switch device with autooff disabled on a dashboard that triggers a small app I wrote, TV Wrangler, to turn on/off the TV, Cable Box(optional), and Sound Bar (Optional). The app has some timings built in to control double taps on the dashboard's virtual switch.

https://raw.githubusercontent.com/arnbme/hubitat/refs/heads/master/tvWrangler.groovy

I have a virtual switch named "TV" and a Rules Machine rule named "TV Switch". I'm simplifying a bit, but the trigger event is "When TV turns changed.

When the rule is triggered, it writes a "start" message to the log, issues the command "push('Power') on Broadlink Remote Control", then writes a "end" message to the log.

This doesn't fail all the time, but I haven't been able to make it fail consistently. The confusing thing is that I get the same log and events entries whether it works or fails (i.e., turns the TV off then on immediately). The events and log only show one command being issued to RM3.

The reason "TV" is defined as virtual switch instead of a virtual button is because I'm turning the TV on/off from my iPhone (via HomeKit Integration), and Apple Home doesn't support buttons.

The new hubitat UI no longer displays the saved codes list under the virtual devices. All the saved codes still work and I can import all the existing codes into the Broadlink System Manger. I just can't see them in each virtual device. Maybe I'm missing something.

Does it say [Object] in that status instead? If so that was a fix one of most recent Beta updates.

1 Like

yep Beta 2.4.0.125 displays them correctly.

1 Like

I'm on 2.4.0.125 and I don't see the saved codes. I must be missing something.

I'm hitting an issue with my Broadlink integration that I am hoping I can get help with. I have a completed the steps to add a command from my blind remote to both the Broadlink app itself and to the App in Hubitat. I did verify that it worked for both.

The problem I seem to be having is that the code in the Hubitat App seems to stop working after about a day. I see the light blinking on the Broadlink when I send the stored code so it would seem it is getting the command but it does not trigger the blind to open. If I do the same thing in the Broadlink app at that time it works and the app triggers the blind to open.

I don't think it matters but it's a Zemismart blind.

Do you have your Broadlink hub set to a fixed IP?

Can you see the codes on the device page?

Yup, I have it on a fixed ip. I also moved it to an IOT Wifi Network to isolate it to 2.4GHz because I heard that could be a problem.

Yeah the code I am trying to use is in the state variables. I did verify there is error checking if I fat fingered the code name and so did verify I'm putting the right name in when using Send Stored Code.

Unfortunately it does seem like I get much back from the logs even if I enable debugging. It also does not help that the integration is UDP from what I can tell. So no real way for this integration to do any sort of verifying or error checking. I can only see that Hubitat says the event was triggered and I see the indicator light on the Broadlink hub light up so I know it received it.