Z-wave Command_Class_Meter no distinction between import and export

thecem · December 26, 2019, 6:13pm

The Topic is ralated to the smart meters, in my case to the qubino zmnhtdx and zmnhxdx.

The import and export values will be presented in the same entities:

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_7

or for the other meter:

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy_2

If I analyse the parameter which was send from both meters, I get this:

zmnhxdx with 340.0kWh import (0x21) and 1.2kWh export (to grid) (0x41):

2019-12-26 15:18:23.562 Detail, Node028, Received: 0x01, 0x16, 0x00, 0x04, 0x00, 0x1c, 0x0e, 0x60, 0x0d, 0x01, 0x01, 0x32, 0x02, 0x21, 0x24, 0x00, 0x00, 0x0d, 0x48, 0x00, 0x00, 0xc7, 0x00, 0x25
2019-12-26 15:18:23.562 Detail,
2019-12-26 15:18:23.562 Info, Node028, Response RTT 151 Average Response RTT 159
2019-12-26 15:18:23.562 Info, Node028, Received a MultiChannelEncap from node 28, endpoint 1 for Command Class COMMAND_CLASS_METER
2019-12-26 15:18:23.562 Detail, Node028, Refreshed Value: old value=false, new value=false, type=bool
2019-12-26 15:18:23.562 Detail, Node028, Changes to this value are not verified
2019-12-26 15:18:23.562 Info, Node028, Received Meter report from node 28: Energy=340.0kWh
2019-12-26 15:18:23.562 Detail, Node028, Refreshed Value: old value=340.0, new value=340.0, type=decimal
2019-12-26 15:18:23.562 Detail, Node028, Changes to this value are not verified
2019-12-26 15:18:23.562 Detail, Node028, Expected reply and command class was received
2019-12-26 15:18:23.562 Detail, Node028, Message transaction complete
2019-12-26 15:18:23.562 Detail,
2019-12-26 15:18:23.562 Detail, Node028, Removing current message
2019-12-26 15:18:23.562 Detail, Node028, Notification: ValueChanged

2019-12-26 15:05:09.565 Detail, Node028, Received: 0x01, 0x16, 0x00, 0x04, 0x00, 0x1c, 0x0e, 0x60, 0x0d, 0x01, 0x01, 0x32, 0x02, 0x41, 0x24, 0x00, 0x00, 0x00, 0x0c, 0x00, 0x00, 0xc7, 0x00, 0x0c
2019-12-26 15:05:09.565 Detail,
2019-12-26 15:05:09.566 Info, Node028, Received a MultiChannelEncap from node 28, endpoint 1 for Command Class COMMAND_CLASS_METER
2019-12-26 15:05:09.566 Detail, Node028, Refreshed Value: old value=false, new value=true, type=bool
2019-12-26 15:05:09.566 Detail, Node028, Changes to this value are not verified
2019-12-26 15:05:09.566 Info, Node028, Received Meter report from node 28: Exporting Energy=1.2kWh
2019-12-26 15:05:09.566 Detail, Node028, Refreshed Value: old value=340.0, new value=1.2, type=decimal
2019-12-26 15:05:09.566 Detail, Node028, Changes to this value are not verified
2019-12-26 15:05:09.566 Detail, Node028, Notification: ValueChanged

zmnhtdx with 0.6kWh import (0x21) and 138.1kWh export (to grid) (0x41):

2019-12-26 15:35:55.812 Detail, Node027, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x1b, 0x0a, 0x32, 0x02, 0x41, 0x24, 0x00, 0x00, 0x05, 0x65, 0x00, 0x00, 0xc4, 0x00, 0x09
2019-12-26 15:35:55.812 Detail,
2019-12-26 15:35:55.813 Detail, Node027, Refreshed Value: old value=false, new value=true, type=bool
2019-12-26 15:35:55.813 Detail, Node027, Changes to this value are not verified
2019-12-26 15:35:55.813 Info, Node027, Received Meter report from node 27: Exporting Energy=138.1kWh
2019-12-26 15:35:55.813 Detail, Node027, Refreshed Value: old value=138.0, new value=138.1, type=decimal
2019-12-26 15:35:55.813 Detail, Node027, Changes to this value are not verified
2019-12-26 15:35:55.813 Detail, Node027, Notification: ValueChanged
2019-12-26 15:35:55.852 Detail, Node027, Notification: ValueChanged

