This device https://www.zigbee2mqtt.io/devices/PJ-1203A.html exposes some string timestamps using numeric exposes. (timestamp_a, timestamp_b)
expose definitions:
{
"access": 1,
"description": "Timestamp at power measure (phase a)",
"label": "Timestamp a",
"name": "timestamp_a",
"property": "timestamp_a",
"type": "numeric"
},
{
"access": 1,
"description": "Timestamp at power measure (phase b)",
"label": "Timestamp b",
"name": "timestamp_b",
"property": "timestamp_b",
"type": "numeric"
},
received values:
{
"ac_frequency": 58.98,
"current_a": 0,
"current_b": 0,
"energy_a": 481.84,
"energy_b": 480.1,
"energy_flow_a": "consuming",
"energy_flow_b": "consuming",
"energy_produced_a": 0,
"energy_produced_b": 0,
"linkquality": 33,
"power_a": 0,
"power_ab": 0,
"power_b": 0,
"power_factor_a": 100,
"power_factor_b": 100,
"timestamp_ a": "2025-03-17T18:06:43.830Z",
"timestamp_b": "2025-03-17T18:06:44.077Z",
"update_frequency": 10,
"voltage": 122.7
}
I expected that a numeric expose could never have a string value? So is this a bug, or can numeric exposes be string timestamps ?
This device https://www.zigbee2mqtt.io/devices/PJ-1203A.html exposes some string timestamps using numeric exposes. (timestamp_a, timestamp_b)
expose definitions:
received values:
I expected that a numeric expose could never have a string value? So is this a bug, or can numeric exposes be string timestamps ?