Get 2 sets of data #23
Comments
|
This is the master branch and not Carrier Sense ? Looking at the last bit of log, my working theory around what is occurring is that the receiver portion of the code is thinking that the signal is complete and sending it for processing, but then the signal continues and a second signal is captured and sent for processing. The receiver watches the signal strength ( rssi ), and if it drops for a period of time the receiver considers signal is complete. And these devices typically repeat the same message numerous times during a single transmission so this is a potential cause. Looking at number of pulses and signal duration can assist in determining if this is the cause. FYI - this line here provides details about the signal to assist in debugging this - rtl_433_ESP\src\rtl_433\r_api.c - line 852 For your issue with the LED continually flickering ( signal being received ), this is likely caused by noise being received by the receiver. The receiver code is coded to consider rssi over -82 ( MINRSSI ) as a valid signal. As this is a potential issue, I'm working on new receiver logic using CC1101 Carrier Sense to resolve this issue. This is in the Carrier Sense branch, and just needs to have the examples updated before publishing. Question for you, I have been using the OpenMQTTGateway package to provide the production framework for this, and it also supports have a CC1101 and BME280 on the same device, have you looked at it ? |
|
Hi, I tried the openmqttgateway a few months back, and it bricked my ESP32, so wasn't game to try again.
I removed the extra data in rtl_433_ESP\src\rtl_433\r_api.c - line 852 as mqtt wouldn't send the message with the extra data. I have tried #define MQTT_MAX_PACKET_SIZE 512 but that didn't work even if I bumped it up to 1024, its as if it wouldn't change. However I have since read recently that other people were having the same problem and that if I set client.setBufferSize(512) it might fix the problem - I will give it a go and maybe be able to see rest of message and get back to you. I didn't realise the weather station would send more than one message.. but now that you have pointed it out, it makes sense. Anyways thanks for your help/info.. |
|
So I set the mqtt buffer size using set client.setBufferSize(512) and it worked. Here is the output, interestingly it is not doing 2 x messages since I added back to rtl_433_ESP\src\rtl_433\r_api.c - line 852 so that the extra data gets sent. 15:27:29 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.0,"humidity":66,"wind_dir_deg":113,"wind_avg_km_h":3.672,"wind_max_km_h":7.344,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-60,"duration":464037,"espid":"2115"} 15:30:41 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.5,"humidity":67,"wind_dir_deg":338,"wind_avg_km_h":0,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-60,"duration":452733,"espid":"2115"} 15:33:04 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.7,"humidity":68,"wind_dir_deg":338,"wind_avg_km_h":0,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-76,"duration":248528,"espid":"2115"} 15:33:53 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.9,"humidity":66,"wind_dir_deg":338,"wind_avg_km_h":0,"wind_max_km_h":0,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-70,"duration":460084,"espid":"2115"} 15:38:41 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":33.4,"humidity":62,"wind_dir_deg":45,"wind_avg_km_h":0,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-58,"duration":454641,"espid":"2115"} 15:40:17 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":33.4,"humidity":62,"wind_dir_deg":338,"wind_avg_km_h":1.224,"wind_max_km_h":3.672,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-70,"duration":436907,"espid":"2115"} 15:41:53 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":33.3,"humidity":63,"wind_dir_deg":338,"wind_avg_km_h":1.224,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-70,"duration":436269,"espid":"2115"} 15:43:29 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.1,"humidity":66,"wind_dir_deg":113,"wind_avg_km_h":6.12,"wind_max_km_h":7.344,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-70,"duration":451817,"espid":"2115"} 15:45:05 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.5,"humidity":66,"wind_dir_deg":68,"wind_avg_km_h":1.224,"wind_max_km_h":3.672,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-62,"duration":448624,"espid":"2115"} |
|
I notice after 20 minutes it was dropping messages.. so I moved the esp32 over a bit - 50mm, and I was getting the 2 messages again. At that stage it was approx 15M from the weather station. I have moved it to less than 10M from the weather station (line of sight) thinking it would get a better signal, but the problem is the same. 20:47:29 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":27.1,"humidity":81,"wind_dir_deg":45,"wind_avg_km_h":0,"wind_max_km_h":0,"rain_mm":716.10004,"mic":"CRC","protocol":"Fine Offset Electronics WH1080/WH3080 Weather Station","rssi":-54,"duration":464109,"espid":"2115"} I have been using both the stubby antenna that came with the CC1101 module and a 173mm antenna which I replaced a pig tail antenna with on another module. The 173mm one has the best range, but gets the most double signals. The stubby antenna has very limited range, and drops around 1/2 of massages, but also has less of the double messages. I have ordered a couple more CC1101 modules with different antenna from aliexpress to see if that makes a difference. [(https://www.aliexpress.com/item/32763406584.html?spm=a2g0o.9042311.0.0.11b34c4dpsiEZS)] I version of RTL_433_ESP I have downloaded/installed is the master branch. Should I try the Carrier Sense version ? |
Feel free to report the conditions of your test, it can help the community to progress or the community can help you identify what was going wrong. |
|
|
Looking at the message log it is definitely invoking the callback twice for each message, if you look at the signal duration you will see that the same value repeats. My next hypothesis is that the decoder is being invoked twice per signal, let me recreate your minimal config and see if I can recreate the issue. I presume your using the current master which has a workaround for the device going deaf #16 ? Thanks for sharing pictures of your board, looks very well done. How are you handling accuracy of the bme280 with it being in the same enclosure? I find that mine read several degrees high due to heat from the esp32. |
|
Hi, the master I am using is either dated 21/12 or 24/12. I just noticed an update on here and downloaded it. I dont have the board in an enclosure so I think the BME280 isnt effected by heat. I will probably put board in a stevensons screen - made of wood so I am thinking it will probably be ok. I have read that temperature and humidity readings should be taken 1.25M above ground level, and away from any heat radiation source - concrete walls, paving etc.. my weather station is 5M above ground so probably isn't 100% correct anyways. The ESP32 will also be put into deep sleep between sensor/weather station readings so that will keep temp down If I do put in a case. As for the board itself, it works ok, however I have got a new version on the way as I am not happy with the voltage regulator i used and so will use another one, which of course has different pin layout. I have also decided to not have the battery built into board so it can sit behind the board in a smaller case if I decide to put it in one in the future. I have made the new board with ADC pins exposed so can be used for other projects as well. I can sent you the gerber/schematics file of the PCB if you are interested (or anyone else for that matter) once I have tested and am happy it works as it should. They cost US$5.90 for 5 boards including freight from JLCPCB in HK, and I have within 3 weeks of ordering. Maybe can be had for cheaper in USA or EU if they do small run PCB manufacturing there, or other HK/China manufacturers. |
|
So I attempted to recreate your issue in the branch 'issue-#23', using the example code. And I could not recreate the issue. Could you take that branch and attempt to recreate on a test device? 1 - To use the example, you need to clone to repo I have included in the sample a couple of compiler directives to provide more details about the received signal. This is what I receive In my test environment I have 2 LaCrosse TX141 devices that are pretty chatty The first a TX141-Bv2 sends the same data with a tiny gap, so the receiver thinks its two signals and processes each separately. The second a TX141W ( a temperature/humdity/wind sensor ) sends a single signal, with 2 parts, the first part is temperature/humidity data and the second part is the wind data. |
|
Hi, I have cloned the new repo issue 23, I compiled your simple example, and the only changed I have made are as follows: ` #define DEVICES #else Here is the output from terminal monitor - I used with both CC1101 with stubby antenna it came with and the CC1101 with the 173mm antenna I soldered to board: STUBBY ANTENNA: 14:03:29.060 -> ets Jun 8 2016 00:22:57 LONG ANTENNA 14:59:47.564 -> ets Jun 8 2016 00:22:57 |
|
Here is one where there are 2 messages together: |
|
PS I reformatted the comment so it was more readable, the usage of triple back ticks makes it easy on the eyes to spot things Looking at the log data, my receiver code thinks a single message was received ( the single line of raw data and signal details ), and it was passed once to the rtl_433 code ( Once in the method Looking at the raw signal, there is this Am thinking that this is the expected behaviour, and the second message is valid data received from the sensor. |
|
Thanks for formatting it, I could not work out how to do it. I don't get the 2 messages with the SDR rtl_433 receiver, so does this mean that the SDR rtl_433 is ignoring the second message ? I was wondering if me changing it to listen for only my weather station is when it started to happen. I will have it listen for a few more devices and see if it goes back to just decoding the one signal. |
|
What issue is occurring as a result of the second signal ? Do you need to code a duplicate message filter? Ie if current message equals previous message and gap is less than x minutes, drop the message |
|
Mostly the issue is the data is all being written to a database on the rpi, so I am now storing twice as much data as before or I will be when I switch over from SDR to this. I graph it over a week/month/year, and also compare previous months/years.. its a farmers obsession with the weather. Would just do the duplicated message filter in my code before sending to mqtt (compare the last json data to the current json data) or could I do a signal time check in rtl_433_esp code somewhere, as in if new message within 1/2 sec of last one drop it, which is maybe easier ? |
|
As the message callback is in the middle of the rtl_433 code am thinking it would make more sense in your code. As their may be other users with different use cases.
I’m glad we found the issue though, I had thought it was a code error from the recent update and not a signal issue.
… On Jan 22, 2022, at 9:01 AM, davoau ***@***.***> wrote:
Mostly the issue is the data is all being written to a database on the rpi, so I am now storing twice as much data as before or I will be when I switch over from SDR to this. I graph it over a week/month/year, and also compare previous months/years.. its a farmers obsession with the weather.
Would just do the duplicated message filter in my code before sending to mqtt (compare the last json data to the current json data) or could I do a signal time check in rtl_433_esp code somewhere, as in if new message within 1/2 sec of last one drop it, which is maybe easier ?
—
Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEXEFGAW4RQSNUSSVTD4KNTUXK2D3ANCNFSM5MF5WBPA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.
|
|
I have been playing around to see if I could recreate what I had before with just getting the one message, and also with the rtl_433_callback check for multiple messages from the weather station. In the callback function I put a if new message is less than 200 millisec's since last message return - I saw that the messages were around 97ms apart. It fixed the problem of multiple messages. Then I changed the number of devices I check to what I had before, as below, and I only get one message again now (I removed the time check in callback). Do you know why this is - I am just curious ? |
|
As the duplicate message was part of the signal decode and triggered by a short gap I'm not sure how this change would have affected that. Also I was thinking further your comment around not sending a message if the previous message was sent within 200 milliseconds, and this would break the LaCrosse TX141W Wind speed sensor. It sends a 2 part message which is then transmitted as 2 separate messages, one with temperature and one with wind speed. |
|
I am wondering if it because it takes time to process the the signal, as in check which device it is from, and then the rest is lost. I have now got the ESP32 with rtl_433_ESP working as well as the SDR_RTL_433 setup (not as reliable over distance of +15M from weather station though), just waiting for my new PCB's to come so I can connect to solar and put out in yard. When/if I am happy with the new PCB's, where do you I suggest I post about it to make available gerber/schematics files if anyone else is interested ? |
|
The signal receiver logic and the decoder logic have rudimentary separation from each other. The signal receiver is interrupt driven, and the decoder is part of the Arduino loop. The only part that is shared is the start and end of signal detection, which is also part of the Arduino loop. And the signal receiver uses multiple 'trains' to store the interim messages, to avoid overwriting a signal being processed with one being received. For this scenario, the decoder time is not the issue as the signal receiver is receiving a single message, that is passed to the decoder as single decode stream. If this was problematic, it would have shown up when I dig into the received signals. For the gerber/schematics files, you could add them to this repo thru a pull request and include any required notes in a file. Or I wonder if the OpenMQTTGateway team would be interested ? PS I consider myself a junior / intermediate ESP coder, and haven't been doing it much longer than yourself. |
|
@davoau stumbled on this learning more about the ESP project and saw that TASTEY looking board .. Is that something you are still working on? Did you ever land on the best antenna ? Im struggling with range issues as well .. if you would like to chat out-of-band on this, please feel free to ping me at cgmckeever [at] gmail ... |
Hi, I am getting 2 sets of data coming from the rtl_433_Callback function - or the function is being called twice.
This has only started happening since I updated to the new version of rtl_433_ESP.
The following modifications is all I have done in relation to rtl_433_ESP library/code:
rtl_433_ESP\include\rtl_433_devices.h - line 120
#define DEVICES
DECL(fineoffset_wh1080)
/* Add new personal decoders here. */
#define NUMOFDEVICES 1
#endif
rtl_433_ESP\src\rtl_433_ESP.cpp - line 206
#else
memcpy(&cfg->devices[0], &fineoffset_wh1080, sizeof(r_device));
#endif
rtl_433_ESP\src\rtl_433\r_api.c - line 852
/*
data_append(data,
"protocol", "", DATA_STRING, r_dev->name,
"rssi", "RSSI", DATA_INT, cfg->demod->pulse_data->signalRssi,
"duration", "", DATA_INT, cfg->demod->pulse_data->signalDuration,
NULL);
*/
void rtl_433_Callback(char* message) {
Log.notice(F("Received message : %s" CR), message);
DynamicJsonBuffer jsonBuffer2(JSON_MSG_BUFFER);
JsonObject& RFrtl_433_ESPdata = jsonBuffer2.parseObject(message);
String mqttSubTopic;
String model = RFrtl_433_ESPdata["model"];
String id = RFrtl_433_ESPdata["id"];
if (model != 0) {
mqttSubTopic += "/" + model;
if (id != 0) {
mqttSubTopic += "/" + id;
}
}
RFrtl_433_ESPdata["espid"] = espID;
char JSONmessageBuffer[RFrtl_433_ESPdata.measureLength() + 1];
RFrtl_433_ESPdata.printTo(JSONmessageBuffer, sizeof(JSONmessageBuffer));
mqttPublish(mqttSubTopic, JSONmessageBuffer );
}
void loop()
{
rf.loop();
}
I also have BME280 sensor connected to the ESP, which is run in another loop on cpu core 1, and rf.loop is run on core 2 (default for ESP32 loop function).
It doesnt happen everytime, probably 2/3 of the time.
I also have SDR_RTL_433 running on a rpi0, and I only get the one set of data every 136 secs.
The following output shows both the weather station data and BME280 - BME280 sensor is read every 60secs, and the weather station sends out a message every 136 secs.
10:05:52 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.8,"humidity":69,"wind_dir_deg":315,"wind_avg_km_h":0,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:05:52 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.8,"humidity":69,"wind_dir_deg":315,"wind_avg_km_h":0,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:06:20 - rtl_433_ESP/SENSORS {"espid":"2115","temperature":30.84,"humidity":75.58,"abs_humidity":24.00,"dewpoint":26.02,"heatindex":38.88,"pressure":1007.50,"altitude":21.64,"sealevel":1008.41}
10:07:20 - rtl_433_ESP/SENSORS {"espid":"2115","temperature":30.84,"humidity":75.58,"abs_humidity":24.00,"dewpoint":26.02,"heatindex":38.88,"pressure":1007.50,"altitude":21.64,"sealevel":1008.41}
10:07:28 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.7,"humidity":69,"wind_dir_deg":315,"wind_avg_km_h":1.224,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:08:20 - rtl_433_ESP/SENSORS {"espid":"2115","temperature":30.84,"humidity":75.58,"abs_humidity":24.00,"dewpoint":26.02,"heatindex":38.88,"pressure":1007.50,"altitude":21.64,"sealevel":1008.41}
10:09:04 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.8,"humidity":70,"wind_dir_deg":315,"wind_avg_km_h":1.224,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:09:04 - rtl_433_ESP/Fineoffset-WHx080/150 {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":32.8,"humidity":70,"wind_dir_deg":315,"wind_avg_km_h":1.224,"wind_max_km_h":2.448,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:09:20 - rtl_433_ESP/SENSORS {"espid":"2115","temperature":30.84,"humidity":75.58,"abs_humidity":24.00,"dewpoint":26.02,"heatindex":38.88,"pressure":1007.50,"altitude":21.64,"sealevel":1008.41}
The function that publishes the MQTT message is used for both rtl_433_ESP and BME280, so I dont think its from there or else it would show the same problem for BME280.
Here is the data from arduino terminal:
10:18:45.700 -> rtl_433_ESP(6): Signal length: 471335, Gap length: 47771067, Signal RSSI: -74, train: 0, messageCount: 4, pulses: 189
10:18:45.747 -> rtl_433_ESP(6): RAW (471517): +531-963+516-951+498-960+509-950+503-943+545-941+532-947+499-963+1493-931+551-939+1515-900+527-957+1494-932+1498-964+528-923+1518-929+520-952+499-942+1521-925+1505-950+1496-942+504-939+1509-937+532-938+542-904+1531-959+1453-975+478-1010+483-956+1474-988+1477-938+1481-977+505-966+1468-971+1472-954+1502-957+507-941+541-930+524-946+1485-932+1515-933+1509-936+1503-993+1443-988+1449-966+1478-965+532-932+1488-949+1480-979+1473-954+1495-957+1485-918+1532-928+529-958+517-958+1486-945+1483-960+1489-952+1508-925+524-950+1497-941+1478-968+507-966+1490-957+527-920+1521-914+524-917+1536-863+1605-923+494-951+518-953+1482-966+1488-952+1479-943+1513-944+1547-903+521-932+1488-915+1535-937+529-960+1474-954+520-956+1482-964+536-926+504-921+548-942+1509-6437+1484-822+548-24756+1483-398+555-939+519-924+547-937+540-896+549-965+530-924+529-936+545-915+1558-855+556-950+1465-1003+449-1001+1455-964+1480-968+503-977+1491-924+499-988+473-1021+1436-982+1489-950+1504-918+517-958+1478-968+556-903+505-956+1493-949+1492-961+551-911+507-963+1492-944+1496-940+1484-968+510-931+1516-946+1487-940+1506-960+541-914+533-941+509-948+1529-909+1528-902+1526-902+1528-919+1534-927+1481-988+1464-982+511-935+1502-928+1527-938+1513-905+1538-910+1511-933+1508-945+520-929+548-919+1519-926+1526-930+1543-883+1530-932+507-955+1491-957+1466-958+537-935+1501-938+525-936+1508-938+511-955+1481-964+1494-942+528-914+554-949+1488-942+1495-941+1503-945+1511-926+1505-947+514-936+1501-925+1522-926+551-941+1488-964+520-911+1536-914+529-962+541-913+524-933+1511-985+148-195+199-2320+0-3267+0-818+0-35000+100-299+74-376+0-378+75-357+75-381+0-811+0-1214
10:18:45.887 -> rtl_433_ESP(6): Pre run_ook_demods: 227464
10:18:45.887 -> rtl_433_ESP(7): demod(6) - Fine Offset Electronics WH1080/WH3080 Weather Station
10:18:45.887 -> Fine Offset WH1080 data {80} ff a9 62 cc 47 01 03 09 53 04
10:18:45.887 -> rtl_433_ESP(6): data_output {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":31.6,"humidity":71,"wind_dir_deg":90,"wind_avg_km_h":1.224,"wind_max_km_h":3.672,"rain_mm":716.10004,"mic":"CRC"}
10:18:45.887 -> N: Received message : {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":31.6,"humidity":71,"wind_dir_deg":90,"wind_avg_km_h":1.224,"wind_max_km_h":3.672,"rain_mm":716.10004,"mic":"CRC"}
10:18:45.934 ->
10:18:45.934 -> rtl_433_Callback running on core 1
10:18:45.934 -> mqttSubTopic: /Fineoffset-WHx080/150
10:18:45.934 ->
10:18:45.934 -> mqttPublish running on core 1
10:18:45.934 -> mqttTopic: rtl_433_ESP/Fineoffset-WHx080/150
10:18:45.934 -> jsonMessage: {"model":"Fineoffset-WHx080","subtype":0,"id":150,"battery_ok":1,"temperature_C":31.6,"humidity":71,"wind_dir_deg":90,"wind_avg_km_h":1.224,"wind_max_km_h":3.672,"rain_mm":716.10004,"mic":"CRC","espid":"2115"}
10:18:45.934 -> pulse_demod_pwm(): Fine Offset Electronics WH1080/WH3080 Weather Station
10:18:45.981 -> bitbuffer:: Number of rows: 1
10:18:45.981 -> [00] {87} ff 52 c5 98 8e 02 06 12 a6 09 5c
10:18:45.981 -> Fine Offset WH1080 data {80} 7f a9 62 cc 47 01 03 09 53 04
10:18:45.981 -> rtl_433_ESP(6): # of messages decoded 1
10:18:45.981 -> rtl_433_ESP(6): Signal processing time: 251183
10:18:45.981 -> rtl_433_ESP(6): Post run_ook_demods memory 227464
When I connect the ESP32 to my computer, and monitor on the terminal it stops sending the RF data twice, and the blue LED on the ESP flickers continually - never goes out. If not connected to PC there is a clear flashing of the blue LED.
Anyways any help would be great.
Thanks
The text was updated successfully, but these errors were encountered: