Re: IRe: [weewx-user] High CPU on 5.10

['Ian Millard' via weewx-user]

Should the last command be: -weectl database calc-missing Sent from my iPad.On 30 May 2024, at 03:28, Mark Jenks  wrote: I ran this, and did the recalc-missing, and it seems to be running better.   Except there is only one record in those tables.Not sure why that would cause that issue.weectl database add-column appTempweectl database add-column cloudbaseweectl database add-column visibilityweectl database add-column windrunweectl database add-column cloud_coverweectl database add-column aqiweectl calc-missingOn Tuesday, May 28, 2024 at 8:10:45 PM UTC-5 Mark Jenks wrote:Seasons itself doesn't do it, and Belchertown with no settings on it is doing it.   So, I'm adding those columns now and recalculating now.On Tuesday, May 28, 2024 at 1:15:56 PM UTC-5 mh081...@gmail.com wrote:I think this was the Problem with missing Database extended schema object. I had the same problem as i upgraded from weewx 4 to 5. I solved this with.weectl database add-column appTempweectl database add-column cloudbaseweectl database add-column visibilityweectl database add-column windrunweectl database add-column cloud_coverweectl database add-column aqiweectl calc-missingweectl calc-missing appTempvince schrieb am Dienstag, 28. Mai 2024 um 19:38:07 UTC+2:The other test would be to disable belchertown, enable seasons, and see if that’s ok. That would check the db vs. the v5 calculated aka synthetic readings feature that slowed some folks down.On Tuesday, May 28, 2024 at 10:25:10 AM UTC-7 Tom Keffer wrote:I thought of the appTemp angle, but those queries involve thousands of small aggregate intervals, not one query over 4 years. Still, it's worth a try.On Tue, May 28, 2024 at 9:07 AM vince  wrote:You seem to be hacking randomly and praying.  I'd suggest deleting Belchertown at this point, verifying it is deleted, then add it back in.  Do not customize it yet.  Just run the default setup, it works.  Really.My guess is you are missing the appTemp element in the db.  There are a bunch of threads on this re: Belchertown and v5 weewx.Check your mariadb schema and see if it is missing appTemp.  If you have the old wview-compatible db you'd have about 50 elements in it.  If you later switched to the v4 and above bigger wview-extended schema, you'd have 114 elements in it.  Sorry but I don't know the mariadb commands to count them nor check.For sqlite3 it would be:  'echo ".schema" | sqlite3 mydbname  | wc -l'On Tuesday, May 28, 2024 at 3:59:19 AM UTC-7 Mark Jenks wrote:I removed the last two from skin.conf, and it still does the large query.   I'll keep digging tonight.generator_list = weewx.cheetahgenerator.CheetahGenerator, weewx.reportengine.CopyGenerator, user.belchertown.HighchartsJsonGeneratorOn Monday, May 27, 2024 at 10:06:02 PM UTC-5 Mark Jenks wrote:false alarm so far.  mqtt is tied to belchertown.    So, seems to be belchertown like you suspected.   Digging more tomorrow.On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote:I just ripped mqtt out also.  I'll check it in the morning and see if that makes a difference.On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote:Bad news?  I uninstalled belchertown, and it's still hitting high CPU on mariadb and python3.  This is the hit to the DB.SELECT * FROM archive WHERE dateTime > 1704088800 AND dateTime <= 1735711200 ORDER BY dateTime ASCOn Monday, May 27, 2024 at 7:16:36 PM UTC-5 Tom Keffer wrote:That query is asking for every single record over 4 years of data --- about 400,000+ records with a 5 minute archive interval. That's not the use pattern when an xtype is causing the problem.It's hard to imagine why the Belchertown skin would need data at that density. Try isolating the problem by shutting off the imagegenerator, then the cheetahgenerator (you can do that by modifying generator_list in skin.conf).Then once you know which one is the culprit, then start trimming their respective sections in skin.conf until you isolate the plot or tag that is causing the problem.On Mon, May 27, 2024 at 4:47 PM Mark Jenks  wrote:Just built a new weewx on my Fedora 38 this morning, and attached it to my mariadb.  It has 13 years worth of data in it.I am running Belchertown and mqtt, and installed Windy.  But I just removed Windy to see if that was it, but still does it.  Python and/or moriadb goes to 100% CPU.Mariadb says the high query during that time is:  SELECT * FROM archive WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime ASCBut that makes no sense, since I can query my entire archive table (select *) in about 3 seconds.Any thoughts on how to catch what is going on?   I could enable debug, but hoping for a better way other that looking at a ton of logs.Thanks!



