Broadlink binding [4.1.0.0;4.3.x)

Add-on Marketplace Bundles
,
185

I have the same problem here… On the RM3-Mini 44057… Powercycle didn’t help, recreating the thing same problem… any ideas?

186

It is a bug. There is a small change in the protocol for these devices. I am trying to fix it, but I’m having some trouble getting my development environment to work again.

187

I just fixed… :smiley:

As far as it seems the initialization for the RM3 Mini is inherit from the RM4.

In particular:

protected void getStatusFromDevice()

fail sending command 0x24 (Unsupported command on the RM3 Mini?).

Overriding the same function on the RM3 44057 class seem to solve the problem.

    @Override
    protected void getStatusFromDevice() throws BroadlinkStatusException, IOException {
           InetAddress address = InetAddress.getByName(thingConfig.getIpAddress());
        if (!address.isReachable(3000)) {
            throw new IOException("Cannot reach " + thingConfig.getIpAddress());
        }
    }

I can make the PR if you want

188

I just pushed a pull request to fix the RM3 Mini issue.

189

Made a new alpha version available for openhab 4.3.6 that fixes the RM3 mini issues. The change will be part of openhab 5.x.

1 Like
190

I just saw this exception in the log. Any clue what went wrong here?

2025-08-15 20:47:34.661 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
	at org.openhab.binding.broadlink.internal.handler.BroadlinkRemoteModel4MiniHandler.getStatusFromDevice(BroadlinkRemoteModel4MiniHandler.java:59) ~[?:?]
	at org.openhab.binding.broadlink.internal.handler.BroadlinkBaseThingHandler.updateItemStatus(BroadlinkBaseThingHandler.java:236) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
	at java.lang.Thread.run(Thread.java:840) [?:?]

Before that exception there are lots of these

2025-08-15 18:53:53.398 [WARN ] [dler.BroadlinkRemoteModel4ProHandler] - Online -> Offline due to: Couldn't authenticate: Authentication failed:response from device during authentication was null, check if correct mac address is used for device.
2025-08-15 18:54:03.533 [WARN ] [dler.BroadlinkRemoteModel4ProHandler] - Received unexpected exception: org.openhab.binding.broadlink.internal.handler.BroadlinkStatusException
191

Hi Bernd, which version of openhab / the broadlink binding are you using? Did you re-create the things after us earlier beta’s?

The warnings indicate that the binding cannot find the device for some reason… I did make a patch for the RM3, which fixes some issues, you can download it from the top post and it will be part of the 5.x release.

192

Hello Anton, I am running OpenHAB 4.3.5 using the offical binding from the store.

Yes, I did recreate the things after previously using the beta.

The problem was only temporary. It worked before and it worked after the problem…

I rebooted OpenHAB and the RM4, hoping this would solve the issue… which it did :smiley: