mqttmapper ???

[eddieb]

Hi,

recently I get some really strange behaviour on my test domoticz system.
It worked fine until somewhere this week, actually after rebooting this morning I see strange values on a temperature sensor

Code: Select all

2026-06-17 18:17:37.446  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=0.00
2026-06-17 18:17:47.515  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=2.00
2026-06-17 18:17:57.482  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=1.00
2026-06-17 18:17:59.228  Haier: onMQTTPublish found myhome/topic/Current_Temp, Device 'Haier - current temp', message '19'
2026-06-17 18:18:07.446  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=1.00
2026-06-17 18:18:17.462  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=1.00
2026-06-17 18:18:27.486  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=1.00
2026-06-17 18:18:37.452  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=2.00
2026-06-17 18:18:47.467  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=0.00
2026-06-17 18:18:57.537  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=3.00
2026-06-17 18:19:07.452  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=42.00
2026-06-17 18:19:17.422  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=54.00
2026-06-17 18:19:27.451  Haier: onDeviceModified 001/Haier - current temp, myhome/topic/Current_Temp, nValue=0, sValue=44.00

On myhome/topic/Current_Temp the value is 19 (also in mqttexplorer) ...
Yesterday domoticz had it fine, today it is a mess ..

Screenshot 2026-06-17 at 18.43.25.png (193.56 KiB) Viewed 685 times

as far as I know, I did not change anything ...

(on my primary domotics system with the same mqttmapper config it still works as it did)

[FlyingDomotic]

Strange... How loaded is the battery of this module?

[eddieb]

This is the temperature sensor of a Haier Airco ... Not a battery .,,

I run this plugin on 2 different domoticz systems .., exactly the same config ...
this one is on my old "production" domoticz Domoticz 2025.1 (build 16682)

Screenshot 2026-06-25 at 05.44.21.png (156.37 KiB) Viewed 567 times

this one is on my test system Domoticz 2026.2 (build 18039)

Screenshot 2026-06-25 at 05.44.55.png (228.2 KiB) Viewed 567 times

both use MQTT mapper with network interface and point to the same broker (only 1 broker in my net work)
Looking with MQTT explorer shows what the "old" domoticz displays ...

both use the same mapper.json

Code: Select all

 cat Haier.json
{
	"current temp": {
		"topic": "myhome/topic/Current_Temp",
        	"type": "80", "subtype": "5", "switchtype": "0",
        	"mapping": { "item": "", "digits": 1 }
	},

}

[FlyingDomotic]

This could be either an error in MqttMapper, or in Domoticz.

Tie breaker is Domoticz log, where you'll see temperature changes.Are values in same range (around 23°C), or do you have some temp at zero and some other twice 23?. You may also have a look to temperature widget to see if it stays in normal range.

If you can, you may have a look at Domoticz database, to see what's stored in short and long term tables.

As values are swinging between zero and twice "normal" value, I do suspect the graph display to be bogged.

[eddieb]

as far as my knoledge on sqlite3 goes ...

Code: Select all

sqlite> select * from temperature where devicerowid = 198;
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 10:35:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 10:40:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 10:45:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 10:50:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 10:55:00
198|42.0|0.0|0|0|0.0|0.0|2026-06-26 11:00:00
198|39.0|0.0|0|0|0.0|0.0|2026-06-26 11:05:00
198|43.0|0.0|0|0|0.0|0.0|2026-06-26 11:10:00
198|51.0|0.0|0|0|0.0|0.0|2026-06-26 11:15:00
198|50.0|0.0|0|0|0.0|0.0|2026-06-26 11:20:00
198|40.0|0.0|0|0|0.0|0.0|2026-06-26 11:25:00
198|39.0|0.0|0|0|0.0|0.0|2026-06-26 11:30:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 11:35:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 11:40:00
198|1.0|0.0|0|0|0.0|0.0|2026-06-26 11:45:00
198|2.0|0.0|0|0|0.0|0.0|2026-06-26 11:50:00
198|2.0|0.0|0|0|0.0|0.0|2026-06-26 11:55:00
198|44.0|0.0|0|0|0.0|0.0|2026-06-26 12:00:00
198|39.0|0.0|0|0|0.0|0.0|2026-06-26 12:05:00
198|42.0|0.0|0|0|0.0|0.0|2026-06-26 12:10:00
198|52.0|0.0|0|0|0.0|0.0|2026-06-26 12:15:00
198|51.0|0.0|0|0|0.0|0.0|2026-06-26 12:20:00
198|42.0|0.0|0|0|0.0|0.0|2026-06-26 12:25:00
198|40.0|0.0|0|0|0.0|0.0|2026-06-26 12:30:00

[FlyingDomotic]

S, it seems that data written into table is corrupted.

We now have to determine who store it badly:
- Zigbee2Mqtt: not probable, as the other machine gets correct data
- MqttMapper: possible, but no changes for a while.
-> Could you check you're running the same plug-in version on both machines?
-> Could you also check that you're using the same JSON definition for this temperature sensor on both machine?
-> Could you turn MqttMapper debug on, and look at Domoticz log to see what's sent to Domoticz?
- Domoticz: may be, if other configuration parts are the same.

Making the 3 checks/tests described will help to have a diagnostic.