Understanding why one RF device not usable after EFM8BB1 upgrade ? about rf-bridge-efm8bb1 HOT 7 CLOSED

OK, will do thanks.

from rf-bridge-efm8bb1.

Why 0xA6?

With the command the standard PT226x sniffing gets disabled and the sniffing of the defined protocols in RF_Protocols.h is starting.

If it was working with the original firmware just use the original commands for sniffing (0xA4), learning (0xA1) and transmit (0xA5).

from rf-bridge-efm8bb1.

I have now l spent more time deciphering your readme more fully so I think I know you are saying about RfRaw codes (other than 166 and 177). It's not easy reading material mate, I have trouble following it.

Unfortunately it still doesn't work with RfRaw 0xA1, or 0xA4. I get nothing received by the bridge from this device now (but do with other remote keys).
I have bought a second door bell unit like the first for testing, just in case the first was somehow faulty now (even though still activating the actual wireless bell fine).
No change with the new one, nothing received with that either. So it's still like the original firmware code is not the same as it used to be, I can't learn the device...

Using the console and old learning and pressing remote a few times.

0:09:30 HTP: Console
10:09:46 CMD: rfkey 2 1
10:09:46 SRC: WebConsole from 192.168.0.19
10:09:46 RSL: Group 0, Index 1, Command RFKEY, Data 2 1
10:09:46 MQT: stat/sonoff_bridge/RESULT = {"RfKey1":"Start learning"}
10:09:46 SER: Received A0 55
10:10:17 SER: Received A2 55
10:10:17 MQT: stat/sonoff_bridge/RESULT = {"RfKey1":"Learn failed"}

With RfRaw 0xA4 I get only this after setting and button press on remote.

10:41:21 CMD: RfRaw 0xA4
10:41:21 SRC: WebConsole from 192.168.0.19
10:41:21 RSL: Group 0, Index 1, Command RFRAW, Data 0xA4
10:41:22 MQT: stat/sonoff_bridge/RESULT = {"RfRaw":"OFF"}
10:41:22 SER: Received A0 55

Perhaps I'm still not understanding the way I'm supposed to do this stuff ?

from rf-bridge-efm8bb1.

Please flash the original firmware for the RF Bridge and test and record the data. Maybe on this data we can see why it isn't working.

On the other side the command 0xB1 should sniff any timing/protocol!?

from rf-bridge-efm8bb1.

This is what I get from rfraw 0xB1 and pressing the doorbell TX once for about 200mS.

10:08:06 HTP: Console 10:08:32 CMD: rfraw 177 10:08:32 SRC: WebConsole from 192.168.10.91 10:08:32 RSL: Group 0, Index 1, Command RFRAW, Data 177 10:08:33 MQT: stat/sonoff_bridge/RESULT = {"RfRaw":"ON"} 10:08:33 MQT: tele/sonoff_bridge/RESULT = {"RfRaw":{"Data":"AAA055"}} 10:08:38 MQT: tele/sonoff_bridge/RESULT = {"RfRaw":{"Data":"AA B1 05 00B4 01E0 00D9 006E 13F6 01011010101031101010311031313110013101010110011034 55"}} 10:08:38 MQT: tele/sonoff_bridge/RESULT = {"RfRaw":{"Data":"AA B1 03 009D 01EA 13CE 01011010101001101010011001010110010101010110011002 55"}} 10:08:38 MQT: tele/sonoff_bridge/RESULT = {"RfRaw":{"Data":"AA B1 03 00A1 01EA 13C4 01011010101001101010011001010110010101010110011002 55"}} 10:08:38 MQT: tele/sonoff_bridge/RESULT = {"RfRaw":{"Data":"AA B1 03 00A0 01EA 13C4 01011010101001101010011001010110010101010110011002 55"}}
I will not have time and means to reflash the bridge and do more testing till I catch up on some high priority stuff...

from rf-bridge-efm8bb1.

As sniffed with command 0xB1 I can see the sync time is about 5000µs. The default minimum sync time in the source was 6000µs. So try the new master: d112fbb

from rf-bridge-efm8bb1.

This result speaks volumes...

14:31:11 HTP: Console
14:31:14 SER: Received A4 13 B0 00 AA 01 E0 3D D1 05 55
14:31:15 MQT: tele/sonoff_bridge/RESULT = {"RfReceived":{"Sync":5040,"Low":170,"High":480,"Data":"3DD105","RfKey":"None"}}
14:31:54 CMD: rfkey 2 1
14:31:54 SRC: WebConsole from 192.168.0.19
14:31:54 RSL: Group 0, Index 1, Command RFKEY, Data 2 1
14:31:54 MQT: stat/sonoff_bridge/RESULT = {"RfKey1":"Start learning"}
14:31:54 SER: Received A0 55
14:31:57 SER: Received A3 13 B0 00 A0 01 E0 3D D1 05 55
14:31:57 MQT: stat/sonoff_bridge/RESULT = {"RfKey1":"Learned"}
14:31:57 CFG: Saved to flash at F9, Count 106, Bytes 3584

and then this positive result from Home Assistant for a second confirmation....

Well done.

from rf-bridge-efm8bb1.