The nice thing of the RFlink is the single antenna, You can even mount a much larger antenna with an extension cord. And I like the build of it, a simple shield, and there are already cases for it. The range is also a bit better, i think because of the antenna.
-
New plugin for RFLink Gateway
-
@Icesory said:
Has some one experience with the difference between Homeduino and RFLink? I have looked at the RFLink firmware and I think it is really complicated programmed. But the RFlink hard can be better.
I didn’t do much research, but I believe that the major difference is that Homeduino more or less just exposes the RF antenna through USB and requires the use of other libraries outside of the Arduino (like RFControl) to interpret the signals and transform commands into correct signals. The RFLink is a plugin based framework (like Pimatic itself ) that also runs the encoding and decoding on the Arduino. It then attempts to abstract the different signal encoding/decoding for many different devices behind a single, relatively simple and unified protocol.
In terms of hardware, I think that a Homeduino may also be built using the exact same hardware as the RFLink with a bit of tweaking of the pin/interrupt configs (which I failed at, hence the existence of this Pimatic plugin ) The other way around is not possible as I’ve understood that the RFLink really requires an Arduino Mega due to its more extensive feature set.
Let the devs correct me if my descriptions have butchered the truth too much
-
@Moustaggio your explanation is right. RFLink dose the encoding on the arduino.
For me the RF quality is interesting. At the I buy many different RF receivevers to determine, which is the best for us. I am plan to develop an PCB for the Rpi like the RFLink PCB. But I want the best receiver for this. So I think I will order an Aurel Rtx-mid-v5
pimatic rocks!!!
-
@Icesory said:
Has some one experience with the difference between Homeduino and RFLink? I have looked at the RFLink firmware and I think it is really complicated programmed. But the RFlink hard can be better.
We are the the ones writing the code for the RFlink Gateway…
If you believe things can be done in a better way then we for sure want to hear about it!
contact email is frankzirrone@gmail.comAt the moment we are adding more protocols and making various other changes to simplify the communication layer even more.
-
Thumbs up, its very stable now!
-
@sweebee Great to hear that! Any luck with implementing the PIRs?
-
@Moustaggio Not yet, coffee script is driving me crazy with that stupid indentation faults.
-
Got it My text editor was doing strange things. I created a pull request https://github.com/sirchia/pimatic-rflink/pull/3
Added the PIR and ContacSensor.
-
I found a temp sensor And sends this:
debug [pimatic-rflink]: data: "20;18;Alecto V4;ID=5948;TEMP=00cb;HUM=53;"
Whats with the temperature? 20,3 degrees i guess?
-
@sweebee said:
Whats with the temperature? 20,3 degrees i guess?
Yes, according to the protocol reference the temperature value is defined as:
TEMP=9999 => Temperature (hexadecimal), high bit contains negative sign, needs devision by 10
NB, HUM is a hex value also -> 83%
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Hello, i need your help!
I installed pimatic (fresh install), we added plugin pimatic rf-link but does not connect with Arduino board…
Arduino board with 433MHz superheterodyne kit I tested it on another raspberry and works well with Domoticz.
I initially tried “/dev/tty.usb 641 modem”
“plugins”: [
{
“plugin”: “cron”
},
{
“plugin”: “rflink”,
“driverOptions”: {
“serialDevice”: “/dev/USB0”
}
},
{
“plugin”: “mobile-frontend”
}
],debug [pimatic-rflink]: Connect failed (Cannot open /dev/USB0), retry in 32 seconds
debug [pimatic-rflink]: Opening connection to RFLink device…
debug [pimatic-rflink]: Attempt to reconnect to device…Thanks in advance for answers.
-
@Andi-Tudor /dev/USB0 doesnt seem right. IT should be something like /dev/ttyUSB0
-
@sweebee said:
/dev/ttyUSB0
Yes it is my fault “/dev/USB0”.
I modified “/dev/ttyUSB0” but does not receive anything.debug [pimatic-rflink]: send: "10;REBOOT;"
warn [pimatic-rflink]: No ready message received within connection timeout, reboot device
debug [pimatic-rflink]: Connection to RFLink device opened
debug [pimatic-rflink]: Opening connection to RFLink device…
debug [pimatic-rflink]: Attempt to reconnect to device…
debug [pimatic-rflink]: Close event from serial device
debug [pimatic-rflink]: Connect failed (No ready message received within connection timeout after reboot, reconnect), retry in 16 seconds
debug [pimatic-rflink]: send: "10;REBOOT;"
warn [pimatic-rflink]: No ready message received within connection timeout, reboot device -
You mentioned heterodyne. Rflink can’t use that. Are you sure you are using an arduino (mega) with the rflink board and firmware?
Arduino mega doesn’t have a ttyUSB, mine is ttyACM0.
-
Using Arduino Mega 2560, 433Mhz-Superheterodyne-3400.
I followed the instructions here:
http://www.nemcon.nl/blog2/2015/07/aaIn Domoticz it works very well (RFLink Gateway USB /dev/ttyUSB0), but I want to work in Pimatic.
-
After several restarts works (/dev/ttyUSB0)
debug [pimatic-rflink]: data: "20;06;AB400D;ID=48;SWITCH=1;CMD=OFF;"
debug [pimatic-rflink]: data: “20;05;AB400D;ID=48;SWITCH=1;CMD=ON;”I do not know how. But now I’m happy.
Thank you. -
New RFLink firmware published:
Changelog R38:
Note: Elmes changed into Keyloq you might have to re-learn the device…- New Device: Initial NodoNRF sensor receive support (2.4ghz) (Thanks: Martinus)
- New Device: Nodo 3.8 slave support
- New Device: Catching of anti-tampering for Atlantic sensors
- New Device: Oregon, extra checks for out of range values
- New Device: Tunex MF-0211 temperature sensor
- New Device: Alecto V3 Rain - Alternative version of WS1200
- New Device: Byron SX21
- New Device: MC145026 based sensors
- New Device: FunkBus remote control support (Insta/Berker/Gira/Jung) (receive only) (Thanks: D.)
- New Device: Kingpin motor controls
- New Device: Livolo
- New Device: Koch remote controls
- New Device: Additional X10 protocol devices
- New Device: Forest “Touch Sense Motors” Curtain control (Thanks: JPe)
- New Device: Faher motor controller DC305, DC307
- New Device: Biltema 84056 temperature and humidity sensor
- New Device: Logipark
- New Device: Friedland EVO doorbell Decor ED1/ED3 (receive only)
- New Device: Friedland DC4 PIR
- New Device: Lobeco door sensors
- New Device: Hadex T093, WH5029
- New Device: FineOffset Temperature & Humidity sensors
- New Device: XT200 temperature sensor
- New Device: Conrad RSL blind controller 640579
- New Device: Smartwares SH5-TDR-A / SHS 5300 Heating Controller / Radiator Valve (Initial support)
- New Device: BFT port opener remotes (Thanks: CS.)
- New Device: Etekcity ZAP
- Added: Oregon, extra checks for out of range values
- Fixed: Oregon Rain sensors (PCR800 and others) (Thanks: D.)
- Fixed: Oregon humidity
- Fixed: Esic WT450H detection
- Fixed: Alecto V1 wind speed values
- Fixed: Alecto V3 Rain values and added battery level support (Thanks: D.)
- Fixed: EverFlourish EMW203T detection
- Fixed: Xiron/Aok humidity
- Fixed: Added more range checks on Aster protocol
- Fixed: Optimized Conrad RSl transmit function
- Fixed: Additional checks on Keeloq protocol
- Fixed: Additional checks on Chuango protocol
- Fixed: Improved EV1527 / Chuango recognition (some issues left)
- Fixed: Added support for the ProMax master buttons
- Fixed: Improved ProMax signal detection
- Fixed: Some changes to X10 command parsing (Thanks: JPe)
- Fixed: RTS increased broadcast time
- Fixed: Ikea Koppla transmit bug
- Fixed: Ikea Koppla dimming issue
- Fixed: Oregon wind speed
- Changed: Created a seperate Novatys plugin
- Changed: Smoke detectors now respond as a switch as well
- Changed: Corrected Elmes label into Keyloq label
- Changed: Splitted the WS1100/WS1200 plugin to improve compatibility
- Changed: Improved WS1200 signal handling
- Changed: Improved incoming command parsing
- Changed: Big speed-up for plugin 1 converted packets
- Changed: Regrouped plugins so new ones can be added more easily
-
@Moustaggio : Nice work!
I use the original nodo software and have some KlikAanKlikUit devices, Flamingo smokedetectors AlectoV1, Xiron, slave nodo’s.
I would like to use Pimatic in the future and i tried the RFlink plugin, and it seems to work ok for the KlikAanKlikUit devices.I would like to also get the AlectoV1 and Xiron info in Pimatic.
I saw u already stared with the conversion of Homeduino to Rflink… But it is still commented out…
Have u already tried it? Had some troubles? Why stopped?Im not a coffee programmer, but if i can help to test and/or develop further the plugin, please let me know.
Kind regards,
Ivan Verdonck -
Hi,
Is there any active development for the rflink plugin?
I’m really missing support temperature/humidity sensors…BR,
Redferne