Acurite 5-in-1 (5n1) Infrequent Signals

[Quella]

I have recently installed and setup rtl_433 (a great tool by the way) on a Raspberry Pi with a NooElec NESDR Mini 2+ 0.5PPM TCXO RTL-SDR & ADS-B USB Receiver which which picks up my AcuRite Tower sensors with ease; about eight of them in different areas. Today, I'm feeding this output to a NodeRed server and extracting it. 

Looking for any feedback or options regarding collecting the 5-in-1 data as this has so much more detail then the tower sensors.  It seems RTL_443 only sees this device once or at most twice in a 24hr period not the normal 18-60second to the display units

I'm running rtl_433 with:

rtl_433 -R40 -C customary -F json:/home/pi/Documents//weather.json (as pi user)

I see the below as the tool loads:
Registered 1 out of 108 device decoding protocols
Found 1 device(s)

trying device 0: Realtek, RTL2838UHIDIR, SN: 00000001
Detached kernel driver
Found Rafael Micro R820T tuner
Using device 0: Generic RTL2832U OEM
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
Sample rate set to 250000.
Bit detection level set to 0 (Auto).
Tuner gain set to Auto.
Reading samples in async mode...
Tuned to 433.920MHz.

My many tower sensor get logged to the file which looks like this:
{"time" : "2018-08-30 10:10:21", "model" : "Acurite tower sensor", "id" : 12265, "sensor_id" : 12265, "channel" : "A", "temperature_F" : 88.700, "humidity" : 58, "battery_low" : 0}
{"time" : "2018-08-30 10:10:27", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 81.140, "humidity" : 68, "battery_low" : 0}
{"time" : "2018-08-30 10:10:27", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 81.140, "humidity" : 68, "battery_low" : 0}
{"time" : "2018-08-30 10:10:27", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 81.140, "humidity" : 68, "battery_low" : 0}
{"time" : "2018-08-30 10:10:28", "model" : "Acurite tower sensor", "id" : 9876, "sensor_id" : 9876, "channel" : "C", "temperature_F" : 81.500, "humidity" : 69, "battery_low" : 0}
{"time" : "2018-08-30 10:10:28", "model" : "Acurite tower sensor", "id" : 9876, "sensor_id" : 9876, "channel" : "C", "temperature_F" : 81.500, "humidity" : 69, "battery_low" : 0}
{"time" : "2018-08-30 10:10:28", "model" : "Acurite tower sensor", "id" : 9876, "sensor_id" : 9876, "channel" : "C", "temperature_F" : 81.500, "humidity" : 69, "battery_low" : 0}
{"time" : "2018-08-30 10:10:29", "model" : "Acurite tower sensor", "id" : 9711, "sensor_id" : 9711, "channel" : "A", "temperature_F" : 98.600, "humidity" : 72, "battery_low" : 0}
{"time" : "2018-08-30 10:10:29", "model" : "Acurite tower sensor", "id" : 9711, "sensor_id" : 9711, "channel" : "A", "temperature_F" : 98.600, "humidity" : 72, "battery_low" : 0}
{"time" : "2018-08-30 10:10:29", "model" : "Acurite tower sensor", "id" : 9711, "sensor_id" : 9711, "channel" : "A", "temperature_F" : 98.600, "humidity" : 72, "battery_low" : 0}

However, the 5-in-1 (5n1) does not show up in the logs as expected. I have also tried to enable all protocols (-G) instead of limiting to only the Acurite (-R40) and I do not see any changes.

When I do a -D -D I get some of the output here which looks more like my tower sensors and not the 5-in-1 (which is reporting to an AcuLink bridge and uploading to WX while also being received by an Acurite display unit; so I know the 5-in-1 is functional)

