Topic: GW1100 & wunderground and strange temperature fluctuations.

[Jiveborn]

Has anyone encountered these incorrect peaks in the temperature graph? I use the Ecowitt GW1100 and let it feed the wunderground directly. I have the latest firmware and restarted it several times, it still continues.

https://www.wunderground.com/dashboard/pws/IWESTUPP2

Best regards Jan.

[Gyvate]

1. need not be the console, could be the sensor - the WH32 (DP40)
2. is your DP40 also registered to yout HP2551 console (HP1000SE Pro console) ?
If so, what does the HP2551 console show ?
If not, register the WH32/DP40 to the HP2551 console and see what it gives on ecowitt.net and the other sites.
3. which console(s) post(s) to the other weather sites ? (PWS, WC)
as they don't show this behaviour.
4. Is your GW1100 closely located to a potential source of interference ?

[Jiveborn]

1. need not be the console, could be the sensor - the WH32 (DP40)
2. is your DP40 also registered to yout HP2551 console (HP1000SE Pro console) ?
If so, what does the HP2551 console show ?
If not, register the WH32/DP40 to the HP2551 console and see what it gives on ecowitt.net and the other sites.
3. which console(s) post(s) to the other weather sites ? (PWS, WC)
as they don't show this behaviour.
4. Is your GW1100 closely located to a potential source of interference ?   Not really

#3: I use two GW1100 and the Console. EasyWeather consol feeds WOW and and https://www.wunderground.com/dashboard/pws/IUPPHR3  with normal graphs,   GW1100-1 feeds https://www.ecowitt.net/home/index?id=56422  and  https://www.wunderground.com/dashboard/pws/IUPPHR2  and  https://app.weathercloud.net/map#8191310659.   The GW1100-2 feeds https://www.wunderground.com/dashboard/pws/IWESTUPP2.

Best regards Jan

[Gyvate]

what is important to know is to which console(s) the WH32/DP40 outdoor T/H sensor is registered and which output these consoles (the WH32 is connected to) produce. From there we can find out who/what the "culprit" might be.
You can register all three of your consoles at ecowitt.net - and I suggest you do so.

[Jiveborn]

what is important to know is to which console(s) the WH32/DP40 outdoor T/H sensor is registered and which output these consoles (the WH32 is connected to) produce. From there we can find out who/what the "culprit" might be.
You can register all three of your consoles at ecowitt.net - and I suggest you do so.

I will register the other two (GW1100-1 and GW1100-2) on ecowitt.net - will return when this is done. Thank you very much for your suggestions. Unfortunately, I am far from professionals so I learn something new every day.

Best regards Jan

[Jiveborn]

Hello again! Now I have all three registered on Ecowitt: https://www.ecowitt.net/home/index?id=56422
It will probably take a day before we can see the history on the graphs.

