Python Plugin: MqttMapper

Python and python framework

Moderator: leecollings

Post Reply
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

Yes I did, no luck. Could you as a test go back to the previous version?
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

I think it is working again. I did a full reboot off the rpi and know it is working again. I going to to test the rest now and let you know.
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
FlyingDomotic
Posts: 474
Joined: Saturday 27 February 2016 0:30
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Contact:
Contact FlyingDomotic

Re: Python Plugin: MqttMapper

Post by FlyingDomotic »

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/domoti ... n/releases

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

Code: Select all

2026-02-01 11:32:53.643  Mapper: Local context:
2026-02-01 11:32:53.644  Mapper:  ----> 'Devices'              '{}'
2026-02-01 11:32:53.644  Mapper:  ----> 'Domoticz'             '<module 'Domoticz' (built-in)>'
2026-02-01 11:32:53.645  Mapper:  ----> 'Images'               '{}'
2026-02-01 11:32:53.645  Mapper:  ----> 'Parameters'           '{'HardwareID': 50, 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/', 'StartupFolder': '/opt/domoticz/', 'UserDataFolder': '/opt/domoticz/userdata/', 'WebRoot': '', 'Database': '/opt/domoticz/userdata/domoticz.db', 'Language': 'nl', 'Version': '26.1.26-1', 'Author': 'Flying Domotic', 'Name': 'Mapper', 'Address': '192.168.178.50', 'Port': '1883', 'SerialPort': '', 'Username': '', 'Password': '', 'Key': 'MqttMapper', 'Mode1': 'MqttMapper.json', 'Mode2': '', 'Mode3': '', 'Mode4': '', 'Mode5': '', 'Mode6': 'Verbose+', 'DomoticzVersion': '2025.2 (build 16836)', 'DomoticzHash': '3b8a9cf2f', 'DomoticzBuildTime': '2025-10-26 10:11:08'}'
2026-02-01 11:32:53.646  Mapper:  ----> 'Settings'             '{'DB_Version': '170', 'LightHistoryDays': '2', 'MeterDividerEnergy': '1000', 'MeterDividerGas': '100', 'MeterDividerWater': '1000', 'RandomTimerFrame': '15', 'ElectricVoltage': '230', 'CM113DisplayType': '0', '5MinuteHistoryDays': '1', 'SensorTimeout': '10000', 'SensorTimeoutNotification': '0', 'UseAutoUpdate': '0', 'UseAutoBackup': '1', 'CostEnergy': '2442', 'CostEnergyT2': '2442', 'CostGas': '6218', 'CostWater': '16473', 'UseEmailInNotifications': '1', 'EmailPort': '25', 'EmailAsAttachment': '0', 'DoorbellCommand': '0', 'SmartMeterType': '0', 'NotificationSensorInterval': '43200', 'NotificationSwitchInterval': '0', 'RemoteSharedPort': '6144', 'Language': 'nl', 'DashboardType': '0', 'MobileType': '0', 'WindUnit': '0', 'TempUnit': '0', 'SecStatus': '0', 'SecOnDelay': '30', 'ReleaseChannel': '0', 'RaspCamParams': '-w 800 -h 600 -t 1', 'AcceptNewHardware': '0', 'ZWavePollInterval': '60', 'ZWaveEnableDebug': '0', 'ZWaveNetworkKey': '0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10', 'ZWaveEnableNightlyNetworkHeal': '1', 'BatteryLowNotification': '30', 'AllowWidgetOrdering': '1', 'ActiveTimerPlan': '0', 'HideDisabledHardwareSensors': '0', 'WebTheme': 'elemental', 'FloorplanPopupDelay': '750', 'FloorplanFullscreenMode': '0', 'FloorplanAnimateZoom': '1', 'FloorplanShowSensorValues': '1', 'FloorplanShowSwitchValues': '0', 'FloorplanShowSceneNames': '0', 'FloorplanRoomColour': 'Blue', 'FloorplanActiveOpacity': '25', 'FloorplanInactiveOpacity': '5', 'Location': '52.490216;4.947436', 'ProwlAPI': '0', 'NMAAPI': '0', 'PushoverAPI': '0', 'PushoverUser': '0', 'PushALotAPI': '0', 'WebLocalNetworks': '127.0.0.*;192.168.178.*', 'SecPassword': 'd41d8cd98f00b204e9800998ecf8427e', 'ProtectionPassword': 'd41d8cd98f00b204e9800998ecf8427e', 'EmailFrom': '0', 'EmailTo': '0', 'EmailServer': '0', 'EmailUsername': '0', 'EmailPassword': '0', 'UVCParams': '-S80 -B128 -C128 -G80 -x800 -y600 -q100', 'TempHome': '20', 'TempAway': '15', 'TempComfort': '22.0', 'ClickatellAPI': '0', 'ClickatellFrom': '0', 'ClickatellPassword': '0', 'ClickatellTo': '0', 'ClickatellUser': '0', 'NMAEnabled': '1', 'ProwlEnabled': '1', 'PushALotEnabled': '1', 'PushoverEnabled': '1', 'ClickatellEnabled': '1', 'HTTPURL': 'aHR0cHM6Ly93d3cuc29tZWdhdGV3YXkuY29tL3B1c2h1cmwucGhwP3VzZXJuYW1lPSNGSUVMRDEmcGFzc3dvcmQ9I0ZJRUxEMiZhcGlrZXk9I0ZJRUxEMyZmcm9tPSNGSUVMRDQmdG89I1RPJm1lc3NhZ2U9I01FU1NBR0U=', 'HTTPEnabled': '0', 'HTTPField1': '0', 'HTTPField2': '0', 'HTTPField3': '0', 'HTTPField4': '0', 'HTTPTo': '0', 'KodiIPAddress': '224.0.0.1', 'KodiEnabled': '0', 'KodiPort': '9777', 'KodiTimeToLive': '5', 'ShowUpdateEffect': '0', 'ShortLogInterval': '5', 'DisplayPowerUsageInkWhGraph': '1', 'PushbulletAPI': '0', 'PushbulletEnabled': '0', 'DegreeDaysBaseTemperature': '18.0', 'LmsPlayerMac': '00:04:20:12:65:EF', 'LmsDuration': '5', 'LmsEnabled': '1', 'MyDomoticzUserId': '0', 'MyDomoticzSubsystems': '0', 'SendErrorNotifications': '0', 'HTTPPostContentType': 'YXBwbGljYXRpb24vanNvbg==', 'SendErrorsAsNotification': '0', 'HTTPPostData': '0', 'HTTPPostHeaders': '0', 'PushsaferAPI': '0', 'PushsaferEnabled': '0', 'OneWireSensorPollPeriod': '0', 'OneWireSwitchPollPeriod': '0', 'LogEventScriptTrigger': '1', 'Title': 'Domoticz', 'CostEnergyR1': '2263', 'CostEnergyR2': '2263', 'GCMEnabled': '0', 'PushsaferImage': '0', 'WeightUnit': '0', 'DisableDzVentsSystem': '0', 'DzVentsLogLevel': '3', 'EnableEventScriptSystem': '1', 'IFTTTEnabled': '0', 'EmailEnabled': '0', 'IFTTTAPI': '0', 'TelegramAPI': '0', 'TelegramChat': '0', 'TelegramEnabled': '0', 'EventSystemLogFullURL': '1', 'FCMEnabled': '0', 'MaxElectricPower': '9000', 'Unique_ID': '20ee2d55-8d8c-4f6d-8106-97dafa47fb0f', 'ShortLogAddOnlyNewValues': '0', 'AllowPlainBasicAuth': '1', 'Domoticz_Version': '2025.2 (build 16836)', 'ForecastHardwareID': '40', 'HourIdxElectricityDevice': '624485', 'HourIdxGasDevice': '0', 'Currency': '���', 'P1DisplayType': '0', 'ESettings': '{"ConvertWaterM3ToLiter":false,"DisplayFlowWithLines":true,"DisplayOutsideTemp":true,"DisplayTime":true,"Extra1Field":"Data","Extra1Icon":"heater","Extra2Field":"CounterToday","Extra2Icon":"power","Extra3Field":"CounterToday","Extra3Icon":"other","UseCustomIcons":true,"idBatterySoc":-1,"idBatteryWatt":-1,"idExtra1":688,"idExtra2":901,"idExtra3":506,"idGas":-1,"idOutsideTempSensor":610,"idP1":619,"idSolar":919,"idTextSensor":-1,"idWater":-1}', 'events_recent_list': '12,13'}'
2026-02-01 11:32:53.646  Mapper:  ----> '_plugin'              '<pluginV1.pluginV1 object at 0xf0f7e090>'
2026-02-01 11:32:53.647  Mapper:  ----> 'json'                 '<module 'json' from '/usr/lib/python3.11/json/__init__.py'>'
2026-02-01 11:32:53.647  Mapper:  ----> 'os'                   '<module 'os' (frozen)>'
This log is not requested by MqttMapper...
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

