Python Plugin: MqttMapper

Post by **waltervl** » Wednesday 07 January 2026 23:03

NvBgm wrote: Wednesday 07 January 2026 19:33 Can anyone help me with the MQTT Mapper?
I've installed the plugin and it works fine. Now I want to import a value from the MQTT broker, which works fine to a certain extent. The correct meter is created.
But I don't get the value; it stays at zero.
In the MQTT Explorer, I see 38 under 'Value'. The value in the MQTT Explorer isn't in JSON format. It should display it with the code below.
Code: Select all
{
    "Waterverbruik": {
        "topic": "p1monitor/watermeter/day/watermeter_consumption_liter",
		"type": "243", "subtype": "33",  "switchtype": "2",
        "mapping": { "item": "" }
    }
}
In the logfile of Domoticz i get:

MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]

Look at the end. this is not the value i looking for.. 'QoS': 0

It is looking at the correct topic with Quality of Service 0.
That is correct.
What if you through MQTT explorer send a new value eg 25, do you see it listed in the log?

FlyingDomotic · Wednesday 07 January 2026 23:23

Is it possible to get a copy of what Mqtt Explorer shows when you receive a change in the considered topic?

NvBgm · Post by **NvBgm** » Thursday 08 January 2026 9:47

I'll try it.

In the Domoticz log, I see the following:

Code: Select all

 
2026-01-08 07:23:34.591 MQTT mapper: MqttClient::onDisconnect Disconnected from 192.168.2.24:1883
2026-01-08 07:23:34.591 MQTT mapper: MqttClient::Close
2026-01-08 07:23:34.591 MQTT mapper: onMQTTDisconnected
2026-01-08 07:23:40.126 MQTT mapper: Reconnecting
2026-01-08 07:23:40.183 MQTT mapper: MqttClient::onConnect
2026-01-08 07:23:40.183 MQTT mapper: MqttClient::onConnect connect to 192.168.2.24:1883, ID=Domoticz_MqttMapper_22_1767853420
2026-01-08 07:23:40.248 MQTT mapper: onMQTTConnected
2026-01-08 07:23:40.248 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-08 07:23:40.248 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-08 07:23:40.324 MQTT mapper: onMQTTSubscribed
2026-01-08 07:23:51.107 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-08 07:23:51.107 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-08 07:23:51.107 MQTT mapper: MqttClient::onDisconnect Disconnected from 192.168.2.24:1883
2026-01-08 07:23:51.107 MQTT mapper: MqttClient::Close
2026-01-08 07:23:51.107 MQTT mapper: onMQTTDisconnected

When i send with MQTT explorer another valeu i see in the log:

Code: Select all

2026-01-08 09:45:33.091 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 57 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-08 09:45:33.091 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-08 09:45:33.091 MQTT mapper: MqttClient::onDisconnect Disconnected from 192.168.2.24:1883
2026-01-08 09:45:33.091 MQTT mapper: MqttClient::Close
2026-01-08 09:45:33.091 MQTT mapper: onMQTTDisconnected
2026-01-08 09:45:34.108 MQTT mapper: Reconnecting
2026-01-08 09:45:34.168 MQTT mapper: MqttClient::onConnect
2026-01-08 09:45:34.168 MQTT mapper: MqttClient::onConnect connect to 192.168.2.24:1883, ID=Domoticz_MqttMapper_22_1767861934
2026-01-08 09:45:34.220 MQTT mapper: onMQTTConnected
2026-01-08 09:45:34.220 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-08 09:45:34.220 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-08 09:45:34.277 MQTT mapper: onMQTTSubscribed

FlyingDomotic · Post by **FlyingDomotic** » Thursday 08 January 2026 10:16

NvBgm wrote: Thursday 08 January 2026 9:47 I'll try it.

In the Domoticz log, I see the following:

Code: Select all

 
2026-01-08 07:23:51.107 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-08 07:23:51.107 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.

It seems that the MQTT packet received by Domoticz is an illegal one (topic length seems corrupted). MQTT connection is deleted by Domoticz before MqttMapper receives the packet (thus, not doing any changes into device).

It could be interesting to install MqttExplorer (from https://mqtt-explorer.com/) to try getting sent frame.

What's kind of device is sending these frames?

NvBgm · Post by **NvBgm** » Friday 09 January 2026 11:36

The frames are sent to the broker from the 'P1monitor' application.
https://www.p1-monitor.nl/
Via MQTT explorer, everything seems to be coming in correctly.
When I try to retrieve them from MQTTmapper to Domoticz, it fails.
Even when I make a public call from MQTTexplorer to the device in Domoticz, I don't get the value. The MQTTmapper does generate everything correctly.
In the Domoticz log, it seems to only send the 'QoS'.
The time, date, and value are not.

Code: Select all

2026-01-08 09:45:34.220 MQTTmapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]

FlyingDomotic · Post by **FlyingDomotic** » Friday 09 January 2026 14:49

In MqttMapper, message:

Code: Select all

2026-01-08 09:45:34.220 MQTTmapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]

