LiXee ZLinky_TIC report erroneous values

[zen2]

What happened?

I use zlinky configured liked this: (set by frontend)

'0x00158d0005d2a74e':
  friendly_name: '0x00158d0005d2a74e'
  linky_mode: standard
  energy_phase: three_phase
  production: 'false'
  measurement_poll_interval: 60
  tarif: auto
  kWh_precision: 3

the device report correctly values:

{
  "active_enerfy_out_d01": 9727.493,
  "active_enerfy_out_d02": 12918.045,
  "active_power": 2052,
  "active_power_max": 2740,
  "active_power_max_ph_b": 1500,
  "active_power_max_ph_c": 3960,
  "active_power_ph_b": 2100,
  "apparent_power": 18175,
  "apparent_power_ph_b": null,
  "apparent_power_ph_c": 31158,
  "available_power": 12,
  "average_rms_voltage_meas_period": 236,
  "average_rms_voltage_meas_period_ph_c": 236,
  "average_rms_voltage_measure_period_ph_b": 239,
  "current_date": "E220706160550",
  "current_index_tarif": 2,
  "current_price": "HEURE PLEINE",
  "current_summ_delivered": 28878.282,
  "current_tarif": "H PLEINE/CREUSE",
  "current_tier1_summ_delivered": 12362.719,
  "current_tier2_summ_delivered": 16515.563,
  "drawn_v_a_max_n1": 2580,
  "drawn_v_a_max_n1_p2": 2650,
  "drawn_v_a_max_n1_p3": 4010,
  "last_seen": "2022-07-06T16:06:18+02:00",
  "linkquality": 167,
  "message1": "PAS DE MESSAGE",
  "message2": "",
  "meter_serial_number": "021976758997",
  "power_threshold": 12,
  "relais": null,
  "rms_current": 2,
  "rms_current_ph_b": 1,
  "rms_current_ph_c": 7,
  "rms_voltage": 238,
  "rms_voltage_ph_b": 238,
  "rms_voltage_ph_c": 236,
  "site_id": "25317944963012",
  "software_revision": 2,
  "status_register": "003A4401",
  "update": {
    "state": "idle"
  },
  "update_available": false
}

but some of them are definitively wrong:

  "apparent_power": 18175,
  "apparent_power_ph_b": null,
  "apparent_power_ph_c": 31158,

I suppose that value are in VA and not in Watt but that should be likely comparable and mesuring powers of each phase with another device (shelly 3EM), i got:

phase1: 401 W
phase2: 1645 W
phase3: 0 W

Anyway I got a 12 KVA subscriptions so 3 x 4 KVA and so apparent_power values have to be defined (not null) and should present not so big values.

Note: I've already unplug zlinky, delete it from zigbee2mqtt, reset zlinky then replug the device, reassociate it, configured it and restart zigbee2mqtt.

What did you expect to happen?

correct apparent_power* values

Zigbee2MQTT version

1.26.0-dev commit: [ee227d85](https://github.com/Koenkk/zigbee2mqtt/commit/ee227d85)

Adapter firmware version

20220219

Adapter

CC1352P-2

[zen2]

@vk496 @SilentT-FR : I think you are related to this device integration.

[zen2]

Apparently another user from french home assistant community got the same problem with zigbee2mqtt and zlinky set as standard mode and triphase.

[zen2]

Could this log error be directly related ?

Failed to configure '0x00158d0005d2a74e', attempt 3 (Error: ConfigureReporting 0x00158d0005d2a74e/1 haElectricalMeasurement([{"attribute":"activePowerMaxPhB","minimumReportInterval":60,"maximumReportInterval":900,"reportableChange":1}], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE')
at Endpoint.checkStatus (/home/zigbee2mqtt/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:317:28)
at Endpoint.configureReporting (/home/zigbee2mqtt/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:694:22)
at async Promise.allSettled (index 19)
at Object.configure (/home/zigbee2mqtt/node_modules/zigbee-herdsman-converters/devices/lixee.js:640:10)
at Configure.configure (/home/zigbee2mqtt/lib/extension/configure.ts:115:13))

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[zen2]

It seems that everything is working fine now... By looking at my logs it seems that a new version of zigbee2mqtt (1.27.0) have make it works correctly. I think a reconfiguration at zigbee level of devices was necessary.