[weewx-user] Re: weewx-wdc Skin v3.0.0 available

[Greg from Oz]

Also is there a setting for time of last rain? E.G 5 days 3 hours 2 minutes



On Wednesday, 8 March 2023 at 14:22:58 UTC+11 Greg from Oz wrote:

> OK figured out group_distance was missing in the Defaults in weewx.conf
> group_distance = km
> Fixed it.
>
>
> On Wednesday, 8 March 2023 at 13:50:20 UTC+11 Greg from Oz wrote:
>
>> Looks good. Windrun is in miles though.
>>
>>
>> On Tuesday, 7 March 2023 at 06:22:15 UTC+11 David Bätge wrote:
>>
>>> Hi all,
>>>
>>>
>>> I just wanted to inform you that a new version is available for the 
>>> weewx-wdc 
>>> skin  for download 
>>> 
>>> .
>>>
>>>
>>> This release includes some big updates and refactoring:
>>>
>>>- Several Bugfixes and enhancements for weewx-forecast
>>>- Show weather data for a specific day - Daily archive
>>>- Make diagrams configurable per context (per period) / Refactor 
>>>diagrams configuration. Diagrams can now be configured per context, eg. 
>>>day, week or month. Per default, the day and week pages do not include 
>>> the 
>>>outTemp min/max/avg diagram anymore.
>>>- Make show_min, show_max, show_sum configurable for stat tiles 
>>>- Support for custom data_bindings
>>>- Configurable Icons
>>>- Configurable unit for diagrams
>>>- Configurable Rounding
>>>- Configurable markers for diagrams
>>>- Automatic Refresh (via http-equiv="refresh")
>>>- Added new climatogram (combined chart consisting of rain as bar 
>>>and temp as line) for statistics and yearly statistics pages
>>>- Update radar_img to allow for raw HTML (for using eg. iFrames as 
>>>radar maps)
>>>
>>>
>>> Also included is "Support for combining different diagram types" (eg. 
>>> line and bar). I added an own implementation of chart rendering based 
>>> directly on D3.js , which will replace the current nivo 
>>> library  in a future release. The direct usage of 
>>> D3 allows for really custom implementations, so I am very open to new ideas 
>>> of visualizations.
>>>
>>>
>>> Please see 
>>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#ENABLE_D3_DIAGRAMS 
>>> for 
>>> more information if you want to test this out in v3.0.0.
>>>
>>>
>>> Since this release includes a near rewrite of the skin.conf, you likely 
>>> have to make some changes to it, if you had the skin very heavily 
>>> customized in a previous version.
>>>
>>>
>>> The wiki  was updated to 
>>> include information about all the new features and configurations. If you 
>>> encounter any problem or bug, just let me know!
>>>
>>>
>>> Thank you all for your feedback/contributions to the skin!
>>>
>>>
>>> Changelog/Download: 
>>> https://github.com/Daveiano/weewx-wdc/releases/tag/v3.0.0
>>>
>>

-- 
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/3840a650-2860-4098-baad-046ef87ff061n%40googlegroups.com.

[weewx-user] Re: weewx-wdc Skin v3.0.0 available

[Greg from Oz]

OK figured out group_distance was missing in the Defaults in weewx.conf
group_distance = km
Fixed it.


On Wednesday, 8 March 2023 at 13:50:20 UTC+11 Greg from Oz wrote:

