*Gary*

Can't thank you enough
the updated (bme280wx.py) solved my problem and it is working great and no 
more logging issue.
On Saturday, January 23, 2021 at 6:09:59 AM UTC+3 gjr80 wrote:

> Ah, you are running WeeWX v4 and this driver uses WeeWX v3 (legacy) 
> logging, hence the lack of control. Try this version of bme280wx.py, I've 
> changed the logging to v4 logging and changed the offending loginf to 
> logdbg. Rename your old bme280wx.py to say bme280wx_orig.py and then copy 
> the attached bme280wx.py in its place. Restart WeeWX and you should have 
> a quieter log, if you want to turn on the debug logging to see the bme28 
> data in the log just set debug = 1 in weewx.conf and restart WeeWX.
>
> If the driver fails because of an error on my behalf you can revert to the 
> copy you just made.
>
> Gary
> On Saturday, 23 January 2021 at 12:43:02 UTC+10 mksm...@gmail.com wrote:
>
>> Yes. debug =0 in weewx.conf
>>
>> anytime I do changes to a driver I follow these steps
>>
>> sudo /etc/init.d/weewx stop
>>
>> *make the changes and save*
>>
>> sudo /etc/init.d/weewx start
>>
>> On Saturday, January 23, 2021 at 5:36:12 AM UTC+3 gjr80 wrote:
>>
>>> Did you have debug = 0 in weewx.conf and did you restart WeeWX?
>>>
>>> Gary
>>>
>>> On Saturday, 23 January 2021 at 12:26:55 UTC+10 mksm...@gmail.com wrote:
>>>
>>>> I am realy sorry I missed to mention that changing line 78
>>>>
>>>>         loginf('BME280 data %s' % bme280data)
>>>> to
>>>>         logdbg('BME280 data %s' % bme280data)
>>>>
>>>> did not work
>>>>
>>>> On Saturday, January 23, 2021 at 4:50:58 AM UTC+3 gjr80 wrote:
>>>>
>>>>> Not sure why you are thanking me, you took no notice of what I 
>>>>> suggested. Commenting out log lines is a poor choice, in future if you 
>>>>> ever 
>>>>> want to troubleshoot you have no means of obtaining any meaningful log 
>>>>> info 
>>>>> unless you again modify source code. A better solution is to change the 
>>>>> log 
>>>>> level of the noisy log output as i suggested so that it is only logged 
>>>>> when 
>>>>> you run WeeWX with debug = 1. 
>>>>>
>>>>> Gary
>>>>> On Saturday, 23 January 2021 at 11:37:31 UTC+10 mksm...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Commenting out line 78 or line 107 only did not work, but Commenting 
>>>>>> out (line 78 & 107) did the trick. no more unnecessary writing to 
>>>>>> (/var/log)
>>>>>>
>>>>>> Thank you *vince & gjr80*
>>>>>>
>>>>>> On Saturday, January 23, 2021 at 3:16:42 AM UTC+3 gjr80 wrote:
>>>>>>
>>>>>>> If it's this one 
>>>>>>> <https://gitlab.com/wjcarpenter/bme280wx/-/blob/master/bin/user/bme280wx.py>
>>>>>>>  
>>>>>>> then the only change that is needed is to change the loginf() call 
>>>>>>> at line 78 to logdbg(). Everything else should be left untouched. 
>>>>>>> Commenting out logging to fix a chatty log is really a case of cutting 
>>>>>>> off 
>>>>>>> your nose to spite your face. Just like restarting WeeWX daily, far 
>>>>>>> better 
>>>>>>> to engineer out the problem.
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>> On Saturday, 23 January 2021 at 10:06:06 UTC+10 vince wrote:
>>>>>>>
>>>>>>>> We'd have to see 'exactly' what code you have installed now in 
>>>>>>>> order to help.   At this point we've seen so many partial descriptions 
>>>>>>>> that 
>>>>>>>> it's impossible to know what exactly you're currently running and what 
>>>>>>>> error messages you are seeing when you run that code.
>>>>>>>>
>>>>>>>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/923461d9-a5fe-410c-a7b8-2d22c676bc48n%40googlegroups.com.

Reply via email to