Re: [weewx-user] Connected. Waiting for data. Belchertown

<http://mqtt.dreamwoodestate.net/>", 9011, mqttclient); >>> >>> BTW, ChatGPT told me last week that I should add a "/" in between the 9011 >>> and mqttclient in the client = line. >>> I removed that "/" earli

Re: [weewx-user] Connected. Waiting for data. Belchertown

crypt/live/mqtt.dreamwoodestate.net/cert.pem >>> <http://mqtt.dreamwoodestate.net/cert.pem> >>> keyfile /etc/letsencrypt/live/mqtt.dreamwoodestate.net/privkey.pem >>> <http://mqtt.dreamwoodestate.net/privkey.pem> >>> protocol mqtt >>> >

Re: [weewx-user] Connected. Waiting for data. Belchertown

You have possibly a comment line (starting with "#") in the first line of myconfig.conf. Try to remove it and any other comment line. Here is for exemple the content of my own myconfig.conf file : listener 1883 listener 8083 protocol websockets allow_anonymous false password_file /etc/mosquitto

Re: [weewx-user] Connected. Waiting for data. Belchertown

> II understood that the Belchertown 'mqtt_websockets_topic' should match the > StdRESTful entry - is that correct? No, it is not correct.Should be "weather" in the StdRESTful entry and "weather/loop" in Belchertown 'mqtt_websockets_topic'' > Now to check out the ACL file and MQTT Explorer

Re: [weewx-user] tag formatting with Davis airlink data

t sure if this is the problem, but try using "false" instead of "False". >>> >>> On Fri, Feb 28, 2025 at 7:36 AM jterr...@gmail.com <> >> <>> wrote: >>>> the end of my email was somehow not visible... >>>> >>

Re: [weewx-user] tag formatting with Davis airlink data

m1_0" is computed as " = 1.1 µg/m³" >>>> with the " =" before the value of the tag. >>>> Le vendredi 28 février 2025 à 16:37:20 UTC+1, Tom Keffer a écrit : >>>>> Not sure if this is the problem, but try using "false" instead

Re: [weewx-user] tag formatting with Davis airlink data

alse". >>> >>> On Fri, Feb 28, 2025 at 7:36 AM jterr...@gmail.com <> >> <>> wrote: >>>> the end of my email was somehow not visible... >>>> >>>> (see http://meteo-sciez.fr/site/mesures.php) >>>> >>>>

Re: [weewx-user] WeeWx MQTT publishing, but no data received on topic

mber 5, 2024 at 8:03:39 AM UTC-5 Jacques Terrettaz wrote: >> Which MQTT weewx extension are you using ? >> >> If you are using this one : https://github.com/michael-slx/weewx-mqtt. , >> this extension will not generate a weather/loop topic. >> >>

Re: [weewx-user] WeeWx MQTT publishing, but no data received on topic

Which MQTT weewx extension are you using ? If you are using this one : https://github.com/michael-slx/weewx-mqtt. , this extension will not generate a weather/loop topic. You have to use this one : https://github.com/matthewwall/weewx-mqtt > Le 5 nov. 2024 à 13:11, bmb...@gmail.com a écr

Re: [weewx-user] Sunshine Duration

If you are using a Davis pyranometer, you can keep global_coeff to 1. My Davis weather station is at latitude 46.34 N and I use this value. If you have another solar or light sensor, you will have to adjust the value of global_coeff, and possibly the B_coeff, until you have good results - i.e

Re: [weewx-user] Sunshine Duration

Hello Michael, I have modified the extension (release v1.5) to expose two coefficients used for the calculation. : https://github.com/Jterrettaz/sunduration/tree/v1.5 With this new version , you will have to add this stanza in weewx.conf : [Sunduration] global_coeff = 1.0 B_coef

Re: [weewx-user] Sunshine Duration

OK, thanks. A good "offline" comparison of your sunshine sensor with the formula will be difficult, since with your archive data the fomula will produce only one estimation for a 5 min period, based of the archive radiation measurement , which is the mean radiation measured over of archive peri

Re: [weewx-user] Sunshine Duration