2019-12-26 13:51:10.627 Detail, Node027, Received: 0x01, 0x12, 0x00, 0x04, 0x00, 0x1b, 0x0a, 0x32, 0x02, 0x21, 0x24, 0x00, 0x00, 0x00, 0x06, 0x00, 0x00, 0xc4, 0x00, 0x0f
2019-12-26 13:51:10.627 Detail,
2019-12-26 13:51:10.627 Info, Node027, Response RTT 495 Average Response RTT 491
2019-12-26 13:51:10.627 Detail, Node027, Refreshed Value: old value=false, new value=false, type=bool
2019-12-26 13:51:10.627 Detail, Node027, Changes to this value are not verified
2019-12-26 13:51:10.627 Info, Node027, Received Meter report from node 27: Energy=0.6kWh
2019-12-26 13:51:10.627 Detail, Node027, Refreshed Value: old value=0.6, new value=0.6, type=decimal
2019-12-26 13:51:10.627 Detail, Node027, Changes to this value are not verified
2019-12-26 13:51:10.627 Detail, Node027, Expected reply and command class was received
2019-12-26 13:51:10.627 Detail, Node027, Message transaction complete
2019-12-26 13:51:10.627 Detail,
2019-12-26 13:51:10.627 Detail, Node027, Removing current message
2019-12-26 13:51:10.627 Detail, Node027, Notification: ValueChanged

So how it is possible to distinguish between the import and export values and create an entity for each value of import and export?
Following silabs Z-Wave Application Command Class Specification the values send from qubino device are correct:

0x32 ID 50 Command Class Meter
0x02 Command Meter_Report
_____Scale2(1)__Rate Type(2)__Meter Type (5)
0x41 0_________10___________00001
_______________Export_______Electric meter
or
0x21 0_________01___________00001
_______________Import________Electric meter

_____Precision(3)_Scale1(2)___Size
0x24 001_______00__________100
_______________kwh

It would be nice to get a hint to fix this.
thanks a lot!

firstof9 · December 26, 2019, 6:26pm

Usually exporting power is metered at a negative value.

Example:

thecem · December 26, 2019, 6:35pm

Yes you are right, but it is regarding the energy values in kWh and this will be presented in import and export and will not be negative.
The power could be negative, if you are producing.

firstof9 · December 26, 2019, 6:58pm

I found it easiest to use the integration sensor based of the current power from my meter, I then pump those into utility meters so I can monitor off-peak and on-peak usage and PV production. I have a template setup off the main meter ^{(previous post)} that only monitors the positive value for usage.

Not sure why your’s is dipping to 0 randomly like that, I have an Aeotec HEM and it doesn’t report like that, very odd.

thecem · December 26, 2019, 7:10pm

thanks for the hint I using it the same way to pump the utility meter but its not so exact like the meter values it self. And this is the reason why I’m started the search for this dips.
The Dips going not to 0 (zero) openzwave gets the value from device with correct zwave parameter (different for import 0x21 and export 0x41) but blows it in the one and the same value of this entity, so the value is sometimes the import 1.2kWh and most of time export 138.0kWh. This is why the graph have this dips.

firstof9 · December 26, 2019, 7:34pm

Per the manual it states you should have a separate sensor for import and another for export on your main meter is this not the case?

thecem · December 26, 2019, 7:44pm

unfortunately not, even I add this device to a new installation. I think there must be a problem in the initial device config (z-wave or home assistant) because the device it self, send the different values correct. It seems that ozw or ha is not able to distinguish between both values (because the differences are deep in the meter_report).

thecem · December 26, 2019, 7:46pm

On the meter display I have this sensor values for import an export an all other.

firstof9 · December 26, 2019, 8:12pm

Did you add the device securely? The manual says extra functionality comes by adding it securely.

thecem · December 26, 2019, 8:20pm

I tried both secure and unsecure but no change. But even the qubino support told me that in every case the import and export value will be send.
And you see that both values comes via z-wave and will be right addressed via openzw:

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

firstof9 · December 26, 2019, 8:25pm

Can you post all the entities for your meter(s)?

Example:

My meter reports my kWh like this:

No odd dips like your’s.

