Python Plugin: MqttMapper

[FlyingDomotic]

"Error: Mapper: Can't find device key wican/amperae/SOC" just means that there's no MqttMapper device with that key. IT probably has been deleted...
Just restart plug-in to get the device recreated.

[rron]

Thank you for the reply,

I rebooted the system but still the same.You mean the code in the mqtt.json?

Code: Select all

[},
    "amperae State of Charge": {
        "topic": "wican/amperae/SOC",
        "type": "243", "subtype": "6", "switchtype": "0",
        "mapping": {"item": "", "multiplier": 0.1}/code]

[FlyingDomotic]

Would it be possible to get part of Domoticz's log related to start of MqttMapper plugin?

[rron]

This is the only part I see. I am using docker.

Code: Select all

[ 2026-01-11 16:12:08.121 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY
2026-01-11 16:12:13.079 Error: Mapper: Can't find device key wican/amperae/SOC
2026-01-11 16:12:13.179 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY
2026-01-11 16:12:18.153 Error: Mapper: Can't find device key wican/amperae/SOC
2026-01-11 16:12:18.203 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY /code]

[FlyingDomotic]

The interesting part start with:

Code: Select all

 /home/pi/domoticz/plugins/MqttMapper/xxxx.json is a version 1.0 file

and ends with:

Code: Select all

MqttClient::__init__

Would it be also possible to (temporarily) allow device creation, as this could be a good reason to not create devices successfully?

[rron]

This is what I have in the MqttMapper

[FlyingDomotic]

I wasn't sufficiently clear

Would it be possible to extract part of Domoticz.log concerning MqttMapper between line containing " /home/pi/domoticz/plugins/MqttMapper/MqttMapper.json is a version 1.0 file" and "MqttClient::__init__"?

In addition, if you find any "device creation impossible" in domoticz log, please enable device creation.

[rron]

I am trying to find my domoticz logging. According to my docker-compose.yml it should be in opt/domoticz/userdata/domoticz.log but there is nothing.

[FlyingDomotic]

You found it, you even copy (part of) it in this message:

Code: Select all

2026-01-11 16:12:08.121 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY
2026-01-11 16:12:13.079 Error: Mapper: Can't find device key wican/amperae/SOC
2026-01-11 16:12:13.179 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY
2026-01-11 16:12:18.153 Error: Mapper: Can't find device key wican/amperae/SOC
2026-01-11 16:12:18.203 Error: Mapper: Can't find device key wican/amperae/HV_CAPACITY

[rron]

Ok i try to find the part you mentioned

[FlyingDomotic]

If too complicated, please send me the full log by Private Message.

[FlyingDomotic]

Oh, would you mind doing that for me? My English isn't the best, and I'm not very familiar with this subject. Anyway, thanks so much for this, and I hope it's possible later.

