n7qnm
Junior Member
Posts: 80 
|
Post by n7qnm on Mar 27, 2022 14:16:44 GMT -8
I'm seeing the same thing here, just started in 27.3 - sometimes a reboot fixes it and sometimes not. Gonna set debug, get some data and also check the code.
Clay
N7QNM
|
|
maccampb
New Member
Posts: 21
Raspberry Pi: Yes
Other Device: Linux on X64, Particle Photon, MAC
|
Post by maccampb on Mar 28, 2022 16:35:24 GMT -8
take a look at this post... you can do a local patch on your code to fix until a release is put together by SDL... forum.switchdoc.com/post/13954this line in the file wirelessSensors.py (version 27.3) wtemp = state.OutdoorTemperature Change "wtemp" to "wTemp" and reboot. |
|
taim
New Member
Posts: 32
|
Post by taim on Mar 29, 2022 12:10:02 GMT -8
The typo of „wTemp“ was a great find. Unfortunately, despite of the manual fix, I encountered the same problem of „duplicated“ erroneous data with a different serial number today.  Interestingly though, I also get a false reading in blynk but there it doesn’t result in duplicates.  Here is the data from the database. WeatherData.csv (10.01 KB) |
|
maccampb
New Member
Posts: 21
Raspberry Pi: Yes
Other Device: Linux on X64, Particle Photon, MAC
|
Post by maccampb on Mar 29, 2022 12:27:44 GMT -8
Sorry about that.... the other part of the fix is to discard any data that comes from the FT020 that has a bad id, and likely bad data along with it...
The id from my WeatherRack is 127 so I used this trick... You will have to figure out the id for yours and substitute it..
After this code in wirelessSensors.py:
if (lastFT020TTimeStamp == var["time"]):
# duplicate
if (config.SWDEBUG):
sys.stdout.write("duplicate found\n")
sys.stdout.write('This is the raw data: ' + sLine + '\n')
return "" # bail on the process...
add this code, checking to see that the id is valid, otherwise bail...
if var['id'] != 127: # check for bad id coming from sensor
sys.stdout.write("wirelessSensors.py : bad FT020T ID")
sys.stdout.write("JSON dump:" + json.dumps(var) + '\n')
return "" # bail as well
this completely cleared it for me in my data.
See if that helps...
|
|
|
|
Post by johnso515 on Jul 11, 2022 13:59:21 GMT -8
Folks. I am having a similar problem. Initially I got both spurious low temps (32deg) and high temps (160+deg) that would often go away after a re-boot. I pushed the wtemp fix above and now I get consistent -40deg temp that is persistent across reboots etc. I havent added the "Bad Id" filter as I only see 1 ID in the logs. Any thoughts/suggestions on how to resolve this? The other data points from the sensors (wind, rain, etc.) seem to be OK.
|
|
|
|
Post by SDL on Jul 11, 2022 14:43:01 GMT -8
|
|
|
|
Post by johnso515 on Jul 12, 2022 3:41:17 GMT -8
I am running Version 027.6
I am also running v1.3V of the rtl_433 software per the readme. Is this the latest version? I updated the rtl when I pushed the 27.6 changes last month.
|
|
|
|
Post by SDL on Jul 12, 2022 12:47:08 GMT -8
Should be right.
Can you post some of the spurious readings from the database?
BP
|
|
|
|
Post by johnso515 on Jul 13, 2022 3:03:53 GMT -8
Here is the last 5000 lines from the nohup.out file.
This is what I am seeing:
processing FT020T Data
This is the raw data: {"time" : "2022-07-13 05:25:57", "model" : "SwitchDoc Labs FT020T AIO", "device" : 12, "id" : 188, "batterylow" : 0, "avewindspeed" : 30, "gustwindspeed" : 40, "winddirection" : 221, "cumulativerain" : 7665, "temperature" : 2044, "humidity" : 1, "light" : 131067, "uv" : 251, "mic" : "CRC", "mod" : "ASK", "freq" : 433.983, "rssi" : -0.098, "snr" : 13.864, "noise" : -13.962}
error--->>> Temperature reading from FT020T
This is the raw temperature: 164.4
and
Tick! The time is: 2022-07-13 05:26:43.968472
-------------
Current State
-------------
-------------
latest MainSensor Reading= 2022-07-13 05:26:30
MainDeviceNumber= 220
OutdoorTemperature = -39.99
OutdoorHumidity = 1
The -39.99 rounds to -40 in the dash app and weatherstem
This has been consistent behavior in spite of reboots since I updated the code to fix the wtemp --> wTemp issue.
|
|
|
|
Post by johnso515 on Jul 14, 2022 8:52:01 GMT -8
I've also changed the batteries and reset the WeatherRack but am still getting both the duplicate entries and the spurious temperature readings.
|
|
|
|
Post by SDL on Jul 14, 2022 10:15:27 GMT -8
Thanks for the information. Could you show me the raw data for a duplicate value? I'm wondering about the "id".
Also, show me the duplicate data in the database.
BP
|
|
|
|
Post by johnso515 on Jul 15, 2022 4:30:11 GMT -8
The Ids are the same. Unfortunately. This has been consistent across three resets of the weatherstation. Ids changed but the duplicates continued to show the common Id. Attachments:
|
|
Sopwith
Junior Member
"If it works out of the box - what fun is that?"
Posts: 69
Raspberry Pi: Yes
Other Device: Pico Pi
|
Post by Sopwith on Jul 15, 2022 6:32:24 GMT -8
In reviewing your duplicate data, I noticed the "batterylow" flag is set. You said you replaced the battery, so this is another hint the device itself might not be working properly.
To rule out the SW2 device as the cause, one idea would be to take your SDCard and put it in a Pi connected to a known good SW2 device. It is impractical to buy another device for this type of test. I would be willing to install an image of your existing SDCard on my Pi and run it on my SW2. If I begin to see dups, then we know the issue is not hardware related.
Let me know if you are interested in this type of test. If so, you would need to create an image of your SDCard (e.g dd) and send it to me. I can provide a secure URI for you to place it.
Send me a PM if you are interested in doing this.
Sopwith
|
|
|
|
Post by SDL on Jul 15, 2022 6:40:09 GMT -8
Great idea Sopwith!
johnso515,
1) The duplicate you see up in your attachment is normal. And one is ignored. The WR2 sends each reading out twice, very quickly and the SDR is fast enough to pick both up. So we always throw one away with the same timestamp. I was thinking you were getting multiple IDs. Sorry for the confusion.
2) Now, the bad temperature, that's an issue for sure. Does it always report a bad temperature? And I note that the Light value is at the highest too. Do you ever get the correct temperature? If so, please post a good one too.
BP
|
|
|
|
Post by johnso515 on Jul 15, 2022 10:00:20 GMT -8
I was getting a mix of good values and bad values about two months back. I would see bad values almost every day but the bad values would usually go away after a re-boot or two. Starting about a week back I started getting consistent bad values and have not seen a correct temp reading at all.
|
|
