1.7.2

Breaking changes

• None

New features

• None

Other changes

• Fixed daily metric collection after a new month cycles - @cdolghier
• Upgrade to pyemvue 0.18.1 - @jertel

1.7.1

Breaking changes

• None

New features

• None

Other changes

• Added --debug arg to dump all points to console prior to sending to the database - @jertel
• On startup the new detailedDataHousesEnabled and detailedDataSecondsEnabled values will be printed to console - @jertel
• On startup the version will be printed to console - @jertel
• Fixed issue when hourly and historic data was collected it was discarding the previous minute data - @jertel
• Removed unused --quiet arg - @jertel
• Removed unnecessary --version arg - @jertel
• Refactored --verbose flag to properly use logging level - @jertel
• Removed unnecessary, duplicated queries - @jertel

1.7.0

Breaking changes

• None

New features

• Added detailedDataSecondsEnabled and detailedDataHoursEnabled to selectively fetch one or (or both) seconds- and hours- resolution data iff detailedDataEnabled = true
• Added timezone config to allow configuring the timezone according to which end-of-day is calculated.

Other changes

• Fixed --resetdatabase (broken in 1.6.1)

1.6.1

Breaking changes

• None

New features

• None

Other changes

• Upgrade to Python 3.12.1, replace deprecated datetime invocations - #141 - #jertel
• Fixed extractDataPoints to recurse correctly for nested devices - #140 - #cdolghier

1.6.0

Breaking changes

• Replaced Minute with Hour as normal interval since history is limited to 7 days from Emporia on minute data
• argparse libary was added, must run pip install -r requirements.txt again in the src directory (or pip3 based on install)

New features

• Hour / Day historic data retrieval: allows for history of up to two years to be pulled. Assists in clean numbers/graphs to see daily monthly usage to compare against utilities reports.
• Hour data runs with the get details time, default is 1 hour (3600 seconds). Based on when the program is started, you may be almost 2 hours behind for get hour.
• Moved one-time parameters out of the json config file. Those parameters are now specified as command line arguments (--historydays, --resetdatabase).

Other changes

• Started Changelog for this and future releases
• Added project metadata to vuegraf.py, values can be updated through github automations
• Added command line pairing with help syntax for all values, via argparse lib.
• Updated requirements.txt and setup.py with argparse>= 1.4.0
• Updated vuegraf.json.sample as history and reset database was moved to command line
• Updated Readme.md with above changes
• ran pylint and fixed
  Quote delimiter consistency to all '
  Whitespaces
  Extra lines

With special thanks to @gauthig for initiating these 1.6.0 changes!

1.5.0

• To avoid confusion, detailed data (per second data) will not be collected by default. When collected, this can cause Influx metrics to be incorrect, unless care is taken to exclude the detailed data on each query. To enable detailed data anyway, add the following top-level config setting to your vuegraf.json file: detailedDataEnabled: true.
• Clarify documentation to note that Emporia Utility Monitors are supported.

1.4.0 Release

Changes:

• Add TLS/SSL support to InfluxDB connection
• Add support for historic ingest of energy data
• Upgrade to latest pyemvue library version 0.16.0
• Upgrade to latest InfluxDB 1.x library version 5.3.1
• Upgrade to latest InfluxDB 2.x library version 1.33.0

1.3.4 Release

• Upgrade to PyEmVue 0.15.0 to resolve API change by Emporia

Note that this build's Docker Image is much larger than the previous release. This is due to the need for the newer cryptography Python package's Rust code to be compiled on Alpine distros since there is no pre-built package available on Alpine. Additionally, the docker build command will take significantly longer than it used to, for those that prefer to build their own images.

1.3.3 Release

• Add detailed tag to InfluxDB v2 (already present in InfluxDB v1)
• Avoid pulling details on invalid channels
• Record Balance and TotalUsage (solar only) metrics

1.3.2

• Add support for nested devices

Known Issue:

• The detailed per-second data is not being adjusted correctly by Emporia's servers for nested devices.