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
>>>>>
>>>>>
>>>>> 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/7f9d11e0-887a-4fba-916c-d4f401a8e318n%40googlegroups.com.
