@themillhousegroup what is the latest version I should use (BETA?)
I got the following error (BETA4), does it make any sense?
2018-11-29 20:11:59.100 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-29 20:11:59.104 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILEDI have switched to BETA-6 and this is what I get:
2018-11-29 21:56:25.346 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to UNINITIALIZED
2018-11-29 21:56:25.371 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-11-29 21:56:25.380 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e0-b2-44' changed from ONLINE to UNINITIALIZED
2018-11-29 21:56:25.384 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e0-b2-44' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-11-29 21:56:46.605 [INFO ] [.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Constructed
2018-11-29 21:56:46.891 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-11-29 21:56:46.912 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 21:56:46.919 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 21:56:47.365 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 21:56:47.369 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 21:56:47.374 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from INITIALIZING to ONLINE
2018-11-29 21:56:47.382 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e0-b2-44' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-11-29 21:56:47.392 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e0-b2-44' has been updated.
2018-11-29 21:56:47.395 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e0-b2-44' has been updated.
2018-11-29 21:56:47.833 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e0-b2-44' has been updated.
2018-11-29 21:56:47.838 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e0-b2-44' has been updated.
2018-11-29 21:56:47.841 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e0-b2-44' changed from INITIALIZING to ONLINE
2018-11-29 22:10:35.258 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:10:35.269 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:10:35.275 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:10:35.282 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:14:56.847 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:14:56.853 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:14:56.859 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-29 22:16:31.901 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:16:31.914 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:16:31.924 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:16:31.930 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:17:02.982 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:17:02.990 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:17:02.995 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-29 22:17:35.997 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:17:36.012 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:17:36.019 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:17:36.027 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:18:11.472 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-29 22:18:11.476 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILED
2018-11-29 22:18:46.493 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-29 22:18:46.496 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILED
2018-11-29 22:19:17.009 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:19:17.033 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:19:17.040 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-29 22:19:50.040 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:19:50.054 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:19:50.063 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:19:50.068 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:20:20.121 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:20:20.127 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:20:20.132 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-29 22:21:24.147 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:21:24.169 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:21:24.178 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:21:24.185 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:23:00.731 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:23:00.737 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:23:00.741 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-29 22:24:03.758 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-29 22:24:03.772 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:24:03.781 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-29 22:24:03.786 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-29 22:24:39.199 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-29 22:24:39.205 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILEDAfter reboot I have to Diable the RM3mini Thing and Enable again. I am using OH 2.4M6
Hi again,
@lagging and @smhgit - you guys might want to try BETA-7 that I’ve just published at https://dl.bintray.com/themillhousegroup/generic/org.openhab.binding.broadlink-2.4.0-BETA-7.jar
I have a suspicion that your HANDLER_MISSING errors are due to using a variant of the RM2 which was not (until now) recognised. Cato’s original binding supported the RM2 and five variants (e.g. RM2 Home Plus, RM2 Pro Plus). Since that time, it seems Broadlink has been busy developing new variants, all of which need to have their unique 16-bit code matched for them to be discovered correctly. BETA-7 now handles the original RM2 plus TEN variants, such as the RM2 Pro Plus 2 and RM2 Pro Plus 3.
I’m guessing it’s one of these new ones that you guys have, so hopefully discovery will now be successful. Also, I’ve added logging if we fail to match any known device codes during discovery, so you can let me know what it is your device identifies itself as, as well as what it calls itself on the box.
Hope it helps!
Great! will do that!
my device is the rm3pro+ (they are running out of names)
How to access that? is there a speciefic file for the binding that gets created OR is it alongside openhab’s logging?
thanks @themillhousegroup
PS:
i don’t know if you’ve seen my posts about open ports - is that coherent with other devices(so there is snmp under the hood?)
edit:
installed the new jar. OH sees the binding
the device does not get “discovered” yet 
i will try adding it manually during the weekend
Hi!
Same problem here…two broadlink rm3 and sometime i lost connection to one of them…Its time to try the last beta…
See below, I have two devices (44, ca), ca fails, using BETA 7.
I think that if I will restart the RM3 it will connect but it will good that I will keep it in this state until u (we :-)) find the issue
018-11-30 17:01:10.436 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:01:10.448 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:01:10.457 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:01:10.461 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:02:13.660 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:02:13.667 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:02:13.676 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:26:35.625 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:26:35.639 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:26:35.645 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:26:35.648 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:27:06.230 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:27:06.237 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:27:06.244 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:27:39.253 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:27:39.264 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:27:39.271 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:27:39.275 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:28:11.082 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:28:11.088 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:28:11.096 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:30:44.630 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:30:44.643 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:30:44.649 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:30:44.654 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:31:15.735 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:31:15.743 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:31:15.749 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:35:53.694 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:35:53.705 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:35:53.718 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:35:53.722 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:36:25.826 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:36:25.834 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:36:25.838 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:40:31.183 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:40:31.190 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:40:31.194 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:40:31.197 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:41:06.610 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-30 17:41:06.614 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILED
2018-11-30 17:41:41.649 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-11-30 17:41:41.653 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILED
2018-11-30 17:42:12.215 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:42:12.222 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:42:12.230 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-11-30 17:43:16.242 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-11-30 17:43:16.260 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:43:16.263 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:43:16.269 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-11-30 17:43:46.716 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:43:46.724 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-11-30 17:43:46.729 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE@themillhousegroup
With BETA-7 still the same. Switch going ot off in UI not in Real.
If more Debug is needed contact me.
Yes… after reboot all works again. I have made a switch “ad hoc” to reboot. But this is not the best solution i suppose 
If the binding fails to identify a Broadlink device during discovery, it will be logged at the ERROR level in the standard OpenHAB log file. On my Raspberry Pi (and I suspect most other Linux distros) that will be at:
/var/log/openhab2/openhab.log
By logging at the ERROR level you can be sure of seeing it. But if you’d like to see more details and/or help with the investigation into what’s happening with these RM- devices (like @smhgit), you can go into the OpenHAB console and set the logging level to TRACE:
openhab> log:set TRACE org.openhab.binding.broadlink
You’ll see lots of information about what’s going on with your device(s).
Adding it manually doesnt work for me.
This RM bridge app does not work.
Hi John, i have some troubles downloading last beta…
The requested path was not found…
Hi Bud,
Sorry, somehow a colon got in there - try this link:
https://dl.bintray.com/themillhousegroup/generic/org.openhab.binding.broadlink-2.4.0-BETA-7.jar
Cheers
It works, perfetc John…thank you (for this and for you time to solving binding problems)
I have changed to TRACE mode, lets see if it will help to find issues. Quick question, why update item status is so often?
2018-12-01 15:44:36.041 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-12-01 15:44:36.053 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 15:44:36.062 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 15:44:36.068 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-12-01 15:45:12.077 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticate - failed to receive.
2018-12-01 15:45:12.080 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Attempting to authenticate prior to getting device status FAILED
2018-12-01 15:46:15.558 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 15:46:15.569 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 15:46:15.577 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-12-01 16:00:54.783 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-12-01 16:00:54.798 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 16:00:54.818 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 16:00:54.823 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-12-01 16:01:25.294 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 16:01:25.309 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 16:01:25.316 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-12-01 16:23:31.559 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 16:23:39.117 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 16:24:01.573 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 16:24:09.530 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 16:24:31.584 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 16:24:39.942 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lanCan u add the option to set the update item status interval vi the thing definition?
Here is more data:
2018-12-01 18:34:53.559 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 18:35:06.843 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 18:35:23.974 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 18:35:26.985 [ERROR] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Online -> Offline
2018-12-01 18:35:26.995 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 18:35:27.000 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 18:35:27.004 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan
2018-12-01 18:35:36.853 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 18:35:57.000 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 18:35:57.455 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: We've never actually successfully authenticated with this device in this session. Doing so now
2018-12-01 18:35:57.458 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticating with packet count = 38625
2018-12-01 18:35:57.463 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Sending authentication to rm3-2.lan:80
2018-12-01 18:35:57.466 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Sending authentication complete
2018-12-01 18:35:57.470 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Receiving authentication
2018-12-01 18:35:57.515 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 18:35:57.523 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticated with id '02000000' and key 'F991BF12F991BF122F0536026678AC71'.
2018-12-01 18:35:57.525 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:34-ea-34-e3-c1-ca' has been updated.
2018-12-01 18:35:57.530 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: Authenticated with newly-detected device, will now get its status
2018-12-01 18:35:57.534 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus: Offline -> Online
2018-12-01 18:35:57.543 [hingStatusInfoChangedEvent] - 'broadlink:rm3:34-ea-34-e3-c1-ca' changed from OFFLINE (COMMUNICATION_ERROR): Could not control device at IP address rm3-2.lan to ONLINE
2018-12-01 18:36:06.864 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan
2018-12-01 18:36:27.541 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e3-c1-ca: updateItemStatus; checking host availability at rm3-2.lan
2018-12-01 18:36:37.275 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:34-ea-34-e0-b2-44: updateItemStatus; checking host availability at rm3-1.lan==> /var/log/openhab2/openhab.log <==
2018-12-01 16:53:28.745 [WARN ] [.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Beginning Broadlink device scan ...
2018-12-01 16:53:28.773 [WARN ] [.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Broadlink device scan waiting for 10 seconds to complete ...
2018-12-01 16:53:28.902 [INFO ] [.discovery.BroadlinkDiscoveryService] - Data received during Broadlink device discovery: from 192.1.68.1.21:80[34:ea:34:42:f1:f1]
2018-12-01 16:53:28.909 [DEBUG] [.discovery.BroadlinkDiscoveryService] - Adding new Broadlink device on 192.168.1.21 with mac '34:ea:34:42:f1:f1' to Smarthome inbox
2018-12-01 16:53:38.778 [WARN ] [.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - 10 second wait complete ...
2018-12-01 16:53:38.783 [WARN ] [.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Ended Broadlink device scan...
2018-12-01 16:53:38.788 [INFO ] [link.internal.socket.BroadlinkSocket] - Socket closed
This is what i get from my unsuccesful discoveries
What stands out to me is that Broadlink device discovery: from 192.1.68.1.21:80[34:ea:34:42:f1:f1] would make sense for an mqtt enabled device, however if you scroll up to my nmon scans ( #597 ) , this broadlink device doesn’t have that port open. That doesn’t change if i restart it. purely out of testing completeness: i can try doing the binding having the bridge app open, but even that app didnt’ feel like was funcioning (any command sent to it through it’s “api” wouldn’t work).
Have they created a local connection-proof variant?
Edit:
XD the thing went online adding it manually using the IV and key provided by X-ray in #592
O.O 
that’s a total surprise to me XD - i love such surprises.
2018-12-01 17:19:33.626 [DEBUG] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: initialization complete
2018-12-01 17:19:33.338 [hingStatusInfoChangedEvent] - 'broadlink:rm3:d310766a' changed from UNINITIALIZED to INITIALIZING
2018-12-01 17:19:33.405 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:d310766a' has been updated.
2018-12-01 17:19:33.415 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:d310766a' has been updated.
2018-12-01 17:19:33.606 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:d310766a' has been updated.
2018-12-01 17:19:33.617 [me.event.ThingUpdatedEvent] - Thing 'broadlink:rm3:d310766a' has been updated.
2018-12-01 17:19:33.628 [hingStatusInfoChangedEvent] - 'broadlink:rm3:d310766a' changed from INITIALIZING to ONLINE
2018-12-01 17:19:34.632 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:20:05.046 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:20:35.057 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:21:05.067 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:21:35.076 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:22:05.085 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:22:35.094 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:23:05.103 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:23:35.116 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:24:05.129 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
2018-12-01 17:24:35.141 [TRACE] [nk.handler.BroadlinkBaseThingHandler] - broadlink:rm3:d310766a: updateItemStatus; checking host availability at 192.168.1.21
i’ll have to study the remaining part of the guides now XD
update & questions
I haven’t gotten around the broadlink bridge to work. it just doesn’t detect my device i think.
In the instructions in the box of the rm pro + iwas directed to an app called ihc for EU by broadlink, all of the data was so far managed with that.
i’ve tried using this one https://sourceforge.net/projects/broadlink-manager/ to aquire the codes, it does detect the device and puts it into learning mode, however nothing is learnt it was inconclusive, so i’ve dropped it
following this https://github.com/NightRang3r/Broadlink-e-control-db-dump to aquire the codes i’ve learnt how to make python and pip and python scripts run on windows 10, moved from the ihc app to the e-control app in order to get, with some editing, to this broadlink.map file:
Dario_Luce_Toggle = b20b1c00090f0908100f080f080f080f080f080f08081008100f090f09000100000000000000000000000000
Dario_Led_On = b20e1c00090f090e080f080f090f080f0808100f09081008100f090f09000100000000000000000000000000
Dario_Led_Off = b2211c00090f080f090e080e090f080f090f090810081008100f090f09000100000000000000000000000000
Dario_Dimmer = b2c11c00090f090f0908100f090f090f080f080f08071008100f080f09000100000000000000000000000000
Dario_Vent_Off = b2211c00090e090e080f090e090e0908100f090f09071007100f090e09000100000000000000000000000000
Dario_Vent_1 = b2371c000907100f080e090f080f080f090f090f09071007100e090f08000100000000000000000000000000
Dario_Vent_2 = b1121c00080f080f080f08080f0f080f080f080f08080f080f0f080f08000100000000000000000000000000
Dario_Vent_3 = b2161c00080f080f090e090e0807100f090e090f09081007100f090f09000100000000000000000000000000
Camera_Luce_Toggle = b2071c00090f0907100f090f090f090f090f09100807100f090f080f09000104000000000000000000000000
Camera_Led_On = b2121c00090f0910080f090f090f08100808100f0908100f090f090f08000105000000000000000000000000
Camera_Led_Off = b20b1c0008100810080f080f080f080f080f08081008100f080f080f08000104000000000000000000000000
Camera_Dimmer = b2aa1c00080f080f0808100f080f080f080f080f0808100f080f080f08000105000000000000000000000000
Camera_Vent_Off = b1251c000810071008100810081008080f10081008080f0f080f081008000105000000000000000000000000
Camera_Vent_1 = b1251c000808100f080f080f080f080f0810080f0808100f080f080f08000104000000000000000000000000
Camera_Vent_2 = b2121c00080f090f090f0808100f090f090f090f0908100f090f080f08000104000000000000000000000000
Camera_Vent_3 = b20e1c00080f090f090f080f0907100f090f090f0808100f090f090f08000104000000000000000000000000
Sogg_Luce_Toggle = b21a1c0009100908111009100911091009100910091009100810090811000117000000000000000000000000
Sogg_Led_On = b1161c0009110911081108110810091109091110091008100811080811000117000000000000000000000000
Sogg_Led_Off = b2121c0009100910091009100910091009100908111009100910090811000116000000000000000000000000
Sogg_Dimmer = b2b21c0009100910090811100910091009100910091009100910090811000116000000000000000000000000
Sogg_Vent_Off = b24a1c00091009100a100910091109091110091009100a100910090911000116000000000000000000000000
Sogg_Vent_1 = b23b1c0009081110091009100910091009100910091009100910090811000116000000000000000000000000
Sogg_Vent_2 = b1421c0009100910091009091011091008110911081008110811090910000116000000000000000000000000
Sogg_Vent_3 = b14e1c0008100911081108110809101108110811081108110811080910000116000000000000000000000000
It scares me that respective to most hex codes posted so far mine seem to be 1/2 to 1/3 of the lenght of the others’, and that some commands (like the dimmer ones) should last for about 4 seconds (and they do when commanded from the app) but the string is just as long as the others.
anyhow, now, 2 questions ( i can’t keep going today)
I have submitted a pull request that fixes the issue of SP2 and SP3 always reporting as OFF. Further I have discovered that some parts of the Broadlink binding has an issue where the devices’ acknowledgment packets sent as a response to a command is not handled - causing different issues for different devices.
In my PR for SP2 and SP3, this problem is solved! It is a very small fix and it should be easy to extend this to other devices as well!
PR: https://github.com/themillhousegroup/openhab2-addons/pull/1
The Power consumption values of SP3s are never read since it is not implemented in the binding yet, but having gotten to understand the binding a bit I might implement this and the Night light switch in the near future.