Hi!There is a way to get a single WH2650 from China (=WH2650 + WH32B). You have to request/order it with Fine Offset directly, sales@foshk.com , who will then give the order to Ecowitt for order fulfillment. Price excluding shipment around 42 USD. With fast shipping (FedEx) it becomes 80 USD. Normal China post will probably be around 50 USD. To be verified with Lucy, who will contact you wearing the FOSHK hat in case of an order with FOSHK. Also, as it's a 868 MHz model which is needed here as I understand, the production will take some time.QuoteCan I make the GW1000 pick up the readings from the WH32B ?No, the GW1000 cannot process the values from the WH32B.
A WH2650 would be more suitable - same technology as the GW1000 but without a built-in T / H / P sensor. Instead, the WH2650 comes with a WH32B.
Unfortunately, the WH2650 is not available from the Ecowitt webshop. You will probably have to inquire there by email. Or you can get it from Froggit or Expondo.
But since you already have the WH32B and GW1000, these new purchases are probably not a solution for you.
Sorry!
Oliver
↧
Re: Can you change a Station ID
↧
Re: Fine Offset Clone Models, compatibility matrix and other useful info - MUST READ
change log:
(14-Nov-2020) added Froggit DP70 (=Ecowitt WH55)
(14-Nov-2020) updated sensor hierarchy (footnote 7)
(17-Nov-2020) included Watson as Fine Offset clone seller to footnote d and to the packages
(20-Nov-2020) added acronym scheme (source: Ecowitt)
(21-Nov-2020) updated table: added WS6006/WL6006 and updated footnote 10 on WS6006/WL6006 (source: Ecowitt)
(22-Nov-2020) added Ambient PM2.5 indoor (WH43) and WH31LA (WH55), updated HP3501 sensor compatibility, added Weather Network information
(23-Nov-2020) updated WL6006 info
(24-Nov-2020) added console clone models/brands and their frequencies
(25-Nov-2020) updated HP3501 sensors (with console firmware 1.6.9), added console/screen sizes, added firmware info
(03-Dec-2020) updated WiFi firmware version for Ecowitt and compatible
(07-Dec-2020) added WH31P (Ambient) to the matrix
(10-Dec-2020) added picture of newly released WH45 (release date 10-Dec-2020)
(26-Dec-2020) added picture for HP2551/WS-2000/WS5000 console display overview
(30-Dec-2020) marked WH32E for Ambient as "end-of-life" (exactly "end-of-support" as they have taken it off their portfolio)
(03-Jan-2021) added reference to related discussion thread https://www.wxforum.net/index.php?topic=40837.0
(03-Jan-2021) added remark regarding past 24 h rainfall display of the HP2551 console
(05-Jan-2021) added PanTech as another reseller brand in Australia (HP2551, HP2553 and extra sensors)
(13-Jan-2021) added Froggit DP30 water temperature sensor to the matrix
(17-Jan-2021) added Meteobridge/Weewx/CumulusMX/WeatherDisplay console support info
(22-Jan-2021) updated footnote 9 with the new WN30 (temperature only, waterproof probe, 3 m cable) sensor
(29-Jan-2021) updated firmware info for WIFI firmware 1.5.7 Ecowitt / 4.2.9 Ambient
(02-Feb-2021) update WS68 signal indicator in console pictogram overview - updated announcement for PM2.5 sensor cycling (1-4) in current position with next firmware version
(30-Jan-2021) added Tycon ProWeather TC3000WC (WH2350 Fnbe Offset clone) to the matrix
(02-Feb-2021) updated WS68 signal indicator position on console screen, announcement by Ecowitt to implement PM2.5 indicator (1-4, WH41/43) cycling with next firmware
(26-Feb-2021) added WH35 Leaf Moisture sensor (1-8) to the matrix - sensor already part of firmware 1.6.5
(27-Feb-2021) created a temporary warning regarding firmware 1.6.5 in the firmware section of the matrix footnotes
(02-Mar-2021) updated firmware 1.6.6 for GW1000 - FW 1.6.5 withdrawn, also for WH2650 => latest available FW for WH2650 is 1.6.3 (1.6.5 for early adopters - WH2650 users were not affected by the 1.6.5 side-effects on the GW1000 together with a WH32B - they have another side effect: loss of pressure/barometer data from WH32B)
(03-Mar-2021) moved firmware info into separate post (as the post is reaching its maximum number of characters [2000]); added picture of device list and console identifiers plus update pop-up
(12-Mar-2021) added information about WH2910C console and sensor data uploaded to Ecowitt.net - info on to-be-released FW 1.6.7
(19-Mar-2021) added information about beta-phase WN1900 "low-cost" weather station
(14-Nov-2020) added Froggit DP70 (=Ecowitt WH55)
(14-Nov-2020) updated sensor hierarchy (footnote 7)
(17-Nov-2020) included Watson as Fine Offset clone seller to footnote d and to the packages
(20-Nov-2020) added acronym scheme (source: Ecowitt)
(21-Nov-2020) updated table: added WS6006/WL6006 and updated footnote 10 on WS6006/WL6006 (source: Ecowitt)
(22-Nov-2020) added Ambient PM2.5 indoor (WH43) and WH31LA (WH55), updated HP3501 sensor compatibility, added Weather Network information
(23-Nov-2020) updated WL6006 info
(24-Nov-2020) added console clone models/brands and their frequencies
(25-Nov-2020) updated HP3501 sensors (with console firmware 1.6.9), added console/screen sizes, added firmware info
(03-Dec-2020) updated WiFi firmware version for Ecowitt and compatible
(07-Dec-2020) added WH31P (Ambient) to the matrix
(10-Dec-2020) added picture of newly released WH45 (release date 10-Dec-2020)
(26-Dec-2020) added picture for HP2551/WS-2000/WS5000 console display overview
(30-Dec-2020) marked WH32E for Ambient as "end-of-life" (exactly "end-of-support" as they have taken it off their portfolio)
(03-Jan-2021) added reference to related discussion thread https://www.wxforum.net/index.php?topic=40837.0
(03-Jan-2021) added remark regarding past 24 h rainfall display of the HP2551 console
(05-Jan-2021) added PanTech as another reseller brand in Australia (HP2551, HP2553 and extra sensors)
(13-Jan-2021) added Froggit DP30 water temperature sensor to the matrix
(17-Jan-2021) added Meteobridge/Weewx/CumulusMX/WeatherDisplay console support info
(22-Jan-2021) updated footnote 9 with the new WN30 (temperature only, waterproof probe, 3 m cable) sensor
(29-Jan-2021) updated firmware info for WIFI firmware 1.5.7 Ecowitt / 4.2.9 Ambient
(02-Feb-2021) update WS68 signal indicator in console pictogram overview - updated announcement for PM2.5 sensor cycling (1-4) in current position with next firmware version
(30-Jan-2021) added Tycon ProWeather TC3000WC (WH2350 Fnbe Offset clone) to the matrix
(02-Feb-2021) updated WS68 signal indicator position on console screen, announcement by Ecowitt to implement PM2.5 indicator (1-4, WH41/43) cycling with next firmware
(26-Feb-2021) added WH35 Leaf Moisture sensor (1-8) to the matrix - sensor already part of firmware 1.6.5
(27-Feb-2021) created a temporary warning regarding firmware 1.6.5 in the firmware section of the matrix footnotes
(02-Mar-2021) updated firmware 1.6.6 for GW1000 - FW 1.6.5 withdrawn, also for WH2650 => latest available FW for WH2650 is 1.6.3 (1.6.5 for early adopters - WH2650 users were not affected by the 1.6.5 side-effects on the GW1000 together with a WH32B - they have another side effect: loss of pressure/barometer data from WH32B)
(03-Mar-2021) moved firmware info into separate post (as the post is reaching its maximum number of characters [2000]); added picture of device list and console identifiers plus update pop-up
(12-Mar-2021) added information about WH2910C console and sensor data uploaded to Ecowitt.net - info on to-be-released FW 1.6.7
(19-Mar-2021) added information about beta-phase WN1900 "low-cost" weather station
↧
↧
Re: Fine Offset Clone Model numbers and related information - discussion thread
added information of the WN1900 low-cost weather station (in beta test phase).
see also https://www.wxforum.net/index.php?topic=41643.0
also added GARNI as a reseller of WH2910 clones.
see also https://www.wxforum.net/index.php?topic=41643.0
also added GARNI as a reseller of WH2910 clones.
↧
Re: ECOWITT WEATHER STATIONS API
Hi Ivan13,
Another upload procedure will probably not help in case of server-side problems at WU. A higher timeout or some more tries could help a bit. But the underlying problem on the WU server side remains of course. So far, however, WU always came back from the problems after a few days, until at some point timeouts or connection errors began to occur again. I do not know that the data is collected by WU (pull). All stations have to send the data there themselves (push).
As an an example:
Every Ecowitt station automatically sends data to WU every 16 seconds (if WU is configured) - this is a considerable amount of traffic that must first be processed on the server side.
But the last 2 weeks WU was very unstable ...
Regards, Oliver
Quote
My question referred to a possible loading mode that could be used in addition to that of WUNDERGROUND to send data to weather networks.do you search for an alternative service (like Weathercloud) or an alternative way to get your data to WU?
Another upload procedure will probably not help in case of server-side problems at WU. A higher timeout or some more tries could help a bit. But the underlying problem on the WU server side remains of course. So far, however, WU always came back from the problems after a few days, until at some point timeouts or connection errors began to occur again. I do not know that the data is collected by WU (pull). All stations have to send the data there themselves (push).
As an an example:
Every Ecowitt station automatically sends data to WU every 16 seconds (if WU is configured) - this is a considerable amount of traffic that must first be processed on the server side.
Quote
I have noticed that WUNDERGROUND is very unreliable for this purpose in the last few days.At least today since 10:00 everything seems to be ok for me with WU. I don't see any packet loss or retry.
But the last 2 weeks WU was very unstable ...
Regards, Oliver
↧
Re: Maplins W/S 1001 clone finally died, Ecowitt 2551?
Thanks for the advice. Ordered a GW1002, a 2551 display and 3 soil sensors a few days ago. Now just got to wait for 4-5 weeks for delivery!
I'm not a very patient sort, I've been reading the manual already!
](http://www.wxforum.net/Smileys/default/eusa_wall.gif)

↧
↧
Re: Maplins W/S 1001 clone finally died, Ecowitt 2551?
Thanks for the advice. Ordered a GW1002, a 2551 display and 3 soil sensors a few days ago. Now just got to wait for 4-5 weeks for delivery!I'm not a very patient sort, I've been reading the manual already!
The wait is the downside for sure!
Hope all goes well
Mine worked straight out of the box
↧
Re: Availability of WS-5000
Ladies and Gentleman, it's back!!!
I got an email 2 days ago on the 18 March 2021, 2:31am NZDT by marketing@ambientweather.com.
"BACK IN STOCK | Ambient Weather WS-5000 is back!" was the title.
"THE WAIT IS OVER!
Due to popular demand, our WS-5000 is back in stock.
Get yours before the sell out again!"
Due to popular demand? Were they going to discontinue this, but due to the fact it was popular they didn't?
Anyway, good that it's back. It seems that it's often out of stock. It's good to be back.![Smile :)]()
[Posting this in 2 places]
https://www.wxforum.net/index.php?topic=38467
https://www.wxforum.net/index.php?topic=38658
I got an email 2 days ago on the 18 March 2021, 2:31am NZDT by marketing@ambientweather.com.
"BACK IN STOCK | Ambient Weather WS-5000 is back!" was the title.
"THE WAIT IS OVER!
Due to popular demand, our WS-5000 is back in stock.
Get yours before the sell out again!"
Due to popular demand? Were they going to discontinue this, but due to the fact it was popular they didn't?
Anyway, good that it's back. It seems that it's often out of stock. It's good to be back.

https://www.wxforum.net/index.php?topic=38467
https://www.wxforum.net/index.php?topic=38658
↧
Re: Availability of WS-5000
No, posting only in one place. Duplicate deleted. No double posts allowed. Pick the best place and only post there.
↧
Re: Expected delivery times at this tme of year
Hi!
That is probably always dependent on the current availability of stock items. Experience has shown that orders with 868MHz can take a little longer. I think my personal maximum waiting time was something of 10 or 12 weeks.
You can always ask Lucy whether something is wrong with your order or if she can give you an approximate delivery date.
Actually, I even know that Lucy herself communicates the current status from time to time.
Just ask there by email.
Oliver
Quote
ANyone any ideas of what has happened before in Feb/Mar when ordering?Depends ...
That is probably always dependent on the current availability of stock items. Experience has shown that orders with 868MHz can take a little longer. I think my personal maximum waiting time was something of 10 or 12 weeks.
You can always ask Lucy whether something is wrong with your order or if she can give you an approximate delivery date.
Actually, I even know that Lucy herself communicates the current status from time to time.
Just ask there by email.
Oliver
↧
↧
Re: Expected delivery times at this tme of year
If you have ordered (a) 868 MHz sensor(s)/console(s), it will usually take longer - because in general Ecowitt don't have 868 MHz models on stock, only 915 and 433 MHz models. That means that the items of each order for 868 MHz need to be produced (and tested) before shipment can start. Once they are shipped, Ecowitt (Lucy) will send you an email. Depending on the shipment it can take between 2 - 14 days (not counting lengthy withhold at customs) - FedEx will take 2 days (but is significantly more expensive and by default only applied to items > 100 USD; you can request FedEx shipping for additional fee for articles which do not fall under the default regulation - see shipping policy at the ecowitt.com web site), normal China post can be 7 days but I've already had 20 days (including customs processing). As the New Chinese Year celebrations are over, there shouldn't be extra delay.
↧
Re: Expected delivery times at this tme of year
I just wondered before I asked Lucy. I'll leave it perhaps another week and then email if I've heard nothing.
Suart
Suart
↧
Re: Expected delivery times at this tme of year
I just wondered before I asked Lucy. I'll leave it perhaps another week and then email if I've heard nothing.Lucy is very accurate and neat in these affairs - once they ship, she sends a mail (Junk/Spam folders to be checked
Suart

Usually she also sends a confirmation mail giving you a rough timeline.
below an excerpt example of such a much:
---------------------
"Thanks for your purchasing.

We have received your payment and will ship your order soon.

Please note that we'll need some time to prepare your order.
We'll ship your order with registered mail and the estimated delivery time will
be 6-7 weeks after the shipment due to the Corona Virus.
If it's acceptable, please confirm your shipping address: ...."
---------------------
or the shipment confirmation:
--------------------
"Good day!
Thanks for your waiting!
We have shipped your order of WH32 and WH31 and here's the tracking number: H101866017681060xxxx(China Post).
Please give some days for the tracking information to be updated.
Please note that the delivery time will be around 3-4 weeks due to the Corona Virus.
Please download the attached manuals.
Any question, please let us know.

Best Regards,
--------------------------
The have special COVID-19 caused order processing processes in place in China including desinfection of items and parcels.
This also takes extra time for the service providers.
↧
Re: WS-2000 error
I'm experiencing another occasional error on my station, seems to depend upon the humidity but I occasionally get a spike in solar radiation/UV index which I imagine is because of dew/moisture/liquid on the sensor and I cant see any way of stopping it happening as the station is in a good open space. Happened this morning around 9am then back to normal within half an hour...haven't lost my medal though!
↧
↧
Re: WS-2000 error
I'm experiencing another occasional error on my station, seems to depend upon the humidity but I occasionally get a spike in solar radiation/UV index which I imagine is because of dew/moisture/liquid on the sensor and I cant see any way of stopping it happening as the station is in a good open space. Happened this morning around 9am then back to normal within half an hour...haven't lost my medal though!I don't think there is much you can do about it.
But, occasionally, it happens to me (my station) that for a few seconds the clouds open and the sun shines fully through - and it produces a spike.
That would then be correct, wouldn't it ?
You would need to exclude such a situation, maybe with a webcam which covers your station and the sky above ...
In my cases it relates to the videos my camera records.
But an overreaction of the sensor due to dew drops/rain drops cannot be out-ruled completely either, I'd say.
so maybe not a single cause scenario, but a possible multi cause scenario...
↧
Re: WS-2000 error
Hi G.Brown
How big of a spike to you get (numbers, from what to what)? The fact that it falls back to me points to a normal behavior and an actual condition.
I get them occasionally as well, and more evidenced from my solar array, with high humidity you may get a refractory effect. In addition, if you actually have droplets forming on the sensor , they act as convex lenses.
How big of a spike to you get (numbers, from what to what)? The fact that it falls back to me points to a normal behavior and an actual condition.
I get them occasionally as well, and more evidenced from my solar array, with high humidity you may get a refractory effect. In addition, if you actually have droplets forming on the sensor , they act as convex lenses.
↧
Re: WS-2000 error
↧
Re: WS-2000 error
Hmm that is interesting. Much more of a spike than I would expect. Your spike is near or even above full scale , about 10:30AM right?
OK that is a puzzle. You can get such things from cloud edge effect, but usually that is at high sun time, which you are not at.
Your watts/m² numbers are not even believable under full sun. If you actually get that, buy a lot of solar panels, no, this is some effect or malfunctioning sensor.
for reference, mine https://www.wunderground.com/dashboard/pws/KVANORFO42?cm_ven=localwx_pwsdash
OK that is a puzzle. You can get such things from cloud edge effect, but usually that is at high sun time, which you are not at.
Your watts/m² numbers are not even believable under full sun. If you actually get that, buy a lot of solar panels, no, this is some effect or malfunctioning sensor.
for reference, mine https://www.wunderground.com/dashboard/pws/KVANORFO42?cm_ven=localwx_pwsdash
↧
↧
Re: WS-2000 error
had a look around local stations for a similar effect and found oneand one more
https://www.wunderground.com/dashboard/pws/IGUISB1
https://www.wunderground.com/dashboard/pws/IWHITB20
but most stations near to you don't seem to report solar radiation
So must have some external reason - unlikely that three stations go nuts at the same time
↧
Re: FOSHKplugin - brief introduction
Hi!
Of course you could fill in the last lightning if known to you.
Just insert the last distance and time in the config file under [Status]
You could have a look into your logfiles of last occurance and use these values.
All services supplied by FOSHKplugin then receive this lightning data.
Until the next lightning - that one (and all following) will be saved there automatically through FOSHKplugin.
Regards, Oliver
Quote
Hope that the next lightning event will be stored/buffered by the plugin...It will.
Of course you could fill in the last lightning if known to you.
Just insert the last distance and time in the config file under [Status]
Code: [Select]
[Status]
last_lightning = 20
last_lightning_time = 1615479869
last_lightning is the distance in km and last_lightning_time is the corresponding time stamp as unixdate.You could have a look into your logfiles of last occurance and use these values.
All services supplied by FOSHKplugin then receive this lightning data.
Until the next lightning - that one (and all following) will be saved there automatically through FOSHKplugin.
Regards, Oliver
↧
Re: WS-2000 error
Yeah, and running easyweather , interesting.
Yeah I don't have an answer unless your solar noon (peak) is around 10:30AM, and even then , the numbers are way to high. I looked at your week data , and it tails off after the spikes like it's not reporting your normal high sun time (may have read it wrong) , but that is how it looked to me.
Any chance you have a time zone issue on the console , or WU?
Yeah I don't have an answer unless your solar noon (peak) is around 10:30AM, and even then , the numbers are way to high. I looked at your week data , and it tails off after the spikes like it's not reporting your normal high sun time (may have read it wrong) , but that is how it looked to me.
Any chance you have a time zone issue on the console , or WU?
↧