-- 
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+...@googlegroups.com.
To view this discussion on the web 

Re: [weewx-user] beta of V5.1.0 is available

['Ian Millard' via weewx-user]

Tom,

With a pip install, a big tick in the box for the 4 four bullet points. 
Everything executed perfectly as far as I can see. The journal log is clean 
with no errors. Language options not tested,

Skins, Seasons and weewx-DivumWX Alpha (replacement for weewx-Weather34)
Hardware, Various Ecowitt  and Ecowitt 2000 Hub
Driver weewx-gw1000
Server Debian 12, Apache2 running on a re-purposed Apple MacMini
URLs, https://claydonsweather.org.uk  and 
   https://claydonsweather.org.uk/seasons

IM

> On 25 May 2024, at 23:06, Tom Keffer  wrote:
> 
> python3 -m pip install weewx --upgrade -i 

-- 
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/2D798649-3B72-4D0A-A379-8CABD2F81609%40btinternet.com.

Re: [weewx-user] Error Reading GW1100

['Ian Millard' via weewx-user]

Following on, hers is my open gw1000 stanza in whew.conf: -

[GW1000]
# This section is for the Ecowitt Gateway driver.

# How often to poll the API, default is every 20 seconds:
poll_interval = 4

# The driver to use:
driver = user.gw1000
# gateway device IP address:
ip_address = 192.168.1.89
port = 45000

[[field_map_extensions]]
batteryStatus1 = wh65_batt
barometer = relbarometer


> On 11 May 2024, at 11:21, 'steepleian' via weewx-user 
>  wrote:
> 
> weewx.conf

-- 
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/3F62BDD5-3823-427E-9AE4-8C0B382034BB%40btinternet.com.

Re: [weewx-user] Raddy L7 Weather Station: XML of Current Conditions-How to Feed WeeWx?

['Ian Millard' via weewx-user]

FWIW here you can find a very good online json path finder and validator which 
is very useful in helping to work out a parsing scheme which can be adapted for 
various computer languages: -

https://www.site24x7.com/tools/jsonpath-finder-validator.html

> On 6 Mar 2024, at 21:59, Rich Bell  wrote:
> 
> I have not tried parsing this via MQTTSubscribe, but I have my doubts that it 
> currently handles it.
> rich
> 
> On Wed, Mar 6, 2024 at 3:33 PM vince  > wrote:
>> You have some pretty hideously formatted JSON to parse, but here's what it 
>> looks like in a more readable format after piping it through 'jq' and doing 
>> a little hand editing for readability
>> 
>> {
>> 
>>   "sensor": [
>> {
>>   "title": "Indoor",
>>   "list": [
>> [ "Temperature", "68.9", "°F" ],
>> [ "Humidity", "38", "%" ] ]
>> },
>> {
>>   "title": "Outdoor",
>>   "list": [
>> [ "Temperature", "61.7", "°F" ],
>> [ "Humidity", "29", "%" ] ]
>> },
>> {
>>   "title": "Pressure", "list": [
>> [ "Absolute", "26.76", "inhg" ],
>> [ "Relative", "29.84", "inhg" ] ]
>> },
>> {
>>   "title": "Wind Speed",
>>   "list": [
>> [ "Max Daily Gust", "5.1", "mph" ],
>> [ "Wind", "1.1", "mph" ],
>> [ "Gust", "1.6", "mph" ],
>> [ "Direction", "123", "°" ],
>> [ "Wind Average 2 Minute", "0.4", "mph" ],
>> [ "Direction Average 2 Minute", "111", "°" ],
>> [ "Wind Average 10 Minute", "1.3", "mph" ],
>> [ "Direction Average 10 Minute", "134", "°" ]
>>   ]
>> },
>> {
>>   "title": "Rainfall",
>>   "list": [
>> [ "Rate", "0.0", "inch/hr" ],
>> [ "Hour", "0.0", "inch", "43" ],
>> [ "Day", "0.0", "inch", "44" ],
>> [ "Week", "0.0", "inch", "45" ],
>> [ "Month", "0.0", "inch", "46" ],
>> [ "Year", "5.72", "inch", "47" ],
>> [ "Total", "10.65", "inch", "48" ]
>>   ],
>>   "range": "Range: 0inch to 393.7inch."
>> },
>> {
>>   "title": "Solar",
>>   "list": [
>> [ "Light", "261.36", "w/m²" ],
>> [ "UVI", "1.2", "" ]
>>   ]
>> }
>>   ],
>>   "battery": {
>> "title": "Battery",
>> "list": [ "All battery are ok" ]
>>   }
>> }
>> 
>> 
>> On Wednesday, March 6, 2024 at 11:59:36 AM UTC-8 Michael wrote:
>>> I have officially given up on getting interceptor to work in sniffing mode 
>>> on Phython3.  
>>> 
>>> On Wednesday, March 6, 2024 at 11:17:39 AM UTC-7 matthew wall wrote:
 it looks like the raddy L7 can upload to wundgerground, so if you are 
 using the raddy's wifi, you should be able to use the interceptor driver 
 to capture or directly receive the wunderground output.  setting up the 
 interceptor is not trivial, but there are many examples.
 
 it would be nice if there were a generic json driver, analogous to the 
 fileparse driver.  but the json structure varies a lot from one device to 
 another, and the mechanism for obtaining that json output also varies.  
 for example, the tempest broadcasts json data, whereas the ruddy emits 
 json as a response to http request.  so i understand why no one has 
 written one yet.
 
 m
