Hello Arthur!

Many thanks for all of the great work that you've done on your weewx driver 
for Relko Vazic's ATMOCOM <https://atmocom.com/> device (currently in 
beta). Your driver has been running steadily since earlier this week!

[image: weewx up 4d13h.PNG]


The Atmocom device is still in beta, and as far as I'm aware of, a single 
device is not intended for multiple weather stations; just one weather 
station per one Atmocom device.


KMEELLSW50 
<https://www.wunderground.com/personal-weather-station/dashboard?ID=KMEELLSW50>

I've been testing the device since its arrival last month from Spain with 
the Ambient Weather WS-2000. The WS-2000 has been sending data to Weather 
Underground since 2019015 starting around 17:00 UTC-5. The WS-2000 has 
received three firmware updates for its Display Tablet; i.e., 1.2.1 -> 
1.3.5 on 20190115 when it arrived; 1.3.5 -> 1.3.7 on 20190116; and 1.3.7 -> 
1.3.8 on 20190124. That update process requires a power cycle before SD 
card insertion, and after SD card insertion. The WS-2000 has also received 
three firmware updates for its WiFi; 4.0.2 -> 4.0.9 on 20190116; 4.0.9 -> 
4.1.0 on 20190121; and 4.1.0 -> 4.1.1 on 20190124. That update process 
requires the devices (phone running awnet app and the console) to be on the 
same subnet, and I would power cycle the Atmocom device afterwards. Note 
that it's a painstaking method each time switching back and forth between 
SSIDs as the WS-2000 has a clunky way to enter alpha-numeric strings, and 
no facility of saving SSID and their associated passwords. Needless to say, 
there have been data flow interruptions caused by these updates to the 
WS-2000 and is important to keep in mind when subsequently combing through 
its data.


Kind regards,

Kelly
-- 
V. Kelly Bellis, PLS
17 Union Street
Ellsworth, ME 04605




On Saturday, February 16, 2019 at 5:42:47 PM UTC-5, Arthur Emerson wrote:
>
> I have forked v1.03 of my WeatherFlow UDP station driver, and used it as 
> the base for a new Atmocom interceptor UDP driver that I just committed as 
> v1.00 to GitHub:
>
> https://github.com/captain-coredump/weewx-atmocom-udp/
>
>
> I made one huge improvement with this new driver: "wee_config 
> --reconfigure" is fully supported...with a complete dialog for setting 
> every option...and even builds a simple sensor_map for decoding Weather 
> Underground packets!  (I promise to back-port this feature to the WF driver 
> in the near future.)
>
>
> The README file contains simple installation instructions, and also 
> explains the sensor_map feature and configuration.  *Without a proper 
> sensor_map in weewx.conf, this driver will not log ANY data!*  The 
> sensor_map concept was borrowed from Matthew Wall’s weewx-SDR driver.  I 
> enjoyed the hours that I spent writing the README file to explain 
> everything, and hope that you enjoy reading it just as much when setting up 
> this driver on your own system.
>
>
> Before you curse me out for the added complexity of the sensor_map 
> feature, let me explain the rationale.  I believe that the Atmocom 
> interceptor device can re-broadcast observations from multiple stations, 
> and want to provide the end user with the ability to mix-and-match 
> measurements from multiple units if they have them.  Plus, stations can 
> send data to multiple web services, and having the sensor_map being 
> configurable will let someone do something like log outdoor measurements 
> from Weather Underground updates but indoor measurements from Ambient 
> Weather updates.
>
>
> I do not own an Atmocom interceptor device or station that could even use 
> it, so most of my personal testing was done on self-generated UDP packets.  
> The WeatherFlow UDP driver on which this is based has been running for 
> almost a year now at multiple locations around the world with no 
> reliability issues, so I do not anticipate any huge problems.
>
>
> Note that I have not tested against live hardware for rain accumulation 
> correctness.  If anyone finds a problem, please submit an issue in GitHub.
>
>
> If deemed worthy, can someone please add it to the wiki and wherever 
> third-party drivers are listed?
>
>
> My usual disclaimer applies.  I am not a programmer by trade, and did not 
> sleep in a Holiday Inn Express last night.  Please let me know via GitHub 
> if you find any bugs.  Enjoy.....
>
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to