... is sent at plugin startup to subscribe (means request MQTT for a copy of all incoming messages, including those marked with "retain" flag).
This is *NOT* a copy of received message, which looks like:

Code: Select all

onMQTTPublish found <device topic here>, Device '<device name here>', message '<received message here>'

If you don't see "onMQTTPublish" message in log, it means that MqttMapper don't get data. In addition, if you still have "MQTT protocol violation", it means that Domoticz (before MqttMapper) is not able to read messages properly.

Would it be possible to set MqttMapper debug level to "Extra verbose" and send us Domoticz log (only lines concerned by MqttMapper) ? Use "Configuration" > "Hardware", click on MqttMapper line, set "Debug" to "Extra verbose" and click on "Modify".

With this, we'll see exactly message content, to determine if sent message is really bad, or if this is a Domoticz error.

After reproducing error, you can revert debug level to "Normal".

NvBgm · Post by **NvBgm** » Friday 09 January 2026 20:39

I hope this is the log you ask..

Code: Select all

 2026-01-09 20:37:27.094 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-09 20:37:27.094 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-09 20:37:27.147 MQTT mapper: Processing 'ReadEvent' message
2026-01-09 20:37:27.147 MQTT mapper: Received 2 bytes of data
2026-01-09 20:37:27.147 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-09 20:37:27.147 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-09 20:37:27.147 MQTT mapper: Processing 'onMessageCallback' message
2026-01-09 20:37:27.147 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-09 20:37:30.033 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-09 20:37:30.093 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-09 20:37:30.093 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-09 20:37:30.093 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-09 20:37:30.093 MQTT mapper: Processing 'WriteDirective' message
2026-01-09 20:37:30.094 MQTT mapper: Sending 2 bytes of data
2026-01-09 20:37:30.094 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-09 20:37:30.094 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-09 20:37:30.152 MQTT mapper: Processing 'ReadEvent' message
2026-01-09 20:37:30.152 MQTT mapper: Received 2 bytes of data
2026-01-09 20:37:30.152 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-09 20:37:30.153 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-09 20:37:30.153 MQTT mapper: Processing 'onMessageCallback' message
2026-01-09 20:37:30.153 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-09 20:37:31.506 Status: MQTT mapper: Stop directive received.
2026-01-09 20:37:31.506 MQTT mapper: Pushing 'DisconnectDirective' on to queue
2026-01-09 20:37:31.506 MQTT mapper: Processing 'DisconnectDirective' message
2026-01-09 20:37:31.506 MQTT mapper: Disconnect directive received for 'localhost:1883'.
2026-01-09 20:37:31.506 MQTT mapper: Handling TCP disconnect, socket (localhost:1883) is connected
2026-01-09 20:37:31.506 Queued asynchronous read aborted (localhost:1883), [995] The I/O operation has been aborted because of either a thread exit or an application request.
2026-01-09 20:37:31.506 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-09 20:37:31.506 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-09 20:37:31.506 MQTT mapper: Disconnect event received for 'localhost:1883'.
2026-01-09 20:37:31.506 MQTT mapper: Pushing 'onDisconnectCallback' on to queue
2026-01-09 20:37:31.506 MQTT mapper: Pushing 'onStopCallback' on to queue
2026-01-09 20:37:31.506 MQTT mapper: Processing 'onDisconnectCallback' message
2026-01-09 20:37:31.506 MQTT mapper: Calling message handler 'onDisconnect' on 'module' type object.
2026-01-09 20:37:31.506 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-09 20:37:31.506 MQTT mapper: MqttClient::Close
2026-01-09 20:37:31.506 MQTT mapper: onMQTTDisconnected
2026-01-09 20:37:31.506 MQTT mapper: Deallocating connection object 'localhost' (localhost:1883).
2026-01-09 20:37:31.506 MQTT mapper: Processing 'onStopCallback' message
2026-01-09 20:37:31.506 MQTT mapper: Message handler 'onStop' not callable, ignored.

FlyingDomotic · Post by **FlyingDomotic** » Friday 09 January 2026 21:07

That's exactly the log.

However, it only show an MQTT ping/ping and a plugin "stop" request.

The interesting thing is more receiving a message leading to disconnection.

Restart plugin-in and wait for an incoming message that will trigger an "MQTT protocol violation", and send us the corresponding log.

NvBgm · Post by **NvBgm** » Saturday 10 January 2026 10:36

I have restarted the plugin en this is the log in normaal mode from Domoticz

Code: Select all

 2026-01-10 10:32:53.074 Status: MQTT mapper: Entering work loop.
