Updated to which version of weewx ? And which skin are you referring to ?
And what do your logs showing 'this problem' you still have look like now ?
Interceptor hasn't been updated in almost 3 years so updating that likely
will not help.
Looking at the interceptor code and your original message it seems to me
that you have at least two easy options:
- (1) make the 'unrecognized parameter'(s) be ignored
- (2) make them not be typically logged
For the first option, you can edit the driver (save a copy first) around
line 1342 in interceptor.py and add the various ones you see logged as
unrecognized to the list of labels the driver will ignore. Then it
shouldn't log when it sees those.
Look for this block for where to add more labels for the driver to ignore...
IGNORED_LABELS = [ 'ID', 'PASSWORD', 'dateutc', 'softwaretype', 'action',
'realtime', 'rtfreq', 'weather', 'clouds', 'windspdmph_avg2m',
'winddir_avg2m', 'windgustmph_10m', 'windgustdir_10m', ]
For the second option you could up the logging severity needed to log
unrecognized parameters to begin with. There are 4 places where you will
see code that looks like:
loginf("unrecognized parameter %s=%s" % (n, data[n]))
Change each of them to use 'logdbg' rather than the 'loginf' it reports now
and unless you have weewx.conf setting debug=1 it should not log those
messages any more.
If you have a good list of which parameters it's logging the first option
is probably best, but the second option requires less thinking to do.
On Wednesday, May 3, 2023 at 9:22:27 PM UTC-7 [email protected] wrote:
> I updated weewx but the skin stayed on 4.6.2 so I still have this problem
> even with log_success set to False.
> How can I update the skin file while keeping its settings? Do I need to
> upgrade the interceptor driver too?
>
> Even with 100 MB ram set as log partition, the syslog gets full quite fast
> and until now I didn't get logrotate to work correctly. I just had to copy
> the whole system to a new microSD as the old one got trashed in about a
> year and didn't boot up anymore. So I really have to eliminate any unneeded
> writes to storage. (Maybe 4 instances @ 1min report/ftp interval was just
> taking its toll on the microSD anyway, I wonder how long the new long
> endurance microSD will last...)
>
> [email protected] schrieb am Freitag, 4. März 2022 um 16:28:00 UTC+1:
>
>> Thanks a lot
>>
>> [email protected] schrieb am Freitag, 4. März 2022 um 14:52:19 UTC+1:
>>
>>> Fixed in commit
>>> https://github.com/weewx/weewx/commit/7a210b2817096d467f12907d138c0fbc58294369
>>>
>>> On Fri, Mar 4, 2022 at 5:00 AM Tom Keffer <[email protected]> wrote:
>>>
>>>> In the process of internationalizing the skins, it looks like the
>>>> effect of setting the global log_success got lost. I'll fix that.
>>>>
>>>> In the meantime, you can change the log_success under [StdReport]:
>>>>
>>>> [StdReport]
>>>>
>>>> log_success = False
>>>>
>>>> -tk
>>>>
>>>> On Fri, Mar 4, 2022 at 1:20 AM [email protected] <[email protected]>
>>>> wrote:
>>>>
>>>>> log_success = False
>>>>> log_failure = False
>>>>>
>>>>> Restarted the according weewx instance "weewx-interceptor" multiple
>>>>> times but it keeps logging:
>>>>>
>>>>> Mar 4 10:08:21 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in
>>>>> 2.72
>>>>> seconds
>>>>> Mar 4 10:08:23 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> weewx.imagegenerator: Generated 13 images for report SeasonsReport in
>>>>> 2.39
>>>>> seconds
>>>>> Mar 4 10:08:23 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> weewx.reportengine: Copied 0 files to /var/www/html/weewx_interceptor
>>>>> Mar 4 10:08:25 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> weewx.reportengine: ftpgenerator: Ftp'd 19 files in 1.91 seconds
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter wswarning=False
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter heatindexf=31.7
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter sunhours=0.07
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter tswarning=False
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter leakwarning=False
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter ptrend1=1
>>>>> Mar 4 10:08:50 raspi-wsdi1b weewx-weewx-interceptor[6388] INFO
>>>>> user.interceptor: unrecognized parameter windchillf=35.4
>>>>>
>>>>> and so on...
>>>>>
>>>>> Did I overlook something?
>>>>>
>>>>> And question: Will this logs write to sd card with every log?
>>>>>
>>>>> --
>>>>> 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/a363f4af-49c2-4acf-b38f-d82f33809d86n%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/weewx-user/a363f4af-49c2-4acf-b38f-d82f33809d86n%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/7aa2faec-0874-4d4b-9d22-d62584315fefn%40googlegroups.com.
