Ventilation remote support KNX protocol over RF

Maarten · September 2014

Hi as I'm preparing my house for my homey I have the option to install a Q-Stream Picto 12 Volt Ventilation system with a optional remote. That's nice, but I would rather have homey do the remote function. I called the company Buva but they couldn't give me more info about the technology used.

I found out it uses RF with the KNX protocol. Any idea if this is gonna be supported? It would be really nice if I don't even have to buy the remote. Because I think the communication is wireless by default. Thank you!
PDF with most info
PDF with info
product itself

Emile · September 2014

Ouch, that's scarce documentation. Please do not count on it being supported, as RF KNX is not supported by Homey.

Maarten · September 2014

Okay thank you Emile! Yes I was really suprised that it's not documented well and even the company could not help me further. Thanks again for checking!

p0nts · September 2015

Any information yet?

TarikFaik · February 2016

I also looking for this

FransG · February 2016

Me to

mvtk1990 · April 2016

Same here

Robbertos · December 2016

Any information yet?

Rocodamelshe · December 2016

All the information u need is in the 2nd post of this topic me guess?

bvdbos · December 2016

DId some reading, I think the question you could ask is: Will KNX-router <name> be supported.
https://tweakers.net/reviews/3911/8/doe-het-zelf-domotica-het-nieuwe-tweaken-knx-rf.html
http://knxtoday.com/2014/07/4547/technology-knx-over-ip-new-solutions-for-knx-installations.html

The KNX BAOS binary protocol typically precludes the development of client applications that run in a web browser. For this reason, access to the object server is now possible via the new KNX BAOS Web Services, based on HTTP and Java Script Object Notation (JSON).

bvdbos · December 2016

Or: will the KNX Webservices be supported:
http://www.weinzierl.de/index.php/en/all-knx/software-tools-en/sdk-baos-web-services-en

Slurpgeit · January 2017

I've yet to receive my Homey (it's on it's way as we speak), I would also like to control my ventilation through Homey. Now, these topics had me disappointed at first, but then I did some research. Turns out, this guy:

https://create.arduino.cc/projecthub/kls/arduino-knx-rf-packet-sniffer-7b7a58?ref=platform&ref_id=424_trending___&offset=5

has used the same chip as Homey uses (the CC1101) to sniff stuff from his Siemens KNX setup. He also posted the config he used to achieve this (taken from his "cc1101.cpp"):