2026-01-10 10:32:53.074 Status: MQTT mapper: Started.
2026-01-10 10:32:53.194 Status: MQTT mapper: Initialized version 25.12.9-1, author 'Flying Domotic'
2026-01-10 10:32:53.195 MQTT mapper: Debug logging mask set to: PYTHON PLUGIN DEVICE
2026-01-10 10:32:53.195 MQTT mapper: C:\Domoticz\plugins\MqttMapper\MqttMapper.json is a version 1.0 file
2026-01-10 10:32:53.197 MQTT mapper: pluginV1::__init__
2026-01-10 10:32:53.197 MQTT mapper: 'HardwareID': '22'
2026-01-10 10:32:53.197 MQTT mapper: 'HomeFolder': 'C:\Domoticz\plugins\MqttMapper\'
2026-01-10 10:32:53.197 MQTT mapper: 'StartupFolder': 'C:\Domoticz\'
2026-01-10 10:32:53.197 MQTT mapper: 'UserDataFolder': 'C:\Domoticz\'
2026-01-10 10:32:53.197 MQTT mapper: 'Database': 'C:\Domoticz\domoticz.db'
2026-01-10 10:32:53.197 MQTT mapper: 'Language': 'nl'
2026-01-10 10:32:53.197 MQTT mapper: 'Version': '25.12.9-1'
2026-01-10 10:32:53.197 MQTT mapper: 'Author': 'Flying Domotic'
2026-01-10 10:32:53.197 MQTT mapper: 'Name': 'MQTT mapper'
2026-01-10 10:32:53.197 MQTT mapper: 'Address': 'localhost'
2026-01-10 10:32:53.213 MQTT mapper: 'Port': '1883'
2026-01-10 10:32:53.213 MQTT mapper: 'Key': 'MqttMapper'
2026-01-10 10:32:53.213 MQTT mapper: 'Mode1': 'MqttMapper.json'
2026-01-10 10:32:53.214 MQTT mapper: 'Mode6': 'Debug'
2026-01-10 10:32:53.214 MQTT mapper: 'DomoticzVersion': '2025.2 (build 16997)'
2026-01-10 10:32:53.214 MQTT mapper: 'DomoticzHash': 'cb3b96b72'
2026-01-10 10:32:53.214 MQTT mapper: 'DomoticzBuildTime': '2025-12-15 02:18:55'
2026-01-10 10:32:53.214 MQTT mapper: Device count: 1
2026-01-10 10:32:53.214 MQTT mapper: Device: 1 - ID: 230, Name: 'MQTT mapper - Waterverbruik', nValue: 0, sValue: ''
2026-01-10 10:32:53.214 MQTT mapper: MqttClient::__init__
2026-01-10 10:32:53.214 MQTT mapper: Heartbeat interval set to: 3.
2026-01-10 10:32:53.278 MQTT mapper: MqttClient::onConnect
2026-01-10 10:32:53.278 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768037573
2026-01-10 10:32:53.339 MQTT mapper: onMQTTConnected
2026-01-10 10:32:53.340 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 10:32:53.340 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 10:32:53.392 MQTT mapper: onMQTTSubscribed
2026-01-10 10:33:31.070 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-10 10:33:31.070 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-10 10:33:31.070 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-10 10:33:31.070 MQTT mapper: MqttClient::Close
2026-01-10 10:33:31.070 MQTT mapper: onMQTTDisconnected
2026-01-10 10:33:44.103 MQTT mapper: Reconnecting
2026-01-10 10:33:44.174 MQTT mapper: MqttClient::onConnect
2026-01-10 10:33:44.174 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768037624
2026-01-10 10:33:44.232 MQTT mapper: onMQTTConnected
2026-01-10 10:33:44.232 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 10:33:44.232 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 10:33:44.296 MQTT mapper: onMQTTSubscribed
2026-01-10 10:35:24.383 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-10 10:35:24.383 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-10 10:35:24.383 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-10 10:35:24.383 MQTT mapper: MqttClient::Close
2026-01-10 10:35:24.384 MQTT mapper: onMQTTDisconnected
2026-01-10 10:35:26.087 MQTT mapper: Reconnecting
2026-01-10 10:35:26.149 MQTT mapper: MqttClient::onConnect
2026-01-10 10:35:26.149 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768037726
2026-01-10 10:35:26.213 MQTT mapper: onMQTTConnected
2026-01-10 10:35:26.213 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 10:35:26.213 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 10:35:26.277 MQTT mapper: onMQTTSubscribed

FlyingDomotic · Post by **FlyingDomotic** » Saturday 10 January 2026 10:42

I forgot to mention I need the "Extra verbose" debug version of this log (as it contains the full MQTT message, that will help to determine if content is legal or not).

My bad, sorry!

NvBgm · Post by **NvBgm** » Saturday 10 January 2026 11:06

No sorry .. I hope you can determinate the error from this log ...

Code: Select all

 2026-01-10 11:03:49.105 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:03:49.105 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:49.167 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:49.167 MQTT mapper: Received 2 bytes of data