acurite_txr
bitbuffer:: Number of rows: 3
[00] {57} 26 94 44 c5 09 7d 49 00
[01] {57} 26 94 44 c5 09 7d 49 00
[02] {57} 26 94 44 c5 09 7d 49 00
acurite_txr: row 0 bits 57, bytes 8
acurite_txr Parity: 1100001
acurite_txr: row 1 bits 57, bytes 8
acurite_txr Parity: 1100001
acurite_txr: row 2 bits 57, bytes 8
acurite_txr Parity: 1100001
pulse_demod_pwm_precise(): Acurite 592TXR Temp/Humidity, 5n1 Weather Station, 6045 Lightning
bitbuffer:: Number of rows: 3
[00] {57} 26 94 44 c5 09 7d 49 00
[01] {57} 26 94 44 c5 09 7d 49 00
[02] {57} 26 94 44 c5 09 7d 49 00
Pulse data: 183 pulses
[ 0] Pulse: 158, Gap: 149, Period: 307
[ 1] Pulse: 155, Gap: 148, Period: 303
[ 2] Pulse: 155, Gap: 148, Period: 303
[ 3] Pulse: 155, Gap: 148, Period: 303
[ 4] Pulse: 56, Gap: 97, Period: 153
[ 5] Pulse: 56, Gap: 96, Period: 152
[ 6] Pulse: 104, Gap: 50, Period: 154
[ 7] Pulse: 56, Gap: 96, Period: 152
[ 8] Pulse: 56, Gap: 97, Period: 153
[ 9] Pulse: 103, Gap: 50, Period: 153
[ 10] Pulse: 103, Gap: 50, Period: 153
[ 11] Pulse: 56, Gap: 97, Period: 153
[ 12] Pulse: 103, Gap: 50, Period: 153
[ 13] Pulse: 56, Gap: 97, Period: 153
[ 14] Pulse: 56, Gap: 97, Period: 153
[ 15] Pulse: 103, Gap: 50, Period: 153
[ 16] Pulse: 55, Gap: 98, Period: 153
[ 17] Pulse: 102, Gap: 51, Period: 153
[ 18] Pulse: 55, Gap: 97, Period: 152
[ 19] Pulse: 56, Gap: 97, Period: 153
[ 20] Pulse: 56, Gap: 97, Period: 153
[ 21] Pulse: 102, Gap: 51, Period: 153
[ 22] Pulse: 55, Gap: 98, Period: 153
[ 23] Pulse: 55, Gap: 97, Period: 152
[ 24] Pulse: 56, Gap: 97, Period: 153
[ 25] Pulse: 103, Gap: 50, Period: 153
[ 26] Pulse: 56, Gap: 97, Period: 153
[ 27] Pulse: 56, Gap: 97, Period: 153
[ 28] Pulse: 102, Gap: 51, Period: 153
[ 29] Pulse: 102, Gap: 50, Period: 152
[ 30] Pulse: 56, Gap: 97, Period: 153
[ 31] Pulse: 56, Gap: 97, Period: 153
[ 32] Pulse: 56, Gap: 97, Period: 153
[ 33] Pulse: 103, Gap: 50, Period: 153
[ 34] Pulse: 56, Gap: 97, Period: 153
[ 35] Pulse: 103, Gap: 49, Period: 152
[ 36] Pulse: 57, Gap: 96, Period: 153
[ 37] Pulse: 56, Gap: 97, Period: 153
[ 38] Pulse: 56, Gap: 97, Period: 153
[ 39] Pulse: 56, Gap: 96, Period: 152
[ 40] Pulse: 104, Gap: 50, Period: 154
[ 41] Pulse: 55, Gap: 97, Period: 152
[ 42] Pulse: 56, Gap: 97, Period: 153
[ 43] Pulse: 103, Gap: 50, Period: 153
[ 44] Pulse: 56, Gap: 97, Period: 153
[ 45] Pulse: 103, Gap: 50, Period: 153
[ 46] Pulse: 103, Gap: 50, Period: 153
[ 47] Pulse: 103, Gap: 50, Period: 153
[ 48] Pulse: 103, Gap: 50, Period: 153
[ 49] Pulse: 103, Gap: 50, Period: 153
[ 50] Pulse: 55, Gap: 98, Period: 153
[ 51] Pulse: 102, Gap: 50, Period: 152
[ 52] Pulse: 56, Gap: 97, Period: 153
[ 53] Pulse: 103, Gap: 50, Period: 153
[ 54] Pulse: 56, Gap: 97, Period: 153
[ 55] Pulse: 56, Gap: 97, Period: 153
[ 56] Pulse: 103, Gap: 50, Period: 153
[ 57] Pulse: 56, Gap: 97, Period: 153
[ 58] Pulse: 55, Gap: 98, Period: 153
[ 59] Pulse: 102, Gap: 51, Period: 153
[ 60] Pulse: 55, Gap: 547, Period: 602
[ 61] Pulse: 155, Gap: 148, Period: 303
[ 62] Pulse: 155, Gap: 148, Period: 303
[ 63] Pulse: 155, Gap: 149, Period: 304
[ 64] Pulse: 154, Gap: 148, Period: 302
[ 65] Pulse: 57, Gap: 96, Period: 153
[ 66] Pulse: 56, Gap: 97, Period: 153
[ 67] Pulse: 103, Gap: 50, Period: 153
[ 68] Pulse: 56, Gap: 97, Period: 153
[ 69] Pulse: 56, Gap: 97, Period: 153
[ 70] Pulse: 102, Gap: 51, Period: 153
[ 71] Pulse: 102, Gap: 51, Period: 153
[ 72] Pulse: 55, Gap: 97, Period: 152
[ 73] Pulse: 103, Gap: 50, Period: 153
[ 74] Pulse: 56, Gap: 97, Period: 153
[ 75] Pulse: 56, Gap: 97, Period: 153
[ 76] Pulse: 103, Gap: 50, Period: 153
[ 77] Pulse: 56, Gap: 96, Period: 152
[ 78] Pulse: 104, Gap: 49, Period: 153
[ 79] Pulse: 56, Gap: 97, Period: 153
[ 80] Pulse: 56, Gap: 97, Period: 153
[ 81] Pulse: 56, Gap: 97, Period: 153
[ 82] Pulse: 103, Gap: 50, Period: 153
[ 83] Pulse: 56, Gap: 97, Period: 153
[ 84] Pulse: 56, Gap: 96, Period: 152
[ 85] Pulse: 57, Gap: 96, Period: 153
[ 86] Pulse: 103, Gap: 51, Period: 154
[ 87] Pulse: 55, Gap: 97, Period: 152
[ 88] Pulse: 56, Gap: 97, Period: 153
[ 89] Pulse: 103, Gap: 50, Period: 153
[ 90] Pulse: 103, Gap: 50, Period: 153
[ 91] Pulse: 56, Gap: 97, Period: 153
[ 92] Pulse: 55, Gap: 97, Period: 152
[ 93] Pulse: 56, Gap: 97, Period: 153
[ 94] Pulse: 103, Gap: 50, Period: 153
[ 95] Pulse: 56, Gap: 97, Period: 153
[ 96] Pulse: 103, Gap: 50, Period: 153
[ 97] Pulse: 56, Gap: 96, Period: 152
[ 98] Pulse: 57, Gap: 96, Period: 153
[ 99] Pulse: 56, Gap: 97, Period: 153
[100] Pulse: 56, Gap: 97, Period: 153
[101] Pulse: 103, Gap: 50, Period: 153
[102] Pulse: 56, Gap: 97, Period: 153
[103] Pulse: 56, Gap: 97, Period: 153
[104] Pulse: 103, Gap: 50, Period: 153
[105] Pulse: 56, Gap: 97, Period: 153
[106] Pulse: 102, Gap: 51, Period: 153
[107] Pulse: 102, Gap: 51, Period: 153
[108] Pulse: 102, Gap: 50, Period: 152
[109] Pulse: 103, Gap: 50, Period: 153
[110] Pulse: 103, Gap: 50, Period: 153
[111] Pulse: 56, Gap: 97, Period: 153
[112] Pulse: 103, Gap: 50, Period: 153
[113] Pulse: 56, Gap: 97, Period: 153
[114] Pulse: 103, Gap: 50, Period: 153
[115] Pulse: 55, Gap: 98, Period: 153
[116] Pulse: 55, Gap: 98, Period: 153
[117] Pulse: 102, Gap: 51, Period: 153
[118] Pulse: 55, Gap: 97, Period: 152
[119] Pulse: 56, Gap: 97, Period: 153
[120] Pulse: 103, Gap: 50, Period: 153
[121] Pulse: 55, Gap: 547, Period: 602
[122] Pulse: 155, Gap: 149, Period: 304
[123] Pulse: 154, Gap: 149, Period: 303
[124] Pulse: 155, Gap: 148, Period: 303
[125] Pulse: 155, Gap: 148, Period: 303
[126] Pulse: 56, Gap: 97, Period: 153
[127] Pulse: 55, Gap: 98, Period: 153
[128] Pulse: 102, Gap: 50, Period: 152
[129] Pulse: 56, Gap: 97, Period: 153
[130] Pulse: 56, Gap: 97, Period: 153
[131] Pulse: 103, Gap: 50, Period: 153
[132] Pulse: 103, Gap: 50, Period: 153
[133] Pulse: 56, Gap: 97, Period: 153
[134] Pulse: 102, Gap: 51, Period: 153
[135] Pulse: 55, Gap: 98, Period: 153
[136] Pulse: 55, Gap: 97, Period: 152
[137] Pulse: 103, Gap: 50, Period: 153
[138] Pulse: 56, Gap: 97, Period: 153
[139] Pulse: 103, Gap: 50, Period: 153
[140] Pulse: 56, Gap: 97, Period: 153
[141] Pulse: 56, Gap: 97, Period: 153
[142] Pulse: 56, Gap: 97, Period: 153
[143] Pulse: 102, Gap: 51, Period: 153
[144] Pulse: 55, Gap: 98, Period: 153
[145] Pulse: 55, Gap: 98, Period: 153
[146] Pulse: 55, Gap: 97, Period: 152
[147] Pulse: 102, Gap: 51, Period: 153
[148] Pulse: 56, Gap: 96, Period: 152
[149] Pulse: 56, Gap: 97, Period: 153
[150] Pulse: 103, Gap: 50, Period: 153
[151] Pulse: 103, Gap: 50, Period: 153
[152] Pulse: 56, Gap: 97, Period: 153
[153] Pulse: 56, Gap: 97, Period: 153
[154] Pulse: 56, Gap: 97, Period: 153
[155] Pulse: 102, Gap: 51, Period: 153
[156] Pulse: 55, Gap: 97, Period: 152
[157] Pulse: 103, Gap: 50, Period: 153
[158] Pulse: 56, Gap: 97, Period: 153
[159] Pulse: 56, Gap: 97, Period: 153
[160] Pulse: 56, Gap: 97, Period: 153
[161] Pulse: 56, Gap: 97, Period: 153
[162] Pulse: 102, Gap: 51, Period: 153
[163] Pulse: 55, Gap: 98, Period: 153
[164] Pulse: 55, Gap: 98, Period: 153
[165] Pulse: 102, Gap: 50, Period: 152
[166] Pulse: 56, Gap: 97, Period: 153
[167] Pulse: 103, Gap: 50, Period: 153
[168] Pulse: 103, Gap: 50, Period: 153
[169] Pulse: 103, Gap: 50, Period: 153
[170] Pulse: 102, Gap: 51, Period: 153
[171] Pulse: 102, Gap: 50, Period: 152
[172] Pulse: 56, Gap: 97, Period: 153
[173] Pulse: 103, Gap: 50, Period: 153
[174] Pulse: 56, Gap: 97, Period: 153
[175] Pulse: 103, Gap: 56, Period: 159
[176] Pulse: 56, Gap: 97, Period: 153
[177] Pulse: 56, Gap: 97, Period: 153
[178] Pulse: 102, Gap: 51, Period: 153
[179] Pulse: 55, Gap: 98, Period: 153
[180] Pulse: 55, Gap: 97, Period: 152
[181] Pulse: 103, Gap: 50, Period: 153
[182] Pulse: 56, Gap: 2501, Period: 2557

