[Twiz O´Meter] Instructions for ToM+ upgrade

Something appears to be wrong with the MQTT messages. See this example:

{ "XXX": "255", "SOC": "89.9", "SOH": "100", "B-T": "", "M-T": "", "Tun": "", "kWh": "5.4", "Amp": "-0", "RPM": "", "Nm ": "", "FW ": "", "C01": "4.07", "C02": "4.07", "C03": "4.07", "C04": "4.07", "C05": "4.07", "C06": "4.06", "C07": "4.07", "C08": "4.07", "C09": "4.07", "C10": "4.07", "C11": "4.07", "C12": "4.07", "C13": "4.07", "C14": "4.07", "Pac": "56.90", "T01": "15", "T02": "15", "T03": "14", "T04": "14", "T05": "14", "T06": "14", "T07": "14", "Reg": "", "CLK": "", "FLP": "", "220": "", "CSt": "", "tAY": "", "B12": "", "PN1": "", "PN2": "", "KmT": "0.0", "KmR": "", "KmH": "", "SeT": "", "tKT": "", "tKR": "", "tTM": "", "tKW": "", "t10": "", "t01": "", "tMN": "", "tKH": "", "kW ": "-0.03", "CEt": "", "CdK": "", "C-T": "14", "CKw": "", "Min": "", "T-T": "", "Acc": "", "AnX": "", "AnY": "", "AnZ": "" }

I've captured this MQTT message directly from the MQTT broker, so before it went into Home Assistant.

It appears fine, but check the KmT field, it says 0.0. This confuses my Home Assistant. I've put a "utilty meter" helper on this value, to keep track of daily/monthly km's driven. Because this helper is prepared for input that periodically resets, it will only go up. So, every time the KmT field goes to 0.0 (and then later back up to the real km number of something like 26000.0), the utility meter inserts the 26000 km and in my graphs it seems like I've driven 26000 km in one day.

All the other fields seem fine. Also, I didn't see this behavior on the 1.8 FW version.

Maybe this graph explains it better:



The yellow line is the value as directly taken from the MQTT field, no calculations are done on that. You can see it jumping up and down between 0 and 26000.
The blue line is the utilty meter helper, that can only "ratchet up".

@Delvecchio; what do you make of this?

[edt1]: I think these wrong MQTT messages are only sent as the Twizy is off - not driving. I've set a notification in Home Assistant, so now I can catch these events live. I'll try to confirm if this really only happens when the Twizy is off.
[edit2]: When the KmT value is back up to normal, I'll capture another MQTT message and post it, see if there are other differences.

Here is a MQTT message with the correct KmT field:

{ "XXX": "255", "SOC": "76.1", "SOH": "100", "B-T": "15.71", "M-T": "51", "Tun": "", "kWh": "4.6", "Amp": "-5", "RPM": "0", "Nm ": "0", "FW ": "", "C01": "3.95", "C02": "3.95", "C03": "3.95", "C04": "3.95", "C05": "3.95", "C06": "3.94", "C07": "3.95", "C08": "3.95", "C09": "3.95", "C10": "3.95", "C11": "3.95", "C12": "3.95", "C13": "3.95", "C14": "3.95", "Pac": "55.30", "T01": "16", "T02": "16", "T03": "16", "T04": "15", "T05": "16", "T06": "16", "T07": "15", "Reg": "", "CLK": "", "FLP": "0", "220": "", "CSt": "", "tAY": "-7.48", "B12": "14.44", "PN1": "1", "PN2": "1", "KmT": "26076.0", "KmR": "50", "KmH": "0.0", "SeT": "30", "tKT": "43", "tKR": "39", "tTM": "599", "tKW": "0.5", "t10": "11.6", "t01": "39", "tMN": "0.05", "tKH": "25.9", "kW ": "-0.32", "CEt": "", "CdK": "", "C-T": "24", "CKw": "", "Min": " 602", "T-T": "22.35", "Acc": "1.18", "AnX": "0.30", "AnY": "-6.97", "AnZ": "-333.04" }

I think this was sent when I started my Twizy up, but I'm not 100% sure. I'll observe more events and report back.