2026-01-10 11:03:49.167 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:03:49.167 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:03:49.167 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:03:49.167 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:03:52.013 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:03:52.075 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:03:52.075 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:03:52.075 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:03:52.075 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:03:52.075 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:03:52.075 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:03:52.075 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:52.139 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:52.139 MQTT mapper: Received 2 bytes of data
2026-01-10 11:03:52.139 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:03:52.139 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:03:52.139 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:03:52.139 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:03:52.748 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:52.795 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:52.795 MQTT mapper: Received 61 bytes of data
2026-01-10 11:03:52.795 MQTT mapper: 30 3b 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 72 6d 0;.5p1monitor/waterm
2026-01-10 11:03:52.796 MQTT mapper: 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 72 5f eter/day/watermeter_
2026-01-10 11:03:52.796 MQTT mapper: 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 32 36 2e consumption_liter26.
2026-01-10 11:03:52.796 MQTT mapper: 30 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 0
2026-01-10 11:03:52.796 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-10 11:03:52.796 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-10 11:03:52.796 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-10 11:03:52.796 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-10 11:03:52.796 MQTT mapper: Disconnect event received for 'localhost:1883'.
2026-01-10 11:03:52.796 MQTT mapper: Pushing 'onDisconnectCallback' on to queue
2026-01-10 11:03:52.796 MQTT mapper: Processing 'onDisconnectCallback' message
2026-01-10 11:03:52.796 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-10 11:03:52.796 MQTT mapper: Calling message handler 'onDisconnect' on 'module' type object.
2026-01-10 11:03:52.796 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-10 11:03:52.796 MQTT mapper: MqttClient::Close
2026-01-10 11:03:52.796 MQTT mapper: onMQTTDisconnected
2026-01-10 11:03:52.796 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-10 11:03:52.796 MQTT mapper: Deallocating connection object 'localhost' (localhost:1883).
2026-01-10 11:03:55.014 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:03:55.087 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:03:55.088 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:03:55.088 MQTT mapper: Reconnecting
2026-01-10 11:03:55.088 MQTT mapper: Pushing 'ProtocolDirective' on to queue
2026-01-10 11:03:55.088 MQTT mapper: Pushing 'ConnectDirective' on to queue
2026-01-10 11:03:55.088 MQTT mapper: Processing 'ProtocolDirective' message
2026-01-10 11:03:55.088 MQTT mapper: Protocol set to: 'MQTT'.
2026-01-10 11:03:55.088 MQTT mapper: Processing 'ConnectDirective' message
2026-01-10 11:03:55.088 MQTT mapper: Transport set to: 'TCP/IP', localhost:1883.
2026-01-10 11:03:55.088 MQTT mapper: Connect directive received, action initiated successfully.
2026-01-10 11:03:55.088 MQTT mapper: Pushing 'onConnectCallback' on to queue
2026-01-10 11:03:55.146 MQTT mapper: Processing 'onConnectCallback' message
2026-01-10 11:03:55.146 MQTT mapper: Calling message handler 'onConnect' on 'module' type object.
2026-01-10 11:03:55.146 MQTT mapper: MqttClient::onConnect
2026-01-10 11:03:55.146 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768039435
2026-01-10 11:03:55.146 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:03:55.146 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:03:55.146 MQTT mapper: Sending 47 bytes of data
2026-01-10 11:03:55.146 MQTT mapper: 10 2d 00 04 4d 51 54 54 04 02 00 3c 00 21 44 6f 6d 6f 74 69 .-..MQTT...<.!Domoti
2026-01-10 11:03:55.146 MQTT mapper: 63 7a 5f 4d 71 74 74 4d 61 70 70 65 72 5f 32 32 5f 31 37 36 cz_MqttMapper_22_176
2026-01-10 11:03:55.146 MQTT mapper: 38 30 33 39 34 33 35 .. .. .. .. .. .. .. .. .. .. .. .. .. 8039435
2026-01-10 11:03:55.146 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:55.200 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:55.200 MQTT mapper: Received 4 bytes of data
2026-01-10 11:03:55.200 MQTT mapper: 20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2026-01-10 11:03:55.200 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:03:55.200 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:03:55.200 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:03:55.200 MQTT mapper: onMQTTConnected
2026-01-10 11:03:55.200 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 11:03:55.200 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 11:03:55.200 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:03:55.200 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:03:55.200 MQTT mapper: Sending 60 bytes of data
2026-01-10 11:03:55.200 MQTT mapper: 82 3a 00 01 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 º...5p1monitor/wate
2026-01-10 11:03:55.200 MQTT mapper: 72 6d 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 rmeter/day/watermete
2026-01-10 11:03:55.200 MQTT mapper: 72 5f 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 00 r_consumption_liter.
2026-01-10 11:03:55.200 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:55.253 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:55.253 MQTT mapper: Received 5 bytes of data
2026-01-10 11:03:55.253 MQTT mapper: 90 03 00 01 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю...
2026-01-10 11:03:55.253 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:03:55.253 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:03:55.253 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:03:55.253 MQTT mapper: onMQTTSubscribed
2026-01-10 11:03:58.013 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:03:58.065 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:03:58.065 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:03:58.065 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:03:58.065 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:03:58.065 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:03:58.065 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:03:58.065 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:03:58.132 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:03:58.132 MQTT mapper: Received 2 bytes of data
2026-01-10 11:03:58.132 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:03:58.132 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:03:58.132 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:03:58.132 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:01.011 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:01.081 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:04:01.081 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:04:01.081 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Received 61 bytes of data
2026-01-10 11:04:01.081 MQTT mapper: 30 3b 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 72 6d 0;.5p1monitor/waterm
2026-01-10 11:04:01.081 MQTT mapper: 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 72 5f eter/day/watermeter_
2026-01-10 11:04:01.081 MQTT mapper: 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 32 37 2e consumption_liter27.
2026-01-10 11:04:01.081 MQTT mapper: 30 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 0
2026-01-10 11:04:01.081 Error: (ProcessInbound) MQTT protocol violation: Invalid message length 59 for packet type '3' (iQoS:0, topicLen:13568)
2026-01-10 11:04:01.081 Error: (ProcessInbound) MQTT protocol violation, sending DisconnectedEvent to Connection.
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:01.081 MQTT mapper: Received 2 bytes of data
2026-01-10 11:04:01.081 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:04:01.081 Error: (ProcessInbound) MQTT protocol errored, discarding additional data.
2026-01-10 11:04:01.081 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-10 11:04:01.081 MQTT mapper: Disconnect event received for 'localhost:1883'.
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'onDisconnectCallback' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Processing 'onDisconnectCallback' message
2026-01-10 11:04:01.081 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-10 11:04:01.081 MQTT mapper: Calling message handler 'onDisconnect' on 'module' type object.
2026-01-10 11:04:01.081 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-10 11:04:01.081 MQTT mapper: MqttClient::Close
2026-01-10 11:04:01.081 MQTT mapper: onMQTTDisconnected
2026-01-10 11:04:01.081 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-10 11:04:01.081 MQTT mapper: Deallocating connection object 'localhost' (localhost:1883).
2026-01-10 11:04:04.044 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:04.114 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:04.114 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:07.025 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:07.087 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:07.087 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:10.016 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:10.079 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:10.079 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:13.040 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:13.097 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:13.097 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:13.097 MQTT mapper: Reconnecting
2026-01-10 11:04:13.097 MQTT mapper: Pushing 'ProtocolDirective' on to queue
2026-01-10 11:04:13.097 MQTT mapper: Pushing 'ConnectDirective' on to queue
2026-01-10 11:04:13.097 MQTT mapper: Processing 'ProtocolDirective' message
2026-01-10 11:04:13.097 MQTT mapper: Protocol set to: 'MQTT'.
2026-01-10 11:04:13.097 MQTT mapper: Processing 'ConnectDirective' message
2026-01-10 11:04:13.097 MQTT mapper: Transport set to: 'TCP/IP', localhost:1883.
2026-01-10 11:04:13.097 MQTT mapper: Connect directive received, action initiated successfully.
2026-01-10 11:04:13.097 MQTT mapper: Pushing 'onConnectCallback' on to queue
2026-01-10 11:04:13.150 MQTT mapper: Processing 'onConnectCallback' message
2026-01-10 11:04:13.150 MQTT mapper: Calling message handler 'onConnect' on 'module' type object.
2026-01-10 11:04:13.150 MQTT mapper: MqttClient::onConnect
2026-01-10 11:04:13.150 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768039453
2026-01-10 11:04:13.150 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:13.150 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:13.150 MQTT mapper: Sending 47 bytes of data
2026-01-10 11:04:13.150 MQTT mapper: 10 2d 00 04 4d 51 54 54 04 02 00 3c 00 21 44 6f 6d 6f 74 69 .-..MQTT...<.!Domoti
2026-01-10 11:04:13.150 MQTT mapper: 63 7a 5f 4d 71 74 74 4d 61 70 70 65 72 5f 32 32 5f 31 37 36 cz_MqttMapper_22_176
2026-01-10 11:04:13.150 MQTT mapper: 38 30 33 39 34 35 33 .. .. .. .. .. .. .. .. .. .. .. .. .. 8039453
2026-01-10 11:04:13.150 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:13.213 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:13.213 MQTT mapper: Received 4 bytes of data
2026-01-10 11:04:13.213 MQTT mapper: 20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2026-01-10 11:04:13.213 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:04:13.213 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:04:13.213 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:13.213 MQTT mapper: onMQTTConnected
2026-01-10 11:04:13.213 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 11:04:13.213 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 11:04:13.213 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:13.213 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:13.213 MQTT mapper: Sending 60 bytes of data
2026-01-10 11:04:13.213 MQTT mapper: 82 3a 00 01 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 º...5p1monitor/wate
2026-01-10 11:04:13.213 MQTT mapper: 72 6d 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 rmeter/day/watermete
2026-01-10 11:04:13.213 MQTT mapper: 72 5f 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 00 r_consumption_liter.
2026-01-10 11:04:13.213 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:13.277 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:13.277 MQTT mapper: Received 5 bytes of data
2026-01-10 11:04:13.277 MQTT mapper: 90 03 00 01 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю...
2026-01-10 11:04:13.277 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:04:13.277 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:04:13.277 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:13.277 MQTT mapper: onMQTTSubscribed
2026-01-10 11:04:16.053 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:16.121 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:16.121 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:16.121 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:16.121 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:16.121 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:04:16.121 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:04:16.121 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:16.181 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:16.181 MQTT mapper: Received 2 bytes of data
2026-01-10 11:04:16.181 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:04:16.181 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:04:16.181 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:04:16.181 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:19.014 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:19.076 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:19.076 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:19.076 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:19.076 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:19.076 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:04:19.076 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:04:19.076 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:19.137 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:19.137 MQTT mapper: Received 2 bytes of data
2026-01-10 11:04:19.137 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:04:19.137 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:04:19.137 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:04:19.137 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:22.033 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 11:04:22.095 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 11:04:22.095 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 11:04:22.095 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 11:04:22.095 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 11:04:22.095 MQTT mapper: Sending 2 bytes of data
2026-01-10 11:04:22.095 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 11:04:22.095 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 11:04:22.157 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 11:04:22.157 MQTT mapper: Received 2 bytes of data
2026-01-10 11:04:22.157 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 11:04:22.158 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 11:04:22.158 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 11:04:22.158 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 11:04:23.777 Status: MQTT mapper: Stop directive received.
2026-01-10 11:04:23.778 MQTT mapper: Pushing 'DisconnectDirective' on to queue
2026-01-10 11:04:23.778 MQTT mapper: Processing 'DisconnectDirective' message
2026-01-10 11:04:23.778 MQTT mapper: Disconnect directive received for 'localhost:1883'.
2026-01-10 11:04:23.778 MQTT mapper: Handling TCP disconnect, socket (localhost:1883) is connected
2026-01-10 11:04:23.778 Queued asynchronous read aborted (localhost:1883), [995] The I/O operation has been aborted because of either a thread exit or an application request.
2026-01-10 11:04:23.779 MQTT mapper: Pushing 'DisconnectedEvent' on to queue
2026-01-10 11:04:23.779 MQTT mapper: Processing 'DisconnectedEvent' message
2026-01-10 11:04:23.779 MQTT mapper: Disconnect event received for 'localhost:1883'.
2026-01-10 11:04:23.779 MQTT mapper: Pushing 'onDisconnectCallback' on to queue
2026-01-10 11:04:23.779 MQTT mapper: Pushing 'onStopCallback' on to queue
2026-01-10 11:04:23.779 MQTT mapper: Processing 'onDisconnectCallback' message
2026-01-10 11:04:23.779 MQTT mapper: Calling message handler 'onDisconnect' on 'module' type object.
2026-01-10 11:04:23.779 MQTT mapper: MqttClient::onDisconnect Disconnected from localhost:1883
2026-01-10 11:04:23.779 MQTT mapper: MqttClient::Close
2026-01-10 11:04:23.779 MQTT mapper: onMQTTDisconnected
2026-01-10 11:04:23.779 MQTT mapper: Deallocating connection object 'localhost' (localhost:1883).
2026-01-10 11:04:23.780 MQTT mapper: Processing 'onStopCallback' message
2026-01-10 11:04:23.780 MQTT mapper: Message handler 'onStop' not callable, ignored.
2026-01-10 11:04:23.785 Status: MQTT mapper: Exiting work loop.
2026-01-10 11:04:23.882 Status: MQTT mapper: Stopping threads.
2026-01-10 11:04:23.882 Status: MQTT mapper: Stopped.

