You may want to use "git checkout V26.1.14-1" to get previous version

FYI, version list is available at https://github.com/FlyingDomotic/domoticz-mqttmapper-plugin/releases

Anyway, there's something strange in your logs: I don't known where the following comes from:

2026-02-01 11:32:53.643 ...

Did you authorize Domoticz to create new devices before restarting MqttMapper ?

Would it be possible to check that there's not the same "Mapper" hardware twice (one with hardware 48 and one with 50)?

Do you mean "everything is ok now" or "there's still something wrong"?

If something is still wrong, please describe it.

It seems that there's no more "Mapper: Can't find device" in the log.

Is still something wrong?

I'm back and just tested a new version which add more trace on device creation, and checks for device just after creating it (as Domoticz Python primitive don't return any error.

Would it be possible to update MqttMapper (git pull), set debug (to "Extra verbose", restart it and send me log ?

I'll made a change to trace device creation as it seems there's an not shown error. I won't be able to test it before tomorrow evening or the day after.
Stay tuned!

Is there any errors into Domoticz log related to these devices creation?

It's look like MqttMapper ask for device creation, but Domoticz don't do it. It normally should give some error messages somewhere.

Just a remark, not related to this issue: why creating a percentage device (243/6) as data ...

There's a strange thing in the log. MqttMapper says it'll create "amperae State of Charge" and "amperae Hv Capacity" devices but it seems it don't. Going deeper, this message is show at each MqttMapper startup.

Would it be possible to have a look into Domoticz log, to see if "Device creation" is ...

Could you please copy here content of JSON configuration file?

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

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

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


I got an answer:

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 ...

NvBgm wrote: Sunday 11 January 2026 12:00 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}

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

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


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 ...

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 ...

The interesting part start with: and ends with: Would it be also possible to (temporarily) allow device creation, as this could be a good reason to not create devices successfully?

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

"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.