Just a thought: when both master and slave have a "MQTT Client Gateway with LAN interface" the both are sending their device values to MQTT Topic Domoticz/out and listening to in. As both environments have different devices they have different device IDs. In the MQTT message there is no indication ...

If you use the default settings of WUD, zigbee and zwave you will see you get a zwave, zigbee and wud state topics and homeassistant topic where all the config topics are. This will not have issues if you have only 1 Domoticz MQTT AD gateway. All the devices will be handled by this gateway. If you ...

The discovery topic is by default split from the state topic to ease the system in discovering devices. Else every new message in the integration also has to be checked for config changes. And when you have a lot of devices you will get a lot of unnecessary possible config changes that needs to be ...

What is the Watt value in MQTT in this case? Also minus? Perhaps you have to change the Domoticz kWh device to generating?

Yes, and that seems correct. i see 3 binary sensors in config and 4 sensors. So in Domoticz creates 3 switches and 4 custom sensors. So exactly what WUD configured. It also should be enough to manage the system I suppose. But perhaps in topic WUD/update also config topics are present? It is (or was ...

So what was wrong with the HA Discovery option? From the documentation it just should work.

The Domoticz module published by Domoticz and not a real python module. So nothing to do about this. You cannot run a plugin seperate from Domoticz because of this.

But it looks like python 3.13 is not supported yet by Domoticz. So perhaps uninstall python and install version 3.12

It works for me. Normal log from Domoticz (no debug or something) 2025-07-12 18:07:59.193 MQTTmapper: onMQTTPublish found Marstek, Device 'MQTTmapper - Marstek_SOC', message '{'params': {'dir': 'up', 'id': 'xxxxxxxxxx', 'r_data': [{'name': 'batteryvoltage', 'value': '5426', 'err': '0'}, {'name ...

First parameter in the payload array so should be 1 instead of 0. FlyingDomotic uses the human way of counting, starting with 1 instead of the computer way, starting with 0.
So
"item": "params/r_data/1/value"

FlyingDomotic wrote: ↑Saturday 12 July 2025 9:37

FlyingDomotic wrote: ↑Saturday 12 July 2025 1:00 I'll provide a new README.md file with a full English version, followed by a full French version, in the same document BUT continuous for each language.

Done, new README.md contains now English version followed by French one!

Thanks!

I should apologize... Getting back to my code, I discovered it was already able to extract a numbered item from a list for ... a while. Here's an extract of README.md: In certain cases, payload contains lists (represented by [] delimiters). In this case, you have to specify either list index to use ...

I agree with @waltervl, even if syntax is correct, this is definitively not a standard JOSN file, where you normally should have all items at the same level. In your case, what you have to explain to MqttMapper is: please scan all list items, find those having "name"=xxx, find item "value" and use ...

I do not agree, the JSON that the device is creating is not following normal JSON conventions. It can also be handled by the MQTTmapper but only after serious code changes. And doing it the way you did is definitely not future proof. One single change in format will force to do all other kind of ...

If you cannot have the DR134 send a proper mqtt payload then you could take the route FlyingDomoticz explained earlier: - With MQTT mapper map the complete message to a text device to store the complete payload in that text device - With a dzvents script triggered on a change in the text device read ...

@FlyingDomotic your help requested in this topic please viewtopic.php?p=327147#p327147
Error MQTT mapper: Duplicate xxxxxx node/key

From the manual Transparent transmission : The data received by the serial port is transparently transmitted to the associated topic. Topic distribution: When configuring a topic, you can define an identifier for the topic. After receiving serial port data, the device sends it to the associated ...

I don't know if it's related to this problem. The only devices with RFXMeter do show up in utility, but the Lacrosse TX3 and Depressure and the rest don't show up in temperature or switches. Screenshot 2025-07-10 at 11-29-39 Domoticz.jpg In menu Setup - Users do you have devices assigned to the ...

teo1966 wrote: ↑Thursday 10 July 2025 11:24
I'm getting this error:
Error: Invalid Number Value: '%' for device idx: '%'

In what context? Is there more in the log around this error?

Thank you for your input, realy usefull. Message is always the same, with changing values. Definition of the content of message is by me. Can you also steer the structure of the content to make it more useable? It ideally should look something like: { "params": { "dir": "up", "id": "xxxxxxxxxx", "r ...

If the order in the list is always is the same, so eg batteryvoltage is always the first value in the r_data list you can use the order eg
params.r_data[0].value for batteryvoltage
params.r_data[9].value for internaltemp

Not sure how this could be used in the MQTT mapper JSON configuration file.