When 5-in-1 does show up in the logs I see the below info combined with my tower sensor data:

Maybe once or twice in a 24hr period I see some logged data, but not consistently or as frequently as expected. So, I can pick up the radio signal from the unit, it just is not as often or timed like the tower sensors. Could the other tower sensors be steeping on the 5-in-1 signal, and if so why would the display and bridge pick up the signals at regular intervals?

{"time" : "2018-08-30 12:45:55", "model" : "Acurite tower sensor", "id" : 9876, "sensor_id" : 9876, "channel" : "C", "temperature_F" : 84.380, "humidity" : 65, "battery_low" : 0}
{"time" : "2018-08-30 12:45:55", "model" : "Acurite tower sensor", "id" : 9876, "sensor_id" : 9876, "channel" : "C", "temperature_F" : 84.380, "humidity" : 65, "battery_low" : 0}
{"time" : "2018-08-30 12:46:05", "model" : "Acurite 5n1 sensor", "sensor_id" : 2447, "channel" : "A", "sequence_num" : 0, "battery" : "OK", "message_type" : 49, "wind_speed_mph" : 0.000, "wind_dir_deg" : 22.500, "wind_dir" : "NNE", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}
{"time" : "2018-08-30 12:46:05", "model" : "Acurite 5n1 sensor", "sensor_id" : 2447, "channel" : "A", "sequence_num" : 1, "battery" : "OK", "message_type" : 49, "wind_speed_mph" : 0.000, "wind_dir_deg" : 22.500, "wind_dir" : "NNE", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}
{"time" : "2018-08-30 12:46:05", "model" : "Acurite 5n1 sensor", "sensor_id" : 2447, "channel" : "A", "sequence_num" : 2, "battery" : "OK", "message_type" : 49, "wind_speed_mph" : 0.000, "wind_dir_deg" : 22.500, "wind_dir" : "NNE", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}
{"time" : "2018-08-30 12:46:06", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 83.120, "humidity" : 62, "battery_low" : 0}
{"time" : "2018-08-30 12:46:06", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 83.120, "humidity" : 62, "battery_low" : 0}
{"time" : "2018-08-30 12:46:06", "model" : "Acurite tower sensor", "id" : 3264, "sensor_id" : 3264, "channel" : "B", "temperature_F" : 83.120, "humidity" : 62, "battery_low" : 0}

