Thank You Vince for taking the time to look into this.. The double post was at the begining of the stuff I posted Jul 17 10:10:03 Satcom python3[32727]: weewx-rm_young[32727] INFO weewx.restx: Wunderground-RF: Published record 2023-07-17 10:10:03 PDT (1689613803) Jul 17 10:10:03 Satcom python3[32727]: weewx-rm_young[32727] INFO weewx.restx: Wunderground-RF: Published record 2023-07-17 10:10:03 PDT (1689613803)
Two entries with the same time stamp, not sure if that was a glitch in reporting or if WU was really receiving two. But it doesn't matter now as commenting out those lines you suggested has not only stopped all the verbage in the logs but also appears to have stopped the double posting in the log. I had tried on my own to comment out some lines or to make changes to get it out of debug mode but it always resulted in the program crashing. I was concerned that running 2to3 had created the issue and had not converted the code quite right, but you see the verbage in the original rmyro.py. Here is a link to the modifed rmyro.py if you care to look https://www.dropbox.com/scl/fi/1u382hugjjj7xebqk2c3a/rmyro.py?rlkey=2qk1ybl3vgcscomyvavojbsfa&dl=0 The only other changes I did was changing the baud rate to 9600. Once again Thank You, You quickly fixed several days of frustration. Kevin On Monday, July 17, 2023 at 1:24:13 PM UTC-7 vince wrote: > Short answer is *'if you run unmainted code then you need to freeze to a > setup that works forever, or you need to handle it yoursel*f'. Looks > like you got 2to3 to get you python3 compatible (good) so you're most of > the way there so I'd say keep going on your adventure since you're close.... > > log_success doesn't change debugging logging at all. > > You'd have to point us to a copy of your modified driver to help for > certain, but if you're starting with > https://github.com/abillits/weewx-rmyro/blob/master/rmyro.py then it > looks like it always runs with debugging messages chattering a lot. Check > out the genLoopPackets(self) routine around line 345 in the try: block for > places where it says logdbg(something). You can quiet things down at least > temporarily by commenting those 5 lines in the try: part of the try/except > block out. Better long term fix would be to make it a little more > configurable, but leave that for later. > > try: raw_primary = self._station.get_primary_sensor_data() ##### > logdbg("primary raw: %s" % _fmt(raw_primary)) data = > Station.parse_primary_sensor_data(raw_primary) ##### logdbg("primary > parsed: %s" % data) #if self._secondary is 'enabled': if "enabled" in > self._secondary: raw_secondary = self._station.get_secondary_sensor_data() > ##### logdbg("primary raw: %s" % _fmt(raw_secondary)) data_secondary = > Station.parse_secondary_sensor_data(raw_secondary) ##### logdbg("secondary > parsed: %s" % data_secondary) data.update(data_secondary) packet = > self._data_to_packet(data) ##### logdbg("mapped: %s" % packet) if packet: > yield packet break > > > > You haven't provided any logs showing your WU double post issue, so I > can't comment there. > > -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/65d57ae0-7511-494b-bddf-7840bc0c8ee1n%40googlegroups.com.
