I have one tasmota device that works with domoticz mqtt AD. I had to use tasmota version 11.1.0 to make it work.

Following a long discussion with 'flyingdomotic' it seems there is a bug in the mqtt plugin framework for windows.

viewtopic.php?p=320505#p320505

Really hope that this can be fixed

After 45yrs with computers - unlikely to change horses. Guess I will find another solution.

Sadly I am a neanderthal that runs windows everywhere. The mqtt broker machine is running windows 11 pro 23h2 with eclipse mosquitto 2.0.19. The client machine is Windows 10 22H2 running -- domoticz 2024.7 build 16268 -- mqttmapper 0.48 -- python 3.11.9 32bit. I think the problem is likely to be ...

That is true for the client protocol version request. But Eclipse internally uses:

enum mosquitto__protocol {
mosq_p_invalid = 0,
mosq_p_mqtt31 = 1,
mosq_p_mqtt311 = 2,
mosq_p_mqtts = 3,
mosq_p_mqtt5 = 5,
};

Finally found some verbose logging in the eclipse broker. Domoticz is connecting as a v3.1.1 client.

2024-10-09T11:44:49: New client connected from 192.168.1.140:3308 as Domoticz_MqttMapper_19_1728467088 (p2, c1, k60)

The 'p2' indicates the mqtt protocol version,c1=clean session,k60 = keep alive

I have looked at the mqtt broker documentation and I can see no way to force the protocol version used by the client. I am wondering if there is something in the windows version of the plugin framework that is "casting" (i am not a C programmer) the 8 bit topic len value into a 16 bit value by ...

Hi My understanding is that the eclipse mqqt broker supports both v3 and v5. But I think that is the client that chooses on connection which protocol version it wishes to use. In the case of Domoticz I assume it connects requesting V3.1. Also in the test that I did with the switch my app is not ...

It seems to me that the mqttmapper is calculating the 'topic len' by joining bytes 4 (value 08) and value 00 of the incoming message giving a length of 0800 (2048 decimal). This matches up with a previous test for a status message where byte 4 =12hex and the topic len was calculated as 1200hex 4608 ...

There was a device with th same name and different ID on other hardware. I deleted the device and disabled the hardware. There is no duplicate mqttmapper. I reran the test with the switch . This shows the outbound and inbound MQTT cmd messages. 2024-10-08 08:16:38.851 mymqtt: Worker thread started ...

Hi
Logging is set to verbose. I also was surprised that there was no message for the switch being pressed.

The incoming cmd was generated when I clicked on the domoticz switch. I did not publish a message using mqtt explorer.
The sequence of actions was exactly as described in my message. Before I clicked on the domoticz switch the topic was cleared as shown in the image (before click).

Hi, i have done the following ... 1. Upgraded mqtt mapper to latest version 2. Set a minimal devices file { "Pool Camera Switch": { "topic": "Pool/cmd", "type": "244", "subtype": "73", "switchtype": "0", "set": {"payload": {"command":"#"}}, "mapping": {"item": "command","values": {"OFF": "0", "ON ...

The camera app only sends status updates to the status topic. Domoticz is expected to send commands to the camera when the domoticz switch is turned off/on. The log is when I tried to turn ON the domoticz switch which then seems to send an mqtt message to the broker which is sent to the app ...

Hi
that was in my previous message before the on/off switch test

Hi again Upgraded broker-- no change. Changed the devices json file to have only the command device and then tried turning the switch on. Same problem! 2024-10-05 09:47:41.328 Status: mymqtt: Initialized version 1.0.46, author 'Flying Domotic' 2024-10-05 09:47:41.335 mymqtt: 'HardwareID':'19' 2024 ...

Hi Here is the plugin log when the value changes with mqttmappervalues output. I am going to upgrade the mqtt broker to 2.0.19 to see if there is any difference. 2024-10-05 08:45:26.078 mymqtt: Reconnecting 2024-10-05 08:45:26.079 mymqtt: MqttClient::Open 2024-10-05 08:45:26.080 mymqtt: Protocol set ...

Hi This is strange. The camera app is mine and uses the python paho client to send the status to the broker mqttpayload=json.dumps({"status": "up"}) (rc, msgid) = mqttclient.publish(camera_name+'/camera_status', payload=mqttpayload, qos=1,retain=True) mqtt explorer.png Because it looked OK in MQTT ...

I am using eclipse mosquitto V2.0.18 on windows 64bit on the domoticcz production system. The broker is working on the domoticz production system with MQTT auto discovery without a problem and communicating with the development server for mqtt AD without a problem. The 'status' message in the log ...

I have a camera surveillance app (using python paho) that is communicating with domoticz v2024.7 via mqtt broker. The camera sends status to domoticz and receives commands from domoticz via 2 topics. I have configured MQTTmapper with a devices file (1 text device for status, 1 on/off switch for ...