Re: [weewx-development] Re: wee_extension --uninstall does not remove multiple SKIN_ROOT skin directories

Ok, Sorry, misunderstood. No, you will need to go through the process like class StdReportEngine does in reportengine.py to get the skin name, work out its location and then read the config from its skin.conf. Gary On Saturday, 8 September 2018 11:54:52 UTC+10, Pat O'Brien wrote: > > Hi Gary,

Re: [weewx-development] Re: wee_extension --uninstall does not remove multiple SKIN_ROOT skin directories

Hi Gary, I understand that part (hopefully displayed through the bit of code I shared) - what my concern was that if I'm getting the [[[Extras]]] from the config directly, that doesn't account for anything in skin.conf. So I was asking if there's a way to get "The Extras" (as merged by both co

Re: [weewx-development] Re: wee_extension --uninstall does not remove multiple SKIN_ROOT skin directories

Pat, Through an SLE you can access anything within the WeeWX universe, you just need to know where to find it and the (python) code to access it. So what does self.generator.config_dict give you? On a plain vanilla WeeWX install I can see then entire weewx.conf. Gary On Saturday, 8 September

Re: [weewx-development] notes about grafana, mqtt, influx, and weewx

On Friday, September 7, 2018 at 3:25:04 PM UTC-7, Tom Keffer wrote: > > WeeRT uses InfluxDB to store both LOOP and archive data. > > The data model is discussed > in the README. > > I like the idea of a 'deep' packet which to me has the id

[weewx-development] Re: notes about grafana, mqtt, influx, and weewx

On Friday, September 7, 2018 at 1:57:51 PM UTC-7, mwall wrote: > > if vince does not mind, i'd like to post some of our conversation here > then continue it on this thread > > Absolutely ! Some thoughts: - generating JSON-formatted MQTT topics as input is to me the ideal format - it

Re: [weewx-development] notes about grafana, mqtt, influx, and weewx

WeeRT uses InfluxDB to store both LOOP and archive data. The data model is discussed in the README. The measurement wxpackets is just the raw LOOP packets, one per row. Much like WeeWX, a timestamp and a unit system must be declared for eac

[weewx-development] notes about grafana, mqtt, influx, and weewx

vince and i have been having a discussion about how to get data from weewx into grafana. i figured there are others who could benefit from this discussion, and i'm sure there are some grafana/influx/mqtt users who could contribute. vince's application is to compare data from three different ty

[weewx-development] Re: Potential extension to Belchertown skin

Yeah this is a good idea to make it more flexible. I know I sent you a test package but that content may actually change a bit with the full 0.7 release, so make sure you have backups! Your best bet right now, at least to get things started, is to copy the portions from Gary's highchartsX gene

Re: [weewx-development] Re: wee_extension --uninstall does not remove multiple SKIN_ROOT skin directories

Will do, thanks! Another question which is sort of related. Is it possible for Skin A to get the [[[Extras]]] settings of Skin B from within an SLE? Instead of maintaining 2 sets of Extras for 2 skins, it'd be nice to have 1 across both skins. I started to play around with something like this

[weewx-development] Potential extension to Belchertown skin

I moved this here from weewx-user. I hope this is the correct place. Pat, I am using your Belchertown skin to display data from a Davis Vantage Vue weather station. The Vantage Vue does not have a UV sensor, so the Charts feature of the Belchertown skin shows an empty chart for solar radiation.

[weewx-development] Potential extension to Belchertownk skin

I moved this here from weewx-users. I hope this is the correct place. Pat, I am using your Belchertown skin to display data from a Davis Vantage Vue weather station. The Vantage Vue does not have a UV sensor, so the Charts feature of the Belchertown skin shows an empty chart for solar radiation