> Looks good. Windrun is in miles though.
>
>
> On Tuesday, 7 March 2023 at 06:22:15 UTC+11 David Bätge wrote:
>
>> Hi all,
>>
>>
>> I just wanted to inform you that a new version is available for the 
>> weewx-wdc 
>> skin  for download 
>> 
>> .
>>
>>
>> This release includes some big updates and refactoring:
>>
>>- Several Bugfixes and enhancements for weewx-forecast
>>- Show weather data for a specific day - Daily archive
>>- Make diagrams configurable per context (per period) / Refactor 
>>diagrams configuration. Diagrams can now be configured per context, eg. 
>>day, week or month. Per default, the day and week pages do not include 
>> the 
>>outTemp min/max/avg diagram anymore.
>>- Make show_min, show_max, show_sum configurable for stat tiles 
>>- Support for custom data_bindings
>>- Configurable Icons
>>- Configurable unit for diagrams
>>- Configurable Rounding
>>- Configurable markers for diagrams
>>- Automatic Refresh (via http-equiv="refresh")
>>- Added new climatogram (combined chart consisting of rain as bar and 
>>temp as line) for statistics and yearly statistics pages
>>- Update radar_img to allow for raw HTML (for using eg. iFrames as 
>>radar maps)
>>
>>
>> Also included is "Support for combining different diagram types" (eg. 
>> line and bar). I added an own implementation of chart rendering based 
>> directly on D3.js , which will replace the current nivo 
>> library  in a future release. The direct usage of 
>> D3 allows for really custom implementations, so I am very open to new ideas 
>> of visualizations.
>>
>>
>> Please see 
>> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#ENABLE_D3_DIAGRAMS 
>> for 
>> more information if you want to test this out in v3.0.0.
>>
>>
>> Since this release includes a near rewrite of the skin.conf, you likely 
>> have to make some changes to it, if you had the skin very heavily 
>> customized in a previous version.
>>
>>
>> The wiki  was updated to 
>> include information about all the new features and configurations. If you 
>> encounter any problem or bug, just let me know!
>>
>>
>> Thank you all for your feedback/contributions to the skin!
>>
>>
>> Changelog/Download: 
>> https://github.com/Daveiano/weewx-wdc/releases/tag/v3.0.0
>>
>

-- 
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/00e264eb-b739-4ee4-af4c-a6feeab06be9n%40googlegroups.com.

[weewx-user] Re: weewx-wdc Skin v3.0.0 available

[Greg from Oz]

Looks good. Windrun is in miles though.


On Tuesday, 7 March 2023 at 06:22:15 UTC+11 David Bätge wrote:

> Hi all,
>
>
> I just wanted to inform you that a new version is available for the weewx-wdc 
> skin  for download 
> 
> .
>
>
> This release includes some big updates and refactoring:
>
>- Several Bugfixes and enhancements for weewx-forecast
>- Show weather data for a specific day - Daily archive
>- Make diagrams configurable per context (per period) / Refactor 
>diagrams configuration. Diagrams can now be configured per context, eg. 
>day, week or month. Per default, the day and week pages do not include the 
>outTemp min/max/avg diagram anymore.
>- Make show_min, show_max, show_sum configurable for stat tiles 
>- Support for custom data_bindings
>- Configurable Icons
>- Configurable unit for diagrams
>- Configurable Rounding
>- Configurable markers for diagrams
>- Automatic Refresh (via http-equiv="refresh")
>- Added new climatogram (combined chart consisting of rain as bar and 
>temp as line) for statistics and yearly statistics pages
>- Update radar_img to allow for raw HTML (for using eg. iFrames as 
>radar maps)
>
>
> Also included is "Support for combining different diagram types" (eg. line 
> and bar). I added an own implementation of chart rendering based directly 
> on D3.js , which will replace the current nivo library 
>  in a future release. The direct usage of D3 allows 
> for really custom implementations, so I am very open to new ideas of 
> visualizations.
>
>
> Please see 
> https://github.com/Daveiano/weewx-wdc/wiki/Configuration#ENABLE_D3_DIAGRAMS 
> for 
> more information if you want to test this out in v3.0.0.
>
>
> Since this release includes a near rewrite of the skin.conf, you likely 
> have to make some changes to it, if you had the skin very heavily 
> customized in a previous version.
>
>
> The wiki  was updated to 
> include information about all the new features and configurations. If you 
> encounter any problem or bug, just let me know!
>
>
> Thank you all for your feedback/contributions to the skin!
>
>
> Changelog/Download: 
> https://github.com/Daveiano/weewx-wdc/releases/tag/v3.0.0
>

-- 
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/f7cd087c-9b75-4b0b-bfb0-de1a0e0b5aden%40googlegroups.com.

Re: [weewx-user] OSError: [Errno 113] Aucun chemin d'accès pour atteindre l'hôte cible

[vince]

Sorry - I did not see your reply.

Try "sudo modprobe ftdi_sio"

Then run 'sudo dmesg' again and see if it attached a device in /dev 
successfully...

On Sunday, March 5, 2023 at 10:02:09 AM UTC-8 Blaise Cacramp wrote:

> "lsmod" does not see much.
> And when I try this with "insmod", it's not terrible.
> Sorry, I'm far from being a Linuxien guru
>
> pi@PiMeteo:~ $ lsmod
> Module  Size  Used by
>
> ---
>
> pi@PiMeteo:~ $ insmod /dev/ttyUSB0
> insmod: ERROR: could not load module /dev/ttyUSB0: No such file or 
> directory
>
> Le 05-03-23 à 18:34, vince a écrit :
> > So the pi is seeing the device, but it is not allocating a tty in /dev 
> > to it.
> > You might just need to insmod a kernel module so it assigns a device 
> > in /dev to it.
> >
> > Check your 'lsmod' output and see if the ftdi_sio device is loaded. 
> >  If not, load it with 'insmod' and see if that helps.
>

-- 
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/894f99e4-03d2-4d3e-9796-957a7e43426en%40googlegroups.com.

[weewx-user] Re: Webpage won't connect to MQTT

[vince]

Add a packet filter rule only permitting mqtt/1883 in from the public ip of 
your weewx system, if you have a stable ip from your internet provider...

-- 
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/0bea7630-9bd2-46dd-b724-b8f10a04880cn%40googlegroups.com.

[weewx-user] Re: Webpage won't connect to MQTT

[jterr...@gmail.com]

" *Using a userid and password for authentication for mqtt works...but the 
credentials show up as clear text in the javascript.  So no real security 
there.  Easier to just use an anonymous mqtt server.  It's just weather 
data*."

It depends on the way authentication and access control list (acl)  are 
defined, if any.  Anonymous access imply  that anyone could use your MQTT 
for their own purpose, i.e; even publishing and retrieving their own topics 
.

My mosquito MQTT broker is configured with authentication and acl, with an 
account user=public, password=public . As you said, this account is not 
hidden since it shows up as clear text in the javascript, but it is limited 
to listen to a specific topic; with no rights to publish anything or to 
listen to any other topics.


-- 
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/36181a4a-d25d-40ba-be95-6396621260c1n%40googlegroups.com.

[weewx-user] Re: Webpage won't connect to MQTT

[michael.k...@gmx.at]

It's kind of obvious that the credentials have to show up in the front end, 
if you want to provide the mqtt functionality publicly. Letting subscribe 
any anonymous client to the topic is with "hey, only weather data" no 
problem, I agree. But if you can't restrict publishing on that topic, 
anyone could publish anything, that might get displayed on you website: 
"Welcome users, currently we have 'f**k y*u' degrees in Belchertown", is 
probably not a desired message to be displayed.

You can create a user for your broker, which has only subscribe access to 
limited topics.
The topic list is limited to the ones that carry live data to be shown on 
your site.
Nothing else can be done, but subscribe to the topic.
==> it's no issue to provide these credentials readable for everyone.

Allowing any anonymous user to subscribe (and only subscribe) is also okay. 
It all depends, in which way you can set it up. With my provider, I can't 
configure anonymous access, so the credentials for a "subscribe only" 
client is visible in the front end.

Rich M schrieb am Dienstag, 7. März 2023 um 15:27:49 UTC+1:

> I found two things:  1...there really was no reason to use the proxy 
> server for the mqtt calls.  So I took it out of line, and just ran the 
> request through the cloudflare tunnel.  Worked like a charm.  
>
> 2.  Using a userid and password for authentication for mqtt works...but 
> the credentials show up as clear text in the javascript.  So no real 
> security there.  Easier to just use an anonymous mqtt server.  It's just 
> weather data.  
>
>
>
> On Sunday, March 5, 2023 at 8:04:00 PM UTC-6 gary@gmail.com wrote:
>
>> It's likely that the websockets port is not 443 as that is https and you 
>> do have your reverse proxy set for 9001
>>
>>
>> On Sunday, March 5, 2023 at 7:47:25 PM UTC-5 Rich M wrote:
>>
>>> I've been setting up Weewx with Belchertown, and everything seems to be 
>>> working great...except that I cannot connect to the MQTT within the skin.
>>>
>>> My Mosquito server is running in a docker on my Unraid server, and I 
>>> have an Ubuntu VM that is gathering UDP packets from my Tempest Weatherflow 
>>> station.  Weewx is writing the data to the Mosquito server without 
>>> problem.  I can connect to the server on my local network with MQTT 
>>> Explorer, and I can see the weather data & loop.  
>>>
>>> For the web page, I'm running a Cloudflare tunnel into my network, and I 
>>> have a CaddyV2 reverse proxy between the tunnel and the web server.  I'm 
>>> able to access the website from the Internet without problem:  
>>> https://www.2whippets.org/weather/belchertown/
>>>
>>> I have a DNS entry for mqtt.whippets.org set up in cloudflare for the 
>>> websockets, and I'm able to use MQTT Explorer to connect to the tunnel from 
>>> the internet.  wg://mqtt.2whippets.org on port 443 (with TLS 
>>> encryption).  It goes through the cloudflare tunnel to the caddy proxy that 
>>> has a config as such:
>>>
>>> {
>>>   log
>>>   tls internal
>>>   reverse_proxy 192.168.254.3:9001 
>>> }
>>>
>>> And it works through MQTT Explorer.  
>>>
>>> However, in my Weewx.conf file, my connection looks like this:
>>>
>>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = "ws://mqtt.2whippets.org"
>>> mqtt_websockets_port = 443
>>> mqtt_websockets_ssl = 0
>>> mqtt_websockets_topic = "weather/#"
>>> # disconnect_live_website_visitor = 180
>>>
>>> It doesn't seem to make any difference if I turn on Websockets_ssl.  It 
>>> still fails.  
>>>
>>> I'm using the cloudflare tunnel so that all of the certificates are 
>>> taken care of by cloudflare...and I don't have to open any ports on my 
>>> firewall.  
>>>
>>> Any ideas of where to troubleshoot?
>>>
>>> Thanks
>>>
>>> rm
>>>
>>

-- 
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/5b6b2b8f-7d98-4612-aa19-f39388a3ad7en%40googlegroups.com.

[weewx-user] Re: Webpage won't connect to MQTT

[Rich M]

I found two things:  1...there really was no reason to use the proxy server 
for the mqtt calls.  So I took it out of line, and just ran the request 
through the cloudflare tunnel.  Worked like a charm.  

2.  Using a userid and password for authentication for mqtt works...but the 
credentials show up as clear text in the javascript.  So no real security 
there.  Easier to just use an anonymous mqtt server.  It's just weather 
data.  



On Sunday, March 5, 2023 at 8:04:00 PM UTC-6 gary@gmail.com wrote:

> It's likely that the websockets port is not 443 as that is https and you 
> do have your reverse proxy set for 9001
>
>
> On Sunday, March 5, 2023 at 7:47:25 PM UTC-5 Rich M wrote:
>
>> I've been setting up Weewx with Belchertown, and everything seems to be 
>> working great...except that I cannot connect to the MQTT within the skin.
>>
>> My Mosquito server is running in a docker on my Unraid server, and I have 
>> an Ubuntu VM that is gathering UDP packets from my Tempest Weatherflow 
>> station.  Weewx is writing the data to the Mosquito server without 
>> problem.  I can connect to the server on my local network with MQTT 
>> Explorer, and I can see the weather data & loop.  
>>
>> For the web page, I'm running a Cloudflare tunnel into my network, and I 
>> have a CaddyV2 reverse proxy between the tunnel and the web server.  I'm 
>> able to access the website from the Internet without problem:  
>> https://www.2whippets.org/weather/belchertown/
>>
>> I have a DNS entry for mqtt.whippets.org set up in cloudflare for the 
>> websockets, and I'm able to use MQTT Explorer to connect to the tunnel from 
>> the internet.  wg://mqtt.2whippets.org on port 443 (with TLS 
>> encryption).  It goes through the cloudflare tunnel to the caddy proxy that 
>> has a config as such:
>>
>> {
>>   log
>>   tls internal
>>   reverse_proxy 192.168.254.3:9001 
>> }
>>
>> And it works through MQTT Explorer.  
>>
>> However, in my Weewx.conf file, my connection looks like this:
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = "ws://mqtt.2whippets.org"
>> mqtt_websockets_port = 443
>> mqtt_websockets_ssl = 0
>> mqtt_websockets_topic = "weather/#"
>> # disconnect_live_website_visitor = 180
>>
>> It doesn't seem to make any difference if I turn on Websockets_ssl.  It 
>> still fails.  
>>
>> I'm using the cloudflare tunnel so that all of the certificates are taken 
>> care of by cloudflare...and I don't have to open any ports on my firewall.  
>>
>> Any ideas of where to troubleshoot?
>>
>> Thanks
>>
>> rm
>>
>

-- 
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/ce4e8f9b-9ac1-45ab-b377-2fc6d8acbf27n%40googlegroups.com.

[weewx-user] Re: Bootstrap skin a.k.a "fuzzy-archer" v4.0 preview available

[gary....@gmail.com]

Thanks for that.
See your github discussions.

On Monday, March 6, 2023 at 3:41:40 AM UTC-5 michael.k...@gmx.at wrote:

> Hi Gary,
>
> in some of the latest commits I've put some instructions and example in 
> the shipped configs, yet they are neither complete nor very exhaustive. 
> Maybe we can improve this.
>
> First, where to start from?
>
> The basics: for having live data shown in the charts and gauges, you need:
>
>- A data source (in most cases this your weather station, but it is 
>not limited to this unique source)
>- A MQTT Broker for publishing data from the source and subscribing to 
>the topics you publish
>- Enabling the data source to emit data using MQTT. With weewx, 
>install https://github.com/matthewwall/weewx-mqtt and get it running
>   - Bind to loop packets for have data available more or less 
>   instantly:
>   [StdRestful]
>   [[MQTT]]
>   server_url = mqtt://broker.hivemq.com:1883/
>   topic = 
>   weather_{any_distinctive_string_that_is_valid_for_topics}
>   unit_system = METRIC # or whatever you prefer *but note, 
>   this will have an impact on the "payload_key" for charts and gauges*
>   binding = loop
>   - The MQTT Broker must be publicly available for viewing live data 
>over the internet, to make it easy for now, the assumption is, you use a 
>public MQTT without needing any credentials
>- You need to set up the MQTT client for the frontend in skin.conf:
>   - [JSONGenerator]
>   ...
>   [[MQTT]]
>   [[[connections]]]
>   public_mqtt
>   broker_connection = ws://broker.hivemq.com:8000/mqtt 
>   # wss (encrypted) websocket connection
>   [topics]
>   
>   
> [[weather_{any_distinctive_string_that_is_valid_for_topics}/loop]]
>   type = JSON
>
>
> That should be a working, basic setup, if I didn't miss anything. *Note*: 
> on a https:// linke you need to set up an encrypted broker connection also 
> (wss://) or it won't work.
>
> For the payload_key of each reading:
>
> This is depending of the data source. If you set up everything as 
> described above, for showing "outTemp" it will be outTemp_F. If you use 
> METRIC or METRICWX it will be outTemp_C:
> From skin.conf:
> [LiveGauges]
> [[outTemp]]
> payload_key = outTemp_F# outTemp_C if target_unit 
> 'METRICWX', or 'METRIC'
> minvalue = 0
> maxvalue = 100
> splitnumber = 10   # choose a splitnumber 
> fitting minvalue and maxvalue: e.g.: 0/100: 10, for -20/40: 6
> lineColor = '#428bca', '#b44242'   # colors are RGBa
> lineColorUntil = 32, maxvalue  # color from start of gauge 
> to value, change color of gauge ring to show important marks: 32 is 
> freezing point
> decimals = 1   # decimals for current 
> value in gauge
> #heatMapEnabled = false# disabled heatmap for 
> gauge, default true
> #animation = False # default true
>
> Things will get a bit more complicated if you use a broker that requires 
> user accounts and login credentials.
> gary@gmail.com schrieb am Montag, 6. März 2023 um 02:25:31 UTC+1:
>
>> I see no configuration instructions.
>> Surely there must be some if this uses MQTT for live updates.
>>
>> On Saturday, March 4, 2023 at 6:10:31 PM UTC-5 michael.k...@gmx.at wrote:
>>
>>> Another week over, I've fixed several bugs, added missing functionality 
>>> and did some little enhancements on the styles. I've put everything in the 
>>> master branch by now, so if you want to updated, the feature branch is now 
>>> obsolete. By the way, thanks for the feedback and issues on github. Also 
>>> thanks to Tom, who is always precise in his feedback, helps a lot.
>>>
>>> Still: there is help needed for skin specific translations.
>>>
>>>
>>>
>>>
>>> michael.k...@gmx.at schrieb am Sonntag, 26. Februar 2023 um 15:05:02 
>>> UTC+1:
>>>
 Hi all,

 there is a new version of the Bootstrap skin in the pipeline. Last year 
 this skin has been modernized and updated with interactive gauges and 
 charts, also, using MQTT live updates were made available.

 Preview: https://www.kainzbauer.net/weather/Rif/en/

 The version is still under development, to install it anyway, 
 download the "lang" branch here:

 https://github.com/brewster76/fuzzy-archer/archive/refs/heads/lang.zip

 wee_extension --install lang.zip

 Although I've installed it on several test environments, I cannot 
 guarantee everything will work flawlessly by now.

 If you encounter problems, please file any issues here: 
 https://github.com/brewster76/fuzzy-archer/issues and let me know in