WXforum.net
Weather Station Hardware => Ambient Weather and Ecowitt and other Fine Offset clones => Topic started by: Gyvate on November 20, 2020, 05:35:38 AM
-
Hi everyone,
the Fine Offset clone model overview has been updated, some more useful info added.
See the change log at the end of the thread
it's worth passing by every now and then 8-)
have a look :-)
https://www.wxforum.net/index.php?topic=40730.0
-
This is an excellent tool. Thank you for all your work.
One quick question: Is there a reason that Ambient's clone of the WH2650 Wifi, the ObserverIP, is not listed?
-
as far as I know, the Ambient ObserverIP is still the old, LAN based version which FineOffset also had in their portfolio.
That doesn't have the functionality of the of new WiFi version (Fine Offset WH2650, Froggit WH2600Pro).
This is also mentioned on the page in the respective footnote.
I guess you mean the WS-1550-IP (earlier WS-1400IP)
[ You are not allowed to view attachments ]
https://ambientweather.com/amws1500.html
I didn't see the WiFi version at their web site. The term "wireless" refers here to the transmission between sensor and console and not to the communication of the console with the local network.
In the WiFi version, the LAN outlet is closed/covered and the LEDs on the front are differently labelled (Link old, WiFi new).
[ You are not allowed to view attachments ]
-
further update on table and footnotes - 21-Nov-2020
-
Yes, what Gyvate said 100% true. The Ambient ObserverIP is not the same as the WH2650. Ethernet vs WiFi. But most importantly the firmware is completely different. The new WiFi version uses the same firmware as the GW1000, whereas the ObserverIP version will not show live data on the WS View app. This is because the ObserverIP version (Ethernet) uses the embedded webserver pages to configure and to see the live data. It isn't just because of it being Ambient firmware, as the same is true for the Aercus version of the ObserverIP which I believe they call a WeatherLogger.
The two may look the same at first glance...but when you inspect the LED lights which are named differently and you notice no Ethernet port on the back of the WH2650 you start to realize it is a different device altogether.
-
Yes,
Thank you Gyvate for the great work on this new version of model/part chart.
-
HP3500/HP3501 can not receive multiple sensors (like WH31)?
-
@droiddk
with firmware > 1.6.2 it can receive several more extra sensors, but not all.
see updated matrix.
It can receive WS68, WS80, WH40, 1-8 WH31/WH31-EP, 1-4 WH41, 1-8 WH51, 1 WH57, 1 WH32.
It cannot receive WS80, WH45, WN34, WH55.
-
In the WiFi version, the LAN outlet is closed/covered and the LEDs on the front are differently labelled (Link old, WiFi new).
I wasn't aware of that. Thanks for the clarification.
-
The AW list needs updating.
https://ambientweather.com/amwepmpmwiin.html
Ambient Weather PM25IN PM2.5 Wireless Indoor Particulate Monitor for OBSERVERIP, WS-2000 and WS-5000
https://ambientweather.com/amwh31la.html
Ambient Weather WH31LA Leak Detector for Models WS-2000, WS-5000 Weather Stations
https://ambientweather.com/amwh31p.html
Ambient Weather WH31P Water Proof Probe Sensor for WS-0265, WS-1550-IP, WS-2000, WS-3000, WS-5000 and ObserverIP Series Weather Stations
-
Thanks for the hint.
These buggers had these sensors in a different section ... :roll:
matrix updated
-
:!: HP3500/HP3501 works with WH32.
-
:!: HP3500/HP3501 works with WH32.
correct - it's not explicitly mentioned but you can tell from the picture - will update the matrix accordingly
[ You are not allowed to view attachments ]
-
added Weather Network support by the consoles to the table/matrix
-
added a few more rebranded consoles, mainly from European resellers and updated the Weather Network info
see change log https://www.wxforum.net/index.php?topic=40730.msg419166#msg419166
-
One more discovery: HP3500/3501 supports up to four WH55.
Regards
-
correct - since firmware 1.6.9 - in the manual it still says "pending".
But I've updated the matrix.
-
also added console sizes - screen diagonal or device size where displayless
so people can have a better idea what these pieces look like in real life
This info is often missing in the manuals.
Also added information pertaining to latest firmware versions
-
Hi Everyone,
I know that the related thread "Fine Offset Clone Model numbers, compatibility matrix and other useful info" risks to become what we call in Germany a 'honey-sweating, egg-laying, wool-milk-pig' (in plain English probably a Swiss army knife or a jack of all trades device) ...
still having certain important information at a central place can be very helpful and can make our weather enthusiast life easier and provide orientation.
So if you feel that something is missing, some information is not correct or incomplete, feel free to post in this thread (as some of you already did before).
And there is a good chance that the missing or suggested information will find its way into the "Fine Offset Clone Model numbers, compatibility matrix and other useful info" thread.
We have chosen this approach to have the main information thread locked in order to remain clearly arranged while related discussions can be held here. :grin: 8-).
-
WiFi firmware update to V1.5.6 was updated in the firmware section.
-
added Ambient WH31P (P=pool; waterproof water sensor) to the matrix.
It's part of the WH31 multi-channel family, so far only available through Ambient in the 915 MHz version.
Can be received by an Ecowitt console [see matrix, @915 MHz].
-
added picture of newly released WH45 CO2, PM2.5, PM10, Temperature/Humidity (indoor) sensor
-
As there have been many related questions coming up in recent posts, I have enriched the post by an overview of the HP2551/HP2553/HP1000SEPro (Froggit) console display in a "real-life" picture. You have to scroll down, Between Matrix and change log.
https://www.wxforum.net/index.php?topic=40730.msg420959#msg420959
Merry Christmas and a Happy, Healthy and Safe 2021
-
Temp/Humidity outdoor sensor - WS-2000 - Ambient WH32E is now discontinued per Ambient support.
Think the reference to WH32F was in error.
-
Temp/Humidity outdoor sensor - WS-2000 - Ambient WH32E is now discontinued per Ambient support.
Think the reference to WH32F was in error.
Correct, the "F" should have been an "E", maybe an Early indicator of End-of-live ? :-P
will change that and add the eol remark.
Strange that they took that sensor off their portfolio - it's in no way outdated and you still get it from Ecowitt etc. (but won't work with Ambient consoles, the old proprietary story).
They only have the WH31 multi-channel available now, which is not a full replacement of a WH32, as only the WH32 will be recognized by the consoles as outdoor temperature/humidity sensor (even over all other outdoor T/H sensors like WH65, WS678 and WS80 (Ecowitt terms)).
Possibly just a marketing decision as there may have not been a sufficient number of customers interested in it. Whatever ...
And, by the way, it's not only WS-2000, it's WS-5000 too (just for completeness).
It (the WH32 T/H outdoor sensor) doesn't usually come with either of them (WS-2000 has a T/H sensor in the WH65, WS-5000 in the WS80).
Afaik it had been offered before as optional sensor, but, end of life as it seems ...
Interestingly on Ambient's web page, the sensor description for the WS-2000 is more explicit than the more modern design used for the WS-5000, even though the console is the same for both products. One more reason for the existence of our table. ;) 8-)
-
I suppose that Ambient feels that the WH32E is redundant as the WS80 and WH65 already have outdoor temperature / humidity. But if you want stand alone and a better thermometer placement than either of these stations provide then without the WH32E you don't get the option.
With Ambient though the situation is more difficult than with other Fine Offset resellers. Because with Froggit for example if they don't carry a sensor then you can always order it from Ecowitt. But with Ambient you don't get the option because it won't work with Ambient consoles. I really wished that Ambient would reconsider locking their consoles to not work with Ecowitt sensors.
-
I really wished that Ambient would reconsider locking their consoles to not work with Ecowitt sensors.
Yep me too. Other than Ambient net and customer service they really don't have much to offer, at least for me.
Ambient sensors are also more expensive than Ecowitt's. Thanks to Ambient , I'll just have to bite the bullet and add some Ecowitt products to my weather station line up.
-
The rebranded fine offset devices in Australia are branded as 'Pantech'. These are the generic Ecowitt devices as we have to download firmware updates from the ecowitt web site and I've got a few Ecowitt branded sensors off Amazon that working alongside as and look identical to the Pantech ones. Therefore, could someone please add "Pantech' to the list of 'other' fine offset clones?
-
The rebranded fine offset devices in Australia are branded as 'Pantech'. These are the generic Ecowitt devices as we have to download firmware updates from the ecowitt web site and I've got a few Ecowitt branded sensors off Amazon that working alongside as and look identical to the Pantech ones. Therefore, could someone please add "Pantech' to the list of 'other' fine offset clones?
OK - added - they seem to be the only ones in Australia together with Misol (at 433 MHz).
And of course Ecowitt at amazon.com.au .
Ambient also offers their 915 MHz sensors which seem to be also legal in Australia as their transmission wattage is sufficiently low.
Looks like the band from 915-928 MHz can be used in Australia if the maximum Equivalent Radiated Isotropic Power (EIRP) is not bigger than 1 Watt.
https://www.wirelesstech.com.au/index.php?route=extension/extension/blog/article&article_id=16
The thing is, you need the same frequency for a sensor / console combination.
-
.
.
.
Interestingly on Ambient's web page, the sensor description for the WS-2000 is more explicit than the more modern design used for the WS-5000, even though the console is the same for both products. One more reason for the existence of our table. ;) 8-)
While the consoles for the WS-2000 and the WS-5000 may be physically the same, Ambient Weather does have different SKU #'s for them, namely:
Ambient Weather WS-2000-CONSOLE Console Only, Compatible with WS-2000, WS-1900, WS-2902 Series
$173.99 Availability: Out of stock SKU#: WS-2000-CONSOLE-AC
Ambient Weather WS-5000-CONSOLE Console Only
$173.99 Availability: In stock SKU#: WS-5000-CONSOLE-AC
What's the difference? Certainly setting themselves up for some kind of product differentiation.
-
.
.
.
Interestingly on Ambient's web page, the sensor description for the WS-2000 is more explicit than the more modern design used for the WS-5000, even though the console is the same for both products. One more reason for the existence of our table. ;) 8-)
While the consoles for the WS-2000 and the WS-5000 may be physically the same, Ambient Weather does have different SKU #'s for them, namely:
Ambient Weather WS-2000-CONSOLE Console Only, Compatible with WS-2000, WS-1900, WS-2902 Series
$173.99 Availability: Out of stock SKU#: WS-2000-CONSOLE-AC
Ambient Weather WS-5000-CONSOLE Console Only
$173.99 Availability: In stock SKU#: WS-5000-CONSOLE-AC
What's the difference? Certainly setting themselves up for some kind of product differentiation.
As far as I know there is no technical or functional difference - it's the same console.
SKU numbers (stock keeping unit) are internal company "qualifiers" which serve different purposes, but do not have necessarily anything to do with the functionality.
WS-2000 and WS-5000 are in my observation product names, not item names. They describe the console plus sensor (array)s from a sales (and/or warehouse) perspective.
Ecowitt does the same or something similar.
While you can buy the HP2551 (HP2551-console + WH65 array) or the HP2553 (HP2551-C + WS80 + WH40), the console for it remains the same.
If you want to buy a second or replacement console, you buy the HP2551-C (=HP2551 console). They are technically and functionally interchangeable.
Here they are straightforward.
Whereas with Ambient, their system can lead to confusion. :roll: :shock:
The use of different SKUs for the same item than leads to such curiosities/oddities that SKU 1 can be out of stock while SKU 2 is on stock.
But unless they glue a sticker with the SKU number on it, you cannot tell one from the other. It's like a role play. The same actor wears a different hat.
It's sort of a re-branding within the brand ... :roll:
-
Added the newly released Froggit DP30 water temperature sensor to our matrix where it joins the Ambient WH31P (P like pool) water temperature sensor.
-
added application software support info for consoles by Meteobridge, Weewx, WeatherDisplay and CumulusMX to the matrix
edit was also adding Weather Display
-
New WIFI firmware available
[WL6006]
VER = 1.0.18
ULR = http://download.ecowitt.net/down/filewave?n=WL6006&v=WL6006_Ver1.0.18.hex
DATE = 20200902
SIZE = 121699
NOTES = New Firmware WL6006_Ver1.0.18;1.Use NTP network time synchronization.
[EasyWeather]
VER = EasyWeatherV1.5.7
URL1 = http://download.ecowitt.net/down/filewave?n=EasyWeather_user1&v=user1_ew_157.bin
URL2 = http://download.ecowitt.net/down/filewave?n=EasyWeather_user2&v=user2_ew_157.bin
DATE =
NOTES = New Firmware EasyWeatherV1.5.7;1. Support leaf humidity data uploading.;2. Fixed some bugs with user-customized uploads.;3. Fixed some sensor battery power upload bug.
[AMBWeather]
VER = AMBWeatherV4.2.9
URL1 = http://download.ecowitt.net/down/filewave?n=AMBWeather_user1&v=user1_amb_429.bin
URL2 = http://download.ecowitt.net/down/filewave?n=AMBWeather_user2&v=user2_amb_429.bin
DATE =
NOTES = New Firmware AMBWeatherV4.2.9;1. Fixed some bugs with user-customized uploads.;2. Fixed some sensor battery power upload bug.
Will offer to download and install automatically if you choose your device on the device list
The strange thing is that on top of the WSView app screen, the EasyWeather-WFIxxx V1.5.6 is NOT updated to V1.5.7 - only in the bottom right corner it says EasyWeather V1.5.7 after the update.
Correction - it does show 8-) - but it's sort of a 2 step update
-
added the still to-be-released WH35 Leaf Moisture sensor series (1-8 WH35 type sensors possible per console) to the matrix
The WH35 sensor is already integrated into the latest firmware 1.6.5
You can find it in the sensors entries in the WSView app sensor ID section paging down completely.
[ You are not allowed to view attachments ]
-
created a warning in the firmware section regarding a bug in new firmware 1.6.5
https://www.wxforum.net/index.php?topic=41588.0
-
new updated firmware 1.6.6 for GW1000 released - FW 1.6.5 withdrawn, also for WH2650 => latest available FW for WH2650 is 1.6.3 (or 1.6.5 for early adopters who already updated to 1.6.5 while it was still available -
WH2650 users were not affected by the 1.6.5 side-effects on the GW1000 together with a WH32B).
EDIT after discovery of new WH2650 related bug.
See next post.
-
latest available FW for WH2650 is 1.6.3 (1.6.5 for early adopters)
The WH2650 users were not affected by the 1.6.5 side-effects on the GW1000 together with a WH32B.
However, they have another side effect: loss of pressure/barometer data from WH32B.
A WH2650 on FW 1.6.5 doesn't show the pressure from the WH32B anymore.
Error communicated to Ecowitt.
-
updated information on WH2910C console and extra sensors
preview on soon to-be-released FW 1.6.7 for both GW1000/WH2650.
There had been issues observed with WH2650 on FW 1.6.5/1.6.6 when a WH45 5-in-1 CO2, PM2.5, PM10, T&H combo sensor was also active.
Those are solved with FW 1.6.7
-
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.
-
Ecowitt published / released new HP 2551 console firmware: V 1.7.1
download and installation instructions --> https://www.wxforum.net/index.php?topic=41770.0
firmware section updated accordingly
-
The Ecowitt WH2320 console, sold with the Froggit WH4000SE , reports itself as WS2350 in custom upload:
[stationtype] => EasyWeatherV1.5.7
[freq] => 868M
[model] => WS2350_V2.37
It also reports different items
missing: hourlyrainin and maxdailygust
new?: rainratein
Does anyone already compiled a list fo used data-fields in the custom uploads?
My excel-sheet is already over a year old.
Wim
-
The Ecowitt WH2320 console, sold with the Froggit WH4000SE , reports itself as WS2350 in custom upload:
[stationtype] => EasyWeatherV1.5.7
[freq] => 868M
[model] => WS2350_V2.37
It also reports different items
missing: hourlyrainin and maxdailygust
new?: rainratein
Does anyone already compiled a list fo used data-fields in the custom uploads?
My excel-sheet is already over a year old.
Wim
the customized server sends the following data for a WH4000SE/WH2320E on WiFi firmware V1.5.7 (WS2350 is the FO product name following the Ecowitt naming convention - WS [weather station] instead of WH (weather Hub) with a solar panel [at the outdoor sensor array]):
2021-03-28 18:07:18 CEST (1616947638) altimeter: 30.29913726985207, appTemp: 57.4605929342937, barometer: 30.29264012233571, cloudbase: 6644.228116534675, dateTime: 1616947638, dewpoint: 35.508451204169894, heatindex: 58.193, humidex: 60.6, inDewpoint: 48.84513896384446, inHumidity: 40.0, inTemp: 74.8, maxSolarRad: None, outHumidity: 39.0, outTemp: 60.6, pressure: 29.282, radiation: 222.53, rain: None, rainRate: 0.0, usUnits: 1, UV: 2.0, windchill: 60.6, windDir: 313.0, windGust: 1.1, windSpeed: 0.2
units are imperial
EDITED: see later post for proper data
-
Hi Rainer,
I don't believe this.
Are these key names really the outgoing names in Ecowitt protocol?
For me it looks like weewx vars (after some calculation).
Regards, Oliver
-
the customized server sends the following data for a WH4000SE/WH2320E on WiFi firmware V1.5.7 (WS2350 is the FO product name following the Ecowitt naming convention - WS [weather station] instead of WH (weather Hub) with a solar panel [at the outdoor sensor array]):
2021-03-28 18:07:18 CEST (1616947638) altimeter: 30.29913726985207, appTemp: 57.4605929342937, barometer: 30.29264012233571, cloudbase: 6644.228116534675, dateTime: 1616947638, dewpoint: 35.508451204169894, heatindex: 58.193, humidex: 60.6, inDewpoint: 48.84513896384446, inHumidity: 40.0, inTemp: 74.8, maxSolarRad: None, outHumidity: 39.0, outTemp: 60.6, pressure: 29.282, radiation: 222.53, rain: None, rainRate: 0.0, usUnits: 1, UV: 2.0, windchill: 60.6, windDir: 313.0, windGust: 1.1, windSpeed: 0.2
units are imperial
This is what I get from custom upload (not the API), excluding the "PASSKEY"
[stationtype] => EasyWeatherV1.5.7
[dateutc] => 2021-03-28 11:24:10
[tempinf] => 66.0
[humidityin] => 62
[baromrelin] => 30.269
[baromabsin] => 30.145
[tempf] => 66.9
[humidity] => 60
[winddir] => 354
[windspeedmph] => 2.7
[windgustmph] => 4.5
[rainratein] => 0.000
[eventrainin] => 0.000
[dailyrainin] => 0.000
[weeklyrainin] => 0.000
[monthlyrainin] => 0.878
[yearlyrainin] => 7.020
[totalrainin] => 7.020
[solarradiation] => 624.16
[uv] => 6
[wh65batt] => 0
[freq] => 868M
[model] => WS2350_V2.37
Wim
-
This is the json file that's saved by meteotemplate's ecowitt plugin ( by raffaello di martino ), wh2650 ( stock weldbeck halley and e few other sensors )
{"PASSKEY":"xxxx","stationtype":"WH2650A_V1.6.3","dateutc":"2021-03-28 16:42:33","tempinf":"76.1","humidityin":"52","baromrelin":"30.345","baromabsin":"30.286","tempf":"57.4","humidity":"83","winddir":"116","windspeedmph":"2.68","windgustmph":"4.47","maxdailygust":"11.41","solarradiation":"51.14","uv":"0","rainratein":"0.000","eventrainin":"0.000","hourlyrainin":"0.000","dailyrainin":"0.000","weeklyrainin":"0.000","monthlyrainin":"0.689","yearlyrainin":"4.110","totalrainin":"4.110","temp1f":"71.24","humidity1":"50","soilmoisture1":"82","soilmoisture2":"0","wh65batt":"0","wh25batt":"0","batt1":"0","soilbatt1":"1.5","soilbatt2":"1.3","freq":"868M","model":"WH2650"}
-
Hi Rainer,
I don't believe this.
Are these key names really the outgoing names in Ecowitt protocol?
For me it looks like weewx vars (after some calculation).
Regards, Oliver
Sorry, wrong copy and paste - here are the correct ones
raw data:
PASSKEY=XXXX
stationtype=EasyWeatherV1.5.7
dateutc=2021-03-28+17:34:48
tempinf=75.0
humidityin=41
baromrelin=30.316
baromabsin=29.457
tempf=57.4
humidity=43
winddir=339
windspeedmph=0.4
windgustmph=1.1
rainratein=0.000
eventrainin=0.000
dailyrainin=0.000
weeklyrainin=0.000
monthlyrainin=2.961
yearlyrainin=13.441
totalrainin=80.827
solarradiation=12.11
uv=0
wh65batt=0
freq=868M
model=WS2350
And I don't think that anything is going to change with this model.
The console is limited to the sensors of the WH65 - and I doubt that firmware is going to change that.
The best I can think of is that its Customized server function would also allow to pass on certain extra sensors as it is done with the HP350x consoles.
I guess the development effort is too much (expensive) given there is a GW1000/WH2650 available for a low price.
-
added some more WN1900 info. The outdoor sensor array (5-in-1) used by it: WN67
-
Today, 07-Apr-2021, Ecowitt issued an update to their EasyWeather WiFi firmware used in the consoles WH2320E, WH290x, HP350x and HP2551.
Upgraded version is V1.5.8 claiming to solve the following issues: 1. Optimize domain name resolution.;2. Optimize the uploading stability of custom servers,
the firmware section of the main post was updated.
-
Added info regarding the HP2551 console - pictogram and footnotes/explanation
-
Ecowitt added the WN30 multi-channel waterproof temperature sensor with external probe to their portfolio.
It shares the max number of channels with the WH31 multi-channel T/H sensor family. Now WH31, WH31-EP and WN30.
The 433 MHz version is on stock - 868 MHz and 915 MHz on request - 4-5 weeks production delay after order. Price 17 USD.
It was already sold for a couple of month (today 30-Apr-2021) by resellers (Froggit DP30, 868 MHz, 25 EUR and Ambient WH31P, 915 MHz, 25 USD).
It's a temperature only sensor (humidity under water doesn't make much sense; maybe it does if used in a freezer, but this is not the targeted use scenario),
therefore on the ecowitt.com page listed under Thermometers.
WN30 now also added to the compatibility matrix.
-
Is there a 'complete' list of fields used in the custom uploads? ( an extension of what Oliver asked a few post ago )
I'm particularly interested in the fields uploaded by pm sensors (WH41, WH43, WH45), leaf wettness ( WH35), soil temperature (WN34).
Another question, do the new WN30 report temperature as WH31 do?
-
The Custom Server uploaded sensor values (Ecowitt protocol) are the same which are uploaded to ecowitt.net (i.e. all what is uploaded from your sensor "fleet" is what you see on the ecowitt.net interface - sensor values and battery status of the sensors you have).
It also depends on who does the upload - different consoles have their own sometimes limited set of sensors and sensor related data.
As for the GW1000/WH2650 console, there is a field map for the weather application software weewx which shows all available fields for sensor values (provided the respective sensor is active) of the GW1000 console known today.
https://github.com/gjr80/weewx-gw1000/wiki/Field-map
I speculate that the WN34S are the first set of eight sensors and the WN34L the second set of eight sensors of the 16 soil temperature sensors (S=soil, L=liquid).
Even though the weewx field map shows what the GW1000 provides when being polled, it should be the same content as what is pushed via the custom server functionality.
The sorting of this field map is weewx name ascending by character (while the sorting of the customer server string is different - see below).
Probably the HP2551 console sends the same amount data. GW1000/WH2650 and HP2551 cover the whole sensor portfolio of Ecowitt.
For my sensor "fleet" (see signature) the custom server posting of my GW1000 looks like below:
(s: string variable, #=field length => s:4 = string with field length 4; sequence is: field name, field content, definition is: field length, field value)
e.g. the field name station type is 11 characters long and the field content is "stationname"; its corresponding value is 14 characters long and the field content is "GW1000A_V1.6.6"
a:74:
{s:11:"stationtype";
s:14:"GW1000A_V1.6.6";
s:7:"dateutc";
s:19:"2021-05-01 22:03:14";
s:7:"tempinf";
s:4:"71.4";
s:10:"humidityin";
s:2:"39";
s:10:"baromrelin";
s:6:"29.940";
s:10:"baromabsin";
s:6:"28.907";
s:5:"tempf";
s:4:"49.5";
s:8:"humidity";
s:2:"51";
s:7:"winddir";
s:3:"180";
s:12:"windspeedmph";
s:4:"0.00";
s:11:"windgustmph";
s:4:"1.12";
s:12:"maxdailygust";
s:4:"1.12";
s:14:"solarradiation";
s:4:"0.00";
s:2:"uv";
s:1:"0";
s:10:"rainratein";
s:5:"0.000";
s:11:"eventrainin";
s:5:"0.000";
s:12:"hourlyrainin";
s:5:"0.000";
s:11:"dailyrainin";
s:5:"0.000";
s:12:"weeklyrainin";
s:5:"0.000";
s:13:"monthlyrainin";
s:5:"0.000";
s:12:"yearlyrainin";
s:6:"15.118";
s:11:"totalrainin";
s:6:"15.118";
s:6:"temp1f";
s:5:"49.28";
s:9:"humidity1";
s:2:"51";
s:6:"temp2f";
s:5:"50.90";
s:9:"humidity2";
s:2:"56";
s:6:"temp3f";
s:5:"49.10";
s:9:"humidity3";
s:2:"51";
s:6:"temp4f";
s:5:"50.00";
s:9:"humidity4";
s:2:"50";
s:6:"temp5f";
s:6:"-11.38";
s:6:"temp6f";
s:5:"50.18";
s:9:"humidity6";
s:2:"48";
s:6:"temp7f";
s:5:"43.88";
s:9:"humidity7";
s:2:"51";
s:13:"soilmoisture1";
s:2:"42";
s:13:"soilmoisture2";
s:2:"72";
s:13:"soilmoisture4";
s:2:"64";
s:13:"soilmoisture5";
s:2:"41";
s:8:"pm25_ch1";
s:4:"11.0";
s:16:"pm25_avg_24h_ch1";
s:4:"12.4";s:8:"pm25_ch2";
s:4:"15.0";
s:16:"pm25_avg_24h_ch2";
s:4:"13.2";
s:6:"tf_co2";
s:4:"70.7";
s:8:"humi_co2";
s:2:"41";
s:8:"pm25_co2";
s:3:"7.4";
s:12:"pm25_24h_co2";
s:3:"7.5";
s:8:"pm10_co2";
s:3:"7.9";
s:12:"pm10_24h_co2"
;s:3:"7.9";
s:3:"co2";
s:3:"939";
s:7:"co2_24h";
s:3:"863";
s:14:"lightning_time";
s:10:"1619689115";
s:13:"lightning_num";
s:1:"0";
s:9:"lightning";
s:2:"14";
s:8:"wh65batt";
s:1:"0";
s:8:"wh80batt";
s:4:"3.04";
s:8:"wh26batt";
s:1:"0";
s:5:"batt1";
s:1:"0";
s:5:"batt2";
s:1:"0";
s:5:"batt3";
s:1:"0";
s:5:"batt4";
s:1:"0";
s:5:"batt5";
s:1:"0";
s:5:"batt6";
s:1:"0";
s:5:"batt7";
s:1:"0";
s:9:"soilbatt1";
s:3:"1.6";
s:9:"soilbatt2";
s:3:"1.4";
s:9:"soilbatt4";
s:3:"1.6";
s:9:"soilbatt5";
s:3:"1.4";
s:9:"pm25batt1";
s:1:"5";
s:9:"pm25batt2";
s:1:"5";
s:8:"wh57batt";
s:1:"4";
s:8:"co2_batt";
s:1:"6";
s:4:"freq";
s:4:"868M";
s:5:"model";
s:10:"GW1000_Pro";}
-
Thank you for the prompt reply.
1) your sensor report is super useful ( as it includes lots of sensors )
2) the weewx reference is super complete... but don't think is super 'useful' ( but certainly a good starting point ).
What I mean is that the weewx second column ( the gw1000 field name column ) reports several 'well-known' field name differently, ex:
dateutc reported as datetime
baromabsin reported absbarometer
pm25_ch1 reported as pm251
...
Maybe because these are the fields retrieved by the weewx driver via the api... and the api field names are different from the 'ecowitt protocol' field names ( only an hypothesis, but, if this is true, not a good idea on the ecowitt part... at least to let my life easier ; - )
P.S.
Checked also the weewx interceptor driver... but is has a very limited sensor definition
-
...
Maybe because these are the fields retrieved by the weewx driver via the api... and the api field names are different from the 'ecowitt protocol' field names ( only an hypothesis, but, if this is true, not a good idea on the ecowitt part... at least to let my life easier ; - )
correct - that's the interface description (or record definition in some programming language jargon) into which the GW1000 data are loaded before further processing by weewx
P.S.
Checked also the weewx interceptor driver... but is has a very limited sensor definition
the interceptor driver reads what is sent by the console via the custom server option - if you want to receive the console data via the interceptor driver, you will have to define a sensor_map in weewx if you have more than the "classical" sensors you want to process in weewx;
for the GW1000 the weewx GW1000 API driver is much more elegant, encompasses all sensors the GW10000 can receive and process and is less problematic (and your console custom server option remains free for other purposes you might have).
If you have, e.g. only a HP2551, WS2320E or HP350x console, and want to process their data in weewx, you are stuck with the interceptor driver (unless you get yourself an extra GW1000).
-
I need the list of fields uploaded by the custom ecowitt protocol to update the ecowitt plugin of meteotemplate ( plugin by raffaello dimartino ).
This is the partial list so far ( # is the sensor number, replace with 1-4, 1-8, 1-16?? ):
ecowitt field meteotemplate field
------------- --------------------
freq
model
stationtype
PASSKEY
runtime // only ws1900
dateutc
// T/H/P
tempinf TIN
humidityin HIN
baromrelin P
baromabsin
tempf T
humidity H
feelslikef
windChillf
dewptf
heatindexf
// wind
winddir B
windspeedmph W
windgustmph G
maxdailygust
// light
solarradiation S
uv UV
// rain
rainratein RR
eventrainin
hourlyrainin
dailyrainin R
weeklyrainin
monthlyrainin
yearlyrainin
totalrainin
// wh31-WN30
temp#f T#
humidity# H#
// WN34 soil/water temperature
tf__ch# TS#
// wn35 leaf wettness
leafwettness_ch# LW#
//wh41-43
pm25_ch# PP#
pm25_avg_24h_ch#
// wh45
tf_co2
humi_co2
pm25_co2
pm25_24h_co2
pm10_co2
pm10_24h_co2
co2 CO2_1
co2_24h
// wh51
soilmoisture# SM#
// wh55
leak_ch#
// wh57
lightning_time LT
lightning_num L
lightning LD
// battery status
wh25batt WH25BAT ( 0 = OK; 1 = LOW )
wh26batt WH26BAT ( 0 = OK; 1 = LOW )
wh40batt RBAT NOTE: wh40 does not report battery level ( or only newer ones report battery level ?! )
wh65batt WH65BAT ( 0 = OK; 1 = LOW )
wh68batt WH68BAT ( value: 1.5V battery voltage )
wh80batt WH80BAT ( value: 3V battery voltage )
ws1900batt WS1900BAT ( value 3V battery voltage )
// wh31-WN30
batt# T#BAT ( 0 = OK; 1 = LOW )
// wn34
tf_batt# TS#BAT ( where # = 1..8; value: 1.5V battery voltage )
// wn35
leaf_batt# LW#BAT ( where # = 1..8; value: 1.5V battery voltage )
// wh41-43
pm25batt# PP#BAT ( where # = 1..4; value: 0-5; 0-1 = LOW )
// wh45
co2_batt CO2_1BAT ( value: 0-7; 0-1 = LOW )
// wh51
soilbatt# SM#BAT ( where # = 1..8; value: 1.5V battery voltage )
// wh55
leakbatt#
wh57batt LBAT ( value: 0-5; 0-1 = LOW )
-
...
Maybe because these are the fields retrieved by the weewx driver via the api... and the api field names are different from the 'ecowitt protocol' field names ( only an hypothesis, but, if this is true, not a good idea on the ecowitt part... at least to let my life easier ; - )
correct - that's the interface description (or record definition in some programming language jargon) into which the GW1000 data are loaded before further processing by weewx
Just to be clear, the GW1000 API does not define any field names; rather it specifies what data is available via what API call and how to decode it. The GW1000 driver field names are used internally by the GW1000 driver and deliberately bear no resemblance to those fields used in the Ecowitt upload protocol. The only time these internal driver fields will be visible from outside the driver will be if the field mapping (ie the map from internal driver fields to WeeWX loop packet fields) is such that the internal field name is passed on. This does occur for a number of fields under the driver default field mapping. Again this was a deliberate decision. I don't see any of this as a fault either by Ecowitt or the GW1000 driver.
At best the GW1000 driver default field map gives an indication of what data may be available via the Ecowitt upload protocol but it provides little else regards the Ecowitt upload protocol.
Gary
-
...
Maybe because these are the fields retrieved by the weewx driver via the api... and the api field names are different from the 'ecowitt protocol' field names ( only an hypothesis, but, if this is true, not a good idea on the ecowitt part... at least to let my life easier ; - )
correct - that's the interface description (or record definition in some programming language jargon) into which the GW1000 data are loaded before further processing by weewx
Just to be clear, the GW1000 API does not define any field names; rather it specifies what data is available via what API call and how to decode it. The GW1000 driver field names are used internally by the GW1000 driver and deliberately bear no resemblance to those fields used in the Ecowitt upload protocol. The only time these internal driver fields will be visible from outside the driver will be if the field mapping (ie the map from internal driver fields to WeeWX loop packet fields) is such that the internal field name is passed on. This does occur for a number of fields under the driver default field mapping. Again this was a deliberate decision. I don't see any of this as a fault either by Ecowitt or the GW1000 driver.
At best the GW1000 driver default field map gives an indication of what data may be available via the Ecowitt upload protocol but it provides little else regards the Ecowitt upload protocol.
Gary
@Gary: you said in other words - probably more clearly - what I wanted to say.
davidefa wants (as I read it) to update an interface for Meteotemplate created by one of our community members based on the ecowitt protocol by the help of which Ecowitt sensors can be displayed on the Meteotemplate "skin", i.e. in a self-built block or plugin in the MT terminology - so he needs to know what would all be sent by the GW1000 or a HP2551 console if we were in possession of all available Ecowitt sensors.
Here the weewx GW1000 field map would give an indication what fields that would all (functionally) be.
I personally think that his "complaint" is probably due to a 1:1 translation from his Italian mother tongue into English ;), so it's not a complaint but meant to be a (fair) statement.
For the WN34 and WH35 names in the ecowitt protocol he will have to wait until these sensors become available in the market and someone from our community starts using them.
For all the others he got an example for the names from me (from my sensors posted by a GW1000 ) and can derive the number from the weewx interface (or by due diligence on the ecowitt.com website going through all available sensors) and through "my" table/matrix here in this forum.
You have just made a nice and very useful table.
By the way - in the weewx github wiki the GW1000 API driver is until now NOT mentioned in the overview - only the interceptor driver can be found described under the "Get data from a GW1000" link
(https://github.com/weewx/weewx/wiki)
in my opinion there should be either an additional link for the GW1000 API driver on the main page or as a second option described at the link target page. Your splendid https://github.com/gjr80/weewx-gw1000/wiki seems to fall through the grid (or I am too blind to find the respective entry ...)
Many GW1000 users start unnecessarily using the interceptor driver for a GW1000 due to that link where there is something much better available.
-
Hi!
For the WN34 and WH35 names in the ecowitt protocol he will have to wait until these sensors become available in the market and someone from our community starts using them.
This is the current status from the firmware point of view. However, that may change before the sensors are released:
WN34:
tf_battN (where N = 1..8; output probably voltage)
tf_chN (where N = 1..8 )
WH35:
leaf_battN (where N = 1..8; output probably voltage)
leafwetness_chN (where N = 1..8 )
The batt values are still to be regarded as uncertain. It can also be that these are then output in levels (0-5).
However, I'm relatively sure about the actual values and names. This is how they are stored in the firmware. (And this is how it is implemented in FOSHKplugin.)
Regards, Oliver
-
Thank you Oliver, I did check your plugin v0.07... but not the newly released v0.08 : - (
-
Froggit have announced their DP250, the Froggit version of the Ecowitt WH45 5-in-1 indoor air quality sensor.
https://www.froggit.de/product_info.php?language=en&info=p483_dp250-5-in-1-co2-pm2-5-pm10-temperatur-luftfeuchte-innenraum-luftqualitaets-funksensor--bald-verfuegbar-.html
Updated the matrix accordingly. It's still marked as "available soon" on their web site (10-May-2021) which indicates that they are waiting for a shipment from Fine Offset.
-
The question has come up if the outdoor sensor array which comes with older FineOffset stations like the WH5300 is compatible with a GW1000 or whether it uses the same technology as a WN67 (light weight outdoor sensor array which will come with the WN1900). They are not compatible.
We added corresponding information in footnote 23 regarding the WN67 sensor array.
-
Ecowitt released today, 03-Jun-2021, version 1.7.3 of its HP2551 console firmware.
They fixed some bugs and improved especially German translations - but also introduced a rather annoying bug:
the text for the Indoor T/H sensor is now "WH32" instead of "Indoor" on the main display - hopefully to be fixed soon.
Reported to Ecowitt.
EDIT: one can fix it oneself - once one knows how - quite a hidden and not very logical place ... - see next post
-
I have to revise part of my earlier posting.
I have meanwhile learnt that my observation - that the changed naming of the indoor temperature/humidity sensor of the HP2551 - is not a bug but reveals a feature. The firmware update purged the former name and replaced it by the "WH32" text.
If you don't like this text (I didn't as it was wrong and I preferred the old "Indoor"), you wonder how/where to change it.
I did a long search through the console and the manual - and only got successful by the hint of a forum member.
The WH32B indoor temperature/humidity/pressure sensor is considered to be an OPTIONAL sensor, which I find strange for a console which doesn't have an inbuilt T/H/P sensor and its part of the basic package.
Once you know that you can also find it on the "Optional Sensor Display Mode" page of the console (press 4 x ▼) and also change the sensor's display name on the main display ...
But it's not documented, at least not clearly. Who would expected a basic T/H/P sensor to be an extra or optional sensor ...
And the example picture of the manual does NOT show the WH32B sensor even though it's part of the basic package (console, sensor array, T/H/P indoor sensor).
I will add this info to the console description as I guess I'm not the only one who gets somewhat lost here ...
-
I'm new here and just wanted to say thank you for the great comparison chart and details notes on all the models. Thank you!!!!! It has made mixing my old system with my new one very easy.
I understand it is only showing existing shipping products, but I do wish it had the WH24B, 25B, WS-1200 and WS-0900-IP (all the stuff from the WS-1200-IP system). I was pleasantly surprised to see a WS-1900-CONSOLE pickup everything on my 24B and all my WH31* all over. Granted, the wind gust/speed is half what it should be on the 1900, but then the 1900 isn't listed as being compatible with my old 24B (single vs dual pulse issue).
I know lots of people don't seem to have a fondness for the WH24B array, but it has served me well over the past 5 years (other than the silly humidity sensor always a bit off, which I promptly got a replacement 24B. .. Now I have two... These old 24Bs are great to tinker with and upgrade and mate with the GW1000.)
-
Great thread.
I'm not sure if it has been mentioned before but the the mainly Meteobridge products (NANO etc) used in Davis stations are now able to collect data from the GW1000 gateway device for anyone using a mixed brand environment.
-
Great thread.
I'm not sure if it has been mentioned before but the the mainly Meteobridge products (NANO etc) used in Davis stations are now able to collect data from the GW1000 gateway device for anyone using a mixed brand environment.
The compatibility matrix has a special line for "application" software (weather software), where also Meteobridge is shown as usable with a GW1000/WH2650.
[ You are not allowed to view attachments ]
For Meteobridge this applies to all platforms: MB, MB NANO, MB Pro and MB on RPi
-
Gyvate: For your overview: Froggit now also sells the WH2650 WIFI + WH32B without the WH65 7-in-1 outdoor array (link (https://www.froggit.de/product_info.php?info=p487_wh2600-pro-basisstation-inkl--temperatur-luftfeuche-luftdruck-innenraum-funksensor.html)). This is great if you want the WH2650 console but combine it with the WS68 for example.
I like the WH2650 over the GW1000 because it allows you to place the separate WH32B indoor sensor in an ideal location without requiring the console to be very nearby. The drawback is of course yet another sensor that takes batteries.
-
Gyvate: For your overview: Froggit now also sells the WH2650 WIFI + WH32B without the WH65 7-in-1 outdoor array ** (link (https://www.froggit.de/product_info.php?info=p487_wh2600-pro-basisstation-inkl--temperatur-luftfeuche-luftdruck-innenraum-funksensor.html)). This is great if you want the WH2650 console but combine it with the WS68 for example.
I like the WH2650 over the GW1000 because it allows you to place the separate WH32B indoor sensor in an ideal location without requiring the console to be very nearby *. The drawback is of course yet another sensor that takes batteries.
Last year it was sold with the 7-in-1 outdoor array (as Steinberg Systems SBS-WS-600) for 65 EUR only :eek: =D>, then 85 EUR, now 99 EUR at expondo.de , but still with 3 years warranty (vs. Froggit: 1 year only)
*) yes, see my post at https://www.wxforum.net/index.php?topic=40970.0
It's definitely more flexible if you don't mind the shape (what some people do - design over functionality :roll:)
As for the batteries - indoor they hold longer than 2 years, but you should replace them after two years to avoid leakage
**) yes, I know - you either get it from Fine Offset as WH2650 (+ WH32B) or (now, recently) from Froggit as WH2600 Pro without outdoor array - the Froggit price of 50 EUR is +/- the same as getting it from FineOffset/Ecowitt (42 USD + 19% VAT).
Last year it was sold with the 7-in-1 outdoor array (as Steinberg Systems SBS-WS-600) for 65 EUR only :eek: =D> then 85 EUR and now 99 EUR at expondo.de (http://expondo.de) with a 3-year warranty (vs. 1 year with Froggit only).
-
added CumulusMX >= V12 (3141) as application software for (almost) all new FineOffset clone consoles.
CMX V12 can now use a console (or server, e.g. FOSHKplugin) which posts in Ecowitt protocol to a custom server (here: CMX) as either
- main station
or
- supplementary station to enrich an existing station by extra sensor data
As far as I know adding the Ambient protocol is still "under construction" but planned for a later version => a WH2902 or a WS-2000/WS-5000 console could then also connect to CMX via Ambient protocol and display basic + extra sensors.
Already now the Ambient stations could use their custom server options to connect to CMX via the WU protocol, also from V12 (build 3141) on, (WU protocol however only supports basic sensors, no extra sensors)
-
added the WN34L water temperature and WN34S soil temperature sensors (1-8) as released to the matrix
added the WN35 leaf wetness sensor (1-8) as released to the matrix
the WH31/WN30 family, the WN34 family and the WN35 sensors can have a maximum of 8 different sensors (realized via channels) each per console.
The WN30 water temperature with attached cabled probe is probably meant more for indoor use (aquariums, fish tanks or freezers) while the WN34L is definitely an outdoor sensor (pools etc.)
-
Hi Gyvate, the Ecowitt.net site Battery condition log refers to a WH25 sensor and a WS65 sensor whereas in your 'Fine Offset (FOSHK) Weather Stations i.e. consoles, sensors and clones' thread they are referred to differently. Which one is correct? I'm trying to rename them so I know what they are.
Thanks again. Gordon.
-
Hi Gyvate, the Ecowitt.net site Battery condition log refers to a WH25 sensor and a WS65 sensor whereas in your 'Fine Offset (FOSHK) Weather Stations i.e. consoles, sensors and clones' thread they are referred to differently. Which one is correct? I'm trying to rename them so I know what they are.
Thanks again. Gordon.
So who is correct ? Both ! 😛
In 2020 Ecowitt introduced a new acronym scheme which can also be found in the main thread.
https://www.wxforum.net/index.php?topic=40730.0 acronym scheme
Including the exception for WH65/WH69 [WS65/WS65] - the example is for the WH69/WS69 only though.
There is some legacy naming e.g. WH65 as this was built before they decided to streamline their sensor acronyms.
On ecowitt.net the WH65/WS65 is shown as WS65, whereas in the GW1000 API and in the api string sent with the
custom server option it still says WH65.
WS is more correct as the WH65 has a solar panel - and its battery status is in most locations (unless extreme conditions)
not very helpful as the battery is allmost never used. Mainly for the first startup.
The supercapacitor charged by the solar panel holds for 2+ days to keep the station running - only if it expires, the
batteries would be used. It needs very cold weather and very little solar radiation over a couple of days for such a situation to occur.
Maybe after some massive volcano eruption ...
-
thanks and WH25?
-
WH24 is the WH65 predecessor (the "boat") and the WH25 is the WH32B predecessor
-
thanks again, its strange that Ecowitt use the name of the 'predecessor' on their site.
-
It is to keep us amused and confused. Same with ambient and everyone else.
I figure some day I will order a weather sensor and a bread toaster will arrive because I made a mistake.
-
thanks again, its strange that Ecowitt use the name of the 'predecessor' on their site.
yep, but what they mean (in most cases) is the WH32B. Even though, a real (old) WH25 can be received by a GW1000 and then posted to ecowitt.net and there you can't tell the difference.
@Rover1822 - the WH32B could be interpreted as Bread ... #-o - the B is already there (even though it stands here for (an indoor WH32 with an additional) barometer
-
It is to keep us amused and confused. Same with ambient and everyone else.
I figure some day I will order a weather sensor and a bread toaster will arrive because I made a mistake.
Couldn't resist :grin:
[ You are not allowed to view attachments ]
https://patents.google.com/patent/US4913046A/en
The invention proposes a temperature measuring device for a bread toaster, with a sensing element (1) which is in communication with the toasting chamber (25) through a radiation guide channel (A, B, C, D). The radiation guide channel (A, B, C, D) is formed of several passageways (11, 12, 13) arranged in spaced apart serially disposed partition walls (4, 6, 8).
App-controlled toaster will sear emojis or the weather forecast onto your toast
https://www.6sqft.com/app-controlled-toaster-will-sear-emojis-or-the-weather-forecast-onto-your-toast/
-
Just questioning here for a friend who's looking to buy a WN1900 console.
The chart shows that the WN1900 can read the outdoor temp WH32. However the manual states the sensors it can read and the wh32 is not listed. (page 11 & 12).
https://osswww.ecowitt.net/uploads/20210930/WN1900%20Manual.pdf
-
It's a yes and no.
Our friend @Ivan13 from Italy who was one of the beta testers wrote here in the forum on 21-Mar-2021:
"At the moment on sensor id all the sensors that are compatible with a classic gw1000 are appearing, with the exception of the WH32 sensor and the leaf wetness sensor that will be added with the next firmware that will be released."
So it's a matter of time when the next firmware will be released. As far as I know no firmware update for the WN1900 occurred so far, but I may have missed that.
The WN35 which wasn't availale in the beta firmware appears in the manual though. So the WH32 should also go (but still to be verified).
However, I haven't seen the WH32 being explicitly mentioned in their manuals or any other console (except in the WH32 itself ;).
It wouldn't make much sense as a WS68 is supported (via WS View) and a WH65 too (even though not mentioned). And a WS68 needs an extra WH32 and a WH40 for being a full station.
I wouldn't expect too much from a WN1900 console - for some (probably poor design) reason it doesn't show solar data (even though when connected to a WH65 the WS View app shows them) on its screen - I guess it's due to the WN67 outdoor array it comes with in a package which has neither a solar cell nor solar sensors. The WN1900 console is sold separately for +/- 40 USD.
-
I use the wh32 sensor with the wn1900 console and it is both displayed on the console and the data is uploaded online normally, I believe the other sensors are also read, even the leaf wetness ones, but at the moment I use the console only with the wh32
https://drive.google.com/drive/folders/1rN5gueu2YxQ3BVlO-YWb6SCkKFfJIRh6
-
Froggit firmware verisons?
The chapter 3. firmware - update - versions does not list Froggit at all - so how is it with their devices? Are they directly ecowitt firmware usable? eg. does DP1500 just use same firmware as Ecowitt GW1100, or?
As Froggit now finally seems to be able to offer all the parts I'm actually interested in.
-
Hi!
Are they directly ecowitt firmware usable?
Yes.
Oliver
-
Froggit firmware verisons?
The chapter 3. firmware - update - versions does not list Froggit at all - so how is it with their devices? Are they directly ecowitt firmware usable? eg. does DP1500 just use same firmware as Ecowitt GW1100, or?
As Froggit now finally seems to be able to offer all the parts I'm actually interested in.
If you had read the full thread carefully, you could have noticed that all non-Ambient FineOffset clone devices use the same (Ecowitt) firmware. 8-)
The first sentence goes:
"there are two types of firmware for the FineOffset/Ecowitt (clone) consoles: "
In the matrix the DP1500 is listed as a clone of the GW1000.
The firmware section does not stand on its own - it assumes that you have also read the paragraphs, sections before.
You can use (and will automatically use in the WSView app) the Ecowitt firmware. Froggit do not produce own firmware.
They are only a reseller who has put their own brand name on the devices (as other resellers also do).
But you CANNOT use the firmware for the GW1100 on a DP1500 - they are not compatible and the WS View app will not offer this update anyway. GW1000 and GW1100 have different firmware !
-
central thread on stations, consoles, sensors, firmware etc. was recently updated several times:
excerpt from change log:
(30-Oct-2021) added Ambient WiFi firmware change to V 4.3.2
(03-Nov-2021) added the new WS90 all-in-one outdoor array (beta testing phase) and the WH31 with DCF77 support (868 MHz, Europe only)
(06-Nov-2021) added information about new Wittboy station (WS90 + GW2000) - footnote 27
(07-Nov-2021) added information that with firmware 1.7.6 the HP2551 console keeps last lightning strike time stamp over a reboot/restart
(14-Nov-2021) added change log for GW1100 firmware V2.0.7
(16-Nov-2021) added Ambient WS-5050 station (=WS-5000 without rain gauge)
(21-Nov-2021) added info about GW2000 (still in beta testing phase)
-
Console/device firmware 1.7.7 for the HP2551 console was released by Ecowitt. See console manuals and software page.
Now the (cycling - when chosen) temperature/humidity display on the right hand side of the console window shows:
- T/H indoor
- T/H WH31/WN30 extra sensors
- T/H from the WH45 5-in-1 T/H/PM2.5/PM10/CO2 combo sensors
The console picture and the pictogram have been updated correspondingly
A pictogram for an inserted functional SD card has been added on top - symbol will also show defective cards - no symbole = no card inserted
[ You are not allowed to view attachments ]
Also the WN34/35 sensors will be shown on the main page
They cycle with the WH51 Soil Moisture sensors.
-
In the past 2 1/2 month many, many questions have been asked in new, separate posts most of which are basically already answered in our MUST READ - Fine Offset Clone Models,sensor compatibility,firmware + other info post/thread. Also from more experienced users and not first time posters.
We can only encourage every visitor (included repeated visitors ;)) of this forum to read this thread through completely from beginning to the end.
It is kept as up-to-date as possible and contains much more information than "just" the compatibility matrix (which in itself can be of tremendous help).
It also has a change log which documents added, updated, modified, revised information.
There was an original plan to take our sticky posts as a baseline for a Fine Offset (clone) WiKi, which then didn't find much resonance among the visitors of several fora (meteohub, Cumulus, wxforum, etc.).
There it has remained the sticky post collection. Maybe a bit less structured and organized than a WiKi could, but nonetheless a solid source of information.
Please make use of it !
-
in the new device firmware 1.7.8 for the HP2551 console a big list of changes and fixes has been included. See the firmware section of the main thread.
The point 5 of the change log is a bit cryptical - the optional sensor page has been moved into the Setup --> More [Setup] area as Sensors Names&Data.
I made a remark in the console section 2.2 of the main thread.
-
@Gyvate:
in the compatibility list it is listed that the WH32B is compatible with the GW2000. It is a comparable device like the GW1000/1100 where there is no compatibility with the WH32B. Is this an error in the scheme :?: I couldn't find an option in the GW2000 to add a WH32B (WH32 can though).
-
that's well spotted - some wrong copy and paste with the last update - have to blame the cat for crossing my keyboard ... \:D/
it's corrected now
-
Gyvate, you know I admire and respect the work you have done with the matrix of products . I just wish it wasn't an image for the matrix as it can't be text searched. An HTML table instead (or divs) , would solve that. :)
In your free non paid time, of course. :)
And don't hit me
- Rover
-
Gyvate, you know I admire and respect the work you have done with the matrix of products . I just wish it wasn't an image for the matrix as it can't be text searched. An HTML table instead (or divs) , would solve that. :)
In your free non paid time, of course. :)
And don't hit me
- Rover
I had tried that before, many times - and, at least with the forum software, it's not only a pain in the neck but an almost impossible task. The alignment never worked out and I got quite some hints and support by @galfert those days. It just ended up looking ugly. What should have worked in theory wouldn't work out in practice. That's why I finally decided to switch to a graphics table.
I could think of some html table with keywords and references to the matrix in addition to the graphics.
In fact, what we would really need is a WiKi - that would allow for a completely different structure and presentation.
@galfert during his more active times in this forum had tried and stretched out feelers in many forums (Cumulus, Meteobridge etc. who all have some sort of Ecowitt related sub forum), but the response was very poor. So we gave up on the idea. Or at least postponed it.
A WiKi needs contributors, and a hosting place, and a proper WiKi software. Everybody wants to read it and (almost) nobody wants to build it (and run and maintain it - technically and content-wise).
-
I meant it partly in jest, but like you, I'm sure you hit a web page and do a text search for the data that you were looking for with the browser search option.
It is such a minor thing, and I get it with the constraints of simple machines as I used to host one.
You might want to think of also inserting a PDF as an attachment, as your source before you convert to an image, is a text table of some form. That should translate when saved to a PDF (depending on what you have for software tools) , to a text searchable PDF .
I do document management for a living so I get the process.
Not the best solution, I agree. Better to have that data in a tabular format in HTML , but I get it.
At the end , most can search visually on the image. It is an incredible asset as it is.
- Scott
-
Why is the console called the HP2551 and not HP2550? Everywhere I’ve looked I see it as the HP2550, FOS and even Ecowitt call it the HP2550(_C) where 2551 and 2553 are the kits with a 2550 console. Just wondering….
-
Why is the console called the HP2551 and not HP2550? Everywhere I’ve looked I see it as the HP2550, FOS and even Ecowitt call it the HP2550(_C) where 2551 and 2553 are the kits with a 2550 console. Just wondering….
As far as I remember Ecowitt called it HP2551 already some time ago. And FOSHK called it HP2550 (such deviations between "father" and "daughter" in the naming are quite common).
There has been quite some renaming recently on the Ecowitt web site regarding letters and numbers - and not all in tune with their new naming concept published last year - and now it's HP2550_C there too.
At the end of the day there is no reason (remaining). I can do some housekeeping and name it back to HP2550 where the name occurs in the threads I have taken responsibility on.
Done. When you still find some HP2551 or HP2553, then this refers to station products names: HP2550 console plus different arrays - WH65/WD69, WS68, WS80.
When you talk about a HP2553 station then you have the HP2550 console, the WS80 ultrasonic array and the WH40 rain gauge [plus a WH32B which comes with the console for indoor T/H/P readings)
-
What would be nice is if they changed, or added a version number to units that they have changed. I'm thinking of the WH40 where early versions do not report battery status and new ones do. A simple .X or something to the model number would assist greatly as opposed to "how old is your unit?"
This will probably also apply to the WS90 and those on Beta , versus production kickstarters versions, and probably later production models.
-
Ambient I think is worse with their naming. The WS-1001-WIFI, WS-1200 (and a few others) as stamped on the back are both WS-1002 hardware (one just has a wifi model).. at least for the REV2 hardware models. I think the Rev1 just had less memory and was based on another board (just guessing there).
The comments about the HP2550 identifier came up only because I was looking into the last released software for the boat anchor series consoles and then remembered that its all a mess.
-
News in the thread:
- firmware 1.6.9 released introducing WS90 support for GW1000 and WH2650 consoles/gateways and clones releases - introduced bug not posting to WU
- firmware 1.7.0 released fixing (partly) the WU upload bug; wind data still not uploading
- firmware 1.7.1 released fixing the missing wind data upload to WU
WS View Plus version 2.0.31 released allowing configuration and calibration of WS90 rain data from all Gateway consoles (GW1100 and GW2000 have this option additionally in their WebUI with FW 2.1.3 and higher)
For the rain calibration options to appear in the the rain totals (!) section, a WS90 needs to be connected to the console. Via their API all gateway consoles will send both classical/traditional rain gauge readings if both types of rain gauge (WS90 ["piezo"] and WH40 or WH65/WS69 are registered in parallel to the console. For this a new API command CMD_READ_RAIN (0x57) has been introduced. The response allows the synoptical display the in WS View Plus App >2.0.30. Remark: the WS19x0 consoles haven't received a firmware update yet and won't have this feature (yet).
As for today (28-Apr-2022) it appears that the FineOffset/Ecowitt development is affected by another SARS-CoV-2/COVID-19 related lockdown in China and the development suspended.
EDIT: update
Still firmware 1.7.2 for GW1000/WH2650 has been released today (29-Apr-2022) which is supposed to fix the frequent "spontaneous" reboots of the GW1000/WH2650.
Verbatim "Fix the bug of abnormal startup of the system."
-
added the below table to the main thread (chapter 9) as I consider it very useful
[ You are not allowed to view attachments ]
-
also added a small table to the thread about sensor (array) transmission timings / reporting intervals as chapter 10.
-
Hi all,
I searched and did not find information about the Misol WS-HP3001
http://www.misolie.net/wireless-weather-station-with-5-sensors-5-channels-color-screen-data-logger-connect-to-pc-p-501.html
Is this device the same as the ecowitt HP3500/3501B and can the ecowitt firmware (which SEEMS to connect to far more sensors and idsplay their states) be flashed onto this Misol device ?
Thanks,
-
The HP300x and the HP350x are completely different consoles. The HP300x is not a fully-fledged weather station, it just reads and displays up to 8 WH31 Extra Temperature/Humidity sensors, calculates dew point, nothing else.
Whereas the HP350x console is a fully fledged console which can receive (almost) all Ecowitt sensors - so far except the WS90.
But the HP350x cannot display all sensors; only pass the values thru into the Ecowitt cloud or to a custom server.
See manual of the HP350x console at ecowitt.com.
The HP350x firmware will not work with a HP300x console.
-
Hi Gyvate,
(http://stacjepogody.waw.pl/index.php?action=dlattach;topic=2780.0;attach=3785;image)
Felix, a Polish guy on this forum, seems to have flashed Ecowitt HP3501 Firmware to a Misol HP3001 device and succeed, even though the Wifi do not work cause the Misol device do not have the needed hardware.
http://stacjepogody.waw.pl/index.php?topic=2780.0
-
I read the whole thread (not only one post) in Polish, and it what I understand is that you seem to be able to sort of upgrade the HP3001 firmware to attain some sort of HP3500 look, but it never becomes a real HP3500 due to the lack of hardware. There doesn't seem to be any added value except for getting a one minute archiving instead of a 5 minute archiving.
It looks like making the dashboard of a motorbike look like the dashboard of a car - but only because its dashboard now looks like the dashboard of a car, the motorbike doesn't turn into a car.
If you like playing and experimenting, feel free to do so.
I personally don't see an added value - you update the software but not the hardware (e.g. the WiFi module is missing).
I would recommend rather getting a proper modern WiFi weather station - but everyone can do as they like...
-
He also said that Wind speed/gust are accurate with an updated firmware and that it can read sensors from the HP1001 (the one he got)
So, appart from the Wifi functionnality... it work like an HP3500.
I bought a kit from Misol, it was 90€ for the HP3001+5 sensors just 15€ more then the sensors alone, i will flash the ecowitt firmware and report here the result.
-
Good luck with your endeavours !
And to make other readers aware aware - the "only WiFi missing" is quite a big part of the functionality missing which comes with the WiFi capability:
- posting to weather services including the nice internet ecowitt.net dashboard in the Ecowitt cloud and using the Ecowitt app on a smartphone
- using data logger programs via custom server
- ....
that's all not available
-
Well not really in my case, cause i got a WH2650, the wifi functionnality is already met by this device.
Adding this HP3001 + 5 sensors which cost nearly the same price of the 5 sensors alone (90€ vs 70€)... will display my sensors datas ... PLUS save datas to an SD card in CSV format.
Which is pretty great .. if it works, i will come back for a feedback.
-
Well not really in my case, cause i got a WH2600, the wifi functionnality is already met by this device.
Adding this HP3001 + 5 sensors which cost nearly the same price of the 5 sensors alone (90€ vs 70€)... will display my sensors datas ... PLUS save datas to an SD card in CSV format.
Which is pretty great .. if it works, i will come back for a feedback.
That's not the point - of course you can have WiFi access to the weather services if you have another device which has it. That's trivial.
But the HP3500 firmware flashed HP3000 device alone cannot. And that's the point !
I could also add a HP3001 to my equipment, and my consoles will post to the weather services whether I have it or not.
But why would I do so ? I rather take a WH2650/Froggit WH2600 Pro WiFi displayless console for 30 EUR and have it post all Ecowitt sensor data not only to the weather services but also to an old (or new) Android tablet using the Personal Weather Tablet app or the Ecowitt app on a big display.
If you are into tinkering and like add such a piece to your existing devices - fine.
But we have to be clear that this may not be an option for someone who still has nothing else and wants to get a cheap entry into the weather universe.
For this I cannot recommend such an approach.
-
You say "that's not the point" ..? You are against the idea and now say "it's trivial" ... you just seems against the idea for no reason appart from the missing wifi functionality, i do not get it ...
We know that the firmware will not push the wifi functionnality cause the hardware is not present but the device is STILL a good device and even better flashed.
You say "the "only WiFi missing" is quite a big part of the functionality missing which comes with the WiFi capabilit", not for everybody ... you think of your situation, not everybody is in the same case and clearly i'm not.
And some people need those data only logged onto an SD card cause they got no internet in some places. If it work, i will buy an other kit to put in my shed that i got in the mountain and just physically harvest data once every 2 month or so, even without the display .. the logging is already a very good functionnality.
"I could also add a HP3001 to my equipment, and my consoles will post to the weather services whether I have it or not.
But why would I do so ? I rather take a WH2650/Froggit WH2600 Pro WiFi displayless console for 30 EUR and have it post all Ecowitt sensor data not only to the weather services but also to an old (or new) Android tablet using the Personal Weather Tablet app or the Ecowitt app on a big display."
So ... you got your equipment which already post to the web as you say, why add a HP3001 ?
1 - To display information in a an other room
2 - To log datas on an SD card
Then you say you would rather add a WH2650 which would be redundant as you stated that your equipment already post to the web. Unless i missed something ?
Then finally you come back on track
"If you are into tinkering and like add such a piece to your existing devices - fine.
But we have to be clear that this may not be an option for someone who still has nothing else and wants to get a cheap entry into the weather universe.
For this I cannot recommend such an approach."
Yes it's to add to an already existing system, you never asked before going bazinga... :D
And i will add that EVEN in a low cost option it's still good.
1 - Waldbeck Halley Station (WH2650+ 7in1 station) cost 95€ and you get : Wifi
2 - Add the Misol HP3001 + 5 sensors for extra 90€ and you got (total 185€) : Wifi, A display (not as good as a 2550 of course), a SD Logger and 5 more sensors.
=> Is there any cheaper solution to get a kit able to display and post to the internet, with 5 extra temp/hygro sensors ? Maybe there is ... but i do not know how to achieve it, till then it look like it's the cheaper entry into the weather universe.. IF you need extra temp/hygro sensors (like i do), is this one.
Flashing would add some extra free functionnalities.
My car, BMW 330 as been flashed ... does it make a Pörsche ..? No .. it do not, but man ... there is a big difference and i would do it again. (it was not free in this case... :-P)
But i understand that you better keep people away to avoid people crying for help after bad flash or so ... i still think all informations should be given to people, they got to decide themselves.
Maybe there will be problems after flashing, no communisation with sensors .. display problem .. who knows, i decided to try and as i said .. i will report here for other people that would be in the need of those conclusions.
-
No point getting upset ...
It seems that I have hit a nerve with my comments - no intention here
Honni soit qui mal y pense.
My only purpose in commenting was making it clear for other (not so expert) readers, what the caveats and missing functionalities of this approach are as a single approach.
Using it as a low-cost console for an existing setup is surely an option - but somehow this didn't come across for me clearly before.
Maybe my incapacity of understanding what you were implicitly aiming at.
-
Do not worry, i still like you .. ;)
Something i noted today, my WH2650 has been disconnected from AC for 15mins and it lost track of rain, weekly, monthly and yearly... too bad they do not save those datas in a permanent memory.
Maybe someone already built a 5V power supply with a power bank ?
-
Hello All,
Just to confirm, i bought a Misol 3001, flashed a HP3501 firmware (1.69) and APPART from the wifi function (which the 3001 DO NOT HAVE THE HARDWARE FOR), my 3001Flashed3501 work as a 3501 would, i got gust, temperatures, Lux... all sensors as been automatically detected. And all infos seems acurate.
-
Hi there! Could you please add a note to the sensor comparability matrix explaining what the various symbols mean? For instance, I understand that an X means not compatible, and a + means compatible... but what does (+) and - mean?
-
"-" and "x" mean the same - not compatible resp. cannot be used, received
"(+)" means "in principle yes", but nobody would reasonably use a WN67 with these consoles - you'll understand this when you read the footnotes to the WN67 array.
it's sort of a "crippled" array - no idea why Ecowitt built it in the first place.
Regarding "x" and "-" - I'll replace the "x" by "-" next time the matrix is updated.
-
Dear All, can someone help me figure out these consoles on the Froggit website?
Are the WS60 and FT0100 consoles Fine Offset clones?
https://www.froggit.de/product_info.php?info=p298_ws60-funk-farb-wetterstation-inkl--1-funksensor--funkuhr--wecker--wettervorhersage.html
https://www.froggit.de/product_info.php?language=en&info=p200_wetterstation-ft0100.html
I am mostly interested in their precision for temperature compared to the WH32 and GW1100. Will I be able in the future to add other sensors even if not able to display their readins on the console but at least control them with my computer via Wifi?
-
Dear All, can someone help me figure out these consoles on the Froggit website?
Are the WS60 and FT0100 consoles Fine Offset clones?
https://www.froggit.de/product_info.php?info=p298_ws60-funk-farb-wetterstation-inkl--1-funksensor--funkuhr--wecker--wettervorhersage.html
https://www.froggit.de/product_info.php?language=en&info=p200_wetterstation-ft0100.html
I am mostly interested in their precision for temperature compared to the WH32 and GW1100. Will I be able in the future to add other sensors even if not able to display their readins on the console but at least control them with my computer via Wifi?
No , they are not Foshk devices.
-
1. they are not Fine Offset clones - Froggit (like Ambient and many other resellers) also sell weather stations from other manufacturers.
2. It's doubtable that their temperature sensor would be more precise than a WH32 outdoor or indoor sensor. (The GW1100 has - for indoor - SHT40 chips inbuilt - so not too bad).
These two "weather stations" I'd rather call toys compared to the simplest but fully fledged Ecowitt / FineOffset weather station like a GW1101, a WS2320E or a WS2910 station.
They look like being on the level of a WH2800 which is just a thermometer/humidity/barometer - not a real weather station - but marketing usually just says anything
-
They really don't look like anything F/O makes. I agree with Gyvate
-
Thanks a lot for the quick reply. My main goal is to measure temperature inside and outside, and maybe in the future expand to air quality and solar radiation. But I don't want to invest much initially because I don't know if I will expend in other things.
So I am wondering if the precision of GW1100/WH32 is really that much better then one of these "stations" I have mentioned. Or even something like this https://www.amazon.de/Technoline-moderne-Wetterstation-schwarz-Hochglanz/dp/B07NDVJVSS
Otherwise the WH2800 is on sale now https://shop.ecowitt.com/products/wn2800 , I am located in Europe but don't mind using a different frequency. I don't understand if the outdoor sensor provided with the WH2800 is the WH32, because the whole package is reasonably cheaper.
I am not interested in rain/weather so seems like a waste to have a fully fledged weather station.
Any suggestions?
-
I don't think anyone here, is going to be able to give you a comparison against the F/O clones with an unknown weather station. it is hard enough to compare the models of F/O clones.
-
Be careful when you say you don't mind using a different frequency , this , depending on country, is illegal to do. Sure , you can do it, be advised , you are breaking the law of whatever country if the frequency is not one of those approved.
-
Be careful when you say you don't mind using a different frequency , this , depending on country, is illegal to do. Sure , you can do it, be advised , you are breaking the law of whatever country if the frequency is not one of those approved.
On the Ecowitt website it is marked as "global" frequency, so I guess it's ok to use. In any case do you guys know anything about the WH2800 precision and if the sensor included is the WH32?
-
What country are you located in?
Also read Gyvate's excellent post https://www.wxforum.net/index.php?topic=40730.msg417956#msg417956
-
Be careful when you say you don't mind using a different frequency , this , depending on country, is illegal to do. Sure , you can do it, be advised , you are breaking the law of whatever country if the frequency is not one of those approved.
On the Ecowitt website it is marked as "global" frequency, so I guess it's ok to use. In any case do you guys know anything about the WH2800 precision and if the sensor included is the WH32?
I'm not sure those are the questions you need answers for, especially if you want to control them from your computer. (I'm not exactly sure what that means -- control). If you want to be able to see the data from your phone or computer, you are going to need a device that transmits that data -- a gateway to a service or use the ecowitt app. The 2800 doesn't do that, afaik. If you want to add sensors, especially things like AQ or even more temp/humidty sensors, you should go with a GW1100 and some WH31s to start. Amazon has that bundle in the US for $48.
-
Thanks a lot for the quick reply. My main goal is to measure temperature inside and outside, and maybe in the future expand to air quality and solar radiation. But I don't want to invest much initially because I don't know if I will expend in other things.
So I am wondering if the precision of GW1100/WH32 is really that much better then one of these "stations" I have mentioned. Or even something like this https://www.amazon.de/Technoline-moderne-Wetterstation-schwarz-Hochglanz/dp/B07NDVJVSS
Otherwise the WH2800 is on sale now https://shop.ecowitt.com/products/wn2800 , I am located in Europe but don't mind using a different frequency. I don't understand if the outdoor sensor provided with the WH2800 is the WH32, because the whole package is reasonably cheaper.
I am not interested in rain/weather so seems like a waste to have a fully fledged weather station.
Any suggestions?
The Ecowitt WH2800 transmits at 433 MHz which is legal is Europe, only proner to electromagnetic interference.
The same piece is sold as GARNI 281 in Europe for about 40 EUR and at 868 MHz which is preferrable over 433 MHz.
It comes with one special WH31 sensor (Temp/RH extra sensor with DCF time signal receiver) which can be used for outdoor temperature - the indoor sensor is inbuilt in the console. You can connect two more WH31 sensors (total max three) if you like.
The WH31 and a WH32 have the same sensor chips.
For a WH2800 it doesn't matter that you only have WH31 and no WH32 - you define the meaning of your sensor(s). All three (if active) can be shown, switching manually or cycling automatically every 2-3 seconds.
The WH2800 / GARNI 281 can not be extended beyond the three WH31.
A GW1100 can use all available Ecowitt sensors. However it has no display. You want a display you can repurpose an old (or new) Android tablet with the Personal Weather Tablet (PWT) app.
Or look the live data up in the WS View Plus, the Ecowitt app or at ecowitt.net (provided you register and create an account there).
The WH2800/GARNI 281 cannot send any data to weather networks.
-
Thanks a lot for the quick reply. My main goal is to measure temperature inside and outside, and maybe in the future expand to air quality and solar radiation. But I don't want to invest much initially because I don't know if I will expend in other things.
So I am wondering if the precision of GW1100/WH32 is really that much better then one of these "stations" I have mentioned. Or even something like this https://www.amazon.de/Technoline-moderne-Wetterstation-schwarz-Hochglanz/dp/B07NDVJVSS
Otherwise the WH2800 is on sale now https://shop.ecowitt.com/products/wn2800 , I am located in Europe but don't mind using a different frequency. I don't understand if the outdoor sensor provided with the WH2800 is the WH32, because the whole package is reasonably cheaper.
I am not interested in rain/weather so seems like a waste to have a fully fledged weather station.
Any suggestions?
The Ecowitt WH2800 transmits at 433 MHz which is legal is Europe, only proner to electromagnetic interference.
The same piece is sold as GARNI 281 in Europe for about 40 EUR and at 868 MHz which is preferrable over 433 MHz.
It comes with one special WH31 sensor (Temp/RH extra sensor with DCF time signal receiver) which can be used for outdoor temperature - the indoor sensor is inbuilt in the console. You can connect two more WH31 sensors (total max three) if you like.
The WH31 and a WH32 have the same sensor chips.
For a WH2800 it doesn't matter that you only have WH31 and no WH32 - you define the meaning of your sensor(s). All three (if active) can be shown, switching manually or cycling automatically every 2-3 seconds.
The WH2800 / GARNI 281 can not be extended beyond the three WH31.
A GW1100 can use all available Ecowitt sensors. However it has no display. You want a display you can repurpose an old (or new) Android tablet with the Personal Weather Tablet (PWT) app.
Or look the live data up in the WS View Plus, the Ecowitt app or at ecowitt.net (provided you register and create an account there).
The WH2800/GARNI 281 cannot send any data to weather networks.
Thank you for all these excellent information, that's what I was looking for! I am located in Europe, so as you mention the global frequency of the WH2800 is ok.
I think I will reduce considerably my goals, the GW1100 doesn't have a display, and I don't want to open my phone just to look at the data. I would like to start with the most simple setup. If I can't find a cheap Android device I will probably go with the WH2800.
Where do you find the Garni 281 for 40 euros?
-
I know this is hard, do not, please, rush out and buy the cheapest thing you can. Ponder it, you talked about expansion (maybe), re-evaluate , save your pennies , or not. I believe all of us here are trying to help, and there are very few that have not made a bad initial decision.
-
I know this is hard, do not, please, rush out and buy the cheapest thing you can. Ponder it, you talked about expansion (maybe), re-evaluate , save your pennies , or not. I believe all of us here are trying to help, and there are very few that have not made a bad initial decision.
I appreciate the advice, and have been reading and thinking about this for a while now, I want a decent quality instrument, but I realize that adding sensors is more expensive than what I thought, and as I mentioned I am not really interested in wind, rain, etc. I should also not overdoit just to buy a cool toy :-)
-
Where do you find the Garni 281 for 40 euros?
https://www.alza.de/garni-281-d5358390.htm 41 EUR
https://www.garni-meteo.cz/meteorologicka-stanice-garni-281.html 56 EUR
https://stacje-pogody.pl/1452_stacja_pogody_garni_281.html 57 EUR
https://www.prva.sk/detail/garni-281-meteorologicka-stanice/kk388d270249.aspx 48 EUR 50 EUR
https://www.gigatron.sk/garni-281-meteorologicka-stanice/
-
Where do you find the Garni 281 for 40 euros?
https://www.alza.de/garni-281-d5358390.htm 41 EUR
https://www.garni-meteo.cz/meteorologicka-stanice-garni-281.html 56 EUR
https://stacje-pogody.pl/1452_stacja_pogody_garni_281.html 57 EUR
https://www.prva.sk/detail/garni-281-meteorologicka-stanice/kk388d270249.aspx 48 EUR 50 EUR
https://www.gigatron.sk/garni-281-meteorologicka-stanice/
Thank you for the info. At this price I am debating if I should get the GW1100. The only issue I see is that some reviews complain about the wifi, I turn off my router every night so I wouldn't want to go through the setup every time my router is turned off. Some very recent reviews complain about this and the bad English translations. What are people experiences with the GW1100?
-
in your case the WH2800 would probably be the best (and healthiest) solution as the console doesn't transmit but only receives. It's not increasing the electro-smog in your place.
The GW1100 is a different story - you can get its info only via WiFi and you need to display that info on either some webpage or some device like a tablet. In any case WiFi will be involved.
Disconnecting the GW1100 from the router (by switching the router off or disabling its WiFi functionality) is not an issue as long as you have reserved the IP address of the GW1100, which it receives via DHCP from the router. Most routers offer such a possibility (binding the DHCP leased IP address to the MAC address of the device which makes it a quasi static IP address).
Most GW1100 WiFi issues discussed in the forum have either to do with the pairing or have more to do with the idiosyncracies of their network infrastructure setup than with the GW1100 itself - even though the tendency is first to blame the device (GW1100).
You want to avoid this and want also to avoid radiation overdose, go for a GW2000 (meanwhile also available as a single device). It has a WLAN and LAN connection - your choice. It can do all what a GW1100 can do. Connected via a LAN cable it may not need to be disconnected in the first place. It's also a displayless console (hub/gateway) by the way.
I think if you only want a fancy toy which only shows temperature (indoor and up to 3 other places), humidity and barometric pressure, even provides a simple weather forecast and shows moon phases - go for the WH2800 - it's 32 USD at Ecowitt.
You want more - or want to remain open for future expansion - a GW1100 or a GW2000 is the console of your choice (plus at least either a WH32 outdoor or/and a WH31 extra T/H sensor). If some day you want to expand, you can reuse what you already have. The WH2800 is a single appliance - no expansion possible, no outer world connection possible - just a little T/H/P display.
-
Thanks for the further explanation Gyvate and for those links! I have decided to buy the WH2800, but now I am having trouble finding where to buy. Most those link are out of stock or don't ship to western Europe.
I could buy from Ecowitt website but they charge $14 for shipping. I am not in a rush, where else can I find this? Aliexpress? Thanks again!
-
you won't get it cheaper anywhere else than with Ecowitt ...
you'll end up with around 48 USD including shipping and taxes (import VAT).
At the few sites inside Europe where it is available it will be rather 60+ EUR - but 868 MHz. i.e. sensors compatible with Europe 868 MHz consoles.
As this is a closed system, you can use the 433 MHz version - only the outdoor sensors will not be reusable later with a 868 MHz console - but that's right now anyway not your goal ...
-
you won't get it cheaper anywhere else than with Ecowitt ...
you'll end up with around 48 USD including shipping and taxes (import VAT).
At the few sites inside Europe where it is available it will be rather 60+ EUR - but 868 MHz. i.e. sensors compatible with Europe 868 MHz consoles.
As this is a closed system, you can use the 433 MHz version - only the outdoor sensors will not be reusable later with a 868 MHz console - but that's right now anyway not your goal ...
You are right, cheapest to get it from Ecowitt. I am just wondering if this setup is that much better in terms of precision than other cheaper alternatives such as some of the Garni or Baldr, or any of the other brands that have very similar small station with one outside sensor.
-
you won't get it cheaper anywhere else than with Ecowitt ...
you'll end up with around 48 USD including shipping and taxes (import VAT).
At the few sites inside Europe where it is available it will be rather 60+ EUR - but 868 MHz. i.e. sensors compatible with Europe 868 MHz consoles.
As this is a closed system, you can use the 433 MHz version - only the outdoor sensors will not be reusable later with a 868 MHz console - but that's right now anyway not your goal ...
You are right, cheapest to get it from Ecowitt. I am just wondering if this setup is that much better in terms of precision than other cheaper alternatives such as some of the Garni or Baldr, or any of the other brands that have very similar small station with one outside sensor.
regarding precision, the sensors used for the WH2800 are the same (WH31) as with the bigger personal weather stations - they are using Sensirion SHT31*) sensors. You're not likely to get higher precision in the low price segment of "enhanced" thermometers. Pretty unlikely. Even to get the same is unlikely. On the other hand you normally cannot expect the features of a BMW car in a Fiat 500 car.
Here, with Ecowitt, you would get the same sensors used in/with their high-end products even in their low cost segment.
Also, be realistic, you want a Swiss knife (a high quality multi-purpose tool) for a few cents, you won't get it (or it will fall apart at 1st or 2nd use).
*) you want to know more, have a look at https://www.sensirion.com
-
added some information about the Ecowitt Gateway API (aka GW1000 API) to the main thread as chapter 14
-
First post folks, been following since I bought my WS-5000 14 months ago.
Well, the temperature sensor in the WS80BN failed. It's sending a temp of 108.5 f out to various weather services. I read the other very dense thread about ecowitt, fineoffset and Ambient compatibilty. Since the ambient version of the WH32 is no longer being sold I just want to confim I can't use the ecowitt WH32 version due to the blanket statement statement about ecowitt->ambient doesn't work, but the reverse does ( ambient -> ecowitt.
Correct?
My call to Ambient Weather says I need to buy a replacement sensor array to the tune of $195 rather than just replace the outdoor temp sensor compnentry. Also correct?
A side question, is there a way to disable sending the bogus data out to the verious weather services? The only thing I can see in the console settings is to disable the entire WS80BN. The wind data is still useful to me until I sort all this out.
Thanks!
-
there is hope ...
1. maybe you find an (old, used?) Ambient WH32E e.g. on ebay
2. if you manage to get an (older model) Ambient WH31E (maybe also on ebay or so) - it can be converted into a WH32 (Ambient WH32E) - with the newer hardware revision it hasn't been verified yet - some little soldering needed https://www.wxforum.net/index.php?topic=43206.0
3. depending on the hardware revision of your WS80 (Ambient WS-5000 ARRAY) you can get a replacement sensor for about 16 USD from Ecowitt: https://shop.ecowitt.com/products/sht35-temp-hygr
It is for the WS80 and WS90 sensor arrays.
this is even a high precision sensor for temperature/rel. humidity. As this sensor is the same for Ambient branded and Ecowitt or reseller branded WS80, it's not affected by the firmware lock as it comes before the unit which manages the firmware information and the transmission RF frequency.
You will have to take your array down, open the radiation shield (should be easy to do) and have a look if the inserted T/RH sensor has the same connector as the one offered in the Ecowitt shop.
-
Ambient has released version 1.9.0 for the WS-200/5000 (scroll to the very bottom): https://ambientweather.com/faqs/question/view/id/1415/ (https://ambientweather.com/faqs/question/view/id/1415/)
-
Hi!
For the records:
The firmware v1.9.0 from Ambient Weather is (this time checked) binary identical to the v1.9.0 from Ecowitt.
Oliver
-
Hi!
For the records:
The firmware v1.9.0 from Ambient Weather is (this time checked) binary identical to the v1.9.0 from Ecowitt.
Oliver
noted
"WiKi" (=MUST READ thread) updated
the device firmware is independent of the (re-) seller and Ambient's restrictions are included for everyone - only that non-Ambient consoles then don't use it
-
Ambient has released version 1.9.0 for the WS-200/5000 (scroll to the very bottom): https://ambientweather.com/faqs/question/view/id/1415/ (https://ambientweather.com/faqs/question/view/id/1415/)
Someone should ping Ambient and have them fix the page ordering.
-
Pretty obvious the inclusion was a slap in on the firmware page, as seen by the indentation, lack of header, etc.
I assume this will be fixed.
I am going to be interested if the new firmware , for some strange reason, allows , non ambient sensors. I was intrigued by Oliver's post that they where binary the same. I will install tomorrow and see.
-
Pretty obvious the inclusion was a slap in on the firmware page, as seen by the indentation, lack of header, etc.
I assume this will be fixed.
I am going to be interested if the new firmware , for some strange reason, allows , non ambient sensors. I was intrigued by Oliver's post that they where binary the same. I will install tomorrow and see.
Yeah .. um. no You can't read non-ambient sensors on an ambient piece of hardware. You can, however, read ambient sensors on ecowitt/clones.
The console firmware is the same on all the units (clones, Ambient etc..). Ambient's WiFi software is different (Easyweather vs AmbWeather).
-
I am going to be interested if the new firmware , for some strange reason, allows , non ambient sensors. I was intrigued by Oliver's post that they where binary the same. I will install tomorrow and see.
as said earlier - there is no difference in the firmware but in the hardware. non-Ambient consoles do not use the "Ambient-check" in the firmware and therefore can also receive Ambient sensors.
-
Installed the v1.9.0 on my WS-2000. No issues other than it wiped out my WiFi settings , had to re-select.
Gyvate, my post about it maybe read EcoWitt, sensors, is because it has happened in the past. When the WH57 (lightning) first came out , the WS-2000 was displaying data from the Ecowitt WH57. The next firmware update for the WS2000 removed that ability. I'm not arguing that Ambient can read Ecowitt sensors, just that it has happened in the past :).
The basic rule is of course Ambient consoles will not display any other sensors other than their own brand.
-
Installed the v1.9.0 on my WS-2000. No issues other than it wiped out my WiFi settings , had to re-select.
Gyvate, my post about it maybe read EcoWitt, sensors, is because it has happened in the past. When the WH57 (lightning) first came out , the WS-2000 was displaying data from the Ecowitt WH57. The next firmware update for the WS2000 removed that ability. I'm not arguing that Ambient can read Ecowitt sensors, just that is has happened in the past :).
The basic rule is of course Ambient consoles will not display any other sensors than their own brand.
I don't know how the firmware is programmed and how exactly the distinction is made. Maybe they use a white list with devices to be chaecked and the WH57/WH31L wasn't included yet in that version you are referring to and was simply added in the next FW version.
-
More than likely something along that line, it has happened a couple of times with newly released sensors.
-
I don't know how the firmware is programmed and how exactly the distinction is made. Maybe they use a white list with devices to be chaecked and the WH57/WH31L wasn't included yet in that version you are referring to and was simply added in the next FW version.
My guess is that sensors transmit a slight different packet, one or more bits, depending on a solder pad, like the one that change a WH31 in a WH32.
Ambient consoles check that bits, the others simply ignore them, maybe in the same way, a solder pad.
This way the firmware is the same but the behaviour depends on solder pads.
-
Or, it is contained within the firmware, and the firmware has the ability to detect what console it is on. Probably what you were thinking. Because, as Oliver pointed out, the firmwares were binary the same, they had the same origin F/O , Ecowitt, and probably, because of the agreement between F/O and Ambient, there is only one firmware, but when installed on an Ambient device, the restrictions are enforced.
So, yes there is hardware difference , or boot loader difference on the Ambient, that allows it to be identified as Ambient.
-
Or, it is contained within the firmware, and the firmware has the ability to detect what console it is on. Probably what you were thinking. Because, as Oliver pointed out, the firmwares were binary the same, they had the same origin F/O , Ecowitt, and probably, because of the agreement between F/O and Ambient, there is only one firmware, but when installed on an Ambient device, the restrictions are enforced.
So, yes there is hardware difference , or boot loader difference on the Ambient, that allows it to be identified as Ambient.
I don't think it's that complicated. The device can identify itself by name:
on the "about" page of a HP25x0/WS-n000 console an Ecowitt console will show HP2550, a Froggit console HP1000SE-Pro, an Ambient console WS-2000 or WS-5000 as model. (or WS-2902 for a WH2910).
This information will be accessible to the firmware and can serve as "switch" to check the connected sensors for the "Ambient bit" *) or not;
and if it's Ambient see if the sensor name is in an Ambient sensor list (so far there doesn't seem to be the same name for different sensor models in the Ecowitt, Froggit or Ambient "name spaces" - see matrix).
*) this "bit" maybe a real bit or just an identifier of some sort
but agreed - we are speculating here
-
I looked at the matrix and have a question...can you connect the WH 57 lightning sensor to the older Observer IP (1400)??? I currently have one extra sensor reporting to Ambient weather (WH31p). I was hoping to add the WH57 but unsure if it will work.
Thanks
-
I looked at the matrix and have a question...can you connect the WH 57 lightning sensor to the older Observer IP (1400)??? I currently have one extra sensor reporting to Ambient weather (WH31p). I was hoping to add the WH57 but unsure if it will work.
Thanks
I don't think the old observer IP can receive an Ambient WH31L while the new Observer IP 2.0 would be able to do so.
An Ambient ObserverIP module wouldn't be able to receive an Ecowitt WH57 (general incompatibility between Ambient consoles and Ecowitt sensors --> footnotes to the matrix).
If that OberserverIP 1.0 module is a non-Ambient FineOffset clone (e.g. Renkforce etc.), it could receive Ecowitt sensors, however, I doubt that it can receive sensors beyond the "boat" (WH24), a (up to eight) WH31E/P or a WH65.
And that would have to be a WS-1550 ObserverIP afaik.
For this (i.e. beyond these few also mentioned in the WS-1550 manual) the WiFi model WH2650 would be needed. The old ObserverIP (LAN only) and the old arrays are not in the matrix as that's old hardware.
-
Hello folks,
Thanks for the advice I received on this forum I bought an Ecowitt 2800 which comes with a WH32 outdoor sensor. I'm quite happy with the unit and works flawlessly and now would like to add a couple more sensors.
Could someone advise if the 2800 supports up to three sensors? I am also confused as to which sensor I should buy. On the Ecowitt website now they sell the 2810 with a WH31 but mine came with the 32. What are the differences between the 2810 and 2800?
And should I buy two WH31 or 32? The 31 can only be used indoor? I don't understand the differences between the two. Also on the Ecowitt website it is specified that the 31 supports up to eight channels, but I already have a 32 and there's no mention that the 32 supports multiple channels. So will two 31 be compatible with one 32? my unit is on frequency 433Mhz.
Thank you
-
1. the sensors need to transmit on the same frequency on which the console receives
2. the sensor provided with the WH28x0 is a special WH31 family sensor with an in-built radio time signal receiver.
see https://www.wxforum.net/index.php?topic=40730.0 footnote 28. Sensor #2 and 3 don't need to be of this type - they can be simple WH31 sensors. No WH32. The console doesn't understand a WH32, plus there can only be one WH32 outdoor sensor per console. And the WH32B (indoor) is only meant for HP2550 and WH2650 consoles.
2. Sometimes the extra T/H sensor which comes with a WH2800 console is named WH32F, which is admittedly confusing - but it is a special WH31 only.
WH31 family sensors have DIP switches for channel selection - real WH32 sensors don't have DIP switches.
The special WH31 for WH28x0 consoles sensors have only three channels to choose. They correspond to the normal WH31 channels 1, 2 and 7.
I have a WH2800 (even on 868 MHz, a WH2800 clone model formerly sold under the GARNI brand) and it receives my normal WH31 sensors channel 1, 2, 7.
3. Afaik there are no significant differences between WH2800 and WH2810 ...
EDIT: typo correction
-
Thank you for the reply and explanation.
I believe I have a real WH32, it does not have any DIP switches and it's marked "WH32".
My unit is WN not WH, not sure if there's any difference. And also on the manual there's no mention of the channels but I have the "set/ch" button and I see I have the channel number light, although it is turned off.
I have emailed Ecowitt but I am still confused as what you described doesn't match completely with what I have.
In short I have to buy a WH31, correct?
-
let me check the latest manual to avoid to talk cross-purpose ....
maybe they upgaded their hardware ....
Does your "WH32" not have a little horizontally moveable switch in the battery compartmnet above the batteries ?
Can you post a picture of the opened battery compartment !?
The station naming etc. is a bit confusing - it appears that there are two versions:
WH2800 (or WN2800*) with only one WH32 outdoor sensor
and
WH2810 with maximum three sensors of the infamous WH32F (camouflaged WH31 with DCF) type where also normal WH31 sensors work, only without automatic time correction.
*) for "H", "S" and "N" see the MUST READ thread
-
The strange thing is that mine is the WN2800 with the button clearly marked with CH to change the channel and the channel led.
But the fact that I have the WH32 makes me wonder if the unit really supports channels.
Here's the picture
-
That rather looks like a real WH32 outdoor - does the console receive its readings and displays them as outdoor temperatur/humidity ?
-
yes it's does.
-
The FAQ at ecowitt says the 2810 can support additional sensors, not the 2800. Hmmm
-
The strange thing is that mine is the WN2800 with the button clearly marked with CH to change the channel and the channel led.
But the fact that I have the WH32 makes me wonder if the unit really supports channels.
Here's the picture
what do you read on the console label ? WH2800 or WH2810 ?
They can be a bit sloppy with their names :sad: -
They may use the same button layout and button labels for both console types.
I guess at the end of the day you will have to try .... (and depending on where you live just buy the piece [WH31] and send it back again if it doesn't work). On the other hand it's a 11 USD piece
-
you are correct, I might have to just by and test, I wanted to buy two units. If I opened the unit is there a way I can figure out if it supports multiple channels?
There is no firmware update for this kind of unit, correct?
-
you won't find anything when you open it - it has a label on the reverse side.
1 or 3 sensors is a firmware thing, not a hardware thing.
And that's not one of the more "professional" private weather stations of Ecowitt - it's just a temperature/humidity/barometer piece.
Nothing much to be expected from it.
Even the simpler (basic sensors rain, wind, solar, temp, hum only) weather stations like a WS2320E or a WH2910 don't have the possibility of firmware upgrade either.
Only the more sophisticated and powerful model do.
I wanted to buy two units
I guess you mean two WH31 ;)
-
yes I meant two WH31 :grin:
So what are the sensors that come with the WH0310/WH0270? Are those comparable to WH31 in terms of quality and precision? It seems they have a radiation shield for outdoor use.
-
I have no idea what these WH53 sensors are - anyhow they are only for these mini consoles
these are not weather stations, just displays for single sensors - and the WH5 are not compatible with the fully fledged weather consoles.
-
information on the newly released WFC01, the intelligent IoT water timer (valve) has been added to the MUST READ thread, chapter 16
https://www.wxforum.net/index.php?topic=40730.0
-
Supposedly the latest firmware for the HP3500 1.7.2 supports the WS90.
-
correct - matrix updated
the max sensor per console table was already updated 8-)
-
Okay I thought I knew what the +/- symbols meant, but what does RED mean? newly changed? and what's a red X vs a black - ?
-
Okay I thought I knew what the +/- symbols meant, but what does RED mean? newly changed? and what's a red X vs a black - ?
red is supposed to mean "-" and green "+" (and, admittedly, there were 3-4 red "+" which sneaked in without explicit 'permission' - will be corrected with the next update)
in the application columns "+" and "-" are all black -
in other places I don't find any more "black sheep", and "X" I couldn't find either (maybe I'm blind and don't see the wood for the trees)
at least not in the console/sensor compatibility matrix
but if there still is/are one/some, a more detailed hint would be appreciated
-
WS90/HP3501 RED +
WS68/ObserverIP BOLD RED - (vs non bold -)
LeafSensor/HP3501 BOLD RED X
-
WS90/HP3501 RED +
WS68/ObserverIP BOLD RED - (vs non bold -)
LeafSensor/HP3501 BOLD RED X
should be settled by now - maybe I'm a bold guy .... \:D/
-
I see that section 2.3 shows the SensorID menus for Ecowitt and Garni. Although the Ecowitt has the "Boden" name bug, maybe we should update that. And maybe also show an Ambient screen as well.
-
Section 15: Has anyone noticed a file 20YYMMWS90-A.CSV, 20YYMMWS90-RF-A.CSV and ditto for both for WS80?
Its in the code:
F:\Init.txt
F:\FactoryInit.txt
F:\20%02d%02dA.CSV
F:\20%02d%02dAllsensors_A.CSV
F:\Backup-A.CSV
F:\20%02d%02dWS90-A.CSV
F:\20%02d%02dWS90-RF-A.CSV
F:\20%02d%02dWS80-A.CSV
F:\20%02d%02dWS80-RF-A.CSV
F:\user.bin
F:\factory.bin
%02d is formatting (integer, 2 digits, left padding with zeros). Also, Don't expect your backups to be named properly after 2099, :lol:
-
will check once I'm close to my console again 8-) - mine should show ...(if this text is meant for the general firmware version)
-
Dear all,
Can someone suggest a console with a display that can accept multiple temperature/humidity sensors, at least 4/5?
It would nice if the time and date would be synchronized with radio signal so I don't have to set it every time the power goes out.
Thanks
-
did you read the MUST READ thread ?
https://www.wxforum.net/index.php?topic=40730.0
it appears to me that not - otherwise this question wouldn't have come ...
there are at least two tables/matrices which show how many T/RH sensors can be read by which console
and one table which shows which and how many can be displayed by which console
the consoles which can have one outdoor T/RH sensor [WH32 outdoor or T/RH sensor of an array] (only one can be the official outdoor T/RH sensor) and up to 8 so-called extra T/RH sensors (WH31 family) and have a display to show them are:
HP25x0, HP350x, WN19x0
-
Thank you for your message. I have actually started with that table but to be honest I got overwhelmed quite quickly.
There are three WN19xx and WN18xx which seem quite similar, maybe only difference is touch screen.
The HP35xx has smaller screen and no touch screen so it's cheaper than HP25xx.
I am surprised that the LCD screen consoles are much cheaper than the HP26xx or HP25xx.
Do you know why? Which one is better?
-
it's not HP26xx and HP25xx - it's HP25x0: HP2550 and HP2560 (--> MUST READ)
they are more expensive, because
- their screen is bigger (--> MUST READ, chapter 1 footnote 16)
- they have a (higher quality) TFT screen
for the differences between HP2550 and HP2560 see MUST READ chapter 2
better ? that's a context dependent question => no absolute answer possible
I personally prefer and have the HP2550 which comes with a separate indoor T/RH/P sensor.
-
There are no touch screen units, there is one touch button unit which I find a bit sensitive.
-
There are three WN19xx and WN18xx which seem quite similar, maybe only difference is touch screen.
the WN18xx consoles are more indoor focussed - they don't show Wind, Rain and Pressure on their display but have an extra inbuilt CO2 sensor.
what do they have in common with the WN19xx consoles:
a) no display of solar/UV readings
b) no display of WH41/43 PM2.5 air quality sensors
c) no display of data of the WH45 air quality 5-in-1 indoor sensor
d) local GW1000 API (i.e. the data of ALL sensors connected to the console, also not displayed sensor data, can be read via the local Ecowitt Gateway API (aka "GW1000 API") --> MUST READ
e) data of all connected sensors will be posted to ecowitt.net and displayed there (provided the console is registered under one's account and the posting has been activated via the WS View Plus app or via WebUI).
No touch screen with any console - only touch buttons instead of mechanical buttons with the WN182x, WN1980 and HP2560 consoles.
By the way - this can all be seen comparing the specifications/descriptions on www.ecowitt.com
on shop.ecowitt.com is even a compare function available - or you check our matrix
-
Thank you for the info. I understand that I MUST READ but you can concede that there's a lot of models and small differences between models, which you explained in a more intuitive way than the matrix.
I have used the comparative tool on Ecowitt but frankly is quite useless, the information are not thoroughly filled, and I am not making things up, on the comparator it clearly says TOUCH on ecowitt website for WN1980. Also on the Amazon Ecowitt shop it says clearly "touch display" for the HP2561 MUST READ :-P
The description of the HP2560 is also useless on their website, it basically doesn't say anything.
https://ibb.co/PQN2f0M
(https://ibb.co/PQN2f0M)
I am trying to understand the GW1000 API, does that allow to connect a DIY built sensor to the console? I would like to make my own air quality sensor.
-
There are no touch screen units, there is one touch button unit which I find a bit sensitive.
Thanks, please see my post, this is not clear at all on two different pages, on Amazon it says "touch screen". So you prefer the unit with the mechanical buttons? I wonder if the mechanical buttons are more durable.
Is it possible that in the 2560 they also improved some other hardware?
-
There are no touch screen units, there is one touch button unit which I find a bit sensitive.
Thanks, please see my post, this is not clear at all on (1) two different pages, on Amazon it says "touch screen". So you prefer the unit with the mechanical buttons? I wonder if the mechanical buttons are more durable.
(2) Is it possible that in the 2560 they also improved some other hardware?
(1) you have to understand Chinese English - it's touch buttons only and that's what they mean
(2) no - (--> MUST READ) - there are differences but imo not really improvements
even the new WiFi modem is now in both consoles, HP2550 and HP2560. Just read the MUST READ thread chapter 2
Among all complaints regarding different hardware I didn't see any complaint about mechanical buttons of the HP2550 console being broken. Anyhow, you are usually not pressing them every day 8-).
The local Ecowitt Gateway API is meant to retrieve data or to configure the console - not for adding non-Ecowitt sensors.
That's clearly written in the MUST READ thread
The API serves various purposes:
1. request device information (device type/name, firmware version, RF reception frequency)
2. retrieve and add/change posting to weather networks (Ecowitt, Weather Underground [WU], WeatherCloud, WOW and a freely customized server address/domain, path, port and posting interval)
3. retrieve and add/change sensor calibration offsets or gain factors
4. register or disable sensors
5. retrieve information about registered sensors and their battery charge status
6. retrieve information of console/gateway runtime since last reboot
7. retrieve sensor readings (observations) on request
8. initiate a reboot of the console/gateway
-
There are no touch screen units, there is one touch button unit which I find a bit sensitive.
Thanks, please see my post, this is not clear at all on two different pages, on Amazon it says "touch screen". So you prefer the unit with the mechanical buttons? I wonder if the mechanical buttons are more durable.
Is it possible that in the 2560 they also improved some other hardware?
I stand corrected. There is more than one unit with touch buttons/ keys … the WN1980 and 2560.
Perhaps you should start a thread with what you are looking to do and we can help point you to a specific model.
-
wxfan -
The GW1000 API is for writing your own software to receive the sensor data from the Ecowitt gateways, which in turn get that data via RF transmissions from the actual sensors. If you build a DIY sensor and wanted the data displayed on an Ecowitt console, you would have to replicate the RF transmissions somehow.
With some work and possible programming, you can get the data from the gateway via API or custom server function and display that data on a web page or a tablet (search for the app Personal Weather Tablet) which would be much more customizable than a weather station console. I mention the PWT app as an example. I have not personally tried it and therefore cannot endorse it.
-
There are no touch screen units, there is one touch button unit which I find a bit sensitive.
Thanks, please see my post, this is not clear at all on (1) two different pages, on Amazon it says "touch screen". So you prefer the unit with the mechanical buttons? I wonder if the mechanical buttons are more durable.
(2) Is it possible that in the 2560 they also improved some other hardware?
(1) you have to understand Chinese English - it's touch buttons only and that's what they mean
(2) no - (--> MUST READ) - there are differences but imo not really improvements
even the new WiFi modem is now in both consoles, HP2550 and HP2560. Just read the MUST READ thread chapter 2
Among all complaints regarding different hardware I didn't see any complaint about mechanical buttons of the HP2550 console being broken. Anyhow, you are usually not pressing them every day 8-).
The local Ecowitt Gateway API is meant to retrieve data or to configure the console - not for adding non-Ecowitt sensors.
That's clearly written in the MUST READ thread
The API serves various purposes:
1. request device information (device type/name, firmware version, RF reception frequency)
2. retrieve and add/change posting to weather networks (Ecowitt, Weather Underground [WU], WeatherCloud, WOW and a freely customized server address/domain, path, port and posting interval)
3. retrieve and add/change sensor calibration offsets or gain factors
4. register or disable sensors
5. retrieve information about registered sensors and their battery charge status
6. retrieve information of console/gateway runtime since last reboot
7. retrieve sensor readings (observations) on request
8. initiate a reboot of the console/gateway
Thank you. But then consoles without the API such as the HP2560 can't do those things? I am surprised that what should be the top of the line console doesn't have API. How would we do those things on the HP2560?
-
the local Ecowitt Gateway API was mainly built for gateways - the design of the HP2550/HP2560 is older
you can get all values from a HP25x0 console by having it post its observation via the custom server function or by using the http-API. Other actions you can do with button on the displayed interface pages.
As a displayless console/gateway doesn't have this possibilities, the local Ecowitt Gateway API was created.