There are 2 problems:
The first problem is that the supported device classes for HEM v1 were incorrect from the perpper1db. The HEM v1 supports Association (needed for reports), but pepperdb did not indicate this fact. To fix this, perform steps below:
+ Go to [Configuration] / [Groups and Modules] and find your HEM node.
+ Click the button with 3 lines (far right) to open parameter editor.
+ Find ZWaveNode.NodeInfo and for value, add 85 to the end (make sure to seperate previous value with a space).
+ Press SAVE button.
Now, you need to add the association to HG so it can see reports.
+ Click the HEM node to the left of the button with 3 lines.
+ Next to the "Sensor" dropdown, hit the SETUP button.
+ You should see the "Associations" TAB!
+ Next to the "Add" button, enter 1 for node id.
+ Click the "Add" button.
Automated reports can now be seen!
HG will start receiving report data, but this is where the 2nd problem will occur, but fortunately, is mainly cosmetic. The current version of HG has difficulty reading the automated reports from HEM, so you will see "Generic" and "Binary" value reports instead of correct Meter and MultiInstance report values. I have the HEM v1 so was able to develop a fix. I will be submitting the code to Gene in the next day, so it may be coming soon to the HG updater. For now, a c# script can be added that transforms these reported value names so they show up in the correct areas in the energy widget. I'll need to see if I can create one that works for you, since I am currently running a version of HG with my code fix which negates the need for this script.