I see that the new firmware has arrived. GW3000A_V1.0.1 On Tuesday, February 18, 2025 at 5:21:55 PM UTC [email protected] wrote:
> In the mean time my GW3000 is installed already in my test environment, so > if there is anything I can help with, let me know. I've got no problem even > with a still-not-ready, potentially buggy, bleeding edge version of the > driver in my test environment. > > steepleian schrieb am Montag, 17. Februar 2025 um 13:22:43 UTC+1: > >> Good news indeed. Thank you for your update. >> Ian >> https://claydonsweather.org.uk >> >> On 17 Feb 2025, at 10:50, 'Rainer Lang' via weewx-user < >> [email protected]> wrote: >> >> >> >> Ecowitt has confirmed that the missing piezo data, the WH7 time stamp of >> the last lightning event and the LDS01 depth will be added to the SD card >> data with the next firmware for the GW3000 and WS6210. >> >> @Gary: the header text now contains for temperatures a one-character >> representation of °C and F - this will become two letters/characters "°" >> and "C" resp. "F" >> >> All the LDS values have already been added to the WiFi firmware of the >> other consoles (those which have two firmwares) for the Customized Server >> and for those people using the Interceptor driver it can now also be >> retrieved >> (of course you have to use an extended version of the driver and not the >> "barebone" version at GitHub - that could get an update with all now >> existing sensors and values ...) >> The world has significantly changed in the past years ... there are user >> created (tested and working) complete versions available though >> Gary's local API driver looks up to date (probably LDS01 to be added) >> On 13.02.2025 09:23, Rainer Lang wrote: >> >> there are a few more things to be considered from the bigger perspective >> with the GW3000 >> - some referring to the SD card archiving of also other sensor values >> (e.g. LDS01, WH57 ...), the file name change etc - all needs to be >> streamlined - already a few things were sorted with the last firmware >> upgrade >> - some referring to the customized server posting >> >> The WiKi is quite up to date regarding the expected-to-be situation and >> partly also regarding the "missing feature" situation. >> https://meshka.eu/Ecowitt/dokuwiki/doku.php?id=start#gw3000 >> there is a table with the so-far existing observations in the CSV files >> corresponding to the header items - and the known missing ones >> >> all this also needs to be synchronized with the WS6210 console, which is >> the other one having the API accessible SD card option >> >> Some field testing may also be needed >> >> an educated guess would be the end of the month - but they might be faster >> On 12.02.2025 09:17, 'Ian Millard' via weewx-user wrote: >> >> No problem Gary. >> I see that Gyvate has submitted the request to Ecowitt however I have no >> sense on how quickly they can respond. >> Ian >> >> Sent from my iPad. >> >> On 11 Feb 2025, at 10:55, gjr80 <[email protected]> wrote: >> >> Thanks for your trouble Ian, I hadn't picked up on the piezo bug. I set >> my GW3000 and WS90 up and let it run for a couple days in December before >> looking at the csv files. Unfortunately those two days had no rain so >> didn't think anything of the lack of rain data. Just looked back over the >> last 7 weeks and no rainfall was recorded in the csv files. >> >> I saw your wxforum post, so I guess we wait. My WH40 is in the mail so I >> guess chances are it will be here before any firmware update is released. >> >> Gary >> >> On Tuesday, 11 February 2025 at 10:47:35 UTC+10 [email protected] >> wrote: >> >>> ...... It does seem however that it only creates columns for the >>> traditional rain gauge and not a piezeo rain gauge, even if priority is set >>> to piezo. I am not sure if this is a bug, an oversight or deliberate. This >>> happens even when the WH40 is disabled. A somewhat disappointing outcome. >>> >>> On Monday, February 10, 2025 at 10:29:25 PM UTC Steeple Ian wrote: >>> >>>> Hi Gary, >>>> >>>> I have the two types of rain gauge and the GW3000 arrived today. >>>> >>>> Attached is a .zip of the 6 CSV files from my SD Card after a few hours >>>> running. >>>> >>>> Regards, >>>> Ian >>>> >>>> >>>> >>>> On Friday, February 7, 2025 at 2:12:04 PM UTC Auchtermuchty Weather >>>> wrote: >>>> >>>>> I have a GW3000 in the UK, Very happy to help if I can. >>>>> >>>>> On Thursday, 6 February 2025 at 04:50:03 UTC [email protected] >>>>> wrote: >>>>> >>>>>> >>>>>> My GW3000 is on the way, so it should arrive in a week or so. >>>>>> gjr80 schrieb am Freitag, 31. Januar 2025 um 08:59:46 UTC+1: >>>>>> >>>>>>> Yes, 433MHz here. I have a WH40 on the way, what's another rain >>>>>>> gauge... >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Friday, 31 January 2025 at 03:14:25 UTC+10 [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> I just ordered a GW3000, but it won't ship before March. >>>>>>>> >>>>>>>> [email protected] schrieb am Dienstag, 28. Januar 2025 um >>>>>>>> 07:10:54 UTC+1: >>>>>>>> >>>>>>>>> >>>>>>>>> I have a spare WH40 for 868MHz, but you are not in Europe, are >>>>>>>>> you? Too bad the GW3000 868MHz is sold out currently, I won't get one >>>>>>>>> before end of February, I assume. >>>>>>>>> gjr80 schrieb am Montag, 27. Januar 2025 um 21:08:47 UTC+1: >>>>>>>>> >>>>>>>>>> I have the GW3000 and WS90 so have the haptic sensor covered, and >>>>>>>>>> I can surmise the behaviour with a WH40 only, it is just a case of >>>>>>>>>> confirming what happens when both WS90 (or WS85) and WH40 are >>>>>>>>>> present. >>>>>>>>>> Thanks for the offer, but if I don't get any data responses here I >>>>>>>>>> will >>>>>>>>>> likely just buy a WH40 and wait for the couple of weeks for >>>>>>>>>> delivery. >>>>>>>>>> >>>>>>>>>> All going well I hope to have the new driver with backfill ready >>>>>>>>>> for user testing sometime in 2nd half of February. >>>>>>>>>> >>>>>>>>>> Gary >>>>>>>>>> >>>>>>>>>> On Sunday, 26 January 2025 at 18:06:59 UTC+10 [email protected] >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Gary, all I am missing is the GW3000, since I was waiting for >>>>>>>>>>> your updated driver. How about you? If it's the same situation for >>>>>>>>>>> you, >>>>>>>>>>> tell me the shipping address, I'll get you one, as a donation for >>>>>>>>>>> the >>>>>>>>>>> project, or, if you decline, I'll buy one for myself, but it'll >>>>>>>>>>> take a >>>>>>>>>>> while until I'll arrive. >>>>>>>>>>> gjr80 schrieb am Sonntag, 26. Januar 2025 um 04:29:17 UTC+1: >>>>>>>>>>> >>>>>>>>>>>> Posted in weewx-user to canvass a wider audience. >>>>>>>>>>>> >>>>>>>>>>>> I'm developing a new Ecowitt driver based on the so called >>>>>>>>>>>> local device HTTP API. This driver will have catchup on startup >>>>>>>>>>>> via either >>>>>>>>>>>> local device history files (for supported devices) or Ecowitt.net >>>>>>>>>>>> (for >>>>>>>>>>>> devices that upload to Ecwoitt.net). Ecowitt's documentation of >>>>>>>>>>>> the local >>>>>>>>>>>> device HTTP API and GW3000 SD card data files is somewhat limited, >>>>>>>>>>>> so I was >>>>>>>>>>>> hoping for some practical help from an Ecowitt GW3000 user (if one >>>>>>>>>>>> exists) >>>>>>>>>>>> who has both tipping (WH40) and haptic (WS85/WS90) rain gauges >>>>>>>>>>>> connected to >>>>>>>>>>>> their GW3000. >>>>>>>>>>>> >>>>>>>>>>>> What I am after is the header information from the basic sensor >>>>>>>>>>>> CSV file stored on the GW3000 SD card when the GW3000 is connected >>>>>>>>>>>> to both >>>>>>>>>>>> WH40 and WS85/WS90 rain gauges. The basic sensor CSV file name >>>>>>>>>>>> format is >>>>>>>>>>>> YYYYMMX.csv where YYYY is the year, MM is the two digit month >>>>>>>>>>>> number and X is an upper case letter. The basic sensor file >>>>>>>>>>>> can be downloaded via the local device web page or directly in >>>>>>>>>>>> your browser >>>>>>>>>>>> via http://device_ip_address:81/YYYYMMX.csv where >>>>>>>>>>>> device_ip_address is the device IP address and YYYYMMX.csv is >>>>>>>>>>>> the file name as described previously. You can view the availble >>>>>>>>>>>> SD card >>>>>>>>>>>> history files via the device web page or at >>>>>>>>>>>> http://device_ip_address/get_sdmmc_info. >>>>>>>>>>>> >>>>>>>>>>>> The required data does not contain any sensitive info. >>>>>>>>>>>> >>>>>>>>>>>> thanks, >>>>>>>>>>>> Gary >>>>>>>>>>>> >>>>>>>>>>> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/d/msgid/weewx-user/27c66b98-c8be-4c52-93ec-bc34c60ce637n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/27c66b98-c8be-4c52-93ec-bc34c60ce637n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/d/msgid/weewx-user/B854BC65-02F5-47D9-BA6A-6BF480C1C89B%40btinternet.com >> >> <https://groups.google.com/d/msgid/weewx-user/B854BC65-02F5-47D9-BA6A-6BF480C1C89B%40btinternet.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> To view this discussion visit >> https://groups.google.com/d/msgid/weewx-user/f25dbea6-eb22-48d0-8f01-929628903c85%40gmail.com >> >> <https://groups.google.com/d/msgid/weewx-user/f25dbea6-eb22-48d0-8f01-929628903c85%40gmail.com?utm_medium=email&utm_source=footer> >> . >> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/4bc94a91-980e-4bb5-aa77-0e60cb88f442n%40googlegroups.com.
