# RFLink binding

**URL:** <https://community.openhab.org/t/rflink-binding/7863>\
**Category:** Bindings\
**Tags:** rfxcom, 433, binding\
**Created:** [February 22, 2016, 3:51pm UTC](https://community.openhab.org/t/rflink-binding/7863 "2016-02-22T15:51:45Z")\
**Posts on this page:** 20\
**Page:** 6

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [November 7, 2018, 8:52am UTC](https://community.openhab.org/t/rflink-binding/7863/103 "2018-11-07T08:52:29Z")

</div>

Open a new thread to report the bug  
You can also do it on github

---

<div class="post-metadata">

**Author:** ![cybix32](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/ebca7d/32.png) [@cybix32](https://community.openhab.org/u/cybix32)\
**Post date:** [November 12, 2018, 8:25am UTC](https://community.openhab.org/t/rflink-binding/7863/104 "2018-11-12T08:25:15Z")

</div>

113 are the decimal representation of the hexadecimal value 71. So it is probably a missing conversion?

Peter

---

<div class="post-metadata">

**Author:** ![Chris\_Griffin](https://community.openhab.org/user_avatar/community.openhab.org/chris_griffin/32/27705_2.png) [@Chris\_Griffin](https://community.openhab.org/u/Chris_Griffin)\
**Post date:** [December 11, 2018, 10:52am UTC](https://community.openhab.org/t/rflink-binding/7863/105 "2018-12-11T10:52:41Z")

</div>

We dipped into minus temps last night and this fix does not seem to have worked for me. Any ideas?

> [@Chris\_Griffin](#):
>
> > [@vzorglub](#):
> >
> > case “TEMP”: result.temp = parseInt(value[1], 16); if ((result.temp & 0x8000) \> 0) { // temperature is an signed int16 result.temp = result.temp - 0x10000; } result.temp = result.temp / 10; break;
> 
> Done. Bit of a job getting to node\_red install directory on openhabian but now sorted. Thanks.
> 
> We had a couple of days below 0c last week and was reading 3200degC! Not sure when we’ll get down that low again though. Peaked at 18degC today.

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [December 11, 2018, 10:55am UTC](https://community.openhab.org/t/rflink-binding/7863/106 "2018-12-11T10:55:27Z")

</div>

> [@Chris\_Griffin](#):
>
> We dipped into minus temps last night and this fix does not seem to have worked for me. Any ideas?

I know, I had the same.  
To be honest, I don’t know. It should work.

I have bumped the gitHub issue but it might be worth opening another one.

---

<div class="post-metadata">

**Author:** ![Chris\_Griffin](https://community.openhab.org/user_avatar/community.openhab.org/chris_griffin/32/27705_2.png) [@Chris\_Griffin](https://community.openhab.org/u/Chris_Griffin)\
**Post date:** [December 11, 2018, 11:22am UTC](https://community.openhab.org/t/rflink-binding/7863/107 "2018-12-11T11:22:49Z")

</div>

Just noticed [this comment](https://github.com/cyrilcc/org.openhab.binding.rflink/issues/19#issuecomment-359593828) by Fab33 back in Jan. It has a different value on 3rd line. 0x10000 is replaced with 0x7FFF. I have edited rflink.js accordingly and await the cold again!

…may have to stick my temp sensor in the freezer!

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [December 11, 2018, 1:45pm UTC](https://community.openhab.org/t/rflink-binding/7863/108 "2018-12-11T13:45:39Z")

</div>

Cool,  
Post here if it works  
Thanks

---

<div class="post-metadata">

**Author:** ![Chris\_Griffin](https://community.openhab.org/user_avatar/community.openhab.org/chris_griffin/32/27705_2.png) [@Chris\_Griffin](https://community.openhab.org/u/Chris_Griffin)\
**Post date:** [January 4, 2019, 9:25am UTC](https://community.openhab.org/t/rflink-binding/7863/109 "2019-01-04T09:25:37Z")

</div>

Vincent..

> case “TEMP”: result.temp = parseInt(value[1], 16);  
> if ((result.temp & 0x8000) \> 0) { // temperature is an signed int16  
> result.temp = result.temp & 0x7FFF;  
> result.temp = 0-result.temp;}  
> result.temp = result.temp / 10; break;

This works for me.

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [January 4, 2019, 9:29am UTC](https://community.openhab.org/t/rflink-binding/7863/111 "2019-01-04T09:29:11Z")

</div>

Yes, my problem was odder than that. I discovered that my sensor was publishing negative value with a different ID. So now I have 2 nodes in node-red for this device…

---

<div class="post-metadata">

**Author:** ![curlyel](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/71e660/32.png) [@curlyel](https://community.openhab.org/u/curlyel)\
**Post date:** [January 4, 2019, 10:24am UTC](https://community.openhab.org/t/rflink-binding/7863/112 "2019-01-04T10:24:08Z")

</div>

Vincent, I think **you should get in touch with the RFLink guys** 😉

_Explanation:_  
The decoding of the RF data is usually done by reverse engineering (or “guessing”). So the received data is analyzed and looked for the binary representation of the expected values (“node-id”, “battery value”, “measurement value” etc.).

If you notice the **id is changing for negative values** , then **very likely the id bits are wrongly guessed** (the **sign bit** to indicate negative values is wrongly considered to belong to the device id).  
Therefore you see the id changing…

Though you already found a way to circumvent this flaw, it’s better to get this fixed by the RFLink firmware itself 😉

The RFLink mainainers have been quite responsive in the past. If you point them to your findings here and provide useful data, I’d expect them to fix it quick 😉

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [January 4, 2019, 10:25am UTC](https://community.openhab.org/t/rflink-binding/7863/113 "2019-01-04T10:25:37Z")

</div>

There have been no update on the RFLink firmware for over a year now…  
I am waiting for the next release and then we’ll see

---

<div class="post-metadata">

**Author:** ![curlyel](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/71e660/32.png) [@curlyel](https://community.openhab.org/u/curlyel)\
**Post date:** [January 4, 2019, 10:29am UTC](https://community.openhab.org/t/rflink-binding/7863/114 "2019-01-04T10:29:31Z")

</div>

Well, it’s still alive 😉  
Seems, they are quite busy:

> **[Is RFlink still supported? - Let's Control It](https://www.letscontrolit.com/forum/viewtopic.php?f=11&t=5646)**

Anyway, I’d suggest posting your findings there or get in direct contact to “Stuntteam” 😉

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [January 4, 2019, 10:34am UTC](https://community.openhab.org/t/rflink-binding/7863/115 "2019-01-04T10:34:34Z")

</div>

Coolio, will do.

---

<div class="post-metadata">

**Author:** ![butteryak](https://community.openhab.org/user_avatar/community.openhab.org/butteryak/32/38573_2.png) [@butteryak](https://community.openhab.org/u/butteryak)\
**Post date:** [January 8, 2019, 1:04am UTC](https://community.openhab.org/t/rflink-binding/7863/116 "2019-01-08T01:04:20Z")

</div>

Hello,  
I have RFlink setup and “online” in paper UI. I have my RFlink wired to a NRF24L01 so that I can communicate with Milights.

So far I’ve managed to receive info when I tap a remote.

```csv
16:29:02.692 [INFO] [ig.discovery.internal.PersistentInbox] - Added new thing 'rflink:color:usb0:MiLightv1_14BA_00' to inbox.
16:29:02.694 [INFO] [smarthome.event.InboxAddedEvent] - Discovery Result with UID 'rflink:color:usb0:MiLightv1_14BA_00' has been added.

```

And they show up in my inbox. So I know hardware is functioning properly.  
But if I try to add them as things I get errors.

```csv
16:29:49.833 [ERROR] [thome.core.thing.binding.ThingFactory] - Thing factory (class org.openhab.binding.rflink.internal.RfLinkHandlerFactory) returned null on create thing when it reports to support the thing type (rflink:color).

16:29:49.844 [WARN] [ig.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type rflink:color.

```

Just not sure where to go from here, I know from the documentation that it says send/receive to milight is possible, but there is not much documentation as to how to accomplish this.

Thanks much.  
B

---

<div class="post-metadata">

**Author:** ![vzorglub](https://community.openhab.org/user_avatar/community.openhab.org/vzorglub/32/17166_2.png) [@vzorglub](https://community.openhab.org/u/vzorglub)\
**Post date:** [January 8, 2019, 7:48am UTC](https://community.openhab.org/t/rflink-binding/7863/117 "2019-01-08T07:48:46Z")

</div>

> [@butteryak](#):
>
> Just not sure where to go from here, I know from the documentation that it says send/receive to milight is possible, but there is not much documentation as to how to accomplish this.

For milights, I gave up with RFLink and I went this way:

> [@EspMilightHub new binding for milight limitlessLED and easybulb](https://community.openhab.org/t/espmilighthub-new-binding-for-milight-limitlessled-and-easybulb/39720):
>
> UPDATE: For all OH3 users please update to minimum of 3.1.0 Milestone 1 and the latest binding is merged and built in from now on. Just wanted to let other users of Milight globes know that I have completed a new Binding that allows a single opensource Bridge (bridge created by Chris Mullins aka Sidoh) to automatically find and add Milight globes into OpenHab. The first question Openhab users may have is “Why another binding when one already exists?”, The short answer/s to this is the new OPENS…

Super easy to set-up and works a charm

---

<div class="post-metadata">

**Author:** ![butteryak](https://community.openhab.org/user_avatar/community.openhab.org/butteryak/32/38573_2.png) [@butteryak](https://community.openhab.org/u/butteryak)\
**Post date:** [January 8, 2019, 8:43am UTC](https://community.openhab.org/t/rflink-binding/7863/118 "2019-01-08T08:43:11Z")

</div>

yeah, thats they way i’m going too, I have an ESP8266 coming this week. gonna set it up. thought maybe there might be some advantages, specifically, since I have a wired ethernet connection to the Pi-\>RFlink this would eliminate the need for a bridge, as the RFlink can communicate directly with the lights. I was hoping this would be a more direct way, as apposed to having the bridge as the middle man. Looks like it would be a lot of work to figure out via RFlink/openhab. I only wish there was a wired version of the bridge.  
Thanks!  
Looking forward to working with the RFlink binding anyway for my 433 devices.

---

<div class="post-metadata">

**Author:** ![DirkF](https://community.openhab.org/letter_avatar_proxy/v4/letter/d/d2c977/32.png) [@DirkF](https://community.openhab.org/u/DirkF)\
**Post date:** [March 26, 2019, 6:51pm UTC](https://community.openhab.org/t/rflink-binding/7863/119 "2019-03-26T18:51:59Z")

</div>

Hello everybody,  
i am looking for a current compiled version of RFLink binding to download.  
Could someone provide that?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![bfksoql](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/b2d939/32.png) [@bfksoql](https://community.openhab.org/u/bfksoql)\
**Post date:** [May 3, 2019, 3:05pm UTC](https://community.openhab.org/t/rflink-binding/7863/120 "2019-05-03T15:05:55Z")

</div>

Is there a rflink binding version working on openhab 2.4 ?

---

<div class="post-metadata">

**Author:** ![cailleute](https://community.openhab.org/user_avatar/community.openhab.org/cailleute/32/13293_2.png) [@cailleute](https://community.openhab.org/u/cailleute)\
**Post date:** [July 4, 2019, 1:29am UTC](https://community.openhab.org/t/rflink-binding/7863/121 "2019-07-04T01:29:37Z")

</div>

Looking for the best way to use rflink. So, same question: Is there a binding working on Openhab 2.4 ?

---

<div class="post-metadata">

**Author:** ![cartemere](https://community.openhab.org/user_avatar/community.openhab.org/cartemere/32/22091_2.png) [@cartemere](https://community.openhab.org/u/cartemere)\
**Post date:** [July 6, 2019, 9:59pm UTC](https://community.openhab.org/t/rflink-binding/7863/122 "2019-07-06T21:59:24Z")

</div>

Hello there,

I made some changes on the OpenHab 2 RfLink plugin, and added some functionalities on the Somfy RTS Rollershutter management.  
Full description & setup is available on the Github :

> <https://github.com/cyrilcc/org.openhab.binding.rflink/issues/48>
>
> This is some BIG feature : being able to have a status on the RTS Shutter object…s.
> This means : 
> \- having a feedback status on the Shutter position (like : 50% on the OpenHab Shutter Thing Channel widget)
> \- being able to send a specific target position (like : Input 60% on the OpenHab Shutter Thing Channel widget -\> the store will then start to move in the right direction and stop once at the expected position)
> 
> These features are pretty difficult to develop as the physical RTS Shutter is \*\*passive\*\* : it does NOT send any message, it only listen to messages (from physical remotes as well as from a virtual remote in the RfLink EPROM) and react to these messages.
> So we must "guess" the shutter position by replicating precisely the way the shutter works.

But in a few words :

- RTS Thing mapped on a virtual RfLink remote (internal RfLink rollingcode system) can now **track the rollershutter position** by measuring time between commands nd then guessing the shutter position (you only need to specify the time taken by the rollershutter to move from closed to opened)
- **While moving, the current position of the shutter is displayed** (1 update/second)
- **You can order the shutter to move to a specific position (like : 80%)**. the RfLink plugin will then send an order to move the shutter in the right way, and then send a STOP event once the target position is reached.
- You can “link” existing physical remotes ids, so that the RfLink plugin is able to track the shutter moves from external orders (i.e. **you can mix existing remotes orders with RfLink orders** )

it is for Openhab 2.3 for now, I will try to compile it for OpenHab 2.4  
(BTW : are there any changes on this side ?)

---

<div class="post-metadata">

**Author:** ![cartemere](https://community.openhab.org/user_avatar/community.openhab.org/cartemere/32/22091_2.png) [@cartemere](https://community.openhab.org/u/cartemere)\
**Post date:** [July 15, 2019, 8:31am UTC](https://community.openhab.org/t/rflink-binding/7863/123 "2019-07-15T08:31:56Z")

</div>

About he 2.4 binding compatibility, I can confirm the RfLink 2.3 “direct” binding (i.e. no MQTT or external scripting) works like a charm on a OpenHab 2.4  
(setup : Raspberry Pi 3B+ runnning Raspbian Shelter + Openhab 2.4 installed through Docker)

Installation instructions are available here :

> <https://github.com/cyrilcc/org.openhab.binding.rflink/issues/49>
>
> Hello, 
> I try to build 2.4 version by changes dependency in maven file but it d…oesn\`t seems to start :-( Is there a chance to make it support for oh2.4 ?

PS : last build also include Discovery support for embedded RTS remotes :

> <https://github.com/cyrilcc/org.openhab.binding.rflink/issues/50>
>
> Hello,
> 
> Today, we have some Thing detection on the RfLink plugin from incoming… events.
> \*\*I just implemented the support for RTS remotes registered in the RfLink EPROM\*\*
> 
> This system will scan the RfLink bridge and add the registered remotes.
> To add a remote in the PaperUI Inbox, you must :
> \- enable the discovery on the bridge (i.e. discovery must NOT be disabled)
> \- have some remotes registered in the RfLink bridge (using the RfLink tools)
> \- these remotes must NOT be already registered : If you added them by hand in OpenHab, they won't be detected a second time.
> 
> \*\*CONFIGURATION\*\*
> A\> Ensure you have not disabled the Discovery on the Bridge 
> \<img width="938" alt="Capture d’écran 2019-07-09 à 00 04 33" src="https://user-images.githubusercontent.com/42100737/60846141-d3d0d100-a1de-11e9-9fa1-b7c05c3dfb39.png"\>
> 
> B\> Go in your "INBOX" and clic "Search For Things"
> \<img width="1149" alt="Capture d’écran 2019-07-09 à 00 03 58" src="https://user-images.githubusercontent.com/42100737/60846196-fb279e00-a1de-11e9-8281-0b580f791a15.png"\>
> 
> C\> Choose "RfLink Binding" in the list
> \<img width="1076" alt="Capture d’écran 2019-07-09 à 00 04 53" src="https://user-images.githubusercontent.com/42100737/60846243-198d9980-a1df-11e9-8362-f255254ac38f.png"\>
> 
> The scan will take less than 1 second
> And all eligible remotes will appear in your inbox
> 
> \<img width="1050" alt="Capture d’écran 2019-07-09 à 00 08 16" src="https://user-images.githubusercontent.com/42100737/60846392-8dc83d00-a1df-11e9-8a9b-88ea64ee9a19.png"\>
> 
> Each remote is identified by its characteristics, to prevent unintended mixing
> Example : \*\*\_rts\[0\] RTS-0F0FF0-0 RC=020D\_\*\*
> protocol : rts
> remote number in the RfLink Bridge : \[0\]
> remote address : 0F0FF0
> current rolling code value : 020D
> 
> D\> Validate an entry to add the Thing.
> You can name it as you wish.
> \<img width="754" alt="Capture d’écran 2019-07-09 à 00 08 53" src="https://user-images.githubusercontent.com/42100737/60846412-a0427680-a1df-11e9-903e-ba01149ee8e4.png"\>
> 
> 
> Your logs should show details about the scanning operation : 
> \`Start scanning registered RTS remotes...
> \>\>\> RfLinkPacket \[OUTPUT=10;RTSSHOW;\]
> \<\<\< RTS Record: 0 Address: 0F0FF0 RC: 020D
> Adding rflink:rts:RfLinkUSB:RTS\_0F0FF0\_0 with id 'RTS-0F0FF0-0' and label 'rts\[0\] RTS-0F0FF0-0 RC=020D' to smarthome inbox
> \<\<\< RTS Record: 1 Address: 0F0FF1 RC: 011A
> Adding rflink:rts:RfLinkUSB:RTS\_0F0FF1\_0 with id 'RTS-0F0FF1-0' and label 'rts\[1\] RTS-0F0FF1-0 RC=011A' to smarthome inbox
> \<\<\< RTS Record: 2 Address: 0F0FF2 RC: 0288
> \<\<\< RTS Record: 3 Address: 0F0FF3 RC: 0304
> \<\<\< RTS Record: 4 Address: 0F0FF4 RC: 0402
> Adding rflink:rts:RfLinkUSB:RTS\_0F0FF4\_0 with id 'RTS-0F0FF4-0' and label 'rts\[4\] RTS-0F0FF4-0 RC=0402' to smarthome inbox
> \<\<\< RTS Record: 5 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 6 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 7 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 8 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 9 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 10 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 11 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 12 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 13 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 14 Address: FFFFFF RC: FFFF
> \<\<\< RTS Record: 15 Address: FFFFFF RC: FFFF\`
> 
> 
> Please post here if you encounter any issue

[Previous page](https://community.openhab.org/t/rflink-binding/7863.md?page=5)

[Next page](https://community.openhab.org/t/rflink-binding/7863.md?page=7)