By the way the export value should be a Boolean, not a integer
If you look directly to the values presented from ozw log there is a difference:
Node027, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x1b, 0x0a, 0x32, 0x02, 0x21 , 0x24, 0x00, 0x00, 0x00, 0x06, 0x00, 0x00, 0xc4, 0x00, 0x0f
Node027, Received Meter report from node 27: Energy =0.6kWh
Node027, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x1b, 0x0a, 0x32, 0x02, 0x41 , 0x24, 0x00, 0x00, 0x05, 0x65, 0x00, 0x00, 0xc4, 0x00, 0x09
Node027, Received Meter report from node 27: Exporting Energy =138.1kWh
If I look to the valueId creation in ozw, I think this depth of parameter is not used to create the value id, so HA is not able to distinguish between both, because the valueID is in both cases the same, even if there is a clear information in the standard to address these values like qubino it do.
But the question form me is where is ozw is knowing that this value is “Exporting”, because it decides clearly between both. So there must be a correct correlation btw the hex values and the standard. Only the part with the valueid from ozw to ha hinders to address the right values to the right sensor.
Is there a possibility to create a valueid (in ozw) for a specific value, or to split one?
Has anyone found a solution to this? I’m in same situation, HA cannot differentiate between import and export readings from z-wave energy meter reports. As a workaround, could it be possible to extract the boolean for import/export in the attribute value_id of the sensor, and use template in HA to determine if value should be interpreted as import or export?
I tried this even with the actual mqtt zwave plugin, but the report time are slower and the problem is the same.
HA in combination of zwave don‘t distinguishes between 0x21 energy and 0x41 exporting energy.
Both values will be presented in one value within the one and same entity, so you have these changes between import and export in the graph. Sometimes you see the import value sometimes the export, belonging to power stat of export or import.
@Fishwaldo may you could have a closer look that import get a entity and export get a different one.
Because right now there is only one entity for both values of export and import.
Thanks a lot!