Project Details‎ > ‎

Project updates


Subscribe to posts

Version 1.0 Released

posted Mar 23, 2018, 5:24 PM by Tom Gutwin

Version 1.0 is released.
Let me know if you find any issues.

New updated version 0.99.RC6

posted Mar 2, 2018, 6:54 PM by Tom Gutwin

This should be the golden v1.0 , unless something pops up in the next week.
Many DB fixes that needed to be (and were) fixed before release.

New rest request to dump readings in CSV,JSON or XML

posted Feb 24, 2018, 2:25 PM by Tom Gutwin

I added an option to the rest request for db table data to add the choice of format for the results (CSV, JSON or XML)

     /rest/db/table/reading/200/json

The 200 is the number of rows/results to return.

see the FAQ for rest calls for all the details:    What Does The rest request Result Look Like

Missing readings in DB

posted Feb 24, 2018, 2:19 PM by Tom Gutwin

I broke something that has to be fixed before any further release...
I noticed that kw readings would all of a sudden begin disappearing from the Database and could not figure out why.

I think I found and patched the issue.  (autoCommit was off to allow table rendering of the result sets and never committed any db additions: not good)

I now commit before closing the DB connection.

Testing to see if it solves or regresses other issues.

Release Candidate 4

posted Aug 20, 2015, 7:06 PM by Tom Gutwin

I just released a Release Candidate (version 0.99.RC.4). 
Direct link to the PowerEYERunner.zip file; See the download page for other downloads

It includes a few bug fixes,
as well as improved information on the Servlet Admin page; available via a link on the Options page under PowewrEYE Listener Status.

Only one thing left to fix (before v 1.0) is an improvement to TimeZone Handling by adding a manual over-ride.

1.0 Release Candidate Now Avaialable

posted Jul 17, 2015, 8:07 PM by Tom Gutwin   [ updated Jul 18, 2015, 9:31 PM ]

I have completed the planned items I wanted to include in a 1.0 release.
In preparation, I am releasing a Release Candidate (version 0.99.RC.3). 
Direct link to the PowerEYERunner.zip file; See the download page for other downloads

Features are now frozen for the 1.0 release.
Only bugs will be fixed before 1.0.

Changes since last beta release:
  • The ISY configuration is now enabled/disabled on the Options page
  • The Readings cache size (used internally) was increased and can now be changed on the options page.
  • Database tables can now be archived/dumped out without having to go through the Web Pages
    • Use the REST style service calls
    •            http://localhost:8080/powereye/rest/db/table/<tablename>
                    <tablename> can be reading, energy, load_device, load_type
            or with the optional <number of rows>
               positive number means sorted descending (newest 1st)
               negative number means sorted ascending (oldest 1st)
                    http://localhost:8080/powereye/rest/db/table/<tablename>/100
            These database calls are LOOOOooong so you might want to use a commandline URL query tool like
            wget, or perl or java or whatever.

  • Improved DerbyDB stability, initialization and shutdown hooks.
  • Fixed some menu bugs
  • (attempted to) fix some AJAX threading issues.
    • These are still exposing themselves in a few non-crucial places (the sidebar values don't show up on some pages)
  • Various bug fixes.
note: that the zip file is now to large for this sites limits, so the zip now gets downloaded from a Google Drive location. The link used above should make that transparent.

A few last feature in progress...

posted Jul 15, 2015, 9:48 PM by Tom Gutwin

I have added a few configuration options for:
  • enabling/disabling the ISY connectivity
  • changing the reading cache size (that controls the default number of readings get dumped out in the charts and rest calls)
  • improved PowerEYE Admin servlet page
There is no robust way to dump the database tables out, so that is the last item I am adding for V 1.0.  I have considered various ways to implement this (SQL dialog page, dump a zip file, REST call, or a dedicated dervlet).
I am adding a REST call that will dump out the DB tables to plain text (probably a delimited string).
It will be able to be called WITHOUT going through the Web pages. That way it has minimal overhead and potential problems.

These items will be released in an 0.9 that will lead to a Release Candidate.
1.0  is still coming!

I am still here...

posted May 29, 2015, 8:18 PM by Tom Gutwin

I have just been looking at a few other things recently.
Like a new Raspberry PI, how to proxy and forward  the Rainforest messages.

Plans For Version 1.0

posted Mar 3, 2015, 9:56 PM by Tom Gutwin   [ updated Mar 3, 2015, 10:14 PM ]

I have been working on stability items and fixing bugs.
There are only a few small items I want to add before I call it Version 1.0.
  1. Fix/Improve the Data Table Rendering
    • They are very slow when retrieving the full tables when they have lots of rows
  2. A direct table export  so you don't have to create a web-table 1st.
When??? I am trying for March 29 or sooner. 

I have many ideas for new features for the 1st dot release (1.1) but am holding off to get 1.0 out first.
Some are on my To-Do list.

Updated the beta files

posted Feb 18, 2015, 10:38 PM by Tom Gutwin

The distribution files have been updated with a few notable improvements and fixes:
  • improved database shutdown and cleanup (of the derby.log file)
  • fixed the flickering power and energy readings in the powerPanels
  • more consistent sidePanel and chart sizes
  • improved Servlet console output
  • added the capability to set the EagleDB dir via a context init param or servlet init param (see the discussion group for details)
  • many other bug fixes
Go grab the updated zip or war file

1-10 of 12