[weewx-user] Hilfe
Hello no more data is being sent to my Strato server. Reason: [Errno 32] Datenübergabe unterbrochen (broken pipe) Hallo ich kann keine Daten mehr auf meinem Server hochladen. folgender fehler kommt . Reason: [Errno 32] Datenübergabe unterbrochen (broken pipe) kann mir jemand weiter helfen -- 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/475547e0-b2e8-4da6-9ef5-6c9798815be5n%40googlegroups.com.
[weewx-user] Re: Multi-station system adding ecowitt components - clarification requested
Hi Cameron, I've been in exactly this situation. I started with the GW1000 as a service on top of my original Oregon driver, as it is very neat and straight forward. Because I was unable to get all my Ecowitt variables recorded in the single database (maybe because of overlap since both weather stations report some of the same variables, which I did remap to different names), in the end I went for the weewx_multi strategy with two daemons and two databases which worked out of the box because weewx reports make it in fact quite simple to exploit data from distinct databases. The GW1000 weewx daemon instance does nothing but collect and archive loop data. I have no doubt GW1000 as a service must clearly be a perfectly viable option, and I think I was very nearly there in getting it configured, just sharing my experience faced with the same dilemna ! Kind regards, Pascal On Friday, 16 December 2022 at 13:33:32 UTC+1 Cameron D wrote: > My Oregon WMR300 is still happily chugging away generating weather data > and I thought I'd augment it with some air-quality sensors. > The easiest in my situation seemed to be an Ecowitt WH45 CO2/particle > sensor with a GW1100 gateway, and a WH31 temp/RH sensor thrown in for > almost nothing. > So my new system reports: > 1 x barometer > 3 x temperature > 3 x humidity > 1 each CO2, PM2.5, PM10. > sundry battery and signal strengths > > One of my requirements is to have some plots containing data from both > systems on the one chart. > > There seem to be two choices for driver - the Ecowitt (GW1000) and the > interceptor. Are there any strong reasons to choose one over the other? > > There also seem to be two choices for implementation: > 1. using weewx_multi and keep everything separate. Then use the multiple > binding technique in one skin to incorporate all data in a single report. > 2. use the GW1000 code *as a service* in a single instance of weewx, with > a single database. > > The second method seems in some ways simpler, but am I right in thinking I > would need to remap many of the names to avoid clashes with data from the > WMR300? > > If I choose weewx_multi - is there a suitable systemd unit file I can use > as a template? > > Thanks. > Cameron. > -- 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/453e14f7-383c-41cf-9c92-f9349363cd86n%40googlegroups.com.
Re: [weewx-user] Weewx Plot Issue
The Seasons skin has an automatic provisioning feature where it will
display and plot data which is non-null in your database.
For whatever reason, both extraHumid1 and UV are not null. For example,
look at this packet in your log:
Dec 16 19:59:50 solar weewx[522] DEBUG user.interceptor: mapped
packet: {'dateTime': 1671181189, 'usUnits': 1, 'pressure': 29.92,
'outHumidity': 61.0, 'inHumidity': 51.0, 'outTemp': 62.96, 'inTemp':
71.42, 'windSpeed': 2.91, 'windGust': 6.93, 'windDir': 188.0,
'radiation': 2.45, 'rain': 0.0, 'rainRate': 0.0, 'UV': 0.0,
'extraTemp1': 62.96, 'extraHumid1': 61.0, 'soilMoist1': 48.0,
'soilMoist2': 57.0, 'soilMoist3': 41.0}
Perhaps you have sensors you didn't know you had, or perhaps you are
picking up a neighbor's sensors, or perhaps your sensor mappings are
incorrect. You'll have to sort that out.
If you don't believe these numbers and want to suppress them, you have two
options:
Option 1. Remove them from your sensor mappings. This will cause them to
become null values in your database. Seasons looks back 30 days to decide
whether a sensor has non-null values. So, after a month, it will
self-correct. If you don't want to wait a month, you can modify the
database and set the values to null yourself.
Option 2. Suppress the values from being displayed and plotted. They'll
still be in the database, but they won't get displayed. Go into the Seasons
configuration file Seasons/skin.conf and remove 'extraHumid1' and 'UV' from
options 'observations_stats' and 'plot_groups'.
-tk
On Fri, Dec 16, 2022 at 1:23 AM Robert and Katrina de Keijzer <
randkdekeij...@gmail.com> wrote:
> About a month ago I upgraded Weewx to 4.9.1. I've since noticed the
> webpage is showing some errors and I'm not sure where to look to resolve
> them.
>
> The first issue I noticed was the dates are incorrect on two plots, UV and
> Meter Box.
>
> The second issue I've noticed is contained in the 'Current Conditions
> column.
>
> The data 'extraHumid1 is now displaying data. Previously data displayed
> the temperature for the 'Hot Water'
>
> I'm not sure how to fix this, so any suggestions welcome.
>
> Current webpage and log attached.
>
> Thanks,
>
> Rob
>
>
>
> --
> 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/c3bb475c-bf1b-4db3-9291-02947dcb0b1an%40googlegroups.com
>
> .
>
--
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/CAPq0zEBL5xgZkByxgfw36bayvq41vOWH3HjpO6QN1ktdAHatBw%40mail.gmail.com.
[weewx-user] Multi-station system adding ecowitt components - clarification requested
My Oregon WMR300 is still happily chugging away generating weather data and I thought I'd augment it with some air-quality sensors. The easiest in my situation seemed to be an Ecowitt WH45 CO2/particle sensor with a GW1100 gateway, and a WH31 temp/RH sensor thrown in for almost nothing. So my new system reports: 1 x barometer 3 x temperature 3 x humidity 1 each CO2, PM2.5, PM10. sundry battery and signal strengths One of my requirements is to have some plots containing data from both systems on the one chart. There seem to be two choices for driver - the Ecowitt (GW1000) and the interceptor. Are there any strong reasons to choose one over the other? There also seem to be two choices for implementation: 1. using weewx_multi and keep everything separate. Then use the multiple binding technique in one skin to incorporate all data in a single report. 2. use the GW1000 code *as a service* in a single instance of weewx, with a single database. The second method seems in some ways simpler, but am I right in thinking I would need to remap many of the names to avoid clashes with data from the WMR300? If I choose weewx_multi - is there a suitable systemd unit file I can use as a template? Thanks. Cameron. -- 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/5b5b227f-59e7-4c78-b0a6-7a7906ec7633n%40googlegroups.com.
