weewx 4.10.1 Vantage Vue transmitter question

[phxroa...@gmail.com]

I'm having trouble getting my system (Vue sensor package, regular Davis console, weewx on a Raspberry Pi) to use transmitter channel 2.

My station, installed several years ago, has some new neighbors. To avoid all of us using the default channel 1, I changed mine to use channel 2. I changed the channel on the sensor package and the ISS channel in the weewx.conf file. From the console I verified that it was receiving from channel 2 (though I only waited long enough to see the channel show up for one packet).

Somewhere along the way the console seemed to be taking data from someone using channel 1 instead of channel 2. I know because that sensor package runs out of (solar) battery shortly before dawn every day, and comes up again shortly after dawn. This can't be my station as I just inserted a new CR123 battery in the sensor package this week. The station is at a vacation home so I'm only there sporadically.

I login to the Pi remotely and have tried several commands to force the console to pay attention to channel 2 instead of 1. You can see the whole session in the attached log. I seem to have succeeded in deactivating channel 1, but it still shows as an ISS station, and nothing for channel 2. I've restarted the weewx server a couple of times but I seem to only get data from channel 1, which I believe is not my station.

Any thoughts on how to go about debugging this further or fixing it would be very much appreciated. 

[John Kline]

This has come up before.  The straightforward approach doesn’t work, so you’ll have to use the workaround here:

https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#changing-the-iss-channel-using-weectl-device

Note: the above is written with the weewx 5 command weectl.  You’ll have to substitute wee_device for weectl.

On Sep 13, 2025, at 1:19 PM, phxroa...@gmail.com <phxroa...@gmail.com> wrote:



--
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 weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/1e270f49-a3ac-4bcf-a161-f500284b8772n%40googlegroups.com.

<weewx_logs.txt>

[phxroa...@gmail.com]

Inconclusive result. TxID 1 never changes from "iss" and although it shows as "inactive", packets keep showing up. Similarly, TxID 2 is always "active", but shows as "(N/A)". TxID 3 (the spare I chose), did change to and from "iss".

I'll be on site again in a couple of weeks. I'll see if I can upgrade to the current weewx version (and Vantage driver). I'll also be able to bang on the console with fingers to see if I can change it manually (I'll stop the weewx process while doing that).

[Graham Eddy]

i went through this recently - old ISS (and old envoy) on ch1 and new ISS on ch2 (change new envoy from default to ch2).

the sequence of commands in the documented workaround is important:

from a single envoy’s point of view, at all times there must be >0 stations [including standalone sensor stations as well as ISSs] active but <=1 ISSs active.

so on my new envoy:

1. ISS active on ch1
2. added (non-existent) wireless temp sensor station active on ch3 ➔ ISS on ch1, wireless temp on ch3
3. deactivated ISS on ch1 ➔ just wireless temp on ch3
4. activated ISS on ch2 ➔ ISS on ch2, wireless temp on ch3
5. deactivated wireless temp on ch3 ➔ just ISS on ch2

⊣GE⊢