Re: [weewx-user] FYI: weectl fails to change ISS ID away from 1 on Davis Envoy

['John Kline' via weewx-user]

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, 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⊢ On 16 Aug 2025, at 10:58 pm, 'John Kline' via weewx-user <weewx-user@googlegroups.com> wrote: 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…) On Saturday, 16 August 2025 at 1:00:26 pm UTC+10 Graham Eddy wrote: 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 On Friday, 6 June 2025 at 11:54:46 pm UTC+10 Tom Keffer wrote: I've confirmed this on my own Envoy. I've created issue #1004 to track. On Thu, Jun 5, 2025 at 4:20 PM pannetron <pann...@gmail.com> wrote: 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 -- 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. -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/14ff1957-a60a-41cd-bad5-d3a13dcf6661n%40googlegroups.com. <vp2_chan.txt> -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/D654B3B4-2366-4019-B462-900E8C0D2F92%40johnkline.com. -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/EB68EF97-D1DC-42DC-AF8E-01F27D0F2B0B%40geddy.au. -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/7935EF1E-5E65-4940-8C8F-B217E051C6FA%40johnkline.com.