Actually that’s what I did and I still got the error message.
A day or two before you shared beta 4 of the binding I deleted beta 3 from my OpenHAB addons folder and then I restarted the OpenHAB system.
So, based on your explanation, the system should have “recovered” prior to me moving Beta 4 into the addons folder. Shouldn’t it?
I know I’ve seen the 409 - Conflict error before, but can’t quite remember the context.
Sounds like you’ve done the right thing regarding upgrading your .jar @mjeshurun - I’d suggest poking around the PaperUI, in particular under the Configuration > Things list.
You might find some remnants of an old Thing that you’ll need to manually delete using the bin icon and/or restart OpenHAB again. Sorry I can’t be more helpful, but I’m pretty sure it’s something like that 
@themillhousegroup
I think the conflict issue might come from a bug in the Broadlink binding file.
I just tried adding the RM4 Pro using Beta 4 version of the binding in a new OpenHAB installation on my mac and it gave me the same “Error 409 - Conflict” message.
I didn’t add any other Thing to this OpenHAB installation and yet adding the RM4 Pro failed, showing the same error message as I got on my Raspberry 4 system.
This makes me assume the “409 - Conflict” message might not be caused by remnants of old Things.
Hello,
I have openhab running z-wave binding with many things.
I also have the broadlink RM pro and would like to integrate it with openhab.
Reading this lon thred I am not sure on which point to start, Is there within this thread or other thread a simple guide on what required to install and how to control broadlink through openhab?
Thanks for help
Hi,
Can someone explain please how to install the latest version?
What I should do with the jar file?
Thanks
Place it in your ADDONS folder
ok, thanks. will do.
Do I need also to add MQTT binding?
What else I need? Are there a steps to go through?
Hey Yehuda,
Were you able to successfully add your Broadlink RM Pro to your OpenHAB system as a Thing, or did you also get the “409 - Conflict” message?
Thanks.
Hi,
I am running broadlink binding for RM2 and configure everything (learn codes, item, sitemap, broadlink.map)
I tried a simple TV on/off switch but got the following error and have no idea what the meaning and how to proceed. Can anyone please help me with this?
2020-04-26 22:39:20.286 [ome.event.ItemCommandEvent] - Item ‘TV_ON’ received command TV_POWER_ON
2020-04-26 22:39:20.292 [nt.ItemStatePredictedEvent] - TV_ON predicted to become TV_POWER_ON
2020-04-26 22:39:20.316 [vent.ItemStateChangedEvent] - TV_ON changed from NULL to TV_POWER_ON
2020-04-26 22:39:20.321 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:78-0f-77-18-0d-57[^]: Broadlink RM2 [192.168.3.30]
2020-04-26 22:39:30.049 [ome.event.ItemCommandEvent] - Item ‘TV_ON’ received command TV_POWER_OFF
2020-04-26 22:39:30.057 [nt.ItemStatePredictedEvent] - TV_ON predicted to become TV_POWER_OFF
2020-04-26 22:39:30.080 [vent.ItemStateChangedEvent] - TV_ON changed from TV_POWER_ON to TV_POWER_OFF
2020-04-26 22:39:30.087 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:78-0f-77-18-0d-57[^]: Broadlink RM2 [192.168.3.30]
Hi all,
first of all, thanks a lot for this great binding. I’m using it with an RM Pro+ (US model bought March 2020) and it works awesome with all my IR devices.
I want to share an answer from Broadlink support about supported RF frequency of the RM Pro+ with you:
My question was:
"…
Model: RM pro+
FCC ID: 2ACDZ-RMPRO
It works great with all my IR remote controls (e.g. TV, Tuner, etc.), but does NOT work at all with all my RF devices:
- 3 Fanimation ceiling fans, Model: “Slinger v2, FM002, LP8147S” with remote model “TR39”
- 6 Fanimation ceiling fans, Model: “Zonic, LP8177” with remote model “CR500”
- 1 Liftmaster RV garage door opener: Model “8587WL” with remote control model “880LMW”
- 1 Liftmaster 2-car garage door opener: Model “8355W” with remote control model “886LM”
- 1 CAR2U bridge to convert the CAR2U transmitter, which is fixed installed in my car, to Liftmaster RF frequency
*- 2 URC-2068BC2-R remote controls for ARRIS TV cable receiver (Suddenlink)
I’ve done some google search and found the following information:
The FCC file shows, that the Broadlink RM pro+ uses (here in the US) the 2 RF frequencies 315 MHz and 433 MHz. But all RF remote devices I own (and a lot of other people also) are using 304 MHz as the RF remote control frequency. This looks like a typical frequency for such type of RF remote controls (ceiling fans, etc.).
Do I have a change to control these 304 MHz using devices with the Broadlink RM pro+? The ability to control these devices, was the main reason for me to buy this RM pro+. Maybe, there is a new firmware update to enable the RM pro+ to control these devices also (I already tried to update the firmware of the RM pro+ with the “ihc” Android app, but it’s says, that it is actual version “43”)? If not, it would be a good idea to support this RF frequency beside the already supported 315 MHz and 433 MHz."
Here is the answer from Broadlink support:
"
…
We understand your concern, however, it is regretful to inform you that RM Pro+ only supports IR 38K remote learning as well as RF 315/433 Mhz (RF: 315 MHz range: 305-335MHz and 433 MHz range: 430-440MHz. ) unencrypted code and your appliance frequency which is not matched. So, it will not be supported by any RM devices.
Also, the IR/RF range doesn’t determine the compatibility of an appliance with the BroadLink device. There are numerous other technical factors that determine the successful linking of any appliance.
…
"
It’s too bad, that the scan range is between 305 and 335MHz - just 1-2MHz on the lower end are missing to be able to support all this “cheap” 303.875Mhz (304MHz) RF devices…
I’ve red here (Broadlink RM Pro not learning X10 Security RF), that the RF chip inside the Broadlink RM Pro+ is able to use frequency from 290MHz to 1GHz - so I’m sure, that with a small firmware update it would be possible to support all the 304MHz devices… a really annoying situation.
Just wanted to share this with you.
Frank
Hi,
Has anyone saw this error before? Any suggestion on what can cause it?
Thanks for help
@themillhousegroup any ideas why OpenHAB might fail to add the RM4 Pro on a completely new OpenHAB 2.5.4 install?
I got the same “Error: 409 - Conflict” message even when the RM4 was the only Thing I tried adding to the system.
OK - sounds like I’ve made an error adding this new device type - sorry about that! 
I’ll try and get it fixed ASAP. Apologies again.
1 Like
Hi John,
Can you help me with this error:
[ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:78-0f-77-18-0d-57[^]: Broadlink RM2 [192.168.3.30]
I try everything I know and on this thread but nothing help and I still get it and can’t communicate with the RM2.
Thanks,
Yehuda.
Hi Yehuda,
Can you paste in some surrounding lines (say 5 before and 5 after) from your logs?
I think that will help with the context of what’s going on
Hi John,
Here are the few lines before, it is my rule running to trigger the RM2
2020-04-28 07:51:38.308 [vent.ItemStateChangedEvent] - Remote changed from 2.0 to 1.0
2020-04-28 07:51:38.311 [vent.ItemStateChangedEvent] - ZWaveNode016_SceneNumber changed from 2.0 to 1.0
2020-04-28 07:51:42.487 [ome.event.ItemCommandEvent] - Item ‘Broadlink’ received command TV_POWER_ON
2020-04-28 07:51:42.501 [nt.ItemStatePredictedEvent] - Broadlink predicted to become TV_POWER_ON
==> /var/log/openhab2/openhab.log <==
2020-04-28 07:51:42.518 [ERROR] [handler.BroadlinkRemoteModel2Handler] - rm2:78-0f-77-18-0d-57[^]: Broadlink RM2 [192.168.3.
Thank you :))
I really appreciate the help and all your work on the binding 
Hi John,
I’m having the same issue - Error: 409 - Conflict
I have a BestCon branded RM4C Mini.
This is the first ever time using this binding - here’s what I did:
Download the snapshot:
wget https://github.com/themillhousegroup/openhab2-addons/releases/download/BROADLINK_2.5.BETA_04/org.openhab.binding.broadlink-2.5.1-SNAPSHOT.jar
Copy the jar file to the addons folder
sudo cp org.openhab.binding.broadlink-2.5.1-SNAPSHOT.jar /usr/share/openhab2/addons/
After a few seconds, the following appears in the log
21:04:56.176 [INFO ] [l.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Constructed
I then go into the Inbox in Paper UI, and click Scan. I choose the Broadlink Binding to perform the scan. The following is found:
The log has the following detail:
21:08:04.789 [WARN ] [l.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Beginning Broadlink device scan...
21:08:04.826 [WARN ] [.internal.discovery.DiscoveryProtocol] - Beginning async Broadlink device scan; will wait 10000 ms for responses
21:08:04.864 [WARN ] [.internal.discovery.DiscoveryProtocol] - Broadlink device scan waiting for 10000 ms to complete ...
21:08:05.224 [INFO ] [l.discovery.BroadlinkDiscoveryService] - Data received during Broadlink device discovery: from 192.168.1.117:80 [24:df:a7:4f:7c:e6]
21:08:05.237 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'broadlink:rm4:24-df-a7-4f-7c-e6' to inbox.
21:08:14.875 [WARN ] [.internal.discovery.DiscoveryProtocol] - Device scan: wait complete ...
21:08:14.881 [WARN ] [.internal.discovery.DiscoveryProtocol] - Ended Broadlink device scan...
21:08:14.890 [INFO ] [dlink.internal.socket.BroadlinkSocket] - Socket closed
21:08:14.898 [INFO ] [dlink.internal.socket.BroadlinkSocket] - Receiver thread ended
21:08:14.898 [INFO ] [l.discovery.BroadlinkDiscoveryService] - Discovery complete. Found 1 Broadlink devices
Clicking on the blue tick shows this:
Clicking ADD AS THING shows this popup in the bottom right-hand-corner of the screen, which disappears after a few seconds:
My log shows this:
21:09:00.727 [ERROR] [thome.core.thing.binding.ThingFactory] - Thing factory (class org.openhab.binding.broadlink.internal.BroadlinkHandlerFactory) returned null on create thing when it reports to support the thing type (broadlink:rm4).
21:09:00.745 [WARN ] [ig.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type broadlink:rm4.
I hope this helps a little in fixing!
log:set debug org.openhab.binding.broadlink
and try again
Doesn’t add much, unfortunately. From clicking the scan icon in the Paper UI Inbox:
21:37:34.646 [WARN ] [l.discovery.BroadlinkDiscoveryService] - BroadlinkDiscoveryService - Beginning Broadlink device scan...
21:37:34.668 [WARN ] [.internal.discovery.DiscoveryProtocol] - Beginning async Broadlink device scan; will wait 10000 ms for responses
21:37:34.701 [WARN ] [.internal.discovery.DiscoveryProtocol] - Broadlink device scan waiting for 10000 ms to complete ...
21:37:34.766 [INFO ] [l.discovery.BroadlinkDiscoveryService] - Data received during Broadlink device discovery: from 192.168.1.117:80 [24:df:a7:4f:7c:e6]
21:37:34.783 [DEBUG] [l.discovery.BroadlinkDiscoveryService] - Adding new Broadlink device on 192.168.1.117 with mac '24:df:a7:4f:7c:e6' to Smarthome inbox
21:37:34.809 [DEBUG] [l.discovery.BroadlinkDiscoveryService] - Device 'broadlink:rm4:24-df-a7-4f-7c-e6' discovered at '192.168.1.117'.
21:37:34.831 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'broadlink:rm4:24-df-a7-4f-7c-e6' to inbox.
21:37:44.718 [WARN ] [.internal.discovery.DiscoveryProtocol] - Device scan: wait complete ...
21:37:44.733 [WARN ] [.internal.discovery.DiscoveryProtocol] - Ended Broadlink device scan...
21:37:44.748 [INFO ] [dlink.internal.socket.BroadlinkSocket] - Socket closed
21:37:44.765 [INFO ] [l.discovery.BroadlinkDiscoveryService] - Discovery complete. Found 1 Broadlink devices
21:37:44.765 [INFO ] [dlink.internal.socket.BroadlinkSocket] - Receiver thread ended
21:37:54.378 [ERROR] [thome.core.thing.binding.ThingFactory] - Thing factory (class org.openhab.binding.broadlink.internal.BroadlinkHandlerFactory) returned null on create thing when it reports to support the thing type (broadlink:rm4).
21:37:54.396 [WARN ] [ig.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type broadlink:rm4.
Edit: might be useful data:
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
pi@raspberrypi:~ $ apt list openhab2
Listing... Done
openhab2/stable,now 2.5.3-1 all [installed]