I'm sorry William, but I don't have any great ideas. It looks like you set line_gap_fraction to 0.3, which is pretty high, so there should not be any gaps.
You have a pretty complicated setup, so I can't replicate it. The function weeplot.utilities.xy_seq_line() is responsible for breaking up lines into smaller pieces if None values are found. All I can suggest is to include some print() statements in it to see what it's doing. Or, if you have access to a debugger, you could step through it and figure it out. I know this answer is not very satisfying, but I don't have the time to try to replicate what you have. -tk On Fri, Dec 2, 2022 at 2:29 PM William Garber <[email protected]> wrote: > sqlite> SELECT COUNT(outTemp) FROM archive where dateTime > 1669743900 and > inTemp is NULL; > 54 > sqlite> SELECT COUNT(inTemp) FROM archive where dateTime > 1669743900 and > outTemp is NULL; > 389 > > total rows was 1000 up to that dateTime 1669743900 but that was for a > varying (usually 150) archive_interval. > > On Friday, December 2, 2022 at 12:47:52 PM UTC-8 William Garber wrote: > >> here is a longer log of sql. hope it is not too long. >> >> >> On Friday, December 2, 2022 at 9:42:47 AM UTC-8 William Garber wrote: >> >>> so sorry here is info >>> the stdout and arduino stream/threads both save lines of output (from >>> rtl_433 and from arduino ttyACM0) to the *same queue*. It seems that >>> they may be skipping some input. All arduinos only have an input buffer of >>> 64 bytes but we are talking about arduino output not input. Also if you >>> make the arduino output very frequently like every five seconds, that sort >>> of overwhelms the Atlas and it skips Atlas inputs (it gets overwhelmed by >>> arduino) but if you make the adruino ouput every 15 seconds the Atlas >>> overwhelms the Arduino instead. Here is the driver. >>> I only did not include the debuginfo since I thought it would be far too >>> *large >>> :-)* >>> On Friday, December 2, 2022 at 4:55:39 AM UTC-8 [email protected] wrote: >>> >>>> You're probably right about the nulls, but you didn't supply a log, nor >>>> a sample plot, so it's hard to make more than an educated guess. >>>> >>>> Let's check the database. I'm going to assume that the outside >>>> temperature (outTemp) is showing dots. Change as necessary. >>>> >>>> *sqlite3 /var/lib/weewx/weewx_atlas.sdb* >>>> sqlite> *SELECT dateTime, >>>> DATETIME(dateTime,'unixepoch','localtime'),outTemp FROM archive ORDER BY >>>> dateTime DESC LIMIT 20;* >>>> >>>> This will show the last 20 archive records. See how many nulls are in >>>> there. To take it to the next step, we'll need more information. >>>> >>>> -tk >>>> >>>> On Thu, Dec 1, 2022 at 7:26 PM William Garber <[email protected]> >>>> wrote: >>>> >>>>> any help please :-) >>>>> I tried making gap_fraction = 0.3 (not 0.03) and increased >>>>> archive_interval = 300. >>>>> *QUESTION: Could it be that I just am getting too many nulls in the >>>>> database?* >>>>> >>>>> My weather station is an Acurite Atlas using SDR driver modified for >>>>> indoor temp/humidity/pressure from an arduino. The weewx server is on a >>>>> raspberry pi hooked up to a usb hub. >>>>> The usb hub is connected to the RTL-SDR radio receiver dongle to >>>>> receive the Acurite Atlas packets. The usb hub is also connected to the >>>>> arduino. The modified SDR driver has three streams, stdin/stdout from the >>>>> rtl_433 back-end to RTL-SDR plus ttyACM0 serial over usb connection to the >>>>> arduino. The SDR driver reads these ports with a class called AsyncInput >>>>> which has one instantiation per stream. Each AsyncInput runs in a thread. >>>>> >>>>> *QUESTION It should definitely be drawing lines not points based on >>>>> the weewx.conf attached and the skin.conf attached as far as I can tell.* >>>>> >>>>> The Acurite Atlas send a sequence of about three incomplete packets to >>>>> make a complete set of data plus the data from the arduino. >>>>> *QUESTION: how do incomplete packets get combined?* >>>>> >>>>> -- >>>>> 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/3625616c-3efe-4f42-bcf3-4923d8616656n%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/weewx-user/3625616c-3efe-4f42-bcf3-4923d8616656n%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 on the web visit > https://groups.google.com/d/msgid/weewx-user/7c54e31b-c3ed-4ab7-b5d3-e633893e9083n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/7c54e31b-c3ed-4ab7-b5d3-e633893e9083n%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 on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEB-%3D_veeEnu3DuoHkOUDHqs3oBKxzeRaNfezR40bKk8Ag%40mail.gmail.com.
