If I place the search_list_extensions and template in skin.conf in WEEWXTags folder, they work fine.
However if i place the same in Seasons skin.conf, then they error out. On Tue, 16 Aug 2022 at 14:47, gjr80 <[email protected]> wrote: > I'm a little confused. I read your initial post as the SLEs worked when > used in a skin under WeeWX but the same setup failed when used under > wee_reports. Is this not the case? It would help to know exactly what the > problem is/is not so that I don't spend time looking for a non-existent > fault. > > Gary > > On Tuesday, 16 August 2022 at 18:54:39 UTC+10 [email protected] wrote: > >> I did see the issue when using it in seasons skin even when reports were >> generated as part of 5 min archive period. I then started running >> wee_reports to see if I could debug it.. >> >> On Tue, 16 Aug, 2022, 14:17 gjr80, <[email protected]> wrote: >> >>> I am not sure what you mean. The template can be 'run' either as part of >>> a running WeeWX instance or via wee_reports. The former does not use >>> wee_reports in any way. The latter uses wee_reports which sets up a >>> dummy WeeWX engine to 'run' the reports in the specified (or implied) WeeWX >>> config file. >>> >>> Gary >>> On Tuesday, 16 August 2022 at 18:37:15 UTC+10 [email protected] wrote: >>> >>>> When the template is run via weewxtags skin.conf isn't wee_reports used >>>> then? >>>> >>>> On Tue, 16 Aug, 2022, 11:38 gjr80, <[email protected]> wrote: >>>> >>>>> The error you have posted is from a SLE that only uses the binding to >>>>> the main WeeWX database, it does not use ws_binding, so I am >>>>> confident the error has nothing to do with ws_binding or the lack >>>>> thereof. Nor is it likely an issue with incompatibility with the Seasons >>>>> skin. I suspect the issue is more likely some incompatibility between the >>>>> SLE concerned, MonthStats, and the wee_reports environment. Whilst >>>>> weewx-saratoga was put together in 2021 much of the code, in particular >>>>> the >>>>> SLEs, is some eight or more years old and whilst updated for various WeeWX >>>>> changes over the years it likely has some issues when run using >>>>> wee_reports. I will try to find time to have a look at the problem, >>>>> though unless it is a quick fix it will likely be some time before I have >>>>> time to track down and fix the error. >>>>> >>>>> Not sure what you are trying to achieve, though judging by your >>>>> questions regarding iterating over months/years, I gather you are trying >>>>> to >>>>> develop some sort of historical monthly aggregate based reporting. If that >>>>> is the case, and if you are going to continue to use the weewx-saratoga >>>>> SLEs, I would suggest you just load those SLEs that are required (I >>>>> suspect >>>>> that you probably just want the MonthStats SLE). You might find >>>>> running a separate WeeWX development install with a short (1-2 minute) >>>>> archive interval may compensate for being unable to use wee_reports >>>>> with this SLE. >>>>> >>>>> Gary >>>>> On Monday, 15 August 2022 at 20:38:26 UTC+10 [email protected] >>>>> wrote: >>>>> >>>>>> Is it because the Weewx saratoga has ws_binding as data_binding while >>>>>> Seasons doesnt have. >>>>>> >>>>>> On Monday, 15 August 2022 at 15:53:01 UTC+5:30 [email protected] >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I am trying to use saratoga SLEs inside Seasons skin. I have >>>>>>> specified SLEs like in attacked skin.conf.snip. When I run wee_reports I >>>>>>> get error as attached error_saratoga. >>>>>>> The funny thing is same tmpl works perfectly when included in >>>>>>> skin.conf under WEEWXtags skin.conf (which comes with saratoga extension >>>>>>> installation) >>>>>>> >>>>>>> So I am a bit flummoxed as to why I am not able to use the SLE in >>>>>>> Seasons skin. >>>>>>> >>>>>>> Regards, >>>>>>> Praveen >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "weewx-user" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/weewx-user/Eo9Dd9yBIe0/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/bbf5ac20-5d5e-4471-8292-cc3e77ec8a72n%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/weewx-user/bbf5ac20-5d5e-4471-8292-cc3e77ec8a72n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/Eo9Dd9yBIe0/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/d2b51cb4-ef2f-44fc-8456-e0d8c6fb51aan%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/d2b51cb4-ef2f-44fc-8456-e0d8c6fb51aan%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/Eo9Dd9yBIe0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/b1cc0807-a809-43ef-ba6e-92ce8a3e06can%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/b1cc0807-a809-43ef-ba6e-92ce8a3e06can%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/CA%2BW%3DTmWb09YfBa5gDfwwBL-1UKj%3Dr9VYU8FQ%3D1jTz-i%2BDxw_GA%40mail.gmail.com.