>> 
>> 
>> -- 
>> 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/421d1ce1-9dcf-4148-827d-b97c92a4495cn%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/CAG4CQqyqTkcda9a5EWe6DVbz2oPJtnqf_9Q2kbG%3DWCksxKgsvw%40mail.gmail.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/4AC3D106-F4E4-479A-804D-C374DCEB94EA%40btinternet.com.

Re: [weewx-user] DivumWX Template

['Ian Millard' via weewx-user]

Hi Kjell,

I know its frustrating and there are many others like you out there.

I still cannot give you an exact date but it will be soon.

The public beta will be launched with its own installer (just like 
weewx-Weather34’s installer) but it will only support WeeWX version 5.x.x which 
has been installed by pip.

We believe that this is the way to go in the future as this one method covers 
all operating systems. It is super easy to upgrade and maintain from our 
support point of view. 

If you want to get ready, I recommend that you make a fresh clean install of 
WeeWX 5.x.x into a virtual environment using pip.

Will let you know when the beta is ready. I might even be able to let you have 
an advanced copy. If you have a Telegram account, I have started a group for 
potential early adopters.

Regards,
Ian

> On 4 Mar 2024, at 20:52, G400  wrote:
> 
> Kjell

-- 
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/5566C5CE-6332-4A69-834D-6755C4CC55B2%40btinternet.com.

Re: [weewx-user] WeeWX series tags with Highcharts

['Ian Millard' via weewx-user]

Funnily enough I have been working the other way round. I have been using under 
lying Python code in my skin (formerly weewx-Weather34, but soon to be 
relaunched with a massive code re-write as weewx-DivumWX). I and a fellow 
developer were having trouble with a particularly complicated chart when I 
remembered the serial tags. All became very clear once we worked out the syntax 
required to generate the specific Highcharts serial data). It all becomes clear 
and very easy after that.

> On 4 Sep 2023, at 12:49, bell...@gmail.com  wrote:
> 
> Works

-- 
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/406ADB35-E1D6-4682-BB4A-F27B7D70DDFB%40btinternet.com.

Re: [weewx-user] Re: GW1000 Ecowitt Gateway and WeeWx 5.0

['Ian Millard' via weewx-user]

How did you attempt the install? I am running version 5 with a pip installation. I am also running the Gateway driver and it installed seamlessly using weectl extension install [URL]Sent from my iPad.On 15 Aug 2023, at 05:57, gert.a...@gmail.com  wrote:Hi VinceI followed the installation guide for the driver, but the installation used the folder structure from WeeWx version 4.RgdsGertOn Tuesday, August 15, 2023 at 1:44:12 AM UTC+2 vince wrote:sure why wouldn't it be ?On Monday, August 14, 2023 at 2:03:23 PM UTC-7 gert.a...@gmail.com wrote:HiIs it possible to install the gateway with WeeWx 5.0ThanksGert



