That I have done - as far as I can see, relevant sections of relevant files are comparable. I would be more confident if I didn't have the impression that device handling has some new quirks under Trixie!
On Sunday, March 22, 2026 at 7:01:29 PM UTC-4 Vince Skahan wrote: > Use your old working pi as a reference and compare them line by line. My > guess is you didn’t do whatever initial setup is required so the meteopi > hardware appears as a serial device to the pi os. > > On Sunday, March 22, 2026 at 2:52:14 PM UTC-7 John Smith wrote: > >> Have you set debug=1 in the config file? >> >> Then you need to post, redacted where needed, a full startup log. >> >> On Mon, 23 Mar 2026 at 08:36, 'Peter Fletcher' via weewx-user < >> [email protected]> wrote: >> >>> I am trying to move my 'workhorse' (it runs weewx, as well as a fair bit >>> of home-brew home monitoring and control software) Raspberry Pi 3B to >>> Trixie, and I must confess that I am getting increasingly frustrated with >>> the problems introduced by Debian's assumption that you should be happy to >>> (essentially) recreate your system configuration from scratch every 2 years >>> for the new release. I do have two 3Bs, so I was able to do much of the >>> recreation on a new copy of Trixie on the 'spare' 3B, but I don't have two >>> RTCs, and I don't have a duplicate of the Meteo-Pi that acts as the serial >>> interface to my Vantage Pro 2. I was fairly easily able to install and run >>> weewx (5.1, now updated to 5.2) under Trixie with its simulator driver, and >>> I am now at the point of trying to move the configured Trixie SD card to >>> the hardware-equipped 3B and to run weewx 'for real'. After a few gotchas, >>> I got the RTC working, and made the appropriate modifications to my >>> existing weewx.conf to conform it to the layout of the Trixie installation. >>> I disabled the Console TTY and enabled the serial interface on the Pi, and >>> pointed weewx (successively) to dev/tty, dev/tty0, and dev/tty1. weewx >>> starts up without errors, but reports that it is getting no response from >>> the serial port, and cycles between the 'no response' and 'retrying' >>> messages. I don't believe that this is, strictly speaking, a weewx problem, >>> but has anyone got weewx working with this or a similar combination of >>> operating system and hardware, and/or got any helpful suggestions? >>> >>> -- >>> 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/c6dd5038-da0e-496c-bb67-42b31cc29eb6n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/c6dd5038-da0e-496c-bb67-42b31cc29eb6n%40googlegroups.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/7eeb88d5-59fd-4d3d-9ed0-d79fa50cac0an%40googlegroups.com.