Any thoughts, or things I may be missing as the other sensors seem to be plug and play?

[rich T]

Try moving the Antenna to a different location. Depending on the distance to the 5n1 sensor, the signal might be weak. Do you have the Acurite console in the room with the sdr? How is that reception?

I have 15 sensors including the 5n1 being fed to Node-Red, via RTL_433, all which is running on a RPI3B. I'm using a RTLSDR V3 dongle, which i calibrated after 24 hours of use. Using Magnavox rabbit ear antenna with a inline amp attached to it. This setup has been running fine for several months now without any issues.

[Quella]

Rich,

Thanks for the feedback and I will give moving the unit to another (closer) location a try in the next day or so.  I have only a single Ant. that came with the SDR unit, and happy to purchase a bigger/better one if that would help with receiving the signal.  The weather display unit is nearly twice as far to the 5-in-1 and has to penetrate one outside and two inside walls.  It can be spotty on very hot days, but not bad overall to the display.  The Acurite bridge and the SDR Pi3 are next to each other and have only a single window between them and the 5-in-1; apart from the distance of about 75'-100'.  

If you could provide the Ant. you use I would be happy to test that along with trying to get it closer.  Happy to try anything to get this working as expected.  The bridge has such a small ant. on it that I thought the pull-up that came with the SDR would be better and being near the bridge would give me simular or better reception due to the ant size.  I guess it is a guessing game.  I'll let you know what I find while doing some moving.  It seemed odd that it would only collect it very infrequently while the other tower sensors are rock solid.