-- 
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/99af5f5f-3f49-441d-acf0-e4006a1e734fn%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/E0E36273-3A90-488C-A6E1-0C5835834243%40btinternet.com.

Re: [weewx-user] Re: Weather34 Skin and no rain

['Ian Millard' via weewx-user]

Is your website public. If so can you direct me to it please. Otherwise PM your w34realtime.txt file.Thank you,IanSent from my iPad.On 22 Mar 2023, at 02:10, Peter Peter  wrote:As a side note I also miss the solar radiation reading as well (but get the UV) so I am thinking as per the reading of other conversations that it has something to do with real time filesOn Wednesday, March 22, 2023 at 1:08:36 PM UTC+11 Peter Peter wrote:First question: Is this the correct place/forum/group for Weather34?if yes see nextOk all and thanks to Garry we seem to be collecting data via Weewx including rain butits not showing up in the Weather34 skin. I have been searching around in the weewx conf file etc and looked at various things but cannot find an explanation for the seetings so maybe there is no issue and the settings are just incorrect.the main thing I can see is Weather34RealTime]    realtime_path_only = ""    unit_system = METRICWX    exclude_fields = rain    cache_enable = True    cache_stale_time = 900So I was wondering if the exclude_fields = rain is my issue or the missing paths?and somewhere else there was something to do with rain, mm 5 and I wondered if that was a minimum amount to register or something?    weewx_port = 25252    webserver_address = ""    weewxserver_address = ""    weewx_file_transfer = ""    HTML_ROOT = ""



-- 
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/800ab33e-8ddc-4f16-8ddc-c464b445de0cn%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/F5D1DEA8-D415-468D-965B-3416D2C5E30B%40btinternet.com.

Re: [weewx-user] Re: Trouble viewing new data column(s)

['Ian Millard' via weewx-user]

Gary,Follow up question from me in a similar vein. What is the correct way to add a completely new measurement group to WeeWX, for example part_per_million_per_cubic_meter?IanSent from my iPad.On 17 Jan 2023, at 05:20, gjr80  wrote:If you add a new observation to the database you need to tell WeeWX what unit group it belongs to in order to be able to effectively use the formatting and unit conversion capabilities of the WeeWX tag system in reports. For example, if you add a field that is a pressure once WeeWX knows the new field is a pressure WeeWX knows what default formatting to apply, the correct unit label and you can use the formatting and unit conversion aspects of the tag system to change the format/convert units in a WeeWX report template. If WeeWX does not know what unit group the observation belongs to you just get the raw value from the database (which is typically a float with many decimal places - ie what you are seeing now).There are a number of ways to assign an observation to a unit group. In your case the easiest approach is to add a few lines of code to /home/weewx/bin/user/extensions.py (or /usr/share/weewx/user/extensions.py if you installed WeeWX as a package). Try adding the following to the bottom of extensions.py:import weewx.unitsweewx.units.obs_group_dict['waterTemp'] = 'group_temperature'weewx.units.obs_group_dict['tideHeight'] = 'group_length'(group_temperature was the obvious choice for waterTemp; tideHeight could be group_length, group_altitude, group_rain or group_distance. The deciding factor here is the available units for each group - if you look at the Units appendix to the Customisation Guide you will see what I mean)You will need to restart WeeWX for the changes to take effect. The extensions.py code is run at WeeWX startup and the above lines will make the appropriate unit group assignments for your new fields. You should now be able to use tags based on waterTemp and tideHeight in your reports. You will find some further info on assigning unit groups in the Customising units and unit groups section of the Customisation Guide. You will also find information on the WeeWX tag system in the Tags section of the Customisation Guide.A couple of notes about units.For the WeeWX tag system to correctly and consistently display observation values and units you need to ensure the data you are adding to the database is in the correct units. How you do this depends on how you are inserting data into the database. If you are using a WeeWX service to augment loop packets (the preferred approach) then your service needs to take cognisance of the unit system (ie WeeWX field usUnits) of the loop packet being augmented and add waterTemp and tideHeight to the loop packet using the appropriate units for the unit group each observation belongs to for the unit system used by the loop packet. For example, if the loop packet uses US customary units (ie usUnits = 0) then waterTemp would need to be in Fahrenheit and tideHeight in inches. Once you do this WeeWX takes care of everything else. You will find information on the unit systems, unit groups and units used by WeeWX in the Units appendix to the Customisation Guide.If you are directly inserting data in the WeeWX database (not the preferred approach) then it is up to you to ensure that the values are inserted using units applicable to the database unit system and the unit group used for each observation.Apologies for the long response but the WeeWX tag/unit/formatting system has a lot of moving parts and you need to have them all correctly configured or you will have problems.GaryOn Tuesday, 17 January 2023 at 07:19:24 UTC+10 ja...@runser.net wrote:Incremental progress. As described above but with the addition of a restart I have data in the statistics section but still N/A for Water Temp in "Current Conditions". Further, the data in statistics is formatted as "00.00" instead of the hoped-for "00.00 

