FYI: weectl fails to change ISS ID away from 1 on Davis Envoy

[pannetron]

My setup is a Vantage Pro2 ISS transmitting to an Envoy connected to a Raspberry Pi5. WeeWX 5.1.0 install went fine with the default station ID (iss_id) set to 1. My neighborhood has another Vantage Pro on ID 1 so I wanted to be a good neighbor and change my station's ID to 5. Using "weectl device --set-transmitter-type=1,10" set the ID 1 device to inactive but left it marked as ISS. Running "weectl device -set-transmitter-type=5,0" returned success but failed to set the type to ISS although it did "activate" ID 5. As a workaround, I connected my Envoy to a PC with Davis software and configured the Envoy for ISS ID of 5. Reattaching the Envoy to the Pi and running "weectl device --info", I now see device ID 5 is active *and* an ISS. After configuring the Envoy with the Davis software, I'm back up and running fine with the station ID set to 5. 

Perhaps there's an issue in "weectl device --set-transmitter-type" commanding the Envoy?

Cheers,

Russ P

Nederland CO

https://panneton.net/weather

[Tom Keffer]

I've confirmed this on my own Envoy. I've created issue #1004 to track.

--
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/b697f571-4774-409f-896e-62ba6313e143n%40googlegroups.com.

[Graham Eddy]

any progress on this? i have a new second ISS tracked on a different VM, dip switch ch2, but “weectl device —set-transmitter-type=2,0” does not work according to “weectl device —info” and weewx on the diff VM is collecting data from the old ISS ch1 not the new one. i cannot use pannetron’s workaround (use a PC to change it) as i don’t have a PC. happy to use “screen” to manually type in the config change, if needs be

[Graham Eddy]

more details attached - showing results from “weectl device” commands and also log from starting weewx with (apparently) all ISSs disabled (but still logging data…)

[John Kline]

I had a look at your attachment.  It is important to realize only one channel can be identified as ISS (that’s not one active ISS, that’s one ISS–inactive and active–both count towards the total of 1).  As such, you have to remove the ISS from channel 1 first.

Given the above, step 3 in your attachment is the interesting one.  That should have worked to remove ISS from channel 1.

I have six envoys and can remove the iss label from a channel on all of them.  I do have a different driver, derived from the vantage driver, but I doubt that would make a difference.

Would you try step 3 a couple of more times to remove the ISS label from channel 1?  No need to go further than removing the label and using —info to see if it is removed.

If that doesn’t work, you could try my driver to make the change (and then put back the vantage driver).

John

On Aug 15, 2025, at 9:41 PM, Graham Eddy <g...@geddy.au> wrote:

more details attached - showing results from “weectl device” commands and also log from starting weewx with (apparently) all ISSs disabled (but still logging data…)

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/14ff1957-a60a-41cd-bad5-d3a13dcf6661n%40googlegroups.com.

<vp2_chan.txt>

[Graham Eddy]

hello john,

i did the following 3 times:

weewx@dev:~/vantage$ weectl device --set-transmitter-type=1,10 --config=weewx.conf

Using configuration file weewx.conf

Using driver weewx.drivers.vantage.

Using Vantage driver version 3.6.2 (weewx.drivers.vantage)

Proceeding will set channel 1 to type 10 (none, inactive), repeater: OFF

Are you sure you want to proceed (y/n)? y

Set channel 1 to type 10 (none, inactive), repeater: OFF

weewx@dev:~/vantage$ weectl device --info --config=weewx.conf

Using configuration file weewx.conf

Using driver weewx.drivers.vantage.

Using Vantage driver version 3.6.2 (weewx.drivers.vantage)

Querying...

Davis Vantage EEPROM settings:

    

    CONSOLE TYPE:                   Vantage Pro2

    

    CONSOLE FIRMWARE:

      Date:                         Nov 12 2019

      Version:                      3.88

    

    CONSOLE SETTINGS:

      Archive interval:             300 (seconds)

      Altitude:                     836 (foot)

      Wind cup type:                large

      Rain bucket type:             0.01 inches

      Rain year start:              1

      Onboard time:                 2025-08-16 23:44:13

      

    CONSOLE DISPLAY UNITS:

      Barometer:                    inHg

      Temperature:                  degree_F

      Rain:                         inch

      Wind:                         mile_per_hour

      

    CONSOLE STATION INFO:

      Latitude (onboard):           +37.6

      Longitude (onboard):          -122.1

      Use manual or auto DST?       AUTO

      DST setting:                  N/A

      Use GMT offset or zone code?  GMT_OFFSET

      Time zone code:               N/A

      GMT offset:                   -8.0 hours

      Temperature logging:          LAST

        

    TRANSMITTERS: 

      Channel   Receive   Retransmit  Repeater    Type

         1      inactive      N         NONE      iss 

         2      active        N         NONE      (N/A) 

         3      active        N         NONE      (N/A) 

         4      active        N         NONE      (N/A) 

         5      active        N         NONE      (N/A) 

         6      active        N         NONE      (N/A) 

         7      active        N         NONE      (N/A) 

         8      active        N         NONE      (N/A) 