© 2012-2026 Domoticz | WWW: Domoticz.com

FlyingDomotic · Post by **FlyingDomotic** » Saturday 10 January 2026 11:14

Ok, I got the frame. I now need to analyze it.

Stay tuned!

FlyingDomotic · Post by **FlyingDomotic** » Saturday 10 January 2026 12:06

After a short analysis, this packet seems to be a correct 3.1.1 packet, but an illegal 5.0 one.

Would it be possible to get first packets exchanged between Domoticz and MQTT server, when you (re)start MqttMapper ? These are log lines between MqttMapper (re) start and first ping/pong (frames starting with "C0 00" and "D0 00")

NvBgm · Post by **NvBgm** » Saturday 10 January 2026 13:32

This is the log direct afther starting up the mapper.

Code: Select all

 2026-01-10 13:31:27.474 MQTT mapper: Worker thread started.
2026-01-10 13:31:27.474 Status: MQTT mapper: Entering work loop.
2026-01-10 13:31:27.474 Status: MQTT mapper: Started.
2026-01-10 13:31:27.587 Status: MQTT mapper: Initialized version 25.12.9-1, author 'Flying Domotic'
2026-01-10 13:31:27.587 MQTT mapper: Debug logging mask set to: PYTHON PLUGIN QUEUE DEVICE CONNECTION MESSAGE
2026-01-10 13:31:27.587 MQTT mapper: C:\Domoticz\plugins\MqttMapper\MqttMapper.json is a version 1.0 file
2026-01-10 13:31:27.599 MQTT mapper: pluginV1::__init__
2026-01-10 13:31:27.599 MQTT mapper: 'HardwareID': '22'
2026-01-10 13:31:27.599 MQTT mapper: 'HomeFolder': 'C:\Domoticz\plugins\MqttMapper\'
2026-01-10 13:31:27.599 MQTT mapper: 'StartupFolder': 'C:\Domoticz\'
2026-01-10 13:31:27.599 MQTT mapper: 'UserDataFolder': 'C:\Domoticz\'
2026-01-10 13:31:27.599 MQTT mapper: 'Database': 'C:\Domoticz\domoticz.db'
2026-01-10 13:31:27.599 MQTT mapper: 'Language': 'nl'
2026-01-10 13:31:27.599 MQTT mapper: 'Version': '25.12.9-1'
2026-01-10 13:31:27.599 MQTT mapper: 'Author': 'Flying Domotic'
2026-01-10 13:31:27.599 MQTT mapper: 'Name': 'MQTT mapper'
2026-01-10 13:31:27.599 MQTT mapper: 'Address': 'localhost'
2026-01-10 13:31:27.599 MQTT mapper: 'Port': '1883'
2026-01-10 13:31:27.599 MQTT mapper: 'Key': 'MqttMapper'
2026-01-10 13:31:27.599 MQTT mapper: 'Mode1': 'MqttMapper.json'
2026-01-10 13:31:27.599 MQTT mapper: 'Mode6': 'Verbose+'
2026-01-10 13:31:27.599 MQTT mapper: 'DomoticzVersion': '2025.2 (build 16997)'
2026-01-10 13:31:27.599 MQTT mapper: 'DomoticzHash': 'cb3b96b72'
2026-01-10 13:31:27.599 MQTT mapper: 'DomoticzBuildTime': '2025-12-15 02:18:55'
2026-01-10 13:31:27.599 MQTT mapper: Device count: 1
2026-01-10 13:31:27.599 MQTT mapper: Device: 1 - ID: 230, Name: 'MQTT mapper - Waterverbruik', nValue: 0, sValue: ''
2026-01-10 13:31:27.599 MQTT mapper: MqttClient::__init__
2026-01-10 13:31:27.599 MQTT mapper: Pushing 'ProtocolDirective' on to queue
2026-01-10 13:31:27.599 MQTT mapper: Pushing 'ConnectDirective' on to queue
2026-01-10 13:31:27.599 MQTT mapper: Pushing 'PollIntervalDirective' on to queue
2026-01-10 13:31:27.599 MQTT mapper: Processing 'ProtocolDirective' message
2026-01-10 13:31:27.599 MQTT mapper: Protocol set to: 'MQTT'.
2026-01-10 13:31:27.599 MQTT mapper: Processing 'ConnectDirective' message
2026-01-10 13:31:27.599 MQTT mapper: Transport set to: 'TCP/IP', localhost:1883.
2026-01-10 13:31:27.599 MQTT mapper: Connect directive received, action initiated successfully.
2026-01-10 13:31:27.599 MQTT mapper: Processing 'PollIntervalDirective' message
2026-01-10 13:31:27.599 MQTT mapper: Heartbeat interval set to: 3.
2026-01-10 13:31:27.599 MQTT mapper: Pushing 'onConnectCallback' on to queue
2026-01-10 13:31:27.656 MQTT mapper: Processing 'onConnectCallback' message
2026-01-10 13:31:27.656 MQTT mapper: Calling message handler 'onConnect' on 'module' type object.
2026-01-10 13:31:27.656 MQTT mapper: MqttClient::onConnect
2026-01-10 13:31:27.656 MQTT mapper: MqttClient::onConnect connect to localhost:1883, ID=Domoticz_MqttMapper_22_1768048287
2026-01-10 13:31:27.656 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 13:31:27.656 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 13:31:27.656 MQTT mapper: Sending 47 bytes of data
2026-01-10 13:31:27.656 MQTT mapper: 10 2d 00 04 4d 51 54 54 04 02 00 3c 00 21 44 6f 6d 6f 74 69 .-..MQTT...<.!Domoti
2026-01-10 13:31:27.656 MQTT mapper: 63 7a 5f 4d 71 74 74 4d 61 70 70 65 72 5f 32 32 5f 31 37 36 cz_MqttMapper_22_176
2026-01-10 13:31:27.656 MQTT mapper: 38 30 34 38 32 38 37 .. .. .. .. .. .. .. .. .. .. .. .. .. 8048287
2026-01-10 13:31:27.656 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 13:31:27.714 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 13:31:27.714 MQTT mapper: Received 4 bytes of data
2026-01-10 13:31:27.714 MQTT mapper: 20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ....
2026-01-10 13:31:27.714 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 13:31:27.714 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 13:31:27.714 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 13:31:27.714 MQTT mapper: onMQTTConnected
2026-01-10 13:31:27.714 MQTT mapper: getTopics: '{'p1monitor/watermeter/day/watermeter_consumption_liter'}'
2026-01-10 13:31:27.714 MQTT mapper: MqttClient::Subscribe to [{'Topic': 'p1monitor/watermeter/day/watermeter_consumption_liter', 'QoS': 0}]
2026-01-10 13:31:27.714 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 13:31:27.714 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 13:31:27.714 MQTT mapper: Sending 60 bytes of data
2026-01-10 13:31:27.714 MQTT mapper: 82 3a 00 01 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 º...5p1monitor/wate
2026-01-10 13:31:27.714 MQTT mapper: 72 6d 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 rmeter/day/watermete
2026-01-10 13:31:27.714 MQTT mapper: 72 5f 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 00 r_consumption_liter.
2026-01-10 13:31:27.714 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 13:31:27.771 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 13:31:27.771 MQTT mapper: Received 5 bytes of data
2026-01-10 13:31:27.771 MQTT mapper: 90 03 00 01 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю...
2026-01-10 13:31:27.771 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 13:31:27.771 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 13:31:27.771 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 13:31:27.771 MQTT mapper: onMQTTSubscribed
2026-01-10 13:31:30.025 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 13:31:30.087 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 13:31:30.087 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 13:31:30.087 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 13:31:30.087 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 13:31:30.087 MQTT mapper: Sending 2 bytes of data
2026-01-10 13:31:30.087 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 13:31:30.087 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 13:31:30.147 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 13:31:30.147 MQTT mapper: Received 2 bytes of data
2026-01-10 13:31:30.147 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
2026-01-10 13:31:30.147 MQTT mapper: Pushing 'onMessageCallback' on to queue
2026-01-10 13:31:30.147 MQTT mapper: Processing 'onMessageCallback' message
2026-01-10 13:31:30.147 MQTT mapper: Calling message handler 'onMessage' on 'module' type object.
2026-01-10 13:31:33.023 MQTT mapper: Pushing 'onHeartbeatCallback' on to queue
2026-01-10 13:31:33.086 MQTT mapper: Processing 'onHeartbeatCallback' message
2026-01-10 13:31:33.086 MQTT mapper: Calling message handler 'onHeartbeat' on 'module' type object.
2026-01-10 13:31:33.086 MQTT mapper: Pushing 'WriteDirective' on to queue
2026-01-10 13:31:33.086 MQTT mapper: Processing 'WriteDirective' message
2026-01-10 13:31:33.086 MQTT mapper: Sending 2 bytes of data
2026-01-10 13:31:33.086 MQTT mapper: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2026-01-10 13:31:33.086 MQTT mapper: Pushing 'ReadEvent' on to queue
2026-01-10 13:31:33.162 MQTT mapper: Processing 'ReadEvent' message
2026-01-10 13:31:33.162 MQTT mapper: Received 2 bytes of data
2026-01-10 13:31:33.162 MQTT mapper: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