I can also admit that I let GW1100-2 feed WeatherDisplay (https://www.jiveborn.se/WeatherDisplay/Jiveborn.htm) and, there, all graphs are perfectly ok.

Best regards Jan.

[Jiveborn]

Hello again.

I can only state that the graphs on Ecowitt do not contain any abnormal peaks in temperature. It seems like it only appears in the graphs of wunderground. I have changed places on the Easy Weather console and GW1100-1 to see if anything changes. Otherwise, I can live with the fact that it only occurs in wunderground.

Best regards Jan.

[Gyvate]

one more idea - as wunderground has a different transmission protocol and there were recently issues with the GW1100 posting to WoW:
have you upgraded your GW1100 to firmware V2.0.7 ? (latest firmware with some improvements - see https://www.wxforum.net/index.php?topic=40730.0 ).

[Jiveborn]

one more idea - as wunderground has a different transmission protocoll and there were recently issues with the GW1100 posting to WoW:
have you upgraded your GW1100 to firmware V2.0.7 ? (latest firmware with some improvements - see https://www.wxforum.net/index.php?topic=40730.0 ).

Yes i have upgraded to V2.0.7.
Best regards Jan

[Jiveborn]

Hi again!

Guess what! I moved the GW1100 that controlled https://www.wunderground.com/dashboard/pws/IWESTUPP2 to another room, about 8 meters from the router. Now all graphs at wunderground are ok.  The distance between the GW1100 and the router can be significant.

Best regards Jan.

[Rover1822]

I am glad that worked. It does strike me as unusual that this solved a "peak" issue.  I would have expected that if distance where to come to play between the GW1100 and the router , that one would see data drop outs as opposed to peaks in the data.

Regardless, as you say it worked , there must be something I don't understand.

[Jiveborn]

I am glad that worked. It does strike me as unusual that this solved a "peak" issue.  I would have expected that if distance where to come to play between the GW1100 and the router , that one would see data drop outs as opposed to peaks in the data.

Regardless, as you say it worked , there must be something I don't understand.

Hello again!

Yes, I do not know what happened. The process of changing location and restarting the GW1100 in combination with restarting the router was all I did. In fact, the graphs in the wunderground remain ok again. However, it is possible that it has not solved the problem of peaks in the long run. It should be as you say the opposite, caused dips. I'm happy as long as it works.

Best regards Jan.

[gszlag]

I am glad that worked. It does strike me as unusual that this solved a "peak" issue.  I would have expected that if distance where to come to play between the GW1100 and the router , that one would see data drop outs as opposed to peaks in the data.

Regardless, as you say it worked , there must be something I don't understand.

Hello again!

Yes, I do not know what happened. The process of changing location and restarting the GW1100 in combination with restarting the router was all I did. In fact, the graphs in the wunderground remain ok again. However, it is possible that it has not solved the problem of peaks in the long run. It should be as you say the opposite, caused dips. I'm happy as long as it works.

Best regards Jan.

Sometimes signal dropouts don't appear on the graphs if they are short duration.
Ecowitt and WU data points are 5 minutes apart and unless you got a droupout exactly on the interval it might be missed.

My GW1000 continues to be problematic ( stopped 3 times in the last 7 days) so I will often use something like pwsweather.com which uses 1 minute data intervals. Sometimes best to use the tables instead of graphs.

Curiously  my GW1100 will show my WH32E as full bars but at the same time my GW1000 shows 1 bar or less!

Next step is to move the WH32E closer to the two consoles and see what happens...

[Rover1822]

Sometimes signal dropouts don't appear on the graphs if they are short duration.
Ecowitt and WU data points are 5 minutes apart and unless you got a droupout exactly on the interval it might be missed.

My GW1000 continues to be problematic ( stopped 3 times in the last 7 days) so I will often use something like pwsweather.com which uses 1 minute data intervals. Sometimes best to use the tables instead of graphs.

Curiously  my GW1100 will show my WH32E as full bars but at the same time my GW1000 shows 1 bar or less!

Next step is to move the WH32E closer to the two consoles and see what happens...

I don't argue this, what I have a problem with is "peaks", that means the addition or interpretation of something to make it a peak. Going back and looking at the data , and seeing that the peaks seem to all reach the same level, not a variance , but the same peak level, seems to point to something else. Where? Cause?... I don't know, but it does seem to be artificial.

[Platokidd]

Don't know if this is relative to the issue or not. I found using a usb extension cord helps tremendously with the gw1000 and a must have for the gw1100 to work properly.

Being to close electrical stuff (computers / surge protectors /batter back-ups and other) can interfere with sensor signal strength and/or cause them to stop working all together. That said, I never seen spikes in data.

[gszlag]

Sometimes signal dropouts don't appear on the graphs if they are short duration.
Ecowitt and WU data points are 5 minutes apart and unless you got a droupout exactly on the interval it might be missed.

My GW1000 continues to be problematic ( stopped 3 times in the last 7 days) so I will often use something like pwsweather.com which uses 1 minute data intervals. Sometimes best to use the tables instead of graphs.

Curiously  my GW1100 will show my WH32E as full bars but at the same time my GW1000 shows 1 bar or less!

Next step is to move the WH32E closer to the two consoles and see what happens...

I don't argue this, what I have a problem with is "peaks", that means the addition or interpretation of something to make it a peak. Going back and looking at the data , and seeing that the peaks seem to all reach the same level, not a variance , but the same peak level, seems to point to something else. Where? Cause?... I don't know, but it does seem to be artificial.

I agree - the peaks are highly unusual and you may be entirely correct in that they might be an artificial artifact maybe generated in a software script.

I am pretty sure now that I am losing signal from the WH32E and the GW1000 that I have is not receiving properly. In my case the GW1000 is closer to the WH32E than the GW1100 but the GW1000 drops out and the GW1100 doesn't. I've moved it(the GW1000) around a bit put a longer USB extension and put new lithium batteries in the WH32E. Still unstable as ever.

Here are some dew point peaks from by pwsdashboard website that I am sure is a result of no signal from the WH32E (or not received by the GW1000). When no signal is present the dewpoint jumps to 0C. In ecowitt the graph doesn't show any artifacts but in the ecowitt table you will see the empty line - no temp, no humidity, etc.
--

[Jiveborn]

Yes it was probably too early to celebrate.  Now they are back again, but only on the graphs in wunderground. We will probably have to continue and look for where the fault lies.

Best regards
Jan

[Jibster]

I have the same problem with GW1000 reporting to WU - ecowitt.net and weathercloud reporting looks fine. It started a couple weeks ago. Spikes are showing up across multiple sensors. I changed my WU station ID and I had good reporting for about a day, but then spikes again. At least I am not the only one 
 [ You are not allowed to view attachments ]

[Rover1822]

Ok this is interesting, 1 having a problem is OK, 1, 2 having it, still a low number , but adds credence to the first to not being for that specific setup.

Now, what is in common between 1 & 2. And could be the problem for 1 & 2?

I have a bunch of GW100Os and GW1100, but I don't have any reporting to WU, which seems to be entire issue area.

We kind of know that WU did some work on their stuff around October 20 something , I forget the exact date but that is when they dropped the web cameras. I am not for an instant saying that is the cause or related to the cause. Just strikes me as something to look at as , as , I believe , this started happening a few weeks ago for those affected approximate to the timeline. Possible other things were done?. No idea.

I do know my data to WU doesn't show the issue, but that is from WS-2000 console, which I send out at 16 sec intervals (I should recheck that , I may have changed it)

...Another thing, how many look at their graph data on WU?  I can tell you I very rarely do. Maybe, this will encourage others to have a look, as the issues reported are short duration, you might not notice if not looking at the graph data.
 

[gszlag]

Ok this is interesting, 1 having a problem is OK, 1, 2 having it, still a low number , but adds credence to the first to not being for that specific setup.

Now, what is in common between 1 & 2 and could be the problem for 1 & 2.

I have a bunch of GW100Os and GW1100, but I don't have any reporting to WU, which seems to be entire issue area.

We kind of know that WU did some work on their stuff around October 20 something , I forget the exact date but that is when they dropped the web cameras. I am not for an instant saying that is the cause or related to the cause. Just strikes me as something to look at as , as , I believe , this started happening a few weeks ago for those affected approximate to the timeline. Possible other things were done?. No idea.

I do know my data to WU doesn't show the issue, but that is from WS-2000 console, which I send out at 16 sec intervals (I should recheck that , I may have changed it)

The problematic GW1000 that is dropping the WH32E signal also uploads to WU but there are no spikes so that would seem to eliminate me from this contest. [ You are not allowed to view attachments ]

[Rover1822]

Drop outs, I expect to see when there is a data issue from lost connections, either from sensor to console, or console to router  to site (WU). Peaks, that is something different. Especially when they seem to have the same max level, or similar.

For a break in data, that is making up data in the form of the peak, what I called artificial.

[Jibster]

The spikes started showing up for me on Nov. 17 on WU graphs - station ID KNCRALEI465. On Nov. 23rd I setup my new station ID because I saw on an old post here that it might fix the problem, but after one day of good graphs, the new ID KNCRALEI888 started showing the spikes too - in fact, they seem worse than ever now 

I was going to buy a new GW1000, but seeing that I am not the only one with this issue, I will hold off. I did not delete my old WU ID if anyone wants to do some forensics 

Old ID:
https://www.wunderground.com/dashboard/pws/KNCRALEI465

[Rover1822]

 I added my GW1100 to my devices on WU, once it starts registering data I'll follow to see if I can duplicate.

I do ask this question. How many of those experiencing an issue had multiple devices on WU when they experienced the issue. (Not what they have done since, just the initial count)

[davidefa]

I think that you need a logger/forwarder script ( like the attached one ) that sits between your weather station and wu ( to understand if the spikes are also present in the data sent by gw1000 ).
You need to use the custom upload feature ( in wu format ) to send data to the logger.

1) extract the script in your server
2) verify that the script works correctly ( call the script from the browser, the log is available in the file params.txt )
3) configure the custom upload to upload to the script
4) if everything works as expected the file params.txt should grow every time a 'record' is received and your wu station should also be updated.

Wait for a spike in wu and verify if is also present in the log.

P.S.
My guess is that the custom upload ( in wu format ) misbehaves when a data is not received from the outdoor main sensor ( or something like this )

 [ You are not allowed to view attachments ]

[Jibster]

How many of those experiencing an issue had multiple devices on WU when they experienced the issue. (Not what they have done since, just the initial count)

I just have one: ECOWITT GW1000 | WH32 | WS68 | WH40 | WH57