thecem · December 26, 2019, 8:30pm

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_current	0.1	node_id: 27 value_index: 20 value_instance: 1 value_id: 72057594495926594 power_consumption: 0 unit_of_measurement: A friendly_name: Smart Meter PV Current

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy	174.0	node_id: 27 value_index: 4 value_instance: 1 value_id: 72057594495926338 power_consumption: 0 unit_of_measurement: kVAh friendly_name: PV Solar Energy kVAh

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy_2	138.1	node_id: 27 value_index: 0 value_instance: 1 value_id: 72057594495926274 power_consumption: 0 unit_of_measurement: kWh friendly_name: Solar PV Energy

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power	0.0	node_id: 27 value_index: 8 value_instance: 1 value_id: 72057594495926402 power_consumption: 0 unit_of_measurement: W friendly_name: Smart Meter PV Power

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_power_factor	0.25	node_id: 27 value_index: 24 value_instance: 1 value_id: 72057594495926658 power_consumption: 0 unit_of_measurement: Power Factor friendly_name: Smart Meter PV Power Factor

sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_voltage	235.6	node_id: 27 value_index: 16 value_instance: 1 value_id: 72057594495926530 power_consumption: 0 unit_of_measurement: V friendly_name: Smart Meter PV Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current	1.25	node_id: 22 value_index: 20 value_instance: 3 value_id: 216172782487896386 power_consumption: 140.3 unit_of_measurement: A friendly_name: Smart Meter EG Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current_2	0.11	node_id: 22 value_index: 20 value_instance: 4 value_id: 288230376525824322 power_consumption: 16.4 unit_of_measurement: A friendly_name: Smart Meter EG Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current_3	0.0	node_id: 22 value_index: 20 value_instance: 5 value_id: 360287970563752258 power_consumption: 73.6 unit_of_measurement: A friendly_name: Smart Meter EG Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current_4	1.57	node_id: 28 value_index: 20 value_instance: 3 value_id: 216172782588559682 power_consumption: 370.4 unit_of_measurement: A friendly_name: Smart Meter HZ Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current_5	0.58	node_id: 28 value_index: 20 value_instance: 4 value_id: 288230376626487618 power_consumption: 255.4 unit_of_measurement: A friendly_name: Smart Meter HZ Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_current_6	2.77	node_id: 28 value_index: 20 value_instance: 5 value_id: 360287970664415554 power_consumption: 133 unit_of_measurement: A friendly_name: Smart Meter HZ Current

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy	3066.1	node_id: 22 value_index: 4 value_instance: 1 value_id: 72057594412040258 power_consumption: 274 unit_of_measurement: kVAh friendly_name: Smart Meter EG Energy

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_2	1788.3	node_id: 22 value_index: 0 value_instance: 1 value_id: 72057594412040194 power_consumption: 274 unit_of_measurement: kWh friendly_name: Smart Meter EG Energy

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_3	3070.3	node_id: 22 value_index: 4 value_instance: 2 value_id: 144115188449968194 power_consumption: 237.6 unit_of_measurement: kVAh friendly_name: Smart Meter EG Energy

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_4	1791.6	node_id: 22 value_index: 0 value_instance: 2 value_id: 144115188449968130 power_consumption: 237.6 unit_of_measurement: kWh friendly_name: Smart Meter EG

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_5	435.1	node_id: 28 value_index: 4 value_instance: 1 value_id: 72057594512703554 power_consumption: 843.6 unit_of_measurement: kVAh friendly_name: Smart Meter HZ Energy

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_6	443.0	node_id: 28 value_index: 4 value_instance: 2 value_id: 144115188550631490 power_consumption: 736.3 unit_of_measurement: kVAh friendly_name: Smart Meter HZ Energy

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_7	343.9	node_id: 28 value_index: 0 value_instance: 2 value_id: 144115188550631426 power_consumption: 736.3 unit_of_measurement: kWh friendly_name: Smart Meter HZ

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_energy_8	337.8	node_id: 28 value_index: 0 value_instance: 1 value_id: 72057594512703490 power_consumption: 843.6 unit_of_measurement: kWh friendly_name: Smart Meter HZ

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power	274.0	node_id: 22 value_index: 8 value_instance: 1 value_id: 72057594412040322 power_consumption: 274 unit_of_measurement: W friendly_name: Smart Meter EG Power

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_10	133.0	node_id: 28 value_index: 8 value_instance: 5 value_id: 360287970664415362 power_consumption: 133 unit_of_measurement: W friendly_name: Smart Meter HZ L3

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_2	237.6	node_id: 22 value_index: 8 value_instance: 2 value_id: 144115188449968258 power_consumption: 237.6 unit_of_measurement: W friendly_name: Smart Meter EG saldiert

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_3	140.3	node_id: 22 value_index: 8 value_instance: 3 value_id: 216172782487896194 power_consumption: 140.3 unit_of_measurement: W friendly_name: Smart Meter EG L1

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_4	16.4	node_id: 22 value_index: 8 value_instance: 4 value_id: 288230376525824130 power_consumption: 16.4 unit_of_measurement: W friendly_name: Smart Meter EG L2

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_5	73.6	node_id: 22 value_index: 8 value_instance: 5 value_id: 360287970563752066 power_consumption: 73.6 unit_of_measurement: W friendly_name: Smart Meter EG L3

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_6	843.6	node_id: 28 value_index: 8 value_instance: 1 value_id: 72057594512703618 power_consumption: 843.6 unit_of_measurement: W friendly_name: Smart Meter HZ ?

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_7	736.3	node_id: 28 value_index: 8 value_instance: 2 value_id: 144115188550631554 power_consumption: 736.3 unit_of_measurement: W friendly_name: Smart Meter HZ saldiert

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_8	370.4	node_id: 28 value_index: 8 value_instance: 3 value_id: 216172782588559490 power_consumption: 370.4 unit_of_measurement: W friendly_name: Smart Meter HZ L1

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_9	255.4	node_id: 28 value_index: 8 value_instance: 4 value_id: 288230376626487426 power_consumption: 255.4 unit_of_measurement: W friendly_name: Smart Meter HZ L2

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor	0.65	node_id: 22 value_index: 24 value_instance: 1 value_id: 72057594412040578 power_consumption: 274 unit_of_measurement: Power Factor friendly_name: Smart Meter EG Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_10	0.83	node_id: 28 value_index: 24 value_instance: 5 value_id: 360287970664415618 power_consumption: 133 unit_of_measurement: Power Factor friendly_name: Smart Meter HZ Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_2	0.66	node_id: 22 value_index: 24 value_instance: 2 value_id: 144115188449968514 power_consumption: 237.6 unit_of_measurement: Power Factor friendly_name: Smart Meter EG Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_3	0.68	node_id: 22 value_index: 24 value_instance: 3 value_id: 216172782487896450 power_consumption: 140.3 unit_of_measurement: Power Factor friendly_name: Smart Meter EG Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_4	0.65	node_id: 22 value_index: 24 value_instance: 4 value_id: 288230376525824386 power_consumption: 16.4 unit_of_measurement: Power Factor friendly_name: Smart Meter EG Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_5	0.0	node_id: 22 value_index: 24 value_instance: 5 value_id: 360287970563752322 power_consumption: 73.6 unit_of_measurement: Power Factor friendly_name: Smart Meter EG Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_6	0.52	node_id: 28 value_index: 24 value_instance: 1 value_id: 72057594512703874 power_consumption: 843.6 unit_of_measurement: Power Factor friendly_name: Smart Meter HZ Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_7	0.71	node_id: 28 value_index: 24 value_instance: 2 value_id: 144115188550631810 power_consumption: 736.3 unit_of_measurement: Power Factor friendly_name: Smart Meter HZ Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_8	0.07	node_id: 28 value_index: 24 value_instance: 3 value_id: 216172782588559746 power_consumption: 370.4 unit_of_measurement: Power Factor friendly_name: Smart Meter HZ Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_power_factor_9	0.6	node_id: 28 value_index: 24 value_instance: 4 value_id: 288230376626487682 power_consumption: 255.4 unit_of_measurement: Power Factor friendly_name: Smart Meter HZ Power Factor

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage	234.3	node_id: 22 value_index: 16 value_instance: 3 value_id: 216172782487896322 power_consumption: 140.3 unit_of_measurement: V friendly_name: Smart Meter EG Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage_2	234.9	node_id: 22 value_index: 16 value_instance: 4 value_id: 288230376525824258 power_consumption: 16.4 unit_of_measurement: V friendly_name: Smart Meter EG Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage_3	0.0	node_id: 22 value_index: 16 value_instance: 5 value_id: 360287970563752194 power_consumption: 73.6 unit_of_measurement: V friendly_name: Smart Meter EG Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage_4	234.3	node_id: 28 value_index: 16 value_instance: 3 value_id: 216172782588559618 power_consumption: 370.4 unit_of_measurement: V friendly_name: Smart Meter HZ Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage_5	235.5	node_id: 28 value_index: 16 value_instance: 4 value_id: 288230376626487554 power_consumption: 255.4 unit_of_measurement: V friendly_name: Smart Meter HZ Voltage