I've glanced over these two messages and briefly looked at the differences, and besides the fact that some fields are empty when the Twizy is off (which is to be expected) I don't see any obvious erroneous fields. But I'll collect more data.

Ist das ein Auszug aus dem Kursbuch der deutschen Bahn oder ein klingonisches Kochrezept?

Männer ich bewundere Euch! WIRKLICH.

TwizyChrisy schrieb: Ist das ein Auszug aus dem Kursbuch der deutschen Bahn oder ein klingonisches Kochrezept?

Männer ich bewundere Euch! WIRKLICH.

It may look complicated, but it's not really. The ToM, when connected to the internet, can send out Twizy data to something like a smart home system. I use Home Assistant but there are many. It does this in the form of a long text message, that contains all the information that is available. These are all the possible pieces of information:

XXX unused
SOC Traction battery State of Charge (%)
SOH Traction battery State of Health (%)
B-T ?
M-T ?
Tun Unused
kWh Traction battery energy available (kWh)
Amp Traction battery current (A)
RPM Motor rpm (rpm)
Nm Motor torque
FW Unused
C01 Traction battery cell 01 voltage (V)
C02 Traction battery cell 02 voltage (V)
C03 Traction battery cell 03 voltage (V)
C04 Traction battery cell 04 voltage (V)
C05 Traction battery cell 05 voltage (V)
C06 Traction battery cell 06 voltage (V)
C07 Traction battery cell 07 voltage (V)
C08 Traction battery cell 08 voltage (V)
C09 Traction battery cell 09 voltage (V)
C10 Traction battery cell 10 voltage (V)
C11 Traction battery cell 11 voltage (V)
C12 Traction battery cell 12 voltage (V)
C13 Traction battery cell 13 voltage (V)
C14 Traction battery cell 14 voltage (V)
Pac Traction battery total voltage (V)
T01 Traction battery temperature sensor 1 (°C)
T02 Traction battery temperature sensor 2 (°C)
T03 Traction battery temperature sensor 3 (°C)
T04 Traction battery temperature sensor 4 (°C)
T05 Traction battery temperature sensor 5 (°C)
T06 Traction battery temperature sensor 6 (°C)
T07 Traction battery temperature sensor 7 (°C)
Reg Unused
ECO Unused
Nor Unused
220 Charger plug state (0/1)
CSt Charging state (0/1)
tAY
B12 Aux battery voltage (V)
PN1 ToM extension connector pin1 state (0/1)
PN2 ToM extension connector pin2 state (0/1)
KmT Dashboard total km (km)
KmR Dashboard km remaining on current charge (km)
KmH Dashboard speed (km/h)
SeT Sevcom temperature (°C)
tKT ?
tKR ?
tTM ?
tKW ?
t10 ?
t01 ?
tMN ?
tKH ?
kW ?
CEt Charging completion ETA (min)
CdK kWh charged since start of charge session (kWh)
C-T Charger temperature (°C)
CKw Charging power (kW)
Min Time since start current charge session (s)
T-T Temperature inside ToM black box (°C)
Acc Gyroscope data
AnX Gyroscope data
AnY Gyroscope data
AnZ Gyroscope data

The smart home system can extract any of the values from the message, and use that and/or store that. I mainly use it to make daily and monthly graphs of the odometer:



But it would be equally easy to create graphs of speeds, the cell voltages and cell temperatures, the 12V voltage, etc. Also, in Home Assistant, actions can be triggered by sensor values, for instance displaying an alert on a phone at high or low cell temperatures, or anything else in any of the available fields.

It's actually a brilliant feature of the Tom, and I want to thank @Delvaccio for adding it. It works so incredibly well. It's like the apps many modern cars have, but it transmits much more technical data and, maybe much more important, it allows you to keep all your data local - not transmit it to some Chinese or American cloud provider. Being in control of your own data is quickly becoming much more important - critical, even.

PriusTwizy schrieb:
B-T ? battery temp
M-T ? motor temp
tAY ? trip average inclination
tKT ? trip total Km
tKR ? trip remaing Km
tTM ? trip duration time
tKW ? trip consumed kW
t10 ? trip consumption/10km
t01 ? trip consumption/1km
tMN ? trip cunsumption/minute
tKH ? trip average speed
kW ?consumption in kW