Yes... some people use that way... but wrongly ! May be also because even the software developed by Davis (Weatherlink) to capture Davis Vantage data is proposing the use of a 120 W/m2 threshold for their global irradiance sensor !!! The use of global irradiance sensors is largely discusse

Re: [weewx-user] Sunshine Duration

Yes, correct understanding ! The term "sunshine" and "sunshine duration" is the one used by WMO - see https://library.wmo.int/viewer/68695/?offset=#page=331&viewer=picture&o=bookmark&n=0&q= . Why should we use another nomenclature ? > Le 7 mai 2024 à 11:02, Ton vanN a écrit : > > Correct

Re: [weewx-user] Sunshine Duration

aced the “sunduration.py” and restarted weewx > Do I have to enter this somewhere? > > Jacques Terrettaz schrieb am Donnerstag, 2. Mai 2024 um 18:05:49 UTC+2: > I have added a new field in my extension : is_sunshine > > At each record generation,, the is_sunshine value will

Re: [weewx-user] Sunshine Duration

The WMO definition (threshold at 120 W/m2) is applicable only for the measurements of direct solar irradiance, using pyrheliometric sensors that are all the day moving to point always directly toward the sun position, with the surface of the sensor always perpendicular to the axis sun-sensor.

Re: [weewx-user] Sunshine Duration

I have added a new field in my extension : is_sunshine At each record generation,, the is_sunshine value will be 1 if there is sunshine, otherwise it will be 0. This field is also published in the MQTT stream. See https://github.com/Jterrettaz/sunduration/tree/master > Le 2 mai 2024 à 14:54, ge

Re: [weewx-user] Sunshine Duration

The "sunduration" extension is calculating the total time in a day when there is no clouds between the sun and the Davis radiation sensor. With clouds, the incoming radiation energy is much lower. The formula used in this extension calculates a threshold radiation value that depends on the dat

Re: [weewx-user] Pipe errors etc

t; David. > > On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz <mailto:jterret...@gmail.com>> wrote: >> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi" >> instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html >> >

Re: [weewx-user] Pipe errors etc

Since you have a RaspberryPi, you may also consider buying a "Meteo-pi" instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html The datalogger card is plugged to the console and the HAT card is plugged to the 40-pin header of the RPI and both are linked with a RJ11 cable : no more n

Re: [weewx-user] NEW_ACHIVE_RECORD event chronology

Thanks. Right now I think will follow option 2 and I am looking forward to use the separate extraction of records from accumulators in version 5.1 ! > Le 5 déc. 2023 à 23:36, gjr80 a écrit : > > Like I said, depends whether you wanted to morph the archive record or not. > > Since you are cle

Re: [weewx-user] NEW_ACHIVE_RECORD event chronology

Thanks for the suggestion Gary. But in that case, with a service in archive_ services (after StdArchive) or in report_services , it is a read-only access to the full archive record. The idea of my service was to read some GW1000 sensor archive record values, and depending on these value modify

Re: [weewx-user] NEW_ACHIVE_RECORD event chronology

Yes, this is the case. The GW1000 gateway service only adds sensor values to the LOOP packets. So in that case, there is no way to capture the archive record of GW1000 sensors using a custom service. Thanks for your reply > Le 5 déc. 2023 à 16:38, Tom Keffer a écrit : > > As you're hinting,

Re: [weewx-user] formatting issue in cheetah

Tom, here are my settings : root@meteopi:~# echo $LANG fr_CH.UTF-8 root@meteopi:~# python3 -c "import locale;print(locale.setlocale(locale.LC_ALL))" LC_CTYPE=fr_CH.UTF-8;LC_NUMERIC=C;LC_TIME=C;LC_COLLATE=C;LC_MONETARY=C;LC_MESSAGES=C;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

essage on your system? > > > > On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz <mailto:jterret...@gmail.com>> wrote: >> It should look like : weather/loop. The loop topic is a json containing all >> the data aggregated and is apparently not generated with

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

