Hello! I have a Nice ON2E romote and the Flipper doesn’t seem to be able to read it.
The frequency is 433,92 (marked on the remote and measured with the flipper’s frequency analyser).
In read mode it is not recognised by Flipper.
I attach the photos of the remote and raw files for both buttons. I found the manual for the remote - it supports remote-to-remote copying without access to the gate control unit.
Is it possible to add the support of this type of remotes to Flipper?
RAW_nice_on2e_b1.sub (57.2 KB)
RAW_nice_on2e_b2.sub (56.3 KB)
Quick question, do the RAW recordings work when replayed ?
Tried only once, it worked.
It’s good, thn you have correct modulation. Let’s hope that dev team can implement this protocol. Should be a variant of the already implemented NICE protocols then …
Any update on this topic I’m having the same issue
1 Like
More info on the subject. We discussed Nice One Era in Telegram and one guy analyzed the raw signals I have put here with the Omega device. Here is the info he got:
May be this can help.
UPD
One more raw (button A, single pressing) with info from Omega:
RAW_nice_on2e_b1_oneshot.sub (18.9 KB)
UPD2
More info from the official Nice One broshure:
(https://www.niceforyou.com/sites/default/files/upload/catalogues-brochures/nice_era_one_en.pdf)
433.92 MHz rolling code, with management
of Identity Codes and Certificates,
self-learning and built-in proximity receiver;
with 72 bit O-Code encoding,
also compatible with receivers with
Nice FLOR encoding.
…
Easy memorisation, even at a distance,
thanks to Opera receivers.
There are two options for enabling
a new Inti transmitter, even at a distance
from the system:
• using a transmitter already programmed
in the receiver, thanks to the enabling
Code exchange between the two (figure 1);
…
Yet another system that uses rolling codes improperly…