ImageThank you, I can see know that the SOC and HV_Capacity devices are made, only no values inside. Something wrong in my json config?

Code: Select all

2026-02-01 14:59:03.821  Mapper: pluginV1::__init__
2026-02-01 14:59:03.821  Mapper: 'HardwareID': '50'
2026-02-01 14:59:03.821  Mapper: 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/'
2026-02-01 14:59:03.821  Mapper: 'StartupFolder': '/opt/domoticz/'
2026-02-01 14:59:03.821  Mapper: 'UserDataFolder': '/opt/domoticz/userdata/'
2026-02-01 14:59:03.821  Mapper: 'Database': '/opt/domoticz/userdata/domoticz.db'
2026-02-01 14:59:03.821  Mapper: 'Language': 'nl'
2026-02-01 14:59:03.821  Mapper: 'Version': '26.1.26-1'
2026-02-01 14:59:03.821  Mapper: 'Author': 'Flying Domotic'
2026-02-01 14:59:03.821  Mapper: 'Name': 'Mapper'
2026-02-01 14:59:03.821  Mapper: 'Address': '192.168.178.50'
2026-02-01 14:59:03.822  Mapper: 'Port': '1883'
2026-02-01 14:59:03.822  Mapper: 'Key': 'MqttMapper'
2026-02-01 14:59:03.822  Mapper: 'Mode1': 'MqttMapper.json'
2026-02-01 14:59:03.822  Mapper: 'Mode6': 'Verbose+'
2026-02-01 14:59:03.822  Mapper: 'DomoticzVersion': '2025.2 (build 16836)'
2026-02-01 14:59:03.822  Mapper: 'DomoticzHash': '3b8a9cf2f'
2026-02-01 14:59:03.822  Mapper: 'DomoticzBuildTime': '2025-10-26 10:11:08'
2026-02-01 14:59:03.822  Mapper: Device count: 9
2026-02-01 14:59:03.822  Mapper: Device: 1 - ID: 948, Name: 'Mapper - SmartEVSE charge current', nValue: 16, sValue: '15.700000000000001'
2026-02-01 14:59:03.822  Mapper: Device: 2 - ID: 949, Name: 'Mapper - SmartEVSE max current', nValue: 16, sValue: '16.0'
2026-02-01 14:59:03.822  Mapper: Device: 3 - ID: 950, Name: 'Mapper - SmartEVSE evenergy charged', nValue: 1714, sValue: '1714.0'
2026-02-01 14:59:03.822  Mapper: Device: 4 - ID: 951, Name: 'Mapper - SmartEVSE evtotalenergy charged', nValue: 1070, sValue: '1069.863'
2026-02-01 14:59:03.822  Mapper: Device: 5 - ID: 952, Name: 'Mapper - SmartEVSE state', nValue: 0, sValue: 'Charging'
2026-02-01 14:59:03.822  Mapper: Device: 6 - ID: 953, Name: 'Mapper - SmartEVSE error', nValue: 0, sValue: '0'
2026-02-01 14:59:03.823  Mapper: Device: 7 - ID: 954, Name: 'Mapper - SmartEVSE charge current override', nValue: 0, sValue: '0.0'
2026-02-01 14:59:03.823  Mapper: Device: 8 - ID: 955, Name: 'Mapper - amperae State of Charge', nValue: 0, sValue: '{'SOC': 59.61}'
2026-02-01 14:59:03.823  Mapper: Device: 9 - ID: 956, Name: 'Mapper - amperae Hv Capacity', nValue: 0, sValue: '{'HV_CAPACITY': 3891.6}'
2026-02-01 14:59:03.824  Mapper: MqttClient::__init__
2026-02-01 14:59:03.824  Mapper: Pushing 'ProtocolDirective' on to queue
2026-02-01 14:59:03.824  Mapper: Pushing 'ConnectDirective' on to queue
2026-02-01 14:59:03.825  Mapper: Pushing 'PollIntervalDirective' on to queue
2026-02-01 14:59:03.826  Mapper: Processing 'ProtocolDirective' message
2026-02-01 14:59:03.826  Mapper: Protocol set to: 'MQTT'.
2026-02-01 14:59:03.826  Mapper: Processing 'ConnectDirective' message
2026-02-01 14:59:03.826  Mapper: Transport set to: 'TCP/IP', 192.168.178.50:1883.
2026-02-01 14:59:03.826  Mapper: Connect directive received, action initiated successfully.
2026-02-01 14:59:03.826  Mapper: Processing 'PollIntervalDirective' message
2026-02-01 14:59:03.827  Mapper: Heartbeat interval set to: 3.
2026-02-01 14:59:03.827  Mapper: Pushing 'onConnectCallback' on to queue
2026-02-01 14:59:03.877  Mapper: Processing 'onConnectCallback' message
2026-02-01 14:59:03.877  Mapper: Calling message handler 'onConnect' on 'module' type object.
2026-02-01 14:59:03.877  Mapper: MqttClient::onConnect
2026-02-01 14:59:03.877  Mapper: MqttClient::onConnect connect to 192.168.178.50:1883, ID=Domoticz_MqttMapper_50_1769954343
2026-02-01 14:59:03.878  Mapper: Pushing 'WriteDirective' on to queue
2026-02-01 14:59:03.878  Mapper: Processing 'WriteDirective' message
2026-02-01 14:59:03.878  Mapper: Sending 47 bytes of data
2026-02-01 14:59:03.878  Mapper:      10 2d 00 04 4d 51 54 54 04 02 00 3c 00 21 44 6f 6d 6f 74 69     .-..MQTT...<.!Domoti
2026-02-01 14:59:03.878  Mapper:      63 7a 5f 4d 71 74 74 4d 61 70 70 65 72 5f 35 30 5f 31 37 36     cz_MqttMapper_50_176
2026-02-01 14:59:03.878  Mapper:      39 39 35 34 33 34 33 .. .. .. .. .. .. .. .. .. .. .. .. ..     9954343
2026-02-01 14:59:03.878  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.928  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.928  Mapper: Received 4 bytes of data
2026-02-01 14:59:03.928  Mapper:      20 02 00 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..     ....
2026-02-01 14:59:03.929  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.929  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:03.929  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:03.929  Mapper: MqttClient::onMessage:: Data Verb=CONNACK
2026-02-01 14:59:03.929  Mapper: MqttClient::onMessage:: Data Description=Connection Accepted
2026-02-01 14:59:03.929  Mapper: MqttClient::onMessage:: Data Status=0
2026-02-01 14:59:03.929  Mapper: onMQTTConnected
2026-02-01 14:59:03.929  Mapper: getTopics: '{'wican/amperae/HV_CAPACITY', 'SmartEVSE-5572/MaxCurrent', 'SmartEVSE-5572/EVEnergyCharged', 'SmartEVSE-5572/State', 'SmartEVSE-5572/ChargeCurrent', 'SmartEVSE-5572/Error', 'wican/amperae/SOC', 'SmartEVSE-5572/ChargeCurrentOverride', 'SmartEVSE-5572/EVTotalEnergyCharged'}'
2026-02-01 14:59:03.930  Mapper: MqttClient::Subscribe to [{'Topic': 'wican/amperae/HV_CAPACITY', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/MaxCurrent', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/EVEnergyCharged', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/State', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrent', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/Error', 'QoS': 0}, {'Topic': 'wican/amperae/SOC', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/ChargeCurrentOverride', 'QoS': 0}, {'Topic': 'SmartEVSE-5572/EVTotalEnergyCharged', 'QoS': 0}]
2026-02-01 14:59:03.930  Mapper: Pushing 'WriteDirective' on to queue
2026-02-01 14:59:03.930  Mapper: Processing 'WriteDirective' message
2026-02-01 14:59:03.930  Mapper: Sending 268 bytes of data
2026-02-01 14:59:03.930  Mapper:      82 89 02 00 01 00 19 77 69 63 61 6e 2f 61 6d 70 65 72 61 65     ��.....wican/amperae
2026-02-01 14:59:03.930  Mapper:      2f 48 56 5f 43 41 50 41 43 49 54 59 00 00 19 53 6d 61 72 74     /HV_CAPACITY...Smart
2026-02-01 14:59:03.930  Mapper:      45 56 53 45 2d 35 35 37 32 2f 4d 61 78 43 75 72 72 65 6e 74     EVSE-5572/MaxCurrent
2026-02-01 14:59:03.930  Mapper:      00 00 1e 53 6d 61 72 74 45 56 53 45 2d 35 35 37 32 2f 45 56     ...SmartEVSE-5572/EV
2026-02-01 14:59:03.930  Mapper:      45 6e 65 72 67 79 43 68 61 72 67 65 64 00 00 14 53 6d 61 72     EnergyCharged...Smar
2026-02-01 14:59:03.930  Mapper:      74 45 56 53 45 2d 35 35 37 32 2f 53 74 61 74 65 00 00 1c 53     tEVSE-5572/State...S
2026-02-01 14:59:03.930  Mapper:      6d 61 72 74 45 56 53 45 2d 35 35 37 32 2f 43 68 61 72 67 65     martEVSE-5572/Charge
2026-02-01 14:59:03.930  Mapper:      43 75 72 72 65 6e 74 00 00 14 53 6d 61 72 74 45 56 53 45 2d     Current...SmartEVSE-
2026-02-01 14:59:03.930  Mapper:      35 35 37 32 2f 45 72 72 6f 72 00 00 11 77 69 63 61 6e 2f 61     5572/Error...wican/a
2026-02-01 14:59:03.930  Mapper:      6d 70 65 72 61 65 2f 53 4f 43 00 00 24 53 6d 61 72 74 45 56     mperae/SOC..$SmartEV
2026-02-01 14:59:03.930  Mapper:      53 45 2d 35 35 37 32 2f 43 68 61 72 67 65 43 75 72 72 65 6e     SE-5572/ChargeCurren
2026-02-01 14:59:03.930  Mapper:      74 4f 76 65 72 72 69 64 65 00 00 23 53 6d 61 72 74 45 56 53     tOverride..#SmartEVS
2026-02-01 14:59:03.931  Mapper:      45 2d 35 35 37 32 2f 45 56 54 6f 74 61 6c 45 6e 65 72 67 79     E-5572/EVTotalEnergy
2026-02-01 14:59:03.931  Mapper:      43 68 61 72 67 65 64 00 .. .. .. .. .. .. .. .. .. .. .. ..     Charged.
2026-02-01 14:59:03.931  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.931  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.932  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.932  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.932  Mapper: Pushing 'ReadEvent' on to queue
2026-02-01 14:59:03.981  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.981  Mapper: Received 13 bytes of data
2026-02-01 14:59:03.981  Mapper:      90 0b 00 01 00 00 00 00 00 00 00 00 00 .. .. .. .. .. .. ..     �............
2026-02-01 14:59:03.981  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.981  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.981  Mapper: Received 121 bytes of data
2026-02-01 14:59:03.981  Mapper:      31 31 00 19 77 69 63 61 6e 2f 61 6d 70 65 72 61 65 2f 48 56     11..wican/amperae/HV
2026-02-01 14:59:03.981  Mapper:      5f 43 41 50 41 43 49 54 59 7b 22 48 56 5f 43 41 50 41 43 49     _CAPACITY{"HV_CAPACI
2026-02-01 14:59:03.981  Mapper:      54 59 22 3a 33 38 39 31 2e 36 7d 31 1e 00 19 53 6d 61 72 74     TY":3891.6}1...Smart
2026-02-01 14:59:03.982  Mapper:      45 56 53 45 2d 35 35 37 32 2f 4d 61 78 43 75 72 72 65 6e 74     EVSE-5572/MaxCurrent
2026-02-01 14:59:03.982  Mapper:      31 36 30 31 24 00 1e 53 6d 61 72 74 45 56 53 45 2d 35 35 37     1601$..SmartEVSE-557
2026-02-01 14:59:03.982  Mapper:      32 2f 45 56 45 6e 65 72 67 79 43 68 61 72 67 65 64 31 37 31     2/EVEnergyCharged171
2026-02-01 14:59:03.982  Mapper:      34 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..     4
2026-02-01 14:59:03.982  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.982  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.982  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.982  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.982  Mapper: Received 32 bytes of data
2026-02-01 14:59:03.982  Mapper:      31 1e 00 14 53 6d 61 72 74 45 56 53 45 2d 35 35 37 32 2f 53     1...SmartEVSE-5572/S
2026-02-01 14:59:03.982  Mapper:      74 61 74 65 43 68 61 72 67 69 6e 67 .. .. .. .. .. .. .. ..     tateCharging
2026-02-01 14:59:03.982  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.982  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.983  Mapper: Received 35 bytes of data
2026-02-01 14:59:03.983  Mapper:      31 21 00 1c 53 6d 61 72 74 45 56 53 45 2d 35 35 37 32 2f 43     1!..SmartEVSE-5572/C
2026-02-01 14:59:03.983  Mapper:      68 61 72 67 65 43 75 72 72 65 6e 74 31 35 37 .. .. .. .. ..     hargeCurrent157
2026-02-01 14:59:03.983  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.983  Mapper: Processing 'ReadEvent' message
2026-02-01 14:59:03.983  Mapper: Received 103 bytes of data
2026-02-01 14:59:03.983  Mapper:      31 1a 00 14 53 6d 61 72 74 45 56 53 45 2d 35 35 37 32 2f 45     1...SmartEVSE-5572/E
2026-02-01 14:59:03.983  Mapper:      72 72 6f 72 4e 6f 6e 65 31 20 00 11 77 69 63 61 6e 2f 61 6d     rrorNone1...wican/am
2026-02-01 14:59:03.983  Mapper:      70 65 72 61 65 2f 53 4f 43 7b 22 53 4f 43 22 3a 35 39 2e 36     perae/SOC{"SOC":59.6
2026-02-01 14:59:03.983  Mapper:      31 7d 31 27 00 24 53 6d 61 72 74 45 56 53 45 2d 35 35 37 32     1}1'.$SmartEVSE-5572
2026-02-01 14:59:03.983  Mapper:      2f 43 68 61 72 67 65 43 75 72 72 65 6e 74 4f 76 65 72 72 69     /ChargeCurrentOverri
2026-02-01 14:59:03.983  Mapper:      64 65 30 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..     de0
2026-02-01 14:59:03.983  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.983  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.983  Mapper: Pushing 'onMessageCallback' on to queue
2026-02-01 14:59:03.983  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:03.983  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Verb=SUBACK
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data PacketIdentifier=1
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Topics=[{'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}, {'Status': 0, 'Description': 'Success - Maximum QoS 0'}]
2026-02-01 14:59:03.984  Mapper: onMQTTSubscribed
2026-02-01 14:59:03.984  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:03.984  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Topic=wican/amperae/HV_CAPACITY
2026-02-01 14:59:03.984  Mapper: MqttClient::onMessage:: Data Payload=b'{"HV_CAPACITY":3891.6}'
2026-02-01 14:59:03.986  Mapper: onMQTTPublish: wican/amperae/HV_CAPACITY: 'b'{"HV_CAPACITY":3891.6}''
2026-02-01 14:59:03.986  Mapper: onMQTTPublish found wican/amperae/HV_CAPACITY, Device 'Mapper - amperae Hv Capacity', message '{'HV_CAPACITY': 3891.6}'
2026-02-01 14:59:03.986  Mapper: readValue: {'HV_CAPACITY': 3891.6}, isOnlyMessage: None
2026-02-01 14:59:03.986  Mapper: Setting Mapper - amperae Hv Capacity to >{'HV_CAPACITY': 3891.6}<
2026-02-01 14:59:03.986  (Mapper - amperae Hv Capacity) Updating device from 0:'{'HV_CAPACITY': 3891.6}' to have values 0:'{'HV_CAPACITY': 3891.6}'.
2026-02-01 14:59:03.994  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:03.994  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:03.994  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:03.995  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:03.995  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:03.995  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:03.995  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/MaxCurrent
2026-02-01 14:59:03.995  Mapper: MqttClient::onMessage:: Data Payload=b'160'
2026-02-01 14:59:03.995  Mapper: onMQTTPublish: SmartEVSE-5572/MaxCurrent: 'b'160''
2026-02-01 14:59:03.996  Mapper: onMQTTPublish found SmartEVSE-5572/MaxCurrent, Device 'Mapper - SmartEVSE max current', message '160'
2026-02-01 14:59:03.996  Mapper: nodeMapping: {'item': '', 'multiplier': 0.1}
2026-02-01 14:59:03.996  Mapper: Multiplying by 0.1
2026-02-01 14:59:03.996  Mapper: readValue: 16.0, isOnlyMessage: None
2026-02-01 14:59:03.996  Mapper: Setting Mapper - SmartEVSE max current to 16/16.0
2026-02-01 14:59:03.996  (Mapper - SmartEVSE max current) Updating device from 16:'16.0' to have values 16:'16.0'.
2026-02-01 14:59:04.001  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.001  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/EVEnergyCharged
2026-02-01 14:59:04.001  Mapper: MqttClient::onMessage:: Data Payload=b'1714'
2026-02-01 14:59:04.001  Mapper: onMQTTPublish: SmartEVSE-5572/EVEnergyCharged: 'b'1714''
2026-02-01 14:59:04.002  Mapper: onMQTTPublish found SmartEVSE-5572/EVEnergyCharged, Device 'Mapper - SmartEVSE evenergy charged', message '1714'
2026-02-01 14:59:04.002  Mapper: nodeMapping: {'item': '', 'multiplier': 1}
2026-02-01 14:59:04.002  Mapper: Multiplying by 1
2026-02-01 14:59:04.002  Mapper: readValue: 1714.0, isOnlyMessage: None
2026-02-01 14:59:04.002  Mapper: Setting Mapper - SmartEVSE evenergy charged to 1714/1714.0
2026-02-01 14:59:04.002  (Mapper - SmartEVSE evenergy charged) Updating device from 1714:'1714.0' to have values 1714:'1714.0'.
2026-02-01 14:59:04.006  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.007  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/State
2026-02-01 14:59:04.007  Mapper: MqttClient::onMessage:: Data Payload=b'Charging'
2026-02-01 14:59:04.007  Mapper: onMQTTPublish: SmartEVSE-5572/State: 'b'Charging''
2026-02-01 14:59:04.008  Mapper: onMQTTPublish found SmartEVSE-5572/State, Device 'Mapper - SmartEVSE state', message 'Charging'
2026-02-01 14:59:04.008  Mapper: readValue: Charging, isOnlyMessage: True
2026-02-01 14:59:04.008  Mapper: Setting Mapper - SmartEVSE state to >Charging<
2026-02-01 14:59:04.008  (Mapper - SmartEVSE state) Updating device from 0:'Charging' to have values 0:'Charging'.
2026-02-01 14:59:04.012  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.012  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.012  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.013  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.013  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.013  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.013  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/ChargeCurrent
2026-02-01 14:59:04.013  Mapper: MqttClient::onMessage:: Data Payload=b'157'
2026-02-01 14:59:04.013  Mapper: onMQTTPublish: SmartEVSE-5572/ChargeCurrent: 'b'157''
2026-02-01 14:59:04.013  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrent, Device 'Mapper - SmartEVSE charge current', message '157'
2026-02-01 14:59:04.013  Mapper: nodeMapping: {'item': '', 'multiplier': 0.1}
2026-02-01 14:59:04.014  Mapper: Multiplying by 0.1
2026-02-01 14:59:04.014  Mapper: readValue: 15.700000000000001, isOnlyMessage: None
2026-02-01 14:59:04.014  Mapper: Setting Mapper - SmartEVSE charge current to 16/15.700000000000001
2026-02-01 14:59:04.014  (Mapper - SmartEVSE charge current) Updating device from 16:'15.700000000000001' to have values 16:'15.700000000000001'.
2026-02-01 14:59:04.018  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.018  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.018  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.018  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.019  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.019  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.019  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/Error
2026-02-01 14:59:04.019  Mapper: MqttClient::onMessage:: Data Payload=b'None'
2026-02-01 14:59:04.019  Mapper: onMQTTPublish: SmartEVSE-5572/Error: 'b'None''
2026-02-01 14:59:04.019  Mapper: onMQTTPublish found SmartEVSE-5572/Error, Device 'Mapper - SmartEVSE error', message 'None'
2026-02-01 14:59:04.019  Mapper: readValue: None, isOnlyMessage: True
2026-02-01 14:59:04.019  Mapper: testValue="None" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="No Power Available" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="Communication Error" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="Temperature High" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="EV Meter Comm Error" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="RCM Tripped" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="Waiting for Solar" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="Test IO" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="Flash Error" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: testValue="**Unknown**" (str), readValue="None" (str)
2026-02-01 14:59:04.020  Mapper: Setting Mapper - SmartEVSE error to 0/0
2026-02-01 14:59:04.020  (Mapper - SmartEVSE error) Updating device from 0:'0' to have values 0:'0'.
2026-02-01 14:59:04.025  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.025  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data Topic=wican/amperae/SOC
2026-02-01 14:59:04.026  Mapper: MqttClient::onMessage:: Data Payload=b'{"SOC":59.61}'
2026-02-01 14:59:04.026  Mapper: onMQTTPublish: wican/amperae/SOC: 'b'{"SOC":59.61}''
2026-02-01 14:59:04.026  Mapper: onMQTTPublish found wican/amperae/SOC, Device 'Mapper - amperae State of Charge', message '{'SOC': 59.61}'
2026-02-01 14:59:04.026  Mapper: readValue: {'SOC': 59.61}, isOnlyMessage: None
2026-02-01 14:59:04.026  Mapper: Setting Mapper - amperae State of Charge to >{'SOC': 59.61}<
2026-02-01 14:59:04.026  (Mapper - amperae State of Charge) Updating device from 0:'{'SOC': 59.61}' to have values 0:'{'SOC': 59.61}'.
2026-02-01 14:59:04.030  Mapper: Processing 'onMessageCallback' message
2026-02-01 14:59:04.030  Mapper: Calling message handler 'onMessage' on 'module' type object.
2026-02-01 14:59:04.030  Mapper: MqttClient::onMessage:: Data Verb=PUBLISH
2026-02-01 14:59:04.030  Mapper: MqttClient::onMessage:: Data DUP=False
2026-02-01 14:59:04.030  Mapper: MqttClient::onMessage:: Data QoS=0
2026-02-01 14:59:04.030  Mapper: MqttClient::onMessage:: Data Retain=True
2026-02-01 14:59:04.030  Mapper: MqttClient::onMessage:: Data Topic=SmartEVSE-5572/ChargeCurrentOverride
2026-02-01 14:59:04.031  Mapper: MqttClient::onMessage:: Data Payload=b'0'
2026-02-01 14:59:04.031  Mapper: onMQTTPublish: SmartEVSE-5572/ChargeCurrentOverride: 'b'0''
2026-02-01 14:59:04.031  Mapper: onMQTTPublish found SmartEVSE-5572/ChargeCurrentOverride, Device 'Mapper - SmartEVSE charge current override', message '0'
2026-02-01 14:59:04.031  Mapper: nodeMapping: {'item': '', 'multiplier': 0.1}
2026-02-01 14:59:04.031  Mapper: Multiplying by 0.1
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

This is what I get.
Attachments
wican1.png
wican1.png (128.76 KiB) Viewed 12958 times
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

It is working now. I adjusted the json file to:

Code: Select all

    "amperae State of Charge": {
        "topic": "wican/amperae/SOC",
        "type": "243", "subtype": "6", "switchtype": "0",
        "mapping": {"item": "SOC", "multiplier": 1}
    },
    "amperae Hv Capacity": {
        "topic": "wican/amperae/HV_CAPACITY",
        "type": "248", "subtype": "1", "switchtype": "0",
        "mapping": {"item": "HV_CAPACITY", "multiplier": 1}
	}
}
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
eddieb
Posts: 428
Joined: Wednesday 04 July 2018 7:48
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Netherlands
Contact:
Contact eddieb

Re: Python Plugin: MqttMapper

Post by eddieb »

hi,

is it possible to do a calculation in mapping ?
I have

Code: Select all

"mapping": {"item" : "data/8/value", "multiplier": 1, "digits": 2}
and I want to multiply the value of "data/8/value" with the value of "data/1/value"

or do I need to do this with a dummy device and some lua scripting ?
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC MQTTmapper / SolarEdge SE3500H modbus_tcp / Marstek Venus / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Top
FlyingDomotic
Posts: 474
Joined: Saturday 27 February 2016 0:30
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Contact:
Contact FlyingDomotic

Re: Python Plugin: MqttMapper

Post by FlyingDomotic »

As of now, the only computation allowed is multiplying by a constant.

For more complex things, idea is to extract value(s) and do an external computation with some LUA script, as you guessed it!
Top
eddieb
Posts: 428
Joined: Wednesday 04 July 2018 7:48
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Netherlands
Contact:
Contact eddieb

Re: Python Plugin: MqttMapper

Post by eddieb »

tnx,
I solved it for now
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC MQTTmapper / SolarEdge SE3500H modbus_tcp / Marstek Venus / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Top
hjzwiers
Posts: 305
Joined: Friday 12 January 2018 8:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:
Contact hjzwiers

Re: Python Plugin: MqttMapper

Post by hjzwiers »

I posted something before, but the problem wasnt in mqttmapper ....
Top
BobS
Posts: 17
Joined: Friday 05 June 2015 11:49
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Rotterdam, NL
Contact:
Contact BobS

Re: Python Plugin: MqttMapper

Post by BobS »

Hi,

I am trying to setup a general alert through MqttMapper but I can't get it to work the way I want.

I have a Mqtt Topic: TEST/Itemx/State that can be "OnLine" or "OffLine"
I want the general alert to show up in green with text OnLine or in Red with text OffLine.

I tried several definitions in MqttMapper json file but so far I managed only to get a Green alert with text 1 (or Red alert with text 4) or
a Grey alert with text OnLine or Offline.

Any help is appreciated.
Thanks,
Bob

my json is:
{
"ZZ_Item1_Status Color": {
"topic": "TEST/Item1/State",
"type": "243", "subtype": "22",
"mapping": {"item": "", "default": "0", "values": {"OnLine": "1", "OffLine": "4"} }
},
"ZZ_Item2_Status Text": {
"topic": "TEST/Item2/State",
"type": "243", "subtype": "22",
"mapping": {"item": "", "default": "UNKNOWN", "values": {"OnLine": "OnLine", "OffLine": "OffLine"} }
},
"ZZ_Item3_Status nvalue": {
"topic": "TEST/Item3/State",
"type": "243", "subtype": "22",
"mapping": {"item": "", "default": "0", "nvalue": {"OnLine": "1", "OffLine": "4"} }
},
"ZZ_Item4_Status svalue": {
"topic": "TEST/Item4/State",
"type": "243", "subtype": "22",
"mapping": {"item": "", "default": "0", "svalue": {"OnLine": "OnLine", "OffLine": "OffLine"} }
},
"ZZ_Item5_Status n+svalue": {
"topic": "TEST/Item5/State",
"type": "243", "subtype": "22",
"mapping": {"item": "", "default": "0", "nvalue": {"OnLine": "1", "OffLine": "4"}, "svalue": {"OnLine": "OnLine", "OffLine": "OffLine"} }
}
}
Top
FlyingDomotic
Posts: 474
Joined: Saturday 27 February 2016 0:30
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Contact:
Contact FlyingDomotic

Re: Python Plugin: MqttMapper

Post by FlyingDomotic »

As of now, color is set in nValue and text in sValue for alert device.

MqttMapper is not able to set devices with both nValues and sValues (this is the case for alert device and also for level switchs).

To do it, easiest way is to load alert in a text device with MqttMapper, and write a small dzVent script to copy it in an alert device and set color depending on text (AFIK, this is not possible with LUA).
Top
BobS
Posts: 17
Joined: Friday 05 June 2015 11:49
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Rotterdam, NL
Contact:
Contact BobS

Re: Python Plugin: MqttMapper

Post by BobS »

Oke,
I understand, thanks for the quick response.
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

I have a problem with my MqttMapper. My domoticz docker is on version 2026.2 build 18142. MqttMapper is not working anymore, when I reboot my domoticz i can see the Mapper startup until the first device and after that nothing happening anymore. When I change the MqttMapper.json teh behavior is exactly the same.

Code: Select all

2026-07-28 12:45:01.293  Mapper: /opt/domoticz/userdata/plugins/MqttMapper/MqttMapper.json is a version 1.0 file
2026-07-28 12:45:01.337  Mapper: pluginV1::__init__
2026-07-28 12:45:01.338  Mapper: 'HardwareID': '52'
2026-07-28 12:45:01.338  Mapper: 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/'
2026-07-28 12:45:01.338  Mapper: 'StartupFolder': '/opt/domoticz/'
2026-07-28 12:45:01.339  Mapper: 'UserDataFolder': '/opt/domoticz/userdata/'
2026-07-28 12:45:01.339  Mapper: 'Database': '/opt/domoticz/userdata/domoticz.db'
2026-07-28 12:45:01.339  Mapper: 'Language': 'nl'
2026-07-28 12:45:01.340  Mapper: 'Version': '26.1.26-1'
2026-07-28 12:45:01.340  Mapper: 'Author': 'Flying Domotic'
2026-07-28 12:45:01.340  Mapper: 'Name': 'Mapper'
2026-07-28 12:45:01.341  Mapper: 'Address': '192.168.178.50'
2026-07-28 12:45:01.341  Mapper: 'Port': '1883'
2026-07-28 12:45:01.341  Mapper: 'Key': 'MqttMapper'
2026-07-28 12:45:01.342  Mapper: 'Mode1': 'MqttMapper.json'
2026-07-28 12:45:01.342  Mapper: 'Mode6': 'Verbose+'
2026-07-28 12:45:01.342  Mapper: 'DomoticzVersion': '2026.2 (build 18142)'
2026-07-28 12:45:01.343  Mapper: 'DomoticzHash': '0cb3d4423'
2026-07-28 12:45:01.343  Mapper: 'DomoticzBuildTime': '2026-07-20 13:48:37'
2026-07-28 12:45:01.344  Mapper: Device count: 0
2026-07-28 12:45:01.345  Mapper: Creating device 'SmartEVSE charge current' with key 'SmartEVSE-5572/ChargeCurrent' as unit 1
2026-07-28 12:45:01.345  Mapper: Name='SmartEVSE charge current', Unit='1', Type=243, Subtype=23, Switchtype=0, DeviceID='SmartEVSE-5572/ChargeCurrent', Options='None', Used='True'
I have installed the complete plugin again and still the same. Does anyone know this problem?
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
User avatar
waltervl
Posts: 7005
Joined: Monday 28 January 2019 18:48
Target OS: Linux
Domoticz version: 2026.3
Location: NL
Contact:
Contact waltervl

Re: Python Plugin: MqttMapper

Post by waltervl »

So what has changed between that it worked and not?
Did you change the json? Did you update Domoticz?
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

The wican software changed en also the json output. I tried to change the MqttMapper.json but that didn´t work out for me. After a view times I got the problem that the mapper stopped. I have also done a new install of the MqttMapper bu stil the same problem. This is my json file:

Code: Select all

{
    "SmartEVSE charge current": {
        "topic": "SmartEVSE-5572/ChargeCurrent",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "", "multiplier": 0.1}
    },
    "SmartEVSE max current": {
        "topic": "SmartEVSE-5572/MaxCurrent",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "", "multiplier": 0.1}
    },
    "SmartEVSE evenergy charged": {
        "topic": "SmartEVSE-5572/EVEnergyCharged",
        "type": "243", "subtype": "31", "switchtype": "0",
        "options": {"Custom": "1;kWh"},
        "mapping": {"item": "", "multiplier": 1}
    },
    "SmartEVSE evtotalenergy charged": {
        "topic": "SmartEVSE-5572/EVTotalEnergyCharged",
        "type": "243", "subtype": "31", "switchtype": "0",
        "options": {"Custom": "1;kWh"},
        "mapping": {"item": "", "multiplier": 0.001}
    },
    "SmartEVSE state": {
        "topic": "SmartEVSE-5572/State",
        "type": "243", "subtype": "19", "switchtype": "0",
        "mapping": {"item": ""}
    },
    "SmartEVSE error": {
        "topic": "SmartEVSE-5572/Error",
        "type": "244", "subtype": "73", "switchtype": "18",
        "options": {"SelectorStyle":"1", "LevelOffHidden": "false", "LevelNames":"None|No Power Available|Communication Error|Temperature High|EV Meter Comm Error|RCM Tripped|Waiting for Solar|Test IO|Flash Error|**Unknown**"},
        "mapping": {"item": "", "default": "90",
            "values": {
                "None": "0",
                "No Power Available": "10",
                "Communication Error": "20",
                "Temperature High": "30",
                "EV Meter Comm Error": "40",
                "RCM Tripped": "50",
                "Waiting for Solar": "60",
                "Test IO": "70",
                "Flash Error": "80",
                "**Unknown**": "90"
                }
            }
    },
    "SmartEVSE charge current override": {
        "topic": "SmartEVSE-5572/ChargeCurrentOverride",
        "type": "242", "subtype": "1", "switchtype": "0",
        "options": {"ValueStep": "1", "ValueMin": "0", "ValueMax": "200", "ValueUnit": "A"},
        "initial": {"nvalue": "0", "svalue": "0"},
        "mapping": {"item": "", "multiplier": 0.1},
        "set": {"topic": "SmartEVSE-5572/Set/CurrentOverride", "digits": 0}
    },
    "Ampera-e SOC": {
        "topic": "wican/amperae",
        "key": "wican/amperae-SOC",
        "type": "243", "subtype": "6", "switchtype": "0",
        "mapping": {"item": "SOC"}
    },
    "Ampera-e HV Capacity": {
        "topic": "wican/amperae",
        "key": "wican/amperae-HV_CAPACITY",
        "type": "243", "subtype": "31", "switchtype": "0",
        "options": {"Custom": "1;Ah"},
        "mapping": {"item": "HV_CAPACITY"}
    },
    "Ampera-e HV Capacity kWh": {
        "topic": "wican/amperae",
        "key": "wican/amperae-HV_CAPACITY_KWH",
        "type": "243", "subtype": "31", "switchtype": "0",
        "options": {"Custom": "1;kWh"},
        "mapping": {"item": "HV_CAPACITY_KWH"}
    },
    "Ampera-e Battery Temperature": {
        "topic": "wican/amperae",
        "key": "wican/amperae-BATT_TEMP",
        "type": "80", "subtype": "5", "switchtype": "0",
        "mapping": {"item": "BATT_TEMP"}
    },
    "Ampera-e Control Module Volt": {
        "topic": "wican/amperae",
        "key": "wican/amperae-42-ControlModuleVolt",
        "type": "243", "subtype": "8", "switchtype": "0",
        "mapping": {"item": "42-ControlModuleVolt"}
    },
    "Ampera-e AC Charge Current": {
        "topic": "wican/amperae",
        "key": "wican/amperae-AC_C_C",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "AC_C_C"}
    },
    "Ampera-e AC Charge Voltage": {
        "topic": "wican/amperae",
        "key": "wican/amperae-AC_C_V",
        "type": "243", "subtype": "8", "switchtype": "0",
        "mapping": {"item": "AC_C_V"}
    },
    "Ampera-e Charging Rate": {
        "topic": "wican/amperae",
        "key": "wican/amperae-CHARGING_R_A",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "CHARGING_R_A"}
    }
}
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

