Bug-report. RFLink R30 does wrong protocol.

[costo]

I have several transmitters with the EV1527 chip inside, like those cheap window/door sensors from china.
I am sure these sensors send a 24 bit signal, 20 address bits and 4 data bits.
The timing of the sensors is about 420-450 uS for the short pulse. (seen on Salea logic analyser)
RFLink reports these sensors as:
20;5E;X10;ID=41c801;SWITCH=01;CMD=ON;
this cannot be right because when I transmit the command
10;X10;41c801;01;ON;
with RFLink this signal is totally different on the analyser than the signal sent by the EV1527 sensors.

I like the RFLink software very much, good work from Stuntteam !!
I hope the bug will be corrected asap.

[Stuntteam]

Hi,
Actually there is nothing wrong with the detection itself.. The device is picked up.
However, as there are many devices that use this 'protocol' it is hard to put a name label on it.
So initially all of these sensors were reported as X10 until we have a better name.
As a side effect, sending with X10 is actually resulting in really using the X10 protocol which is different.
Chuango is the first of these sensors that now uses its own label.
You are free to propose a decent label/device name, as long as it fits all devices detected by the plugin.

[costo]

What's in a name ?
There must be many brands and types of transmitters based on the hardware EV1527 encoder or the software implementation of this chip.
Giving that protocol a name referring to a particular brand or type could be misleading.
My personal choice would be to refer to the chip EV1527 and possibly as a sub-type give it a A,B or C depending on the timing.
So I suggest EV1527-A for short timings, EV1527-B for medium timings and EV1527-C for long timings.

At the moment I do not have enough knowledge of RFLink to see how this can be done.
The way it is now seems unworkable for me because I cannot make RFLink transmit the EV1527 protocol,. . . . . . . unless it is possible to let Domoticz retransmit a received code exactly as it is received. (edit: ofcourse impossible because Domoticz receives the string with X10 in it and has no knowledge how the signal looks in reality)
For now I do not have enough knowledge and experience with Domoticz. I just started very recently with this application and have a lot to learn.

edit: Sadly giving RFLink the command: 10;Chuango;41c801;01;ON; does not give a result but just a: 20;06;CMD UNKNOWN;

By the way, this 'Chuango' protocol is not only used in alarm-sensors. I have a 433MHz RGB controller http://www.aliexpress.com/item/RF-Wirel ... 5,201409_5 that uses the software implementation of the EV1527 protocol and i like to have Domoticz imitate this remote.

[oopee]

Maybe related:
I have cheap Chinese PIR. When it detects motion, a lot of information is displayed in log:

2015-09-14 08:43:50.379 RFLink: 20;BB;Chuango;ID=82aaea;SWITCH=02;CMD=ON;
2015-09-14 08:43:50.379 Error: RFLink: Unhandled switch type: Chuango
2015-09-14 08:43:55.876 RFLink: 20;BC;X10;ID=7d5515;SWITCH=01;CMD=ON;
2015-09-14 08:43:55.876 (RFLink) Light/Switch (PIR 2)

In Devices, it's only recognised as X10 device. It works (named as PIR 2) but usually needs two consecutive detections before X10 "kicks in" (see above).
Why error comes up?

Have to say that RFLink is definitely looking promising. I was unable to receive Chinese PIR/windows sensors with RFXCOM because needed protocols disabled others. And with RFLInk I can receive TFA pool sensor perfectly. With RFXCOM I couldn't get anything, not even undecoded signal.

[Stuntteam]

>2015-09-14 08:43:50.379 Error: RFLink: Unhandled switch type: Chuango
This is due to your Domoticz version not being one of the recent beta versions.
Support for the Chuango name was only added recently.
The idea is also to add Chungo transmit to RFLink so that Sirens and switches can be controlled..

[Stuntteam]

What's in a name ?
Giving that protocol a name referring to a particular brand or type could be misleading.
My personal choice would be to refer to the chip EV1527...

Next release of RFLink will use the EV1527 name. Domoticz has been modified for this as well.

The way it is now seems unworkable for me because I cannot make RFLink transmit the EV1527 protocol,. . . . . . .
edit: Sadly giving RFLink the command: 10;Chuango;41c801;01;ON; does not give a result but just a: 20;06;CMD UNKNOWN;

Correct. Reception of Chuango devices was just pulled apart from the generic receive routines.
So far it was tested with various Chuango alarm sensors. There is no transmit yet.
The idea is to add Chuango transmit in a future version so that sirens can be turned and possibly more.
It will depend on the help I get with testing as I have no access to Chuango devices.

By the way, this 'Chuango' protocol is not only used in alarm-sensors. I have a 433MHz RGB controller that uses the software implementation of the EV1527 protocol and i like to have Domoticz imitate this remote.

On 433mhz most devices send the same command a number of times to make sure the signal is received. There could be a problem with this remote when it sends the same signal for power on and power off..
However, in the end that would probably just mean that you need to visually confirm that the device is on or off and you can not rely on its state.
Can you mail me ([email protected]) debug data for the various buttons?

[costo]

Can you mail me ([email protected]) debug data for the various buttons?

Done, happy to help you.

[AxelvanH]

What's in a name ?
There must be many brands and types of transmitters based on the hardware EV1527 encoder or the software implementation of this chip.
Giving that protocol a name referring to a particular brand or type could be misleading.
My personal choice would be to refer to the chip EV1527 and possibly as a sub-type give it a A,B or C depending on the timing.
So I suggest EV1527-A for short timings, EV1527-B for medium timings and EV1527-C for long timings.

At the moment I do not have enough knowledge of RFLink to see how this can be done.
The way it is now seems unworkable for me because I cannot make RFLink transmit the EV1527 protocol,. . . . . . . unless it is possible to let Domoticz retransmit a received code exactly as it is received. (edit: ofcourse impossible because Domoticz receives the string with X10 in it and has no knowledge how the signal looks in reality)
For now I do not have enough knowledge and experience with Domoticz. I just started very recently with this application and have a lot to learn.

edit: Sadly giving RFLink the command: 10;Chuango;41c801;01;ON; does not give a result but just a: 20;06;CMD UNKNOWN;

By the way, this 'Chuango' protocol is not only used in alarm-sensors. I have a 433MHz RGB controller http://www.aliexpress.com/item/RF-Wirel ... 5,201409_5 that uses the software implementation of the EV1527 protocol and i like to have Domoticz imitate this remote.

I also have a lot of devices using the EV1527 chip (and the 2262) which are not 'detected'. So I am also currious when this update will of Rfxcom will be released (I have 249 running at the moment)

[Stuntteam]

[quote="AxelvanHI also have a lot of devices using the EV1527 chip (and the 2262) which are not 'detected'. So I am also currious when this update will of Rfxcom will be released (I have 249 running at the moment)[/quote]

You are in the RFLink section.
The EV1527 and 2262 devices are picked up by RFLink..
Maybe you should get a RFLink Gateway..?