sensor.qubino_goap_zmnhxdx_3_phase_smart_meter_voltage_6	234.3	node_id: 28 value_index: 16 value_instance: 5 value_id: 360287970664415490 power_consumption: 133 unit_of_measurement: V friendly_name: Smart Meter HZ Voltage

zwave.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6	ready	node_id: 27 node_name: Smart Meter PV manufacturer_name: Qubino (Goap) product_name: ZMNHTDx Smart meter S4 S5 S6 query_stage: Complete is_awake: true is_ready: true is_failed: false is_info_received: true max_baud_rate: 40000 is_zwave_plus: true capabilities: zwave_plus,listening,beaming,routing neighbors: 1,5,6,7,12,13,14,15,19,20,21 sentCnt: 65 sentFailed: 0 retries: 0 receivedCnt: 909 receivedDups: 8 receivedUnsolicited: 860 sentTS: 2019-12-26 13:51:13:340 receivedTS: 2019-12-26 15:55:59:091 lastRequestRTT: 350 averageRequestRTT: 344 lastResponseRTT: 505 averageResponseRTT: 499 application_version: 7.09 friendly_name: Smart Meter PV

zwave.qubino_goap_zmnhxdx_3_phase_smart_meter	ready	node_id: 22 node_name: Smart Meter EG manufacturer_name: Qubino (Goap) product_name: ZMNHXDx 3-phase Smart Meter query_stage: Complete is_awake: true is_ready: true is_failed: false is_info_received: true max_baud_rate: 40000 is_zwave_plus: true capabilities: zwave_plus,listening,beaming,routing neighbors: 2,5,12,13,14,15,19,20,21,28 sentCnt: 1519 sentFailed: 2 retries: 6 receivedCnt: 4120 receivedDups: 140 receivedUnsolicited: 2586 sentTS: 2019-12-26 21:28:15:993 receivedTS: 2019-12-26 21:28:47:037 lastRequestRTT: 91 averageRequestRTT: 82 lastResponseRTT: 162 averageResponseRTT: 153 application_version: 1.00 friendly_name: Smart Meter EG

