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⊢ > On 18 Aug 2025, at 3:12 am, 'John Kline' via weewx-user > <[email protected]> wrote: > > 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 <[email protected]> wrote: >> >> 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⊢ >> >>> On 17 Aug 2025, at 12:43 am, Graham Eddy <[email protected]> wrote: >>> >>> 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⊢ >>> >>>> On 17 Aug 2025, at 12:12 am, Tom Keffer <[email protected]> wrote: >>>> >>>> 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. >>> >>> >>> -- >>> 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] >>> <mailto:[email protected]>. >>> To view this discussion visit >>> https://groups.google.com/d/msgid/weewx-user/D12F19B9-E08D-4593-85F3-1D9405D27EA5%40geddy.au >>> >>> <https://groups.google.com/d/msgid/weewx-user/D12F19B9-E08D-4593-85F3-1D9405D27EA5%40geddy.au?utm_medium=email&utm_source=footer>. >> >> >> -- >> 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] >> <mailto:[email protected]>. >> To view this discussion visit >> https://groups.google.com/d/msgid/weewx-user/67E0F108-0905-4D9F-AF3C-71D77EDBD9F1%40geddy.au >> >> <https://groups.google.com/d/msgid/weewx-user/67E0F108-0905-4D9F-AF3C-71D77EDBD9F1%40geddy.au?utm_medium=email&utm_source=footer>. > > > -- > 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] > <mailto:[email protected]>. > To view this discussion visit > https://groups.google.com/d/msgid/weewx-user/A0B554D7-2C85-42E5-83EA-D1959A051753%40johnkline.com > > <https://groups.google.com/d/msgid/weewx-user/A0B554D7-2C85-42E5-83EA-D1959A051753%40johnkline.com?utm_medium=email&utm_source=footer>. -- 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 visit https://groups.google.com/d/msgid/weewx-user/0B54D44A-52BB-46F5-8C8C-B9B5DCDC9556%40geddy.au.
