The one I listed above is specifically designed to have UPS functionality. It lasts several hours running a GW1000 only, Ive not run it to flat and annoyingly I cant see the lights to show the battery level with the GW1000 plugged in directly as the device obscures the level LEDs. But thats easily fixed with a short extension cable.I tested mine with a GW1000 and it lasted 61hours
I looked into various power cell solutions but they generally have issues as not designed for UPS scenarios e.g. do they continue to supply USB power when mains switched on and off repeatedly.
↧
Re: WS-1001 Current Consumption and UPS
↧
Re: Inside temperature problem
Hey guy, little update on my problem.
I just received new T-H sensor which is displaying correct temperature but I figure it out that I still need old T-HP sensor as without it I don't have pressure reading. I am in process of returning sensor to seller, which is going slow due to Covid restrictions, reason that I live outside of EU and fact that seller is not speaking English very well so we have little difficulties in communication.
I am sending him tomorrow my old defective sensor and I hope that it will be accepted to be replaced under warranty but I in case that things go wrong way is there special sensor just for pressure? I see that Froggit is offering only DP50 which is not measuring pressure and I can't find any other sensor alone or in combination with other sensor that measure pressure.
I just received new T-H sensor which is displaying correct temperature but I figure it out that I still need old T-HP sensor as without it I don't have pressure reading. I am in process of returning sensor to seller, which is going slow due to Covid restrictions, reason that I live outside of EU and fact that seller is not speaking English very well so we have little difficulties in communication.
I am sending him tomorrow my old defective sensor and I hope that it will be accepted to be replaced under warranty but I in case that things go wrong way is there special sensor just for pressure? I see that Froggit is offering only DP50 which is not measuring pressure and I can't find any other sensor alone or in combination with other sensor that measure pressure.
↧
↧
Re: Inside temperature problem
So they sent you a WH31 instead of WH32B ![#-o]( "d'oh!")
↧
Re: Inside temperature problem
I didnt explain correctly:
I decided to buy new sensor while waiting to see what will happen with my old - defective one. As it costs 15eur I decided to buy new and in case that I succeed in replacing defective one I would have two working sensors as I need two (one for my balcony)
And when I was buying new one I just disnt pay enough attetion that it dont have pressure sensor and I realize ot it today when I connected new sensor.
So i am seeking sensor for pressure that I can buy in casr that froggit refuse to exchange my defective sensor.
I decided to buy new sensor while waiting to see what will happen with my old - defective one. As it costs 15eur I decided to buy new and in case that I succeed in replacing defective one I would have two working sensors as I need two (one for my balcony)
And when I was buying new one I just disnt pay enough attetion that it dont have pressure sensor and I realize ot it today when I connected new sensor.
So i am seeking sensor for pressure that I can buy in casr that froggit refuse to exchange my defective sensor.
↧
Re: Inside temperature problem
I believe that Froggit and other Fine Offset resellers do not list the WH32B as a separate purchase. This is to prevent people from thinking that they can add another WH32B to their system, as you can only have one of these. The purchase of a WH32B is always a special order so you won't find it on a website. When you order a complete station or a console that needs the WH32B it is always included...and often not mentioned....it just comes with it. But no matter how many consoles you have that need a WH32B, you can only ever use one.
↧
↧
Re: New GW1000 Firmware V1.6.6
Um I've just spotted that I think v1.6.6 has upset the battery level reporting out of the API v0.2.0 (not the customer server / Ecowitt server push). My Weewx loop data from the GW1000-API pull doesn't have it anymore - for any battery levels whatsoever. I get the weather data and sensor signal strength data, just no battery data. I've checked and the customer server data from the FOSHKplugin - that does get it though. Weird. I've posted on the google group for the driver...
I'm getting this out of a direct run of the GW1000-API:
I'm getting this out of a direct run of the GW1000-API:
Code: [Select]
Using configuration file /etc/weewx/weewx.conf
Interrogating GW1000 at x.x.x.x:45000
2021-03-15 19:54:15 GMT (1615838055): UV: 0, co2: 721, co2_24h_avg: 683, dateTime: 1615838055, dayRain: 4.0, daymaxwind: 9.7, extraHumid1: 57, extraHumid17: 53, extraHumid2: 75, extraTemp1: 17.9, extraTemp17: 18.9, extraTemp2: 11.3, inHumidity: 45, inTemp: 21.8, lightning_distance: None, lightning_last_det_time: None, lightning_strike_count: None, luminosity: 0.0, monthRain: 24.0, outHumidity: 84, outTemp: 7.5, pm10: 3.3, pm10_24h_avg: 3.2, pm2_5: 21.0, pm2_51_24h_avg: 24.3, pm2_55: 3.3, pm2_55_24h_avg: 2.6, pressure: 1010.3, rain: None, rainRate: 0.0, relbarometer: 1012.6, soilMoist1: 47, stormRain: 4.0, usUnits: 17, uvradiation: 0.0, weekRain: 5.3, wh26_sig: 4, wh31_ch1_sig: 4, wh31_ch2_sig: 4, wh40_sig: 3, wh41_ch1_sig: 4, wh51_ch1_sig: 4, wh57_sig: 4, wh68_sig: 4, windDir: 279, windGust: 1.0, windSpeed: 0.5, yearRain: 102.6
↧
Re: New GW1000 Firmware V1.6.6
Hi!
I think George (galfert) already wrote there that there were changes in the API access regarding the battery values. There must / will be an update of the weewx driver (as well as other software that accesses the battery values via the API).
Interestingly enough, there is no issue on github yet.
Greetings, Oliver
... links added ...
I think George (galfert) already wrote there that there were changes in the API access regarding the battery values. There must / will be an update of the weewx driver (as well as other software that accesses the battery values via the API).
Interestingly enough, there is no issue on github yet.
Greetings, Oliver
... links added ...
↧
Re: New GW1000 Firmware V1.6.6
Yup, newest firmware removed the old way of getting battery status. For a while now recent firmware supported both methods (old and new) of getting battery status. Now with this latest firmware the old battery reporting method has been removed. This change cleans up the API and makes it much less confusing to deal with as battery status is reported along with each sensors weather data. The old method required a separate battery level routine, and the battery status of all sensors were together in one huge block and it was difficult to deal with because it reported battery level of zero even for sensors that didn't exist (not in use). The new method is much better. But software now needs to catch up to this new method.
↧
Re: New GW1000 Firmware V1.6.6
Yup, newest firmware removed the old way of getting battery status. For a while now recent firmware supported both methods (old and new) of getting battery status. Now with this latest firmware the old battery reporting method has been removed. This change cleans up the API and makes it much less confusing to deal with as battery status is reported along with each sensors weather data. The old method required a separate battery level routine, and the battery status of all sensors were together in one huge block and it was difficult to deal with because it reported battery level of zero even for sensors that didn't exist (not in use). The new method is much better. But software now needs to catch up to this new method.Thanks! Makes sense long term and not critical as all the batteries are reported through Ecowitt.net monitoring anyway. Just messes up my nice dashboard for the time being Ive built off the Weewx loop data... I guess Ill stick myself on the beta roster for Gary then...
By the way, the developer of GW1000 driver for WeeWX (Gary) knows about this (we chatted recently). But like any change...things take time. I'm sure he will get around to whenever he can.
↧
↧
Re: How to directly log data from the Ambient Weather WS-1200-IP / ObserverIP?
by the way, this has all been running smoothly for the last couple of years, but now I have a few RTL-SDR dongles and I've started transitioning to reading the sensors directly by radio. I think the ObserverIP may be obsolete now but even if not, it's always nicer to run your own server.
You need to sniff both 915MHz and 433MHz. If anyone else is looking at this thread again and considering alternative ways to get data, here's the decoded data that rtl_433 returns, to help you decide... (and the uploads to ambient and wunderground).
Mar 14 15:32:09 linux Weather: Sun Mar 14 15:32:09 CDT 2021 station: {"time" : "2021-03-14 15:32:09.404436", "protocol" : 78,
"model" : "Fineoffset-WH24",
"id" : 84,
"battery_ok" : 1,
"temperature_C" : 24.800, "humidity" : 55, "wind_dir_deg" : 14, "wind_avg_m_s" : 3.500, "wind_max_m_s" : 4.480, "rain_mm" : 2028.000, "uv" : 1604, "uvi" : 4, "light_lux" : 57877.000,
"mic" : "CRC", "mod" : "FSK", "freq1" : 914.860, "freq2" : 914.937, "rssi" : -1.623, "snr" : 22.528, "noise" : -24.151}
# neighbour outdoor? Note humidity 127 signifies that the humidity sensor is absent in this device
{"time" : "2021-03-14 16:10:29.147742", "protocol" : 40,
"model" : "Acurite-Tower",
"id" : 10204,
"channel" : "A", "battery_ok" : 1,
"temperature_C" : 24.400, "humidity" : 127,
"mic" : "CHECKSUM", "mod" : "ASK", "freq" : 432.956, "rssi" : -8.766, "snr" : 5.677, "noise" : -14.443}
# freezer
{"time" : "2021-03-14 16:05:51.433011", "protocol" : 41,
"model" : "Acurite-986",
"id" : 7689,
"channel" : "2F", "battery_ok" : 1,
"temperature_C" : -19.444,
"status" : 0, "mic" : "CRC", "mod" : "ASK", "freq" : 432.948, "rssi" : -0.123, "snr" : 15.548, "noise" : -15.670}
# fridge
{"time" : "2021-03-07 14:56:20.326326", "protocol" : 41,
"model" : "Acurite-986",
"id" : 49269,
"channel" : "1R", "battery_ok" : 1,
"temperature_C" : 2.778,
"status" : 0, "mic" : "CRC", "mod" : "ASK", "freq" : 433.938, "rssi" : -0.937, "snr" : 9.229, "noise" : -10.166}
# living room
Mar 14 15:29:43 linux Weather: Sun Mar 14 15:29:43 CDT 2021 indoor1: {"time" : "2021-03-14 15:29:43.164734", "protocol" : 78,
"model" : "Fineoffset-WH32B",
"id" : 110,
"battery_ok" : 1,
"temperature_C" : 25.200, "humidity" : 52, "pressure_hPa" : 1005.600,
"mic" : "CRC", "mod" : "FSK", "freq1" : 914.862, "freq2" : 914.911, "rssi" : -0.138, "snr" : 24.931, "noise" : -25.068}
# back room
Mar 14 15:30:50 linux Weather: Sun Mar 14 15:30:50 CDT 2021 indoor2: {"time" : "2021-03-14 15:30:50.826468", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 224,
"channel" : 2, "battery_ok" : 1,
"temperature_C" : 24.300, "humidity" : 57,
"data" : "b900000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.883, "freq2" : 914.956, "rssi" : -0.131, "snr" : 25.024, "noise" : -25.154}
# bedroom
Mar 14 15:24:38 linux Weather: Sun Mar 14 15:24:38 CDT 2021 indoor3: {"time" : "2021-03-14 15:24:38.699753", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 196,
"channel" : 3, "battery_ok" : 1,
"temperature_C" : 22.600, "humidity" : 57,
"data" : "5500000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.879, "freq2" : 914.929, "rssi" : -0.109, "snr" : 24.401, "noise" : -24.510}
# kitchen
Mar 14 15:29:08 linux Weather: Sun Mar 14 15:29:08 CDT 2021 indoor4: {"time" : "2021-03-14 15:29:08.161605", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 183,
"channel" : 4, "battery_ok" : 1,
"temperature_C" : 27.500, "humidity" : 48,
"data" : "a800000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.875, "freq2" : 914.882, "rssi" : -6.915, "snr" : 17.448, "noise" : -24.363}
192.168.2.240 - - [14/Mar/2021:15:09:50 -0500] "GET /endpoint?
&PASSKEY=...
&stationtype=WS-1501-IP
&dateutc=20210314+20:09:49
&winddir=350
&windspeedmph=6.93
&windgustmph=10.29
&maxdailygust=27.29
&tempf=74.8
&battout=1
&humidity=62
&hourlyrainin=0.00
&eventrainin=0.00
&dailyrainin=0.00
&weeklyrainin=0.07
&monthlyrainin=0.07
&yearlyrainin=1.56
&totalrainin=1.56
&tempinf=77.2
&battin=1
&humidityin=53
&baromrelin=29.43
&baromabsin=29.70
&uv=4
&solarradiation=429.40
&temp2f=75.7...
You need to sniff both 915MHz and 433MHz. If anyone else is looking at this thread again and considering alternative ways to get data, here's the decoded data that rtl_433 returns, to help you decide... (and the uploads to ambient and wunderground).
Mar 14 15:32:09 linux Weather: Sun Mar 14 15:32:09 CDT 2021 station: {"time" : "2021-03-14 15:32:09.404436", "protocol" : 78,
"model" : "Fineoffset-WH24",
"id" : 84,
"battery_ok" : 1,
"temperature_C" : 24.800, "humidity" : 55, "wind_dir_deg" : 14, "wind_avg_m_s" : 3.500, "wind_max_m_s" : 4.480, "rain_mm" : 2028.000, "uv" : 1604, "uvi" : 4, "light_lux" : 57877.000,
"mic" : "CRC", "mod" : "FSK", "freq1" : 914.860, "freq2" : 914.937, "rssi" : -1.623, "snr" : 22.528, "noise" : -24.151}
# neighbour outdoor? Note humidity 127 signifies that the humidity sensor is absent in this device
{"time" : "2021-03-14 16:10:29.147742", "protocol" : 40,
"model" : "Acurite-Tower",
"id" : 10204,
"channel" : "A", "battery_ok" : 1,
"temperature_C" : 24.400, "humidity" : 127,
"mic" : "CHECKSUM", "mod" : "ASK", "freq" : 432.956, "rssi" : -8.766, "snr" : 5.677, "noise" : -14.443}
# freezer
{"time" : "2021-03-14 16:05:51.433011", "protocol" : 41,
"model" : "Acurite-986",
"id" : 7689,
"channel" : "2F", "battery_ok" : 1,
"temperature_C" : -19.444,
"status" : 0, "mic" : "CRC", "mod" : "ASK", "freq" : 432.948, "rssi" : -0.123, "snr" : 15.548, "noise" : -15.670}
# fridge
{"time" : "2021-03-07 14:56:20.326326", "protocol" : 41,
"model" : "Acurite-986",
"id" : 49269,
"channel" : "1R", "battery_ok" : 1,
"temperature_C" : 2.778,
"status" : 0, "mic" : "CRC", "mod" : "ASK", "freq" : 433.938, "rssi" : -0.937, "snr" : 9.229, "noise" : -10.166}
# living room
Mar 14 15:29:43 linux Weather: Sun Mar 14 15:29:43 CDT 2021 indoor1: {"time" : "2021-03-14 15:29:43.164734", "protocol" : 78,
"model" : "Fineoffset-WH32B",
"id" : 110,
"battery_ok" : 1,
"temperature_C" : 25.200, "humidity" : 52, "pressure_hPa" : 1005.600,
"mic" : "CRC", "mod" : "FSK", "freq1" : 914.862, "freq2" : 914.911, "rssi" : -0.138, "snr" : 24.931, "noise" : -25.068}
# back room
Mar 14 15:30:50 linux Weather: Sun Mar 14 15:30:50 CDT 2021 indoor2: {"time" : "2021-03-14 15:30:50.826468", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 224,
"channel" : 2, "battery_ok" : 1,
"temperature_C" : 24.300, "humidity" : 57,
"data" : "b900000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.883, "freq2" : 914.956, "rssi" : -0.131, "snr" : 25.024, "noise" : -25.154}
# bedroom
Mar 14 15:24:38 linux Weather: Sun Mar 14 15:24:38 CDT 2021 indoor3: {"time" : "2021-03-14 15:24:38.699753", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 196,
"channel" : 3, "battery_ok" : 1,
"temperature_C" : 22.600, "humidity" : 57,
"data" : "5500000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.879, "freq2" : 914.929, "rssi" : -0.109, "snr" : 24.401, "noise" : -24.510}
# kitchen
Mar 14 15:29:08 linux Weather: Sun Mar 14 15:29:08 CDT 2021 indoor4: {"time" : "2021-03-14 15:29:08.161605", "protocol" : 113,
"model" : "AmbientWeather-WH31E",
"id" : 183,
"channel" : 4, "battery_ok" : 1,
"temperature_C" : 27.500, "humidity" : 48,
"data" : "a800000000", "mic" : "CRC", "mod" : "FSK", "freq1" : 914.875, "freq2" : 914.882, "rssi" : -6.915, "snr" : 17.448, "noise" : -24.363}
192.168.2.240 - - [14/Mar/2021:15:09:50 -0500] "GET /endpoint?
&PASSKEY=...
&stationtype=WS-1501-IP
&dateutc=20210314+20:09:49
&winddir=350
&windspeedmph=6.93
&windgustmph=10.29
&maxdailygust=27.29
&tempf=74.8
&battout=1
&humidity=62
&hourlyrainin=0.00
&eventrainin=0.00
&dailyrainin=0.00
&weeklyrainin=0.07
&monthlyrainin=0.07
&yearlyrainin=1.56
&totalrainin=1.56
&tempinf=77.2
&battin=1
&humidityin=53
&baromrelin=29.43
&baromabsin=29.70
&uv=4
&solarradiation=429.40
&temp2f=75.7...
↧
Re: Inside temperature problem
Ah that clarify lots of things to me, as I was confused because I could not find any pressure sensor to buy.
I will have to get new CH32B (or whatever marking it has) as I now don't have pressure readings and also fields for inside temperature and humidity are blank. I can switch to CH1 and I did it but I don't like that as permanent solution. Will get new CH32B and use this one sensor for temp and humidity for my other room or balcony.
I will have to get new CH32B (or whatever marking it has) as I now don't have pressure readings and also fields for inside temperature and humidity are blank. I can switch to CH1 and I did it but I don't like that as permanent solution. Will get new CH32B and use this one sensor for temp and humidity for my other room or balcony.
↧
Re: 7.1 osprey humidity sensor malfunctioning
Ecowitt gw1000 (or a newer model) and wh25 (external temp/humidity) are the solution.
↧
Re: 7.1 osprey humidity sensor malfunctioning
Ecowitt gw1000 (or a newer model) and wh25 (external temp/humidity) are the solution.WH25 is an old name of the 1st generation of the outdoor Temp/Hum sensor - the new generation and name is WH32.
See our matrix: https://www.wxforum.net/index.php?topic=40730.0
The GW1000 and the WH2650 are technically identical - where the WH2650 is more flexible regarding the inside T&H&P sensor placement (but maybe doesn't look so nice)
https://www.wxforum.net/index.php?topic=40970.0
So the suggestion is a GW1000 (WH2650) and a WH32. The WH32 is not easy to get alone (Froggit) - you'd need to order in from Ecowitt in China. (12 EUR). It would overwrite the still working temperature values (in a GW1000/WH2650/HP2551), but not at the console of the WH65, which we don't know what it is (maybe a WH3000SE, WH4000SE, ...?? - the original poster (OPer) wasn't clear here) and whether he wants to keep it or not.
So, depending on what the OPer wants, to get the SBS-WS-600 (=Froggit HP1000SE Pro at a 30 EUR cheaper price and longer warranty) might be the best solution for him.
Otherwise, a GW1000 plus a Wh32 from Ecowitt (50 USD, 46 EUR) from Ecowitt in China, is the cheapest version - but also the most time consuming.
My suggestion is imo the financially least expensive and at the same time most rewarding solution (apart from the tinkering approach)
if the goal is to optimize and not to maximize the saving.
↧
↧
Re: 7.1 osprey humidity sensor malfunctioning
Thanks for the quick reply both. So it seems just replacing the H sensor isn't an option, pity, was hoping it was plug and play and the thing only costed a few bucks . I like the fact that with the single unit it has the solar panel and I don't have to worry about its power reserve for a very long time, that was the difference which made me decide to buy it Vs separate sensors for everything. So while the gw1000 is an attractive alternate I'll stick with the single unit. If anyone has a wh65 laying around o could buy for a fair price or trade with my old wh65 old say so ![:)]( "Smile")
.
@gyv quite frankly I'm not sure what the official model is I got. It's sold here by reseller Hesdo as an Alecto ws5500. The model resembles the Y shaped 7 in 1 sensor unit I saw on the pictures, it came together with its indoor station (the multicoloured led one)
.@gyv quite frankly I'm not sure what the official model is I got. It's sold here by reseller Hesdo as an Alecto ws5500. The model resembles the Y shaped 7 in 1 sensor unit I saw on the pictures, it came together with its indoor station (the multicoloured led one)
↧
Re: 7.1 osprey humidity sensor malfunctioning
It's then probably a WH3000SE in Froggit terms - or a WH2910 in Ecowitt terms.
In my suggestion you would get your sensor osprey array exchanged, could read everything as you did before - and have in addition the possibility to add more, different sensors which the WH2910/WH3000SE doesn't support through the WH2650 console.
So, a single unit (sensors) and a GW1000/WH2650 (console) do not exclude each other![8-)]( "Cool")
In my suggestion you would get your sensor osprey array exchanged, could read everything as you did before - and have in addition the possibility to add more, different sensors which the WH2910/WH3000SE doesn't support through the WH2650 console.
So, a single unit (sensors) and a GW1000/WH2650 (console) do not exclude each other
↧
Re: 7.1 osprey humidity sensor malfunctioning
If anyone has a wh65 laying around o could buy for a fair price or trade with my old wh65 old say so1. where do you live ?.
2. what do you consider a fair price ? (plus shipping)
3. I have a brand new spare WH65 which I can sell - if interested, PM me.
↧
conversion soil moisture percent (WH51) to cb (Watermark)
Hi!
The Ecowitt WH51 soil moisture sensor sends its data as a percentage value 0-100, where 0 is dry and 100 is saturated.
Has anyone ever tried to convert to centibar in order to enable a comparison with the watermark sensors? For them the scale goes from 200 (dry) decreasing to 0 (saturated).
I have a weather service that expects the data in cb and I would also like to supply them with the data from my soil moisture sensors.
Can a simple linear conversion 200-wh51value * 2 work there?
Does anyone have more information about the WH51 measurement method?
Capacitive? FDR? TDR? Guess?
Regards, Oliver
The Ecowitt WH51 soil moisture sensor sends its data as a percentage value 0-100, where 0 is dry and 100 is saturated.
Has anyone ever tried to convert to centibar in order to enable a comparison with the watermark sensors? For them the scale goes from 200 (dry) decreasing to 0 (saturated).
I have a weather service that expects the data in cb and I would also like to supply them with the data from my soil moisture sensors.
Can a simple linear conversion 200-wh51value * 2 work there?
Does anyone have more information about the WH51 measurement method?
Capacitive? FDR? TDR? Guess?
Regards, Oliver
↧
↧
Re: Soil Temperature & Water Temperature Sensor Pictures
A little more information on the soil and temp sensor.
It really is nearly ready for those keen and waiting!
It is planned to be listed on the website by Easter and I should have a review of both as soon as possible (transit delays permitting).
It really is nearly ready for those keen and waiting!
It is planned to be listed on the website by Easter and I should have a review of both as soon as possible (transit delays permitting).
↧
Re: conversion soil moisture percent (WH51) to cb (Watermark)
It should be capacitive ( my guess ) as the exposed pcb is non conductive.
↧
Re: conversion soil moisture percent (WH51) to cb (Watermark)
It also depends on what the WH51 percentage means, is it the VVC where 0%= dry, and 100% =saturated, or is it a soil saturation percentage using some "typical" soil porosity value?
I found this page helps explain it a bit (it uses the kPa rather than cB though).
https://www.metergroup.com/environment/articles/what-is-soil-moisture-science-behind-the-measurement/
I found this page helps explain it a bit (it uses the kPa rather than cB though).
https://www.metergroup.com/environment/articles/what-is-soil-moisture-science-behind-the-measurement/
↧