Done: [https://github.com/domoticz/domoticz/issues/6506}

[rron]

I will send you the startup log when I am loading my car again. Only than I will see the fault.

[FlyingDomotic]

Done: [https://github.com/domoticz/domoticz/issues/6506}

I got an answer:

Code: Select all

We are using the mosquito library which i trust

We could interpret this as "Domoticz uses mosquitto, which is rock solid, please investigate on your side, at sender" (or equivalent).

Even if this may seems a bit raw, I should admit that this is the right answer for someone very busy managing a large project like Domoticz.

On my own, I tried to see if something changed in Domoticz on MQTT area. I checked for differences between V2020.2 and 2025.2 and ... nothing changed last 5 years in (this part of) C code. We can safely exclude side effect of a recent Domoticz code change.

That's said, we should investigate a bit on sender side.

So, if I correctly understood, you're using P1 monitor from "https://www.p1-monitor.nl/".

It may be interesting to have used version number, and (part of) parameters related to MQTT (probably its version, if you can get it). I don't known P1 monitor, so I can't tell you how to do that, but I guess some Dutch users here can provide help.

In addition, version of broker used by Domoticz is also useful. A quick way to get it is "mosquitto -h", reading first line which is something like "mosquitto version x.y.z".

It could be also helping to get the view of other tools of these messages.

On machine running mosquitto, you can run:

mosquitto_sub -h localhost -t p1monitor/watermeter/day/watermeter_consumption_liter

and give us few received messages (or error messages)

You may also install MqttExplorer (https://mqtt-explorer.com/), and give us content of "p1monitor/watermeter/day/watermeter_consumption_liter" topic (or error messages if any).

Idea behind these requests is to determine where error could be (bad settings, bad message, ...)

[rron]

This is the part from the mapper logging. I will try this tomorrow when I loading my car.

Code: Select all

domoticz  | 2026-01-17 12:10:43.256  Mapper: Debug logging mask set to: PYTHON PLUGIN
domoticz  | 2026-01-17 12:10:43.258  Mapper: /opt/domoticz/userdata/plugins/MqttMapper/MqttMapper.json is a version 1.0 file
domoticz  | 2026-01-17 12:10:43.443  Mapper: pluginV1::__init__
domoticz  | 2026-01-17 12:10:43.444  Mapper: 'HardwareID': '48'
domoticz  | 2026-01-17 12:10:43.444  Mapper: 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/'
domoticz  | 2026-01-17 12:10:43.444  Mapper: 'StartupFolder': '/opt/domoticz/'
domoticz  | 2026-01-17 12:10:43.445  Mapper: 'UserDataFolder': '/opt/domoticz/userdata/'
domoticz  | 2026-01-17 12:10:43.445  Mapper: 'Database': '/opt/domoticz/userdata/domoticz.db'
domoticz  | 2026-01-17 12:10:43.445  Mapper: 'Language': 'nl'
domoticz  | 2026-01-17 12:10:43.445  Mapper: 'Version': '25.12.9-1'
domoticz  | 2026-01-17 12:10:43.446  Mapper: 'Author': 'Flying Domotic'
domoticz  | 2026-01-17 12:10:43.446  Mapper: 'Name': 'Mapper'
domoticz  | 2026-01-17 12:10:43.446  Mapper: 'Address': '192.168.178.50'
domoticz  | 2026-01-17 12:10:43.446  Mapper: 'Port': '1883'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'Key': 'MqttMapper'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'Mode1': 'MqttMapper.json'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'Mode6': 'Normal'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'DomoticzVersion': '2025.2 (build 16836)'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'DomoticzHash': '3b8a9cf2f'
domoticz  | 2026-01-17 12:10:43.447  Mapper: 'DomoticzBuildTime': '2025-10-26 10:11:08'
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device count: 7
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device: 1 - ID: 867, Name: 'charge current', nValue: 15, sValue: '15.3'
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device: 2 - ID: 868, Name: 'max current', nValue: 16, sValue: '16.0'
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device: 3 - ID: 901, Name: 'evenergy charged', nValue: 30044, sValue: '30044.0'
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device: 4 - ID: 870, Name: 'evtotalenergy charged', nValue: 1002, sValue: '1002.479'
domoticz  | 2026-01-17 12:10:43.448  Mapper: Device: 5 - ID: 871, Name: 'SmartEVSE state', nValue: 0, sValue: 'Ready to Charge'
domoticz  | 2026-01-17 12:10:43.449  Mapper: Device: 6 - ID: 872, Name: 'SmartEVSE error', nValue: 0, sValue: '0'
domoticz  | 2026-01-17 12:10:43.449  Mapper: Device: 7 - ID: 873, Name: 'charge current override', nValue: 0, sValue: '0.0'
domoticz  | 2026-01-17 12:10:43.449  Mapper: Creating device amperae State of Charge
domoticz  | 2026-01-17 12:10:43.450  Mapper: Creating device amperae Hv Capacity
domoticz  | 2026-01-17 12:10:43.450  Mapper: MqttClient::__init__
domoticz  | 2026-01-17 12:10:43.452  Mapper: Heartbeat interval set to: 3.
domoticz  | 2026-01-17 12:10:43.502  Mapper: MqttClient::onConnect
domoticz  | 2026-01-17 12:10:43.502  Mapper: MqttClient::onConnect connect to 192.168.178.50:1883, ID=Domoticz_MqttMapper_48_1768648243
domoticz  | 2026-01-17 12:10:43.554  Mapper: onMQTTConnected
domoticz  | 2026-01-17 12:10:43.554  Mapper: getTopics: '{'SmartEVSE-5572/EVEnergyCharged', 'wican/amperae/HV_CAPACITY', 'SmartEVSE-5572/ChargeCntOverride', 'SmartEVSE-5572/Error', 'SmartEVSE-5572/State', 'wican/amperae/SOC', 'SmartEVSE-5572/ChargeCurrent', 'SmartEVSE-5572/EVTotalEnergyCed', 'SmartEVSE-5572/MaxCurrent'}'
domoticz  | 2026-01-17 12:10:43.555  Mapper: MqttClient::Subscribe to [{'Topic': 'SmartEVSE-5572/EVEnergyCharged', 'QoS': 0}, {'Topic': 'wican/aae/HV_CAPACITY', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrentOverride', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/Error', 'QoS': 0}, {'Topic': rtEVSE-5572/State', 'QoS': 0}, {'Topic': 'wican/amperae/SOC', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrent', 'QoS': 0}, {'Topic': 'SmartEV572/EVTotalEnergyCharged', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/MaxCurrent', 'QoS': 0}]
domoticz  | 2026-01-17 12:10:43.605  Mapper: onMQTTSubscribed
domoticz  | 2026-01-17 12:10:43.609  Mapper: onMQTTPublish found SmartEVSE-5572/EVEnergyCharged, Device 'evenergy charged', message '30044'
domoticz  | 2026-01-17 12:10:43.610  Mapper: Setting evenergy charged to 30044/30044.0
domoticz  | 2026-01-17 12:10:43.621  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrentOverride, Device 'charge current override', message
domoticz  | 2026-01-17 12:10:43.621  Mapper: Setting charge current override to 0/0.0
domoticz  | 2026-01-17 12:10:43.628  Mapper: onMQTTPublish found SmartEVSE-5572/Error, Device 'SmartEVSE error', message 'None'
domoticz  | 2026-01-17 12:10:43.629  Mapper: testValue="None" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.629  Mapper: testValue="No Power Available" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.629  Mapper: testValue="Communication Error" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="Temperature High" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="EV Meter Comm Error" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="RCM Tripped" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="Waiting for Solar" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="Test IO" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="Flash Error" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: testValue="**Unknown**" (str), readValue="None" (str)
domoticz  | 2026-01-17 12:10:43.630  Mapper: Setting SmartEVSE error to 0/0
domoticz  | 2026-01-17 12:10:43.638  Mapper: onMQTTPublish found SmartEVSE-5572/State, Device 'SmartEVSE state', message 'Ready to Charge'
domoticz  | 2026-01-17 12:10:43.639  Mapper: Setting SmartEVSE state to >Ready to Charge<
domoticz  | 2026-01-17 12:10:43.644  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrent, Device 'charge current', message '153'
domoticz  | 2026-01-17 12:10:43.644  Mapper: Setting charge current to 15/15.3
domoticz  | 2026-01-17 12:10:43.649  Mapper: onMQTTPublish found SmartEVSE-5572/MaxCurrent, Device 'max current', message '160'
domoticz  | 2026-01-17 12:10:43.649  Mapper: Setting max current to 16/16.0

[FlyingDomotic]

As of now, I don't see anything strange in this log.
Let's see what'll happen when charging car.

[rron]

I will let you know tomorrow

[rron]

This is the logging when I am charging. I don’t see much difference in the logging.

Code: Select all

| 2026-01-18 12:19:12.158  dzVents: Debug: - Domoticz: start
domoticz  | 2026-01-18 12:19:12.201  Mapper: Debug logging mask set to: PYTHON PLUGIN
domoticz  | 2026-01-18 12:19:12.202  Mapper: /opt/domoticz/userdata/plugins/MqttMapper/MqttMapper.json is a version 1.0 file
domoticz  | 2026-01-18 12:19:12.383  Mapper: pluginV1::__init__
domoticz  | 2026-01-18 12:19:12.384  Mapper: 'HardwareID': '48'
domoticz  | 2026-01-18 12:19:12.385  Mapper: 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/'
domoticz  | 2026-01-18 12:19:12.386  Mapper: 'StartupFolder': '/opt/domoticz/'
domoticz  | 2026-01-18 12:19:12.386  Mapper: 'UserDataFolder': '/opt/domoticz/userdata/'
domoticz  | 2026-01-18 12:19:12.387  Mapper: 'Database': '/opt/domoticz/userdata/domoticz.db'
domoticz  | 2026-01-18 12:19:12.388  Mapper: 'Language': 'nl'
domoticz  | 2026-01-18 12:19:12.389  Mapper: 'Version': '25.12.9-1'
domoticz  | 2026-01-18 12:19:12.391  Mapper: 'Author': 'Flying Domotic'
domoticz  | 2026-01-18 12:19:12.391  Mapper: 'Name': 'Mapper'
domoticz  | 2026-01-18 12:19:12.392  Mapper: 'Address': '192.168.178.50'
domoticz  | 2026-01-18 12:19:12.392  Mapper: 'Port': '1883'
domoticz  | 2026-01-18 12:19:12.394  Mapper: 'Key': 'MqttMapper'
domoticz  | 2026-01-18 12:19:12.394  Mapper: 'Mode1': 'MqttMapper.json'
domoticz  | 2026-01-18 12:19:12.396  Mapper: 'Mode6': 'Normal'
domoticz  | 2026-01-18 12:19:12.397  Mapper: 'DomoticzVersion': '2025.2 (build 16836)'
domoticz  | 2026-01-18 12:19:12.399  Mapper: 'DomoticzHash': '3b8a9cf2f'
domoticz  | 2026-01-18 12:19:12.400  Mapper: 'DomoticzBuildTime': '2025-10-26 10:11:08'
domoticz  | 2026-01-18 12:19:12.401  Mapper: Device count: 7
domoticz  | 2026-01-18 12:19:12.401  Mapper: Device: 1 - ID: 867, Name: 'charge current', nValue: 16, sValue: '15.9'
domoticz  | 2026-01-18 12:19:12.401  Mapper: Device: 2 - ID: 868, Name: 'max current', nValue: 16, sValue: '16.0'
domoticz  | 2026-01-18 12:19:12.402  Mapper: Device: 3 - ID: 901, Name: 'evenergy charged', nValue: 3974, sValue: '3974.0'
domoticz  | 2026-01-18 12:19:12.403  Mapper: Device: 4 - ID: 870, Name: 'evtotalenergy charged', nValue: 1006, sValue: '1006.453'
domoticz  | 2026-01-18 12:19:12.403  Mapper: Device: 5 - ID: 871, Name: 'SmartEVSE state', nValue: 0, sValue: 'Charging'
domoticz  | 2026-01-18 12:19:12.404  Mapper: Device: 6 - ID: 872, Name: 'SmartEVSE error', nValue: 0, sValue: '0'
domoticz  | 2026-01-18 12:19:12.404  Mapper: Device: 7 - ID: 873, Name: 'charge current override', nValue: 0, sValue: '0.0'
domoticz  | 2026-01-18 12:19:12.407  Mapper: Creating device amperae State of Charge
domoticz  | 2026-01-18 12:19:12.409  Mapper: Creating device amperae Hv Capacity
domoticz  | 2026-01-18 12:19:12.409  Mapper: MqttClient::__init__
domoticz  | 2026-01-18 12:19:12.411  Mapper: Heartbeat interval set to: 3.
domoticz  | 2026-01-18 12:19:12.462  Mapper: MqttClient::onConnect
domoticz  | 2026-01-18 12:19:12.462  Mapper: MqttClient::onConnect connect to 192.168.178.50:1883, ID=Domoticz_MqttMapper_48_1768735152
domoticz  | 2026-01-18 12:19:12.513  Mapper: onMQTTConnected
domoticz  | 2026-01-18 12:19:12.513  Mapper: getTopics: '{'SmartEVSE-5572/EVTotalEnergyCharged', 'SmartEVSE-5572/State', 'SmartEVSE-5572/MaxCurrent', 'SmartEVSE-5572/ChargeCurrentOverride', 'wican/amperae/HV_CAPACITY', 'SmartEVSE-5572/EVEnergyCharged', 'wican/amperae/SOC', 'SmartEVSE-5572/ChargeCurrent', 'SmartEVSE-5572/Error'}'
domoticz  | 2026-01-18 12:19:12.514  Mapper: MqttClient::Subscribe to [{'Topic': 'SmartEVSE-5572/EVTotalEnergyCharged', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/State', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/MaxCurrent', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrentOverride', 'QoS': 0}, {'Topic': 'wican/amperae/HV_CAPACITY', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/EVEnergyCharged', 'QoS': 0}, {'Topic': 'wican/amperae/SOC', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrent', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/Error', 'QoS': 0}]
domoticz  | 2026-01-18 12:19:12.564  Mapper: onMQTTSubscribed
domoticz  | 2026-01-18 12:19:12.568  Mapper: onMQTTPublish found SmartEVSE-5572/State, Device 'SmartEVSE state', message 'Charging'
domoticz  | 2026-01-18 12:19:12.569  Mapper: Setting SmartEVSE state to >Charging<
domoticz  | 2026-01-18 12:19:12.574  Mapper: onMQTTPublish found SmartEVSE-5572/MaxCurrent, Device 'max current', message '160'
domoticz  | 2026-01-18 12:19:12.575  Mapper: Setting max current to 16/16.0
domoticz  | 2026-01-18 12:19:12.579  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrentOverride, Device 'charge current override', message '0'
domoticz  | 2026-01-18 12:19:12.579  Mapper: Setting charge current override to 0/0.0
domoticz  | 2026-01-18 12:19:12.585  Mapper: onMQTTPublish found SmartEVSE-5572/EVEnergyCharged, Device 'evenergy charged', message '4019'
domoticz  | 2026-01-18 12:19:12.587  Mapper: Setting evenergy charged to 4019/4019.0
domoticz  | 2026-01-18 12:19:12.599  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrent, Device 'charge current', message '159'
domoticz  | 2026-01-18 12:19:12.601  Mapper: Setting charge current to 16/15.9
domoticz  | 2026-01-18 12:19:12.610  Mapper: onMQTTPublish found SmartEVSE-5572/Error, Device 'SmartEVSE error', message 'None'
domoticz  | 2026-01-18 12:19:12.611  Mapper: testValue="None" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.612  Mapper: testValue="No Power Available" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.612  Mapper: testValue="Communication Error" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.613  Mapper: testValue="Temperature High" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.613  Mapper: testValue="EV Meter Comm Error" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.614  Mapper: testValue="RCM Tripped" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.614  Mapper: testValue="Waiting for Solar" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.615  Mapper: testValue="Test IO" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.615  Mapper: testValue="Flash Error" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.616  Mapper: testValue="**Unknown**" (str), readValue="None" (str)
domoticz  | 2026-01-18 12:19:12.617  Mapper: Setting SmartEVSE error to 0/0

[FlyingDomotic]

I may be wrong, but reading this log, everything is running well, isn't it?

[rron]

No it doesn’t appear in domoticz.