Are you using this extension : https://github.com/michael-slx/weewx-mqtt. ? If yes, this extension does not generate a "loop" json topic needed by the Belchertown skin. In that case, you have to use the following extension : https://github.com/matthewwall/weewx-mqtt/tree/master > Le 25 juil. 20

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

It should look like : weather/loop. The loop topic is a json containing all the data aggregated and is apparently not generated with your setup. Here is an exemple of the content of a weather/loop mqtt message for my station : {"dateTime": "1690272486.0", "barometer_mbar": "1006.4684246818595",

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

et or > javascript errors ... (only errors with geolocation & uncaught type error in > context with windy.com <http://windy.com/>) > > > > On Mon, Jul 24, 2023 at 5:04 PM Jacques Terrettaz <mailto:jterret...@gmail.com>> wrote: >> Another point to

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

continues to say "Connected. Waiting for data." > > Does a Belchertown config file override weewx.conf settings somewhere? > > > On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz <mailto:jterret...@gmail.com>> wrote: >> Two things to consider : >>

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

> router and firewall accordingly. > Yeah - I have dyndns enabled and just opened 9001 on my router, too. > > Unfortunately, it continues to say "Connected. Waiting for data." > > Does a Belchertown config file override weewx.conf settings somewhere? > > >

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

Two things to consider : 1) when opening your website from local network : your mqtt broker is using port 9001 for websockets. If it doesn't works , you may have to verify that this port 9001 is not blocked by a firewall. 2) when opening your website from internet (http://weewxhi.de

Re: [weewx-user] Sunshine Database

Hello, Please double check the line before line 101 - missing parenthesis or something like that. > Le 6 août 2022 à 21:01, Meteo Oberwallis a écrit : > > Hello > Thx for Help. I have the new Code in my sunduration.py and i have this fault: > > Aug 6 20:59:46 Wetter weewx[11829] DEBUG weewx.

Re: [weewx-user] Sunshine Database

Hello, It seems that radiation values are missing for some archive records. Line 92 of sunduration.py had a wrong indentation. This is now corrected in my Github repository. > Le 31 juil. 2022 à 06:45, Meteo Oberwallis a écrit : > > Hello. > I have a Problem, wenn weewx stop an ih restart

Re: [weewx-user] Sunshine Database

Did you try to add group_interval = hour in the [[Defaults]] [[[Units]]] Groups section of weewx.conf ? > Le 22 juil. 2022 à 16:35, Jon B a écrit : > > Thanks. I'm using the Belchertown skin so I think things may be set up > slightly differently. Within this skin, a new observation

Re: [weewx-user] Sunshine Database

@Jon B If you are retrieving the values using weewx tags, you can have the daily total sunshine duration, in hours with the following tag : $day.sunshine_time.sum.hour You can do the same with different aggregation periods , for instance : $yesterday.sunshine_time.sum.hour $week.sunshine_time.s

Re: [weewx-user] Sunshine Database

According to the weewx documentation : Action --reconfigure This action is useful for changing the schema or unit system in your database. It creates a new database with the same name as the old, except with the suffix _new attached at the end (nominally, weewx.sdb_new if you are using SQLite,

Re: [weewx-user] Sunshine Database

@Peter : if one want to update the database using wee_database, the new updated schema with the new field is needed. Otherwise, in case of a manual update of the database structure, the new schema is not needed. > Le 18 juil. 2022 à 16:29, 'Peter Fletcher' via weewx-user > a écrit : > > @Jac

Re: [weewx-user] Sunshine Database

I looked at the code in my GitHub, and it appeared that the last line schema_with_sunshine_time = schemas.wview.schema + [('sunshine_time', 'REAL')] had a wrong indentation. This is corrected now. Sorry ! > Le 18 juil. 2022 à 15:43, Jon B a écrit : > > Sorry for piggybacking on this conver

Re: [weewx-user] Sunshine Database

Hi, Please verify that the last line of the sunduration.py script is schema_with_sunshine_time = schemas.wview.schema + [('sunshine_time', 'REAL')] > Le 18 juil. 2022 à 15:43, Jon B a écrit : > > Sorry for piggybacking on this conversation, but it seemed like an > appropriate place to ask

Re: [weewx-user] Sunshine Database

Hello, If you share with us the code of your radiationhours.py script; it would be more easy to help you. > Le 16 juil. 2022 à 17:08, Meteo Oberwallis a écrit : > > Hello. > > I have under the Version 3.9.2 this Problem: > > Jul 16 17:04:44 Wetter systemd[1]: Starting LSB: weewx weather sys

Re: [weewx-user] Sunshine Database

You are right! I added the rounding to the nearest minute because I was surprised that from time to time, I had a sunshine duration slightly higher that the archive interval, due probably to the delay needed by weewx to process the archive records. Initially, I thought it was not logical to h

Re: [weewx-user] Sunshine Database

Peter, Don't forget the fact that if for any reason Weewx is stopped, it will, during restart, read from the datalogger memory any "missed" archive packets that were not captured during the interruption period. In that case, no loop data are available for these archive records, and you have to

Re: [weewx-user] Sunshine Database

Hello, The final code is here : https://github.com/Jterrettaz/sunduration . The calculation of sunshine time is done for every loop packet (every 2 seconds) and the sum of all these individual loop values within an archive interval will be the archiv

Re: [weewx-user] Sunshine Database

OK. The variable "hauteur_soleil is the elevation of the sun, in degree. >From sunset to sunrise, this value will be negative (i.e. sun below the >horizon). The formula developed by Metro France was validated to be effective only if sun elevation is > 3°. In my own implantation of this algori

Re: [weewx-user] Sunshine Database

OK. What I don't understand is that my code had always a test if hauteur_soleil > 3: (according to Météo France) or more recently if hauteur_soleil > 0: in the function, and this test is not on your function. It should be : hauteur_soleil = asin(sin((pi / 180) * latitude) * sin((pi / 18

Re: [weewx-user] Sunshine Database

The only clue I have is that the problem is not due to an « overloading » of your raspberry pi, but seems to occur with specific dateTime values. You can try to run your script only with a « bad » dateTime : "SELECT dateTime, Radiation from archive where dateTime = 1592614500 » Does the error oc

Re: [weewx-user] Sunshine Database

If you exclude the first one,1592614500 , with a query like "SELECT dateTime, Radiation from archive where dateTime <> 1592614500", will the script stop at 1592614800 ( the next dateTime) or will it continue and stop at 1632611100 ? > Le 30 juin 2022 à 14:34, 'Peter Fletcher' via weewx-user >

Re: [weewx-user] Determine archive interval from within weewx

The Davis VP2 archive are recorded in the datalogger at the exact archive interval. So even if for any reason a service bound to NEW_ARCHIVE_RECORD is running a little bit later that the time the record was captured by the VP2, the data will still be valid, and the "event.record['interval'] " w

Re: [weewx-user] Sunshine Database

On my side, I have looked at the CPU utilization on my raspberry Pi 3B+. I have the mqtt service service installed, so at each loop all data of the packet are sent to the mqtt broker. With mqtt and when calculations of the sunshine threshold is done for each loop packet, the total CPU utilizat

Re: [weewx-user] Sunshine Database

I think it is also OK to do an average for every 30 seconds. It depends also on the weather station used. For instance, a Davis Vantage Pro 2 ISS transmits an updated solar radiation value every 50 to 60 seconds. So with this weather station, even a 1 minute average would not be very differen

Re: [weewx-user] Iterate over records for the last 24h

Thanks gjr80. Yes, I have verified that I have the last data in the archive table. For my first tests, I put the code at the end of the monthly NOAA template file and it was not working. Finally I have added a separate template file in an existing skin, and it works now. I am not sure why, but

Re: [weewx-user] Missing Ordinates on windrose graph [Belchertown]

s. I'll take a look and see if I can figure out > what changed > > On Sunday, July 12, 2020 at 1:13:48 PM UTC-4, Didier Decoodt wrote: > Oh yes... > Pat, have you seen the problem? > > Bonne soirée Jacques > > Le dim. 12 juil. 2020 à 19:08, Jacques Terrett

[weewx-user] Re: Missing Ordinates on windrose graph [Belchertown]

Hi Didier, I see that you are using V1.2b6.That may be the problem... The Belchertown site ( https://belchertownweather.com ) is running also V1.2b6, and I see missing ordinates on the wind rose. All is OK with V 1.1 - see for example on my site : http://meteo-sciez.fr/weewx/belchertown/

[weewx-user] Re: Solar radiation reading without solar sensor !!!!!???????

If the name of the mqtt variable is maxSolarRad, it is not a measurement but the value of the maximal solar radiation expected for your location and calculated by weewx. If you don't need the value, you can remove the "maxSolarRad line in the section [StdWXCalculate] [[Calculations]] of weewx.c

[weewx-user] Re: Skin Belchertown 1.1

Hi Patrick, You have to modify the following lines in skin.conf of Belchertown 1.1 : records_barometer_records = ... records_sun_records = ... Le dimanche 5 juillet 2020 14:06:56 UTC+2, Patrick Tranchant a écrit : > > Hello PAT, > > I just upgraded Weewx to 4.1.1 with Belchertown 1.1 ( already

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

HI, I checked with my Davis station and I am observing exactly the same kind of differences. I think the problem is coming from the vantage weewx driver : Here are my data concerning sunrise : - the console displays 05:46 for sunrise. This is correct - the raw loop data for sunrise, as re

[weewx-user] Re: Driver crash without logs - Weewx

Hi Florentin, Could you please set debug=1 in weewx.conf, restart weewx and share the log file produced during the start and at least the first 3 minutes ? Le jeudi 11 juin 2020 08:55:00 UTC+2, Florentin Prevost a écrit : > > Hi, > > I'm use the prepackaged of weewx 4.1.1 on python3. > > The

Re: [weewx-user] Re: Belchertown Graphs - not showing

Hi Xant, I had a look at your site and it seems that the json files are produced alternatively by different versions of Belchertown skin. Do you have multiple instances of weewx ? Sometimes the beginning of ./json/homepage.json is : { "belchertown_version": "1.1", "generated_timestamp"

Re: [weewx-user] Wind Rose empty in Steel Series

Forget my last message : I used a new Raspberry PI to install weewx V4, and then I transferred my "old" mysql database to the new installation... > Le 4 juin 2020 à 20:01, Jacques Terrettaz a écrit : > > Tom, > > One comment about the old and new database

Re: [weewx-user] Re: Wind Rose empty in Steel Series

torical summaries > manager = weewx.manager.DaySummaryManager > schema = schemas.wview.schema > > > Go with one or the other, but don't mix. > > Or, I could be completely off on this! > > -tk > > > On Wed, Jun 3, 2020 at 11:36 PM Jacques Terre

Re: [weewx-user] Wind Rose empty in Steel Series

Yes, it works. I did the same as yesterday : drop the daily tables, and rebuild them, and no error with the wind tags. > Le 4 juin 2020 à 16:59, Tom Keffer a écrit : > > Let us know if that works. > > On Thu, Jun 4, 2020 at 7:56 AM Jacques Terrettaz <mailto:jterret...

Re: [weewx-user] Wind Rose empty in Steel Series

Yes, it was mixed : DaySummaryManager with the old database schema. I reconfigured with manager = weewx.wxmanager.WXDaySummaryManager Thanks Jacques > Le 4 juin 2020 à 16:38, Tom Keffer a écrit : > > My guess is that your system has a mix of old and new ways of specifying a > database schem

[weewx-user] Re: Wind Rose empty in Steel Series

Interestingly, I had the same kind of errors yesterday concerning wind tags such as *day.wind.count.raw* , *month.wind.count.raw*, *day.wind.max. * This happened after I deleted all daily mysql tables and let weewx rebuild them at startup. I am using weewx V4.1.1 Finally, I restored a full back

Re: [weewx-user] Version 4.1.1

Tom, I replaced the three files and everything is OK now. Thanks Le mercredi 3 juin 2020 00:21:55 UTC+2, Tom Keffer a écrit : > > Wow. That was an obscure bug. Fixed in commit b6d2424 > , > > to appear in V4.1.2.

Re: [weewx-user] Version 4.1.1

Thanks Tom > Le 2 juin 2020 à 14:05, Tom Keffer a écrit : > > I was able to replicate your error. It has to do with some obscure > side-effects of deep copying the configuration dictionary. > > I will figure out a workaround. > > -tk > > On Tue, Jun 2, 202

Re: [weewx-user] Version 4.1.1

e for your issue > > *Graham Eddy* > > On 2 Jun 2020, at 9:27 pm, Jacques Terrettaz > wrote: > > Thanks for the suggestion, but the syntax error is still here after this > change.. > > Le mardi 2 juin 2020 12:52:19 UTC+2, Graham Eddy a écrit : >> >> i

Re: [weewx-user] Re: Version 4.1.1

Thanks for the suggestion, but the syntax error is still here after this change.. Le mardi 2 juin 2020 12:52:19 UTC+2, Graham Eddy a écrit : > > in weewx.conf, try changing “level = {log_level}” to “level = DEBUG" > > > -- You received this message because you are subscribed to the

[weewx-user] Re: Version 4.1.1

I observed also that during the update to 4.1.1, the quotes of the "format" lines were removed. I added them back, but the syntax error is still here. > [Logging] > ... > [[formatters]] > [[[simple]]] > format = "%(levelname)s %(message)s" > [[[standard]]] >

[weewx-user] Re: Version 4.1.1

After some investigation, it seems to be related to the [Logging] section I added in my weewx.conf. This was working perfectly with version 4.1.0. If I remove the [Logging] section, the log is going back /var/log/syslog, and the syntax error disappears. [Logging] version = 1 disable_

[weewx-user] Re: Version 4.1.1

Hi, > I just updated to V4.1.1, and since the update a syntax error is generated for each report : Syntax error: missing option "levelname" in interpolation 2020-06-02 10:29:27 weewx[1944] INFO __main__: Starting up weewx version 4.1.1 2020-06-02 10:29:27 weewx[1944] DEBUG weewx.manager: D

[weewx-user] Re: Belchertown About.inc (consBatteryVoltage)

Hi, use $current.consBatteryVoltage Le mardi 26 mai 2020 23:45:13 UTC+2, Jeff Rabin a écrit : > > Ok, so I'm feeling really stupid, and someone is going to state the > obvious. But how do I put the Console Voltage in the about.inc for > Belchertown skin? > > $station.consBatteryVoltage does n

[weewx-user] Re: Belchertown MQTT update time is chaotic

In the original skin.conf of Belchertown v 1.1 , i see : mqtt_websockets_connected = Connected to weather station live. Data received On my side, I have a running Belchertown 1.1 template, translated in French, ( see http://meteo-sciez.fr/weewx/belchertown/ ) with : mqtt_websockets_connecte

Re: [weewx-user] Belchertown MQTT update time is chaotic

Hi, Text segments ? What do you mean ? > Le 26 mai 2020 à 18:49, Keimpe Bleeker a écrit : > > What remains is the correct connection of text segments, but trhat is realy > minor a minor issue! -- You received this message because you are subscribed to the Google Groups "weewx-user" group.

[weewx-user] Re: Belchertown MQTT update time is chaotic

template weewx/skins/Belchetown/js/belchertown.js.tmpl, verify that the line 839 is : updated_text = "$obs.label.mqtt_websockets_connected " + updated; Le dimanche 24 mai 2020 19:38:27 UTC+2, Keimpe Bleeker a écrit : > > Thank you so much Jacques Terrettaz, you have solved m

[weewx-user] Re: Belchertown MQTT update time is chaotic

I think I have found the problem : In your first post I see : # moment.js default labels formats time_earthquake= "LLL" time_lastUpdated = "LL, LTS" time_snapshot_records_today_header =

[weewx-user] Re: Belchertown MQTT update time is chaotic

HI, Could you verify the line 281 of your Belcherton skin.conf ? By default the line is time_last_updated = "LL, LTS" What is yours ? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

[weewx-user] Re: GUI date/time and current conditions frozen

Hi, You said on your top message that your timezone is UTC - 12 But below I see UTC + 12 Could it be the problem ? Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit : > > Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00 > > -- You received this message because you are subscrib

Re: [weewx-user] Problem with Davis VP2 (Data logger or Konsole)?

The formula include a small correction of the Davis radiation sensor values depending on the temperature. If the temperature is not available, a default temperature of 15°C is used. You can use alternatively 25.0 instead of 15.0 as default temperature - tempe = event.record.get('outTemp', 25

[weewx-user] Re: Problem with Davis VP2 (Data logger or Konsole)?

Hi Meteo Oberwallis, Try to modify the script /usr/share/weewx/user/radiationhours.py as follow : Replace (in line 20 ?) : tempe = float(event.record.get('outTemp')) by tempe = event.record.get('outTemp') if tempe is None: tempe=15 -- You received this message because you are subscribed

Re: [weewx-user] Can Weewx works with weatherLinkIP and Meteobridge?

José, May be a network problem ? How is your RPI3 connected to your network ? Wifi?, wired? Can you ping the IP address of your IP datalogger from the terminal windows of your RPI3 ? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To uns

Re: [weewx-user] Can Weewx works with weatherLinkIP and Meteobridge?

Hi José Could you please post the log beginning with the start of Weewx until the error occurs ? Le jeudi 14 mai 2020 19:48:10 UTC+2, José C. Morales C. a écrit : > > Thanks Tom > > The log say > > May 14 13:37:18 raspberrypi weewx[8856] CRITICAL weewx.engine: >> raise weewx.Wee

Re: [weewx-user] Can Weewx works with weatherLinkIP and Meteobridge?

Hi Tom, If I am not wrong, Weatherlink IP is the Davis IP datalogger, and weewx can normally connect to it using the vantage driver with ethernet connection. Le jeudi 14 mai 2020 19:38:12 UTC+2, Tom Keffer a écrit : > > WeeWX does not support either weatherLinkIP, nor Meteobridge > out-of-the-b

[weewx-user] Re: mqtt and Soilmoisture

On my system, the MQTT names for soil moisture are : soilMoist1_centibar , soilMoist2_centibar, soilMoist3_centibar You can use MQTT Explorer ( http://mqtt-explorer.com ) to connect to your broker and to verify the names. Le lundi 11 mai 2020 19:36:48 UTC+2, Wifi75 a écrit : > > how I can gener

Re: [weewx-user] Weewx V4 : Imagegenerator problems with plot_type = vector and aggregate_type = max

Thanks Glenn and Gary, It is OK with the new xtypes.py. I deleted all month and yearly images, and it took about 40 seconds to generate them all. Much better that 17 minutes! -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe fro

Re: [weewx-user] Weewx V4 : Imagegenerator problems with plot_type = vector and aggregate_type = max

Gary, Thanks for your reply. I can confirm that I occurs each time the monthly charts are refreshed. In the log, same problem at 00:00, 03:00, 06:00 , 12:00 ... etc If I remove the "aggregate_type = max" from this image definition in the Season skin.conf : [[[monthwindvec]]]

[weewx-user] Re: Weewx V4 : Imagegenerator problems with plot_type = vector and aggregate_type = max

here is the log after Weewx startup : May 7 10:44:49 meteopi systemd[1]: Starting LSB: weewx weather system... May 7 10:44:49 meteopi weewx[22175] INFO __main__: Initializing weewx version 4.0.0 May 7 10:44:49 meteopi weewx[22175] INFO __main__: Using Python 3.7.3 (default, Dec 20 2019, 18:57

[weewx-user] Re: Weewx V4 : Imagegenerator problems with plot_type = vector and aggregate_type = max

Here is the log. After the capture of the archive record of 09:00, the cheetahgenerator of the SeasonsReport has been completed, but no imagegenerator completion, and no other reports tasks. At 09:05 : INFO weewx.engine: Launch of report thread aborted: existing report thread still running At

[weewx-user] Weewx V4 : Imagegenerator problems with plot_type = vector and aggregate_type = max

Hi, I have upgraded to Weewx V4, and since the upgrade I have observed that some charts take quite a long time to render. For exemple, in skin.conf of Seasons skin : [[[monthwindvec]]] windgustvec plot_type = vector aggregate_type = ma

[weewx-user] Re: Feeding weewx from Meteobridge

Hi, The Meteobridge Nano SD emulates the network connectivity of a standard Davis IP datalogger. You can therefore configure weewx with the Vantage driver, with ethernet connection at the IP address of your Meteobridge Nano SD and using port 2. Le mercredi 6 mai 2020 03:53:52 UTC+2, Ryan

[weewx-user] Re: Sunshine Time

can > I remove it? > > > > > > Thank you > > Am Freitag, 27. März 2020 12:49:17 UTC+1 schrieb Jacques Terrettaz: >> >> >> Hi, >> With this extension, the sunshine time is recorded as minutes. >> >> So in your case, to have the

[weewx-user] Re: Sunshine Time

Hi, Another way to go, if you want to have the sunshine time recorded as hours, is to mofify the end of the extension to divide it by 60, as follows : if mesure > seuil: event.record['sunshine_time'] = event.record['interval']/60 -- You received this message because y

[weewx-user] Re: Sunshine Time

Hi, With this extension, the sunshine time is recorded as minutes. So in your case, to have the number of hours, you should divide the sum by 60: #set hours = int($day.sunshine_hours.sum.raw*/60*) #set minutes = $day.sunshine_hours.sum.raw - ($hours*60) With a daily sum of 135 minutes

Re: [weewx-user] MQTT Errors

OK, no more errors, but... no data. Please add "/loop" at the end of your mqtt_websockets topic : # MQTT Websockets defaults mqtt_websockets_enabled = 1 mqtt_websockets_host = "test.mosquitto.org" mqtt_websockets_port = 8081 mqtt_websockets_ssl = 1 mqtt_websockets_topic = "

Re: [weewx-user] MQTT Errors

Alex, Since your web site is secure, there is right now an error "the operationis insecure" triggered by the mqtt websockets connection. Could you please use the port 8081 and mqtt_websockets_ssl = 1, and I will have a look again. -- You received this message because you are subscribed to the G

Re: [weewx-user] MQTT Errors

Alex, did you tried to use the unencrypted websocket (port 8080), with mqtt_websockets_ssl = 0 ? If your Belchertown web page is accessible from internet, could you send me the link, so that I can see if there is some javascript websockets errors ? -- You received this message because you

[weewx-user] Re: MQTT Errors

HI, In your configuration, you are using the same port number (8081) to send your data to the MQTT broker and to retrieve them via the skin (websockets). According to the test.mosquitto.org server documentation : The server listens on the following ports: 1883 : MQTT, unencrypted 8883 :

[weewx-user] Re: Homebridge to WeeWX

Hello, There is an indirect way to have weewx data sent to Homebridge : via MQTT On the weewx side, you have to install the MQTT extension : https://github.com/weewx/weewx/wiki/mqtt In Homebridge, you have to install the mqtt plugin : https://www.npmjs.com/package/homebridge-mqttthing, and t

[weewx-user] Re: Sunshine Time

I agree with peter's comment. The Davis solar radiation sensor, or any comparable sensor, is measuring a global radiation ( direct + diffuse) and the surface of the sensor is parallel to the ground. A fixed threshold, such as 120 W/m2, can be used only with sensors measuring direct radiation an

Re: [weewx-user] Looking for sample weewx.conf file that includes two sensor sources for Vantage Pro

Is your VP2 console communicating wirelessly with the ISS ? If this is the case, you could configure your VP2 console to receive temp/hum/rain date from ISS (id=1) and wind data from the anemometer transmitter (id=2). No need to have a separate Envoy to capture wind data, and no need to change

Re: [weewx-user] Re: CloudMQTT & Belchertown Skin

Its looks like MQTT is not enabled in your Belchertown skin. Verify that in weewx.conf, you have : [StdReport] .. [[Belchertown]] skin = Belchertown HTML_ROOT = belchertown [[[Extras]]] . * mqtt_websockets_enabled = 1* and verify that the options

  1   2   >