It sends 3 packets of data each 45s. The sample I've created using Audacity shows one of them (the second graph is a clock waveform I've tried to derive from data).
I've got stuck with decoding binary data from the received sample. I tried simple decoding by assigning "1" to long pulse and "0" to short one, and vice versa, but I didn't find any match of data that was measured. But I didn't really expected to get results here. There is obviously some encoding used, as low pulses have also different length. I've already searched the forum and found that these gadgets sometimes uses Manchester encoding, but I according to Manch. encoding description, the first high pulse should be short and change of data occurs in the middle of clock period.
I know there is a lot of smart and experienced experts here, so, please, could you advice me what type of encoding could be used so I can continue with decoding?
Thanks.
Perhaps you can open it, and try to see if an encoder chip is used.
The protocol can be analyzed on the PC with the Protocol Analyzer, analyzer:start [Nethome]
Can you attach a full audio sample here with what temperature/humidity the device was reading at the time. To me it does not look like Manchester encoding but I need to see the full sample with expected data to be sure. Elsewhere I have written a simple program to extract the bit patterns but I need a few values pre-setting so it can determine 0 & 1 bit lengths, sync length (assuming this uses one) and number of bits per packet.
Hi,
the recorded sample from Audacity is here.
Data from the sensor are at 0:31.5, where the measurement was 8.9°C,23% and at 1:16.5, where it measured 9.9°C,21%.
Erdin: The app looks good, I didn't know such tool exists.
