FREE - Easy to use - More protocols than any other solution - Multiple frequencies - Multiple home automation platforms


29 December 2019

Since some were asking, yes the project is still alive.
However, we get way more support requests than we can handle.

Right now we spend a lot of time on support causing actual development to go very slow.
Obviously we would like to speed up development and release a new version asap.

Regarding support questions:
- If you have a device that is not on the supported device list and is also not working, make debug logs and mail that to us.
- If you have a device that is listed as working but not working as it should, then we can only help if you make debug logs.

For debug logs:
Follow the directions here
Make sure to use RFLink loader or one of the alternatives that are mentioned!
If you send a screenshot from some debug data then we cannot help you.
Make sure to send multiple debug packets a single on/off packet usually wont work very well.
Thus repeat the process and log the same remote button a few times.
Also make sure that you indicate which logged packet belongs to which button / action etc.
In case of a temperature or other sensor, make sure to include packets from various temperatures/conditions.

Asking if a device that is not on the supported device list could be supported is useless.
The general rule is: If it is not listed we do not know.
If you have a specialized device that uses encryption or similar then it is unlikely that it can be supported, if it can be then for sure not quickly.
If the device is listed as "receive only" then it really means that it is only possible to receive signals.
RFLink does not have transmit routines for such devices. Indeed that means there is no transmit for temperature and alike sensors towards their base stations.
It also means there is no transmit for any other kind of device that is listed as receive only, usually because the signal is protected and cannot be replicated easily.

Note that signals from remote controls that have one single button for both on and off functions are not really suitable for automation.
The reason is simple, there is no way to know/predict the actual state.
Due to this we do not work on implementing such devices.

Some people just send an operation/installation/technical manual or some similar document.
This is ONLY useful if you include debug data. We cannot do anything with just a manual.

When we work out additional protocols we usually contact you either with additional questions or we send a test version.
It frequently happens that we do not hear back. Obviously that delays development a lot.

Please follow the guidelines so that we can spend most of our time on development.


Support the project:

The RFLink Firmware development is a freeware project. This means you should not pay for the firmware.
We are not linked to any shops and do not have unlimited resources to buy sensors and devices.
You can support the project by sending in debug data for new sensors, send hardware or
make a donation so we can buy sensors you would like to see supported.