I found most of those items, but I was still getting a bunch of errors. My
system running 3.?? died a few days ago and my backups were not good so I
was installing the version 4 as a replacement - consequently I had less
that 24 hours data on the system I mistakenly installed cmon on.
I am inte
Appreciate you have managed to disable cmon but for future reference manual
uninstallation of an extension is fairly easy once you know what to look
for. There is no simple 'find this and do this', the amount of work
involved and where to work depends on the extension. A skin/report based
exten
On Monday, December 16, 2019 at 1:42:58 PM UTC-8, Ralph Underwood wrote:
>
> I commented out various cmon stuff in weewx.conf and have whew running
> again.
>
>
>
HA - I'm not the only person that Google is auto-correcting 'weewx' to be
'whew' on !
You could 'try' to edit cmon to make it python3
I commented out various cmon stuff in weewx.conf and have whew running
again.
Thanks,
Ralph
On Monday, December 16, 2019 at 1:29:23 PM UTC-8, Ralph Underwood wrote:
>
> OK. I tried doing a wee-extension uninstall with no success. Any hints on
> how/where to remove it? May be simpler to just
OK. I tried doing a wee-extension uninstall with no success. Any hints on
how/where to remove it? May be simpler to just start with another install
of WeeWx.
I did manage to update my program that reads the mqtt data and write to
file pile.txt without those 'b's.
On Monday, December 16
cmon has not been ported to Python 3.
On Mon, Dec 16, 2019 at 2:17 PM Ralph Underwood wrote:
> I tried to install the cmon extension with the version 4 and got this
> error.
>
> I had just restarted my tail of the log so I hope this is enough.
>
> Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weew
I tried to install the cmon extension with the version 4 and got this
error.
I had just restarted my tail of the log so I hope this is enough.
Dec 16 13:02:16 JV-Wx weewx[27906] CRITICAL weewx.engine: obj
= weeutil.weeutil.get_object(svc)(self,config_dict)
Dec 16 13:02:16 JV-Wx
