thanks for the clarification. i will switch the
protocol to ecowitt, but the more immediate problem
is the UTF-8 error which is now preventing weewx
from starting.
On Sunday, January 17, 2021 at 4:30:38 PM UTC+1
galfert wrote:
This thread started with the discussion being
around the Ambient WS-2902 and that is totally
different despite looking like the same unit.
This is because Ambient is the only Fine Offset
clone reseller that changes the firmware and
they limit options. The Ambient version does not
let you upload to custom server address. The
confusion here is that my response was because I
thought you had and Ambient branded unit. Since
you don't have an Ambient branded unit you do
have the option to send to a custom server using
both WU and Ecowitt protocols. The WU protocol
is limited and only sends the basic set of
sensors. The Ecowitt protocol allows you to send
a lot more optional sensors like PM2.5, soil
moisture, extra temp/hum sensors....etc. But
still you'll have to configure the Interceptor
driver to match the protocol type that you set
in you WH2900C for uploading to your custom server.
The GW1000 though is still a more elegant and
newer solution.
* The newest Ambient WS-2902 firmware finally
after many years does gain the ability to send
to a custom server....BUT it is not WU protocol
and it is not Ecowitt protocol....it is
Ambientweather.net protocol and enough
significant differences that the Interceptor
driver will not work. This newest firmware is
not yet officially supported by Ambient. They
haven't yet release the updated awnet mobile app
to enable turning and configuring this option.
All of these complexities and changing nature of
the situation makes it difficult to explain the
situation to cover all possible scenarios...what
model you have and whom it is from and what
firmware version you are running and all the
different supporting protocols that are possible.
Using pfsense to capture and forward packets is
really unnecessary for anyone with a non-Ambient
WH2900C....as it has a built in simple to
configure "Customized" server upload feature.
On Sunday, January 17, 2021 at 7:32:03 AM UTC-5
[email protected] wrote:
For the record, mine is a Chinese Mi-Sol
WH2900C. It is a copy of the Fine Offset
WH2900 or the Ecowitt WS2950. Indeed, the
unit requires a connection to Ecowitt to set
the Time/Date and automatically downloaded
the EasyWeather 1.56 firmware update from
Ecowitt.
I haven't got the outdoor setup done yet,
while i play with getting the unit up and
running. but Ecowitt, shows my indoor
temperature and pressure on the home page. I
use pfsense so can run a packet capture if
it helps. Since editing the weewx.conf file,
i am getting the utf-8 problem. I guess this
is related to me using European accented
characters in my editors which are UTF-8. So
that leaves me with two questions;
1) how to have it accept the UTF-8 characters
2) you mentioned not getting all the sensor
data, unless using Ecowitt. In view, that i
am. Can you tell me what additional
parameters i need in the config file please.
On Sunday, January 17, 2021 at 9:21:33 AM
UTC+1 S R wrote:
almost there, but now
/usr/local/share/weewx # ./bin/wee_reports
Traceback (most recent call last):
File "./bin/wee_reports", line 103, in
<module>
main()
File "./bin/wee_reports", line 51, in main
config_path, config_dict =
weecfg.read_config(options.config_path,
args)
File
"/usr/local/share/weewx/bin/weecfg/__init__.py",
line 180, in read_config
default_encoding='utf-8')
File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1229, in __init__
self._load(infile, configspec)
File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1287, in _load
content = self._handle_bom(content)
On Saturday, January 16, 2021 at
11:30:28 PM UTC+1 galfert wrote:
Yes the best method when using the
Interceptor is to use the Customized
server settings. The path doesn't
matter. But in some firmware
versions it just couldn't be left
blank or it wouldn't send. So just
put in index.php? for the path.
On Saturday, January 16, 2021 at
3:49:17 PM UTC-5 [email protected]
wrote:
OK. So i am homing in a little
closer here.
I have configured the console to
wunderground and it is working.
Now i need to adjust weewx.conf
with the following, but as the
weewx server is on a different
subnet, i will need to use
listen mode.
[Interceptor]
driver = user.interceptor
device_type = wu-client
If i understand, i can point the
console with a custom config to
my server, and then publish from
my server to wunderground right?
if i do that, what will the path
on weewx for the console?
host: weewx.local.lan
Path: ?
ID: xxxxxx
Key: xxxxxx
also, on a side note. I can't
find the log in freebsd.
On Saturday, January 16, 2021 at
9:17:02 PM UTC+1 galfert wrote:
What I understand you are
saying is that you have a
WH2910 and you want to
interface it with WeeWX.
Since you don't have an
Ambient version you do have
the ability to easily use
the Interceptor driver.
Ambient WS-2902 can't
without a lot of extra work.
You, with the WH2910 can
simply install the WeeWX
Interceptor driver and make
sure your WeeWX config is
set to use the Interceptor
driver with the correct WU
client settings:
[Interceptor]
driver = user.interceptor
device_type = wu-client
...or you can add the
Ecowitt GW1000 driver and
the instead use the GW1000
API driver instead of the
Interceptor driver. This
will allow you to add more
sensors.
On Saturday, January 16,
2021 at 2:54:09 PM UTC-5
[email protected] wrote:
actually, mine is
equivalent to the WH2910
- it is not a case of
getting, i already have
On Saturday, January 16,
2021 at 4:42:53 PM UTC+1
galfert wrote:
You have dug up
quite an old thread.
A lot has changed
since. The
recommendation now
is to just acquire
the Ecowitt GW1000
and use the WeeWX
GW1000 API driver.
The GW1000 will
directly pick up
your sensor data (it
doesn't talk to the
display console...as
it is its own
console). You'll get
a much nicer
experience with the
GW1000, which will
also let you add
extra sensors.
https://github.com/gjr80/weewx-gw1000
<https://github.com/gjr80/weewx-gw1000>
On Saturday, January
16, 2021 at 2:43:44
AM UTC-5
[email protected] wrote:
were you able to
get this to work
in the end. can
you share the
weewx details please
On Saturday,
April 1, 2017 at
4:37:01 PM UTC+2
[email protected]
wrote:
I see that
weewx is
said to
support
the FINE
OFFSET
WH2900 , I
was
wondering if
anyone could
share with
me the
protocol and
port
information
that is in
the driver? I
--
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 on the web visit
https://groups.google.com/d/msgid/weewx-user/ec3d9f49-dec2-4045-9832-9d4d6180e22an%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/ec3d9f49-dec2-4045-9832-9d4d6180e22an%40googlegroups.com?utm_medium=email&utm_source=footer>.
