Synergy doorbell not recognized but signal received, RFXtrx433

This is a bit of a long shot…
I bought an el cheapo wireless doorbell, and was hoping to connect it to my Vera Edge.
The brandname is Synergy.
I connected the RFXtrx433 with an USB cable directly to my pc, and started the RFXmngr app.
The setting of “undec” I set to “on”
If I push the button of the doorbell, I see this message:

22-3-2021 20:26:02
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

So a signal is received, but would I be able to use it one way or the other ?
I don’t know anything about this doorbell’s protocol.
Does it end here, or is there a way to “translate” the message in a way that it can be used in the Vera Edge ?

Again using RFXmngr you might try enabling only the ARC protocol and see if a message is received.

I tried that, now the strange thing is, that both ARC and undec must be on, otherwise I receive nothing. Only ARC or only undec does not work.
And if I repeadly push the bell button, I see different data, like 16000000 or 17000000 or 18000000.

================================================
Set Mode

23-3-2021 09:34:02
Packettype = Interface Message
subtype = Interface Response
Sequence nbr = 8
response on cmnd = Set Mode
Transceiver type = 433.92MHz
Firmware version = 240
Firmware Type = Ext
Transmit power = -18dBm
Hardware version = 1.2
Undec on
X10 disabled
ARC enabled
AC disabled
HomeEasy EU disabled
Meiantech disabled
Oregon Scientific disabled
ATI disabled
Visonic disabled
Mertik disabled
AD disabled
Hideki disabled
La Crosse disabled
FS20/Legrand disabled
ProGuard disabled
BlindsT0 disabled
BlindsT1 disabled
AE disabled
Rubicson disabled
FineOffset disabled
Lighting4 disabled
RSL disabled
Byron SX disabled
Imagintronix disabled
KeeLoq disabled
Home Confort disabled
RFU2 disabled
RFU3 disabled
RFU4 disabled
RFU5 disabled
RFU6 disabled
RFU7 disabled

23-3-2021 09:34:04

23-3-2021 09:34:04
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:06

23-3-2021 09:34:06
Packettype = UNDECODED RF Message
UNDECODED ARC:18000000

23-3-2021 09:34:09

23-3-2021 09:34:09
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:11

23-3-2021 09:34:11
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:14

23-3-2021 09:34:14
Packettype = UNDECODED RF Message
UNDECODED ARC:17000000

Only one more thing to try - the X10 protocol. If you cannot get consistent results I doubt that there is a way to receive messages from this device.

I tried that, now the strange thing is, that both ARC and undec must be on, otherwise I receive nothing. Only ARC or only undec does not work.
And if I repeadly push the bell button, I see different data, like 16000000 or 17000000 or 18000000.

================================================
Set Mode

23-3-2021 09:34:02
Packettype = Interface Message
subtype = Interface Response
Sequence nbr = 8
response on cmnd = Set Mode
Transceiver type = 433.92MHz
Firmware version = 240
Firmware Type = Ext
Transmit power = -18dBm
Hardware version = 1.2
Undec on
X10 disabled
ARC enabled
AC disabled
HomeEasy EU disabled
Meiantech disabled
Oregon Scientific disabled
ATI disabled
Visonic disabled
Mertik disabled
AD disabled
Hideki disabled
La Crosse disabled
FS20/Legrand disabled
ProGuard disabled
BlindsT0 disabled
BlindsT1 disabled
AE disabled
Rubicson disabled
FineOffset disabled
Lighting4 disabled
RSL disabled
Byron SX disabled
Imagintronix disabled
KeeLoq disabled
Home Confort disabled
RFU2 disabled
RFU3 disabled
RFU4 disabled
RFU5 disabled
RFU6 disabled
RFU7 disabled

23-3-2021 09:34:04

23-3-2021 09:34:04
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:06

23-3-2021 09:34:06
Packettype = UNDECODED RF Message
UNDECODED ARC:18000000

23-3-2021 09:34:09

23-3-2021 09:34:09
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:11

23-3-2021 09:34:11
Packettype = UNDECODED RF Message
UNDECODED ARC:16000000

23-3-2021 09:34:14

23-3-2021 09:34:14
Packettype = UNDECODED RF Message
UNDECODED ARC:17000000

I tried your X10 suggestion, but no signal received.
So I guess this doorbell is not supported in any way.

Thanks for guiding me through the possible diagnostic steps.

Probably not worth your while for a one off scenario but to properly interrogate that bell you could use an SDR dongle coupled with rtl_433. If that interests you the details are here rtl_433

Peter thanks anyway, it might be useful information in the future.
For this case I will for now change the design (and it will not be el cheapo anymore)…
I am thinking of modifying a Neo Coolcam door sensor, i.e. replace the reed relais with a pushbutton. In that way, it stays ZWave and I can trigger devices in the house from there.

I did, to support an external reed sensor, and it’s working good.

Good to know that, I will try later to add that to the doorbell circuit, with a lowpower relais. So that both the orignal bell as the Zwave extension can work.

Best Home Automation shopping experience. Shop at getvera!

© 2021 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules