Home
-
Why did I use csv and not xml? Sending xml to influx works great but is converted and consumes high memory/cpu. Many people are running this type of influx/grafana stack on a RasberryPI and thus running with csv, allows for an entire year of import to take a few seconds and little memory.
-
Why unsecure influxdb v1? It is a very common stack used on private networks, but strongly recommend all home users to start using secure engines in thier home network to practice Privacy by Design. Also as to why InfluxDB v1 at all, InfluxDB v2 changed from sql to thier own language and some basic functions are missing. I am working on a InfluxDB V2 version and using flux for the grafana dashboard
-
Why only Southern California Edison and PEP. Green Button Data is provided by most utilities as a standard US Department of Energy Standard. But the output format is not standardized. Please create an issue and provide a sample for any other utilities. This also includes non-Solar sample files. If you do, make sure you blank out any personal information in the file like your account number or address. If you want to add logic to parse another file format, please contact me to be a contributor.
-
How can I get more details of my energy usage? Look at something like VUE (https://www.emporiaenergy.com/) and then bring that data back with other github projects.
-
Normal all green button extracts are in local time and this is assumed. The program will convert to UTC time which is the standard for influxdb. You may explicitly set your time zone in the tool of choice when reporting. Grafana converts the data to local browser time zone by default.
-
Added a tag for month, since it is convoluted to group by month in influxql. But it will be calendar month not billing month. Due to weekends and holidays, it seems that the billing date shifts over the year.
SCE updated the Net Metering format for all NEM 2.0 customers.
