How did get around authentication? I get authentication errors after connecting the rm4mini to wifi via app and integration into openhab as a things. file
2023-11-26 18:46:39.476 [WARN ] [handler.BroadlinkRemoteModel4Handler] - Authentication failed:
java.net.ProtocolException: Response from device is not valid. (0x22=0xFF,0x23=0xFF)
at org.openhab.binding.broadlink.internal.BroadlinkProtocol.decodePacket(BroadlinkProtocol.java:192) ~[?:?]
at org.openhab.binding.broadlink.handler.BroadlinkBaseThingHandler.decodeDevicePacket(BroadlinkBaseThingHandler.java:187) ~[?:?]
at org.openhab.binding.broadlink.handler.BroadlinkBaseThingHandler.authenticate(BroadlinkBaseThingHandler.java:144) ~[?:?]
at org.openhab.binding.broadlink.handler.BroadlinkBaseThingHandler.transitionToOnline(BroadlinkBaseThingHandler.java:266) ~[?:?]
at org.openhab.binding.broadlink.handler.BroadlinkBaseThingHandler.updateItemStatus(BroadlinkBaseThingHandler.java:222) ~[?:?]
at org.openhab.binding.broadlink.handler.BroadlinkBaseThingHandler$1.run(BroadlinkBaseThingHandler.java:109) ~[?:?]
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:833) ~[?:?]
Which the stock broadlink binding or old snapshot binding from OH3?
Did you use the app to connect to wifi and then discover via native broadlink binding?
Okay, great I have just configured the same. I did the same but get an authentication error. Did you set it the rm4mini via app and connect it to wifi? Assumption is authentication is blocked because of the app. How did you get around that?
I had the RM4 mini already working with oh3.4 and just migrated to oh4.0.4.
So it was already configured via the app quite some time ago, when I initially set it up in oh3.4. Which is quite some time ago and I don’t really remember how I did it then, sorry
I updated my OpenHAB docker container to 4.1.2 today and, unfortunately, now I’m seeing an ERROR: HANDLER message for my previously working Broadlink RM4 Pro Thing and my pre-configured commands don’t work.
I did the same upgrade on OpenHAB Docker container and received the same error. Follow Broadlink binding [4.1.0;4.2.0) download the jar file save it to the addons folder, also rename or remove old versions of Broadlink jar files if any, then from the GUI select things, your Broadlink device the click the pause or initialize the it should go online.
That’s what I thought I should do, but the new Broadlink Binding is not showing up in the list of available bindings on my OpenHAB – even though I deleted the old binding file, copied the new JAR file into the docker appdata/openhab/addons folder and restarted OpenHAB.
I also didn’t have the option to initialize the “old” Thing I created for the RM4 with the older binding.
The only option I was shown was to delete the Thing. So I deleted it.
And now, for some reason, the “new” 4.1.0;4.2.0 binding isn’t loading by OpenHAB and I can’t add a new Thing.
Any thoughts why the new binding isn’t loading with the system?
Do I need to set the JAR’s file ownership to “UNKNOWN” for OpenHAB to be able to use it?
From what I see, all other files in the OpenHAB appdata folder are set to “UNKNOWN” and “-rwxrwxrwx” permissions.
[EDIT] Seems like changing the ownership and permissions isn’t the cause of the problem.
My openHAB instance still doesn’t run the Broadlink binding even if the JAR file is in the addons folder with JAR file ownswership set to “UNKNOWN” and permissions set to “-rwxrwxrwx”.
)