This is the error I get. I have reinstalled the mapper but still the same

Code: Select all

2026-07-28 15:35:32.520  Status: Mapper: Started.
2026-07-28 15:35:32.520  Status: Mapper: Entering work loop.
2026-07-28 15:35:32.798  Status: Mapper: Initialized version 26.1.26-1, author 'Flying Domotic'
2026-07-28 15:35:32.950  Mapper: 'HomeFolder': '/opt/domoticz/userdata/plugins/MqttMapper/'
2026-07-28 15:35:32.950  Mapper: 'StartupFolder': '/opt/domoticz/'
2026-07-28 15:35:32.951  Mapper: 'UserDataFolder': '/opt/domoticz/userdata/'
2026-07-28 15:35:32.951  Mapper: 'Database': '/opt/domoticz/userdata/domoticz.db'
2026-07-28 15:35:32.951  Mapper: 'Language': 'nl'
2026-07-28 15:35:32.952  Mapper: 'Version': '26.1.26-1'
2026-07-28 15:35:32.952  Mapper: 'Author': 'Flying Domotic'
2026-07-28 15:35:32.952  Mapper: 'Name': 'Mapper'
2026-07-28 15:35:32.952  Mapper: 'Address': '192.168.178.50'
2026-07-28 15:35:32.952  Mapper: 'Port': '1883'
2026-07-28 15:35:32.953  Mapper: 'Key': 'MqttMapper'
2026-07-28 15:35:32.953  Mapper: 'Mode1': 'MqttMapper.json'
2026-07-28 15:35:32.953  Mapper: 'Mode6': 'Verbose+'
2026-07-28 15:35:32.953  Mapper: 'DomoticzVersion': '2026.2 (build 18142)'
2026-07-28 15:35:32.954  Mapper: 'DomoticzHash': '0cb3d4423'
2026-07-28 15:35:32.954  Mapper: 'DomoticzBuildTime': '2026-07-20 13:48:37'
2026-07-28 15:35:32.954  Mapper: Device count: 0
2026-07-28 15:35:32.955  Mapper: Creating device 'SmartEVSE charge current' with key 'SmartEVSE-5572/ChargeCurrent' as unit 1
2026-07-28 15:35:32.955  Mapper: Name='SmartEVSE charge current', Unit='1', Type=243, Subtype=23, Switchtype=0, DeviceID='SmartEVSE-5572/ChargeCurrent', Options='None', Used='True'
2026-07-28 15:35:32.955  Error: Mapper: Device creation failed, Domoticz settings prevent accepting new devices.
2026-07-28 15:35:32.956  Error: Mapper: Call to function 'onStart' failed, exception details:
2026-07-28 15:35:32.998  Error: Mapper: Traceback (most recent call last):
2026-07-28 15:35:32.998  Error: Mapper:   File "/opt/domoticz/userdata/plugins/MqttMapper/plugin.py", line 151, in onStart
2026-07-28 15:35:32.998  Error: Mapper:     _plugin.onStart()
2026-07-28 15:35:32.998  Error: Mapper:     ~~~~~~~~~~~~~~~^^
2026-07-28 15:35:32.998  Error: Mapper:   File "/opt/domoticz/userdata/plugins/MqttMapper/pluginV1.py", line 623, in onStart
2026-07-28 15:35:32.998  Error: Mapper:     newDevice = self.devices[newUnit]
2026-07-28 15:35:32.999  Error: Mapper:                 ~~~~~~~~~~~~^^^^^^^^^
2026-07-28 15:35:32.999  Error: Mapper: KeyError: 1
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
FlyingDomotic
Posts: 474
Joined: Saturday 27 February 2016 0:30
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Contact:
Contact FlyingDomotic

Re: Python Plugin: MqttMapper

Post by FlyingDomotic »

Reason is "Device creation failed, Domoticz settings prevent accepting new devices"

It means that Domoticz is not allowed to create new devices (neither MqttMapper).

To fix this, use "Configuration" > "Parameters" and click on "Authorize device creation for 5 minutes" (or something like this), then restart MqttMapper ("Configuration" > "Hardware", click on MqttMapper hardware line then on "Modify")
Top
rron
Posts: 290
Joined: Sunday 30 March 2014 15:24
Target OS: Linux
Domoticz version: Beta
Location: Waterland
Contact:
Contact rron

Re: Python Plugin: MqttMapper

Post by rron »

Ok that worked for me. I have only to look at the json file because the wican is not working. I can only test that if the car is loading. Thank you I will let you know
Rpi4, Docker, z-wave, zigbee, espeasy, smartevse
Top
Post Reply

Return to “Python”