zwave.qubino_goap_zmnhxdx_3_phase_smart_meter_2 ready node_id: 28 node_name: Smart Meter HZ manufacturer_name: Qubino (Goap) product_name: ZMNHXDx 3-phase Smart Meter query_stage: Complete is_awake: true is_ready: true is_failed: false is_info_received: true max_baud_rate: 40000 is_zwave_plus: true capabilities: zwave_plus,listening,beaming,routing neighbors: 2,5,13,15,19,20,22 sentCnt: 1514 sentFailed: 2 retries: 1 receivedCnt: 3079 receivedDups: 48 receivedUnsolicited: 1553 sentTS: 2019-12-26 21:28:36:960 receivedTS: 2019-12-26 21:28:37:121 lastRequestRTT: 85 averageRequestRTT: 82 lastResponseRTT: 162 averageResponseRTT: 159 application_version: 1.00 friendly_name: Smart Meter HZ

thecem · December 26, 2019, 8:33pm

these are 3 meters with all entities and values.

firstof9 · December 26, 2019, 8:36pm

First I’d say rename your meters so you know which is which, it’s hard to figure out which sensors go to which meter

thecem · December 26, 2019, 8:52pm

they are renamed Smart Meter PV/EG/HZ maybe this will help:

But there is no entity having an import or export value. …energy_7 is the one which have both…

firstof9 · December 26, 2019, 9:05pm

Not sure if the weirdness you are getting is from OpenZwave or something in HA, @Fishwaldo would know for sure, my meter just sends a report every XX mins and updates all the fields, I don’t see an export/import except via positive/negative readings on the watts.

Fishwaldo · December 27, 2019, 1:38am

There should be a Boolean ValueID called exporting that indicates if the values are consumption or production.

I have no idea If that’s exposed in HA tho

thecem · December 27, 2019, 5:51am

Yes there is a valueID it is for smart Meter PV in the case it sends the export value: 72057594495926274
and in the case of import the same number.
Where could I see all valueID‘s?
Is there a command to list all valueID in opzw?
In opzwave log there is a clear difference between both values (shown above) for import and export.

honikos · December 27, 2019, 7:18am

So the Z-Wave report / log distinguishes between Exporting Energy and Energy.
I’m not an expert in templates, but it looks like you can fetch the different values with a template sensor.
I hope here are experts which can give a hint, wehter it’s possible with template sensor or not.

Fishwaldo · December 27, 2019, 8:11am

The list of values is dynamic depending upon the devices capabilities. If you want to see everything unfiltered - you could run ozwcp, but if HA “filters” anything then you need to address it with the HA devs.