void CC1101::setSynco(void)
{
/* Sync word qualifier mode = 15/16 + carrier-sense above threshold */
/* Device address = 0 */
/* Channel spacing = 199.951172 */
/* Modulation format = 2-FSK */
/* Packet length mode = Fixed packet length mode. Length configured in PKTLEN register */
/* Modulated = true */
/* RX filter BW = 270.833333 */
/* TX power = 12 */
/* CRC autoflush = false */
/* Preamble count = 4 */
/* Data format = Normal mode */
/* Carrier frequency = 868.299866 */
/* Data rate = 32.7301 */
/* PA ramping = false */
/* Whitening = false */
/* Channel number = 0 */
/* Address config = No address check */
/* Deviation = 47.607422 */
/* Manchester enable = false */
/* Base frequency = 868.299866 */
/* Packet length = 255 */
/* CRC enable = false */
/***************************************************************
 *  SmartRF Studio(tm) Export
 *
 *  Radio register settings specifed with C-code
 *  compatible #define statements.
 *
 *  RF device: CC1101
 *
 ***************************************************************/
writeReg(0x0000, 0x03); //IOCFG2- GDO2 Output Pin Configuration
writeReg(0x0001, 0x2E); //IOCFG1- GDO1 Output Pin Configuration
writeReg(0x0002, 0x00); //IOCFG0- GDO0 Output Pin Configuration
writeReg(0x0003, 0x41); //FIFOTHR- RX FIFO and TX FIFO Thresholds
writeReg(0x0004, 0x76); //SYNC1- Sync Word, High Byte
writeReg(0x0005, 0x96); //SYNC0- Sync Word, Low Byte
writeReg(0x0006, 0x64); //PKTLEN- Packet Length
writeReg(0x0007, 0x00); //PKTCTRL1- Packet Automation Control
writeReg(0x0008, 0x00); //PKTCTRL0- Packet Automation Control
writeReg(0x0009, 0x00); //ADDR- Device Address
writeReg(0x000A, 0x00); //CHANNR- Channel Number
writeReg(0x000B, 0x08); //FSCTRL1- Frequency Synthesizer Control
writeReg(0x000C, 0x00); //FSCTRL0- Frequency Synthesizer Control
writeReg(0x000D, 0x21); //FREQ2- Frequency Control Word, High Byte
writeReg(0x000E, 0x65); //FREQ1- Frequency Control Word, Middle Byte
writeReg(0x000F, 0x6A); //FREQ0- Frequency Control Word, Low Byte
writeReg(0x0010, 0x6A); //MDMCFG4- Modem Configuration
writeReg(0x0011, 0x4A); //MDMCFG3- Modem Configuration
writeReg(0x0012, 0x05); //MDMCFG2- Modem Configuration //05 def
writeReg(0x0013, 0x22); //MDMCFG1- Modem Configuration
writeReg(0x0014, 0xF8); //MDMCFG0- Modem Configuration
writeReg(0x0015, 0x47); //DEVIATN- Modem Deviation Setting
writeReg(0x0016, 0x07); //MCSM2- Main Radio Control State Machine Configuration
writeReg(0x0017, 0x3C); //Def:30 MCSM1- Main Radio Control State Machine Configuration
writeReg(0x0018, 0x18); //MCSM0- Main Radio Control State Machine Configuration
writeReg(0x0019, 0x2E); //FOCCFG- Frequency Offset Compensation Configuration
writeReg(0x001A, 0x6D); //BSCFG- Bit Synchronization Configuration
writeReg(0x001B, 0x04); //AGCCTRL2- AGC Control
writeReg(0x001C, 0x09); //AGCCTRL1- AGC Control
writeReg(0x001D, 0xB2); //AGCCTRL0- AGC Control
writeReg(0x001E, 0x87); //WOREVT1- High Byte Event0 Timeout
writeReg(0x001F, 0x6B); //WOREVT0- Low Byte Event0 Timeout
writeReg(0x0020, 0xFB); //WORCTRL- Wake On Radio Control
writeReg(0x0021, 0xB6); //FREND1- Front End RX Configuration
writeReg(0x0022, 0x10); //FREND0- Front End TX Configuration
writeReg(0x0023, 0xE9); //FSCAL3- Frequency Synthesizer Calibration
writeReg(0x0024, 0x2A); //FSCAL2- Frequency Synthesizer Calibration
writeReg(0x0025, 0x00); //FSCAL1- Frequency Synthesizer Calibration
writeReg(0x0026, 0x1F); //FSCAL0- Frequency Synthesizer Calibration
writeReg(0x0027, 0x41); //RCCTRL1- RC Oscillator Configuration
writeReg(0x0028, 0x00); //RCCTRL0- RC Oscillator Configuration
writeReg(0x0029, 0x59); //FSTEST- Frequency Synthesizer Calibration Control
writeReg(0x002A, 0x7F); //PTEST- Production Test
writeReg(0x002B, 0x3F); //AGCTEST- AGC Test
writeReg(0x002C, 0x81); //TEST2- Various Test Settings
writeReg(0x002D, 0x35); //TEST1- Various Test Settings
writeReg(0x002E, 0x09); //TEST0- Various Test Settings
}

Now, I am by no means a developer, but I can write some basic stuff when I need to. So I moved over to this page here:

https://developers.athom.com/library/signals/rf/

At first I was hopeful, a lot or parameters seemed to match the ".cpp" file. But when it came to modulation, it said:

"/* Modulation format = 2-FSK */"

However, the Homey dev documentation states:

"The table below shows the radio configuration used by the 433 MHz and 868 MHz receivers. These values cannot be changed by a developer.

Modulation

ASK"

I'm not really that familier with this kind of hardware, but my gut feeling is telling me that that might be a showstopper. Can anyone who actually knows what they're doing comment on this? Or point me in the right direction to start developing an app for KNX?

Thanks!

Pieter · August 2017

Hi Slurpgeit,

I'm interested in this function as well. Do you have any update? Or still waiting on response from developers?

JPe · August 2017

As far as I have found in the Homey documentation, only ASK modulation is possible, this means FSK is not possible. This sounds logical because a receiver cannot receive both types of modulation at the same time, and since Homey has to listen to all these other ASK devices, it is impossible to listen to FSK devices too.

Ventilation remote support KNX protocol over RF

Comments