The Envoy is functionally identical to the VP2, which is why it reports
itself as a VP2. I'm not as confident about the WLIP, but I think it's the
same way.
On Sat, May 14, 2022 at 8:52 PM Ryan Stasel wrote:
> so I have another Envoy, and a Weatherlink IP... and I'm trying to get it
>
ay 16, 2022 9:41 AM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Just flipped drivers to Vantage, two questions
>
>
>
> Skins are left untouched by upgrades.
>
>
>
> The ET is probably being calculated in software. Try setting to hardware:
>
>
>
: weewx-user@googlegroups.com On Behalf Of
Tom Keffer
Sent: Monday, May 16, 2022 9:41 AM
To: weewx-user
Subject: Re: [weewx-user] Just flipped drivers to Vantage, two questions
Skins are left untouched by upgrades.
The ET is probably being calculated in software. Try setting to hardware
Skins are left untouched by upgrades.
The ET is probably being calculated in software. Try setting to hardware:
[StdWXCalculate]
[[Calculations]]
...
ET = hardware
I am reluctant to allow users to set hardware types to arbitrary values
through weewx.conf because 1) it second guesses
Hi Tom,
Sorry, I thought the mis-identification was why ET was showing in WeeWX
(though the Vue doesn't provide that information), so it's just stuck at
0.0.
I can certainly modify the skin, but will that not revert on update?
On Monday, May 16, 2022 at 9:09:53 AM UTC-7 tke...@gmail.com
I'm not sure why this matters. The identification is only for the tag
$station.hardware. Otherwise, it is ignored.
If you want your skin to say "VantageVue" (or, for that matter, anything
else), just replace "$station.hardware" with your preference.
Or, am I missing something?
On Mon, May 16,
Howdy Tom,
So after asking on the wxforum, it sounds like for an Envoy, the station
SHOULD be set to Vantage Pro, even if it's talking to a
Vue: https://www.wxforum.net/index.php?topic=43911.new;topicseen#new
So, seems like there might be something we need to do for the Envoy console
with a
so I have another Envoy, and a Weatherlink IP... and I'm trying to get it
configured, but for some reason, the Envoy (and Weatherlink) are convinced
I have a Vantage Pro2... setting it to a Vue it complains that it found a
Pro... =/
Ticket in with Davis support, but would be curious if anyone
hmm. weewx (possibly) has no lead to the MB crashing twice. so going to
flip back to ambientweatherapi extension for a bit until I can figure
out...
Thank you sir!
On Friday, May 13, 2022 at 3:04:28 PM UTC-7 Ryan Stasel wrote:
> 1. totally fair. guessing he's not going to agree. lol. On MB
1. totally fair. guessing he's not going to agree. lol. On MB you just say
"Vantage" and that covers Pro, Pro2, Vue, and Envoy.
3. I'm still seeing in weewx generated HTML on occasion an "Unknown" for
batt info (after changing archive interval to 5mins). It seemed like those
were in LOOP
1. Yours is a non-standard setup. I'd rather that the MB dev fixed his
implementation.
2. That makes sense.
3. With a 60 second archive interval, it's possible that the console will
occasionally not have seen the battery info, so it shows as N/A. With a 5
minute interval, it should consistently
Thanks Thomas. debug shows:
May 13 10:21:22 raspi-server-misc weewx[6626] DEBUG weewx.drivers.vantage:
Opened up ethernet host 10.0.6.22 on port 2. timeout=4.0,
tcp_send_delay=0.5
May 13 10:21:22 raspi-server-misc weewx[6626] DEBUG weewx.drivers.vantage:
Gentle wake up of console
1. The hardware type is determined by the WRD command. You can check what
it's returning by setting debug=1, then restarting. Look at the log. The
hardware type will be listed and look something like:
May 12 15:22:59 nuc weewx[91691] DEBUG weewx.drivers.vantage: Hardware type
is 16
For whatever
Ah, I see why the noise is there...
May 11 12:48:27 raspi-server-misc weewx[13000] ERROR weewx.engine: The
archive interval in the configuration file (300) does not match the station
hardware interval (60).
May 11 12:48:27 raspi-server-misc weewx[13000] INFO weewx.engine: Using
archive
To be clear, I have "model_type" set to 2 rather than 1. But neither are
the Vue, so I'm not sure if that matters or not. If I just comment that
line out, will it try to figure it out on it's own? There's no
documentation on that parameter in the docs that I can find.
On Wednesday, May 11,
Thanks Thomas. I was looking through the Vantage driver, and was curious if
there was a way to just "force" Vue. Saw something about setting the value
to 17, but not sure that is accurate. Does it read that value out of the
Envoy EEPROM? I can inquire with the MB developer and see if they have
1. I'm afraid I can't offer an opinion on this, because your arrangement is
so non-standard. Normally, the station type is read out of EEPROM.
2. After 30 days, the logic in the skin gives up and figures the sensors
are gone. So, you can either wait that long, or pare down the list of
sensors in
Hi All,
I just flipped drivers to the Vantage driver (having previously used the
ambientweatherapi driver). I have two questions.
1. My page now thinks I have a Vantage Pro 2 rather than a Vue. I'm
interfacing over "ethernet" to a Meteobridge Nano SD in an Envoy. Is there
a different value I
18 matches
Mail list logo