°F". I've walked through the template and inc files but still can't find the right building blocks. I even tried changing the waterTemp column from a double to a double(4,2) but am still getting all the extra zeros.On Monday, January 16, 2023 at 2:16:12 PM UTC-5 James Runser wrote:I'm trying to integrate a home-built tide and temperature monitor into weewx (configured and working without issue with an Acurite Atlas). I'm using a MySQL DB and tried simply inserting my data (waterTemp, tideHeight) into archive. I use current timestamp, usUnits and 10 for the required interval values and let the remaining columns default to null ( except - duh - waterTemp and tideHeight). The data are written without issue but I'm never seeing the results in the Seasons report - I chose waterTemp as the learning value since the skin.conf already had a reference to water temp.My thinking is that my data is not returned by the report engine - based, perhaps - on timestamp? Is there a better way to hook net new data into the flow? I do in fact see the waterTemp 

Re: [weewx-user] Re: Weewx to Mastodon/ActivityPub?

['Ian Millard' via weewx-user]

Intrigued that webcam pictures of Somerset skies above Yeovil are deemed to be 
“Sensitive content” :-)

Sent from my iPad.

> On 21 Dec 2022, at 14:50, Mark Fraser  wrote:
> 
> On 21/12/2022 14:35, DaveStLou wrote:
>> Very interesting. Temporarily I've been duplicating my Twitter posts to 
>> Mastodon using IFTTT but plan to make the change to native support.
>> Would you mind posting a link to your Mastodon profile so we can see the 
>> results?
>> On Wednesday, December 21, 2022 at 8:16:34 AM UTC-6 mfr...@gmail.com wrote:
>>On 21/12/2022 07:45, Glenn McKechnie wrote:
>> > Hi Chris,
>> >
>> > Nothing like finding a day where you can plunge, guilt free, into
>>the
>> > ToDo list. I didn't have a Snow day, but I borrowed yours!
>> >
>> > I started re-purposing Matthew Walls twitter extension (which runs
>> > uses RestX - [StdRESTful] ) and have had good success with it in the
>> > half day or so that it's been runnng. Still some work to do on it
>> > (phttt) but the text part works well enough.
>> >
>> > Your use of the template is interesting - that gives it a bit of
>>flexibility.
>> >
>> > I'll mull that one over while I continue down the media (image)
>>path.
>> >
>> > Alpha is at ...
>> > https://github.com/glennmckechnie/weewx-mastodon
>>
>> >
>> >
>> > On 21/12/2022, Chris Alemany  wrote:
>> >> The snowy weather here on Vancouver Island has given me some
>>unexpected
>> >> time to work on this. I now have a working template file and
>>python script
>> >>
>> >> that will produce and post weewx data to a Mastodon account.
>> >> Just setup an account on your favourite Mastodon server,
>> >> mark it as a bot,
>> >> create an API/Client Key (under development in your account's
>>preferences)
>> >> install the template file to one of your skins (I just added it
>>to the
>> >> Standard skin.
>> >> put the python file somewhere it can be run with cron
>> >> run the python file with a command like this:
>> >>
>> >> sudo python3 weewx_to_mastodon.py --server https://mstdn.ca
>> --wxdata
>> >> https://mywebpage.com/mastodon.json
>> --api_key biglongstring234fssdf
>> >>
>> >> I've attached my working files if anyone is itching to have it,
>>excuse the
>> >> messy code but it should be fairly self explanatory. You should
>>only really
>> >>
>> >> need to modify the values in the json.tmpl file.
>> >>
>> >> On Sunday, December 18, 2022 at 3:40:31 PM UTC-8 Chris Alemany
>>wrote:
>> >>
>> >>> Here is the promised link to the fellow who created a Python
>>script from
>> >>> cumulus on Mac to Mastodon/ActivityPub:
>> >>>
>>
>> https://github.com/buffaloseven/CumulusMX-Customizations/tree/main/integrations
>>  
>> 
>> >>>
>> >>> Sent from my iPhone
>> >>>
>> >>> On Dec 15, 2022, at 6:24 AM, Chris Alemany 
>>wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>>
>> >>>
>> >>> Has anyone had a go at having weewx post to Mastodon/Fediverse,
>>either to
>> >>>
>> >>> an existing @user@server or as an independent instance?
>> >>>
>> >>> There is at least one fellow who has written some Python to do
>>it from his
>> >>>
>> >>> cumulus based system. I will share his GitHub project if
>>someone thinks
>> >>> they can do it.
>> >>>
>> >>> Cheers
>> >>> Chris
>> >>>
>> >>> Sent from my iPhone
>>I've been posting to Mastodon for a while now and I've done it a bit
>>differently.
>>In skin.conf of what ever skin you are using (Seasons for me) I added:
>>[[MastodonHourly]]
>>encoding = strict_ascii
>>template = mastodon.out.tmpl
>>mastodon.out.tmpl contains:
>>Temp: $current.outTemp Humidity: $current.outHumidity\nPressure:
>>$current.barometer\nWind: $current.windDir.ordinal_compass,
>>$current.windSpeed (ave), $current.windGust (gust)\nRain Rate:
>>$current.rainRate Rain Total: $day.rain.sum\nSolar Radiation:
>>$current.radiation UV: $current.UV\nSoil Moisture: $current.soilMoist1
>>Lastly I have this python script run hourly from a Crontab using
>>Mastodon.py and I can upload an image from my webcam at the same time:
>>#!/usr/bin/env python3
>>from mastodon import Mastodon
>>from datetime import datetime
>># Set up Mastodon
>>mastodon = Mastodon(
>>access_token = '',
>>api_base_url = ''
>>)
>>photo_path = '/var/www/html/webcam.jpg'
>>now = datetime.now()
>>spoiler = 'Live weather for #Yeovil at ' + now.strftime('%d/%m/%y
>>%H.00')
>>f = open('/var/www/html/weewx/mastodon.out','r')
>>media = 

RE: [weewx-user] Weewx+Weather34 pop up charts in Mobile

['Ian Millard' via weewx-user]

The pop-up menus are not designed for ideal mobile viewing although you will 
get a better view holding the phone in landscape mode.

We are looking to address this in a massive rewrite which is currently under 
way. In future the new name for weewx-weather34 will be DivumWX.

Ian

Sent from Mail for Windows

From: Raffaello Galli
Sent: 18 October 2022 08:31
To: weewx-user
Subject: [weewx-user] Weewx+Weather34 pop up charts in Mobile

Hi, 
After the installation of weewx+weather34+nginx+php on my raspberry pi,  
everything is working and looking fantastic when I am connected from a pc or 
tablet.

When I am connecting using a mobile the pop charts are not displaying correctly.
Example the  Rainfall or Narometer Almanac or in any case a pop windows that 
contains a chart.
I tried to look at the https://claydonsweather.org.uk/weewx/divumdev/  url to 
see if I had made some mistake, but it has the same behavior.

The problem is ONLY related to the pop windows when they have charts inside.
Tipically a pop window has  two or three iframe and the iframe that contains 
the chart will show half of it and is not scrollable at all (when viewed with a 
phone).

The same effect is reached when you try to emulate a mobile screen shrinking 
the width of a browser on your PC.  Shrink until you have a single list of box 
instead the 3x3 standard page.

Did anyone have the same experience?
Thanks.
-- 
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/ffa07279-3fe7-45b5-8f26-6170c2bfd904n%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/634faaf0.2e0a0220.e405c.7468SMTPIN_ADDED_BROKEN%40gmr-mx.google.com.