...

➔ it persists in having ch1 as 'inactive iss'. which you advise is bad.. could you send me your driver to see if it makes a difference? PM would be fine.

it should not be relevant, but iss_id=2 in my weewx.conf.

cheers

⊣GE⊢

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/D654B3B4-2366-4019-B462-900E8C0D2F92%40johnkline.com.

[John Kline]

Just so we are comparing apples to apples, would you try my driver at:

https://github.com/chaunceygardiner/weewx-vantagenext

You’ll may need to configure the VantageNext section in weewx.conf (but it will look a lot like the vantage section with stuff added).

Then try step 3 again and see if the ISS is removed from channel 1.  If so, then add the ISS to the appropriate channel.

Whether or not this works, remember to uninstall VantageNext and move back to the vantage driver.  The vantage driver is supported by the weewx team.

John

On Aug 16, 2025, at 6:53 AM, Graham Eddy <g...@geddy.au> wrote:

hello john,

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/EB68EF97-D1DC-42DC-AF8E-01F27D0F2B0B%40geddy.au.

[Tom Keffer]

I spent a couple of hours looking at this yesterday and made no progress. The right set of bits seem to be getting sent to the Envoy, yet it does not recognize the ISS. There's something I'm missing in the documentation. I'll keep plugging away at it.

-tk

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/b16780fe-23c5-4605-8915-21e0039fd199n%40googlegroups.com.

[Graham Eddy]

i followed the logic in vantage.py before shouting for help and it all looked fine up to and including the addresses being written to in the EEPROM, but i couldn’t follow the byte-packing of the bits written to EEPROM. i was surprised to see a call at the end of the PROM writing to _setup(), which seemed to read everything back and i thought maybe changes get lost there e.g. timing issue (i am running on a lightly loaded i9)

⊣GE⊢

[Russ Panneton]

FYI, I saw this problem even when using the vantagenext driver. 

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/RT07Vno4nxA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/D12F19B9-E08D-4593-85F3-1D9405D27EA5%40geddy.au.

[Graham Eddy]

installed and reconfigured to use VantageNext driver. unfortunately, no change i.e. ch1 remains ‘active iss’ after three attempts to change via ‘—set-transmitter-type=1,10'

⊣GE⊢

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/7935EF1E-5E65-4940-8C8F-B217E051C6FA%40johnkline.com.

[Graham Eddy]

in Vantage.setTransmitterType(), i inserted 2 sec delays before and after the NEWSETUP command - no improvement, so doesn’t look like timing error

maybe there are significant differences in hardware. i am using a brand, spanking new Envoy + USB Data Logger + ISS ch2 (ultimately replacing my ancient pre-Greentick Envoy and rs232 Data Logger + ISS ch1, which is failing regularly and often)

⊣GE⊢

--
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/D12F19B9-E08D-4593-85F3-1D9405D27EA5%40geddy.au.

[John Kline]

But now you have an easy workaround.

Set the transmitter type for channel 3 to a temp_hum device.  Then remove ISS from channel 1 and add it as channel 2.

Lastly, remove the temp_hum device on channel 3.

On Aug 16, 2025, at 11:11 PM, Graham Eddy <g...@geddy.au> wrote:

in Vantage.setTransmitterType(), i inserted 2 sec delays before and after the NEWSETUP command - no improvement, so doesn’t look like timing error

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/67E0F108-0905-4D9F-AF3C-71D77EDBD9F1%40geddy.au.

[Graham Eddy]

how do i do that? i tried each of:

weectl device --set-transmitter-type=,,3 --config=weewx.conf    # ➔ runtime error

weectl device --set-transmitter-type=1,10,3 --config=weewx.conf

weectl device --set-transmitter-type=1,0,3 --config=weewx.conf

weectl device --set-transmitter-type=1,0,3,0,0 --config=weewx.conf

and none set the temp_hum to ch3 (so i could not then progress to moving iss from ch1 to ch2).

this looks like the same underlying problem as not being able to change ch1.

cheers

⊣GE⊢

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/A0B554D7-2C85-42E5-83EA-D1959A051753%40johnkline.com.

[Tom Keffer]

The channel is the first parameter (not third). Did you see my wiki article on changing the ISS channel?

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/0B54D44A-52BB-46F5-8C8C-B9B5DCDC9556%40geddy.au.

[Graham Eddy]

that worked!

i accept the castigation, noting duckduckgo didn’t find it..

i misunderstood the command syntax in trying to do the workaround myself. i was getting the following (correct) command wrong:

# Temporarily enable a temperature sensor on channel 3:
weectl device --set-transmitter-type=3,1,2

thanks

⊣GE⊢