Aeon HEM3 reports based on consumption changes

[kickus]

I'm using Aeon HEM3 v2 mains powered, to read out electricity consumption.

I have a serious problem. I'm able to receive event based measurement updates only for whole HEM, not for the three clamps separately. I've tested the default settings (where sensors should separately report updates on consumption changes by 10% or 50W, but I've also tried with lower values such as 3%, 10W).

Interesting though, that I'm receiving consumption change based measurement updates only for the whole HEM values. For some reason I do not get the updates for the separate clamps. When explicitly sending an update request, the values (W,kWh,A,V) are read out successfully also for the separate clamps.

I have bad experience (stability issues) of polling the clamp values, since a lot of polling has usually caused the zway server to crash after a few days.

Do you think my problem is related to the Aeon HEM3 firmware? Does anyone else have similar experiences?

[kickus]

Problem solved, or at least I do receive data now from all clamps.
I did receive some more or less magic device settings from the manufacturer (Aeon Labs).

<devices>
<deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[2,1,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[3,1,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[4,50,2]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[5,50,2]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[6,50,2]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[7,50,2]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[8,10,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[9,10,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[10,10,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[11,10,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[13,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[103,8192,4]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[111,60,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[112,120,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[113,120,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[100,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[110,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[200,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[252,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[254,0,2]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[255,0,1]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[102,2048,4]"></deviceconfiguration><deviceconfiguration id="-" instance="0" commandclass="70" command="Set" parameter="[101,4130574,4]"></deviceconfiguration>
<runscript></runscript>
</devices>

I don't know why, but settings 100, 110, 111, 112, 113 does not have any configuration options provided by the gui. The appropriate value of setting 101 was none of the options provided in the gui.

I had to apply the changes through xml.

[jimi.wester]

How did you apply the fix? Have the same problem with my HEM3 G2.

[kickus]

How did you apply the fix? Have the same problem with my HEM3 G2.

Send me your email as a pm, I can sen you some files: a hem manual that describes it and a convenience xls calculator for the binary conversion.

If you are ok with my settings then just apply them through the old expert ui.

One important nondocumented restriction: the reports are either consumption change based or regular, both caacannot be used simultanously.

[jimi.wester]

Sorry but I seem to be to new at this forum. So I cant send PM, maybe I can reply if you send me a "Hello"?

[jimi.wester]

Thanks!! work much better now!
one of the clamps is not reporting, so I have to investigate this, but seems to be working just fine otherwise...

[jensmoes]

Here is an extremely poorly written specification on the Aeon HEM parameters: http://sourceforge.net/p/homegenie/disc ... %29%20.doc which attempts to explain the 101-103 and 111-113 parameters.
Basically 101-103 specifies which events to send in groups 1 through 3 and 111-113 defines the reporting interval related to those groups (111 being the interval for the group in 101. The bits to configure the reports are documented in the last table (split over two pages).