AEON HEM G2 - openzwave endpoint error
Posted: Thursday 23 February 2017 17:53
I have been running Domoticz for a while with a Home Energy Meter HEM G2 (one clamp) working like a charm... I however today realized that the openzwave log file ~/domoticz/Config/OZW_Log.txt is reporting several times per minute a weird error (that does not show up in the domoticz logs):
While the device works flowlessly, this could be a killer for my SDCard on the RPi given all the disk writes due to this error logging and while I decided to move the openzwave logfile to a ram drive (make a symlink to a file in tmpfs) to address this at least temporarily, I have been banging my head on the wall to understand what the root cause is...
Based on all the litterature I could read on this energy meter, the zwave binding endpoints for this device can be 1, 2 or 3 based on the clamps for each of the electrical phases it can measure, depending obviously on the meter versions... I could not find any mention of the culprit endpoint 4...
I am relatively new to Domoticz, coming from the Vera world in which the HEM G2 is notoriously difficult to configure right, so I'd like to hear if anyone else faced a similar situation and possibly found a solution...
Am running domoticz version 3.6591 on a Raspberry Pi2
Thanks
Code: Select all
Error, NodeXXX, Cannot find endpoint map to instance for Command Class COMMAND_CLASS_METER endpoint 4 Based on all the litterature I could read on this energy meter, the zwave binding endpoints for this device can be 1, 2 or 3 based on the clamps for each of the electrical phases it can measure, depending obviously on the meter versions... I could not find any mention of the culprit endpoint 4...
I am relatively new to Domoticz, coming from the Vera world in which the HEM G2 is notoriously difficult to configure right, so I'd like to hear if anyone else faced a similar situation and possibly found a solution...
Am running domoticz version 3.6591 on a Raspberry Pi2
Thanks