[rich T]

As for the stock antenna, don't fully extend it and place on a metal plate of some sort to see if that helps.  The antenna I'm using is a cheap refurbished MG-ANT-6 bought at a local Ollie's store.  I'm also using a cheap inline amplifier I found on amazon.

Did you look for the signal on Gqrx SDR software to see where the signal appears at? I might be wrong, but I believe those dongles do drift over time. After running any of my SDR dongles for the initial 24 hours, I then ran Kalibrate software.

During hot humid days here, the reception might drop for couple minutes then reappear, but does not drop out for the Acurite SmartHub.

[Christian Zuckschwerdt]

Some discussion about the antenna is here: https://github.com/merbanan/rtl_433/issues/749 (gist: unscrew the metal rod and change it).

- bigger antenna is better, but the length matters (tuned to used frequency)

- use a ground plane

- drift is not much of an issue, the default 250k window should cover that. Otherwise go to `-s1024k`

- don't try to put the center frequency right on the signal, use a small offset (say 20 kHz)

[Quella]

Rich,

Thanks again for your input as it has been very helpful!  

It seems that if I drop the ant. down to half the height as you suggested and not move the device, all is working now.  It shows my ignorance of radio as I would have thought the higher/bigger an ant. the better; but I'm still learning.  I will watch the file feed for a few hours and see if the reception becomes more frequent and regular from what I was seeing previously.  I also added an Acurite Lightning Detector yesterday, and have that data being feed into Nodered also.  This lightning sensor, like the tower sensors, was plug and play with rtl_443.  I know the decodes are still a work in progress and hope we can work out the distance info as I do not have a display with lightning option at this time either, only using rtl for the info.  

Love seeing the data and being able to do so much with it.  what a great tool.

Quick question.  Seems the rtl process dies every few days.  Do you just have a tool/script installed to watch the process and restart it if it dies? 

Quella 

[Christian Zuckschwerdt]

rtl_433 is supposed to exit when the receiver fails. For me that happens maybe once a day.

Use some supervision to restart rtl_433 then. S.a. http://triq.net/articles/rtl-433-networking

[Quella]

Thanks for the feedback and recommendations Christian.  I will have a look and work on making the recommended adjustments with my ant.  I will also have a look at the link you provided.  The recommendation that Rich gave to halve the ant. length seems to have done the trick as the 5-in-1 is coming in at more regular times now.  So cool to be able to grab all of this data out of thin air and all the amazing people who have decoded the data!

[Quella]

Good to know it is designed to do this and other have also had the issue and found solutions.  I was planning on writing a script that I can have watchdog monitor and restart it if it dies.  I want to make sure I keep the data flowing.  Last night it died and I lost 5 hours or so while sleeping.  

[rich T]

Glad to hear you are able to capture data now from the 5n1.  About once every two weeks or so, the sdr locks up. Eventually going to add a script to Node-Red to restart the SDR if it did not receive a JSON message within a certain time frame.

Thanks Christian for the additional information and link you provided.

[rich T]

I have a LED connected GPIO pin of the RPI, which blinks when Node-Red receives a JSON message. As long as it is blinking, everything is fine.  I have two Acurite Lightning Detector  being decoded and being fed into node-red / sqlite db.  Over in the WXforum, there is a topic about the Acurite Lightning Detector and the distance data.  Looks like the topic became more active this past month.

[Quella]

Great idea with the LED and a GPIO pin. I will have to do this. Maybe even have a nodred alert to my dashboard or email if nothing is received in a period of time.

I would be interested in seeing the updated data on the lightning detector you mentioned. I’m sure we can work it out as we get more data from people with a display they can relate too. I may buy an HD display to get this info in the house and may help in the deciding farther.

[Quella]

Thanks! I’ll go and get this going on my setup as it seems rather easy and keeps things running.

[rich T]

A notification to the dashboard sounds good.  Check out the WXforum topic about the Acurite Lightning Detector and this https://groups.google.com/forum/#!topic/rtl_433/0XTcPxaMNDk

[Quella]

Thanks for the link and again all your help getting things going (along with Christian).  I'm off to read the info in WXforums you sent over.