FlyingDomotic · Post by **FlyingDomotic** » Saturday 10 January 2026 16:39

Thanks for that!

This message shows:

One connect frame, with version=4 (meaning 3.1.1): 10 2d 00 04 4d 51 54 54 04 02 00 3c 00 21 44 6f 6d 6f 74 69 63 7a 5f 4d 71 74 74 4d 61 70 70 65 72 5f 32 32 5f 31 37 36 38 30 34 38 32 38 37

One connack frame: 20 02 00 00

One subscribe frame: 82 3a 00 01 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 72 6d 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 72 5f 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 00

One suback frame: 90 03 00 01 00

From a previous message, we had a publish frame: 30 3b 00 35 70 31 6d 6f 6e 69 74 6f 72 2f 77 61 74 65 72 6d 65 74 65 72 2f 64 61 79 2f 77 61 74 65 72 6d 65 74 65 72 5f 63 6f 6e 73 75 6d 70 74 69 6f 6e 5f 6c 69 74 65 72 32 36 2e 30 which is a 3.1.1 legal one, but it seems there's a bug in Domoticz, which tries to interpret it as 5.0 frame (and fails).

Is there any Domoticz dev here to try to validate this diag (and fix it if needed)?

Post by **waltervl** » Saturday 10 January 2026 17:34

Better make a GitHub issue for this
@NvBgm what Domoticz version are you on?

NvBgm · Post by **NvBgm** » Saturday 10 January 2026 20:44

My Domoticz version is :

Over Domoticz
Version: 2025.2 (build 16997)
Build Hash: cb3b96b72
Compile Date: 2025-12-15 02:18:55
dzVents Version: 3.1.8
Python Version: 3.11.7 (tags/v3.11.7:fa7a6f2, Dec 4 2023, 19:13:08) [MSC v.1937 32 bit (Intel)]

FlyingDomotic · Post by **FlyingDomotic** » Sunday 11 January 2026 0:04

@NvBgm: do you want to open the issue or do you prefer I do it for you?

NvBgm · Post by **NvBgm** » 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.

rron · Post by **rron** » Sunday 11 January 2026 13:47

I made a new topic in the mapper config file the SOC for my car but the error in the domoticz log is"Error: Mapper: Can't find device key wican/amperae/SOC"
The wican module of my car gives in the mqtt explorer wican/amperae/SOC. I am on Version: 2025.2 (build 16836)

And the json file is

Code: Select all

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

Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Re: Python Plugin: MqttMapper

Who is online