Hello together,

then thanks to all of you for your quick reactinos, feedback and support ...

So we could close the post for now ... ...

Yes, id 107 is a virtual switch, that is in use … Your information is new and very valuable in the current chat of my subject and good to know for us all … and me … to avoid futher investigations on probably similar MQTT messaging … I had such a case lately before the new beta, searching for the „err ...

Hello together, after testing your proposal message ... { "command": "udevice", "idx" : 107, "nvalue" : 1, } instead of my simple one ... { "idx" : 107, "nvalue" : 1 } there was no difference in my domoticz setup ... still no echoing back of MQTT messages to domoticz/out ... strange. After this, I ...

Thanks to all of you ... for your investigations ...

Checking it and come back ...

The message is initiated by a RPIZ PIR embedded in a nodered flow, that triggers the following simple payload to "domoticz/in", which is a domoticz virtual switch { "idx" : 107, "nvalue" : 1 } In domoticz you can see the virtual switch reacting on that message value change. In nodered there is a ...

Sorry, but there is really no echoing back of the MQTT messages ... and there was no change elsewhere else ...

Probaboy, there is the value itself not in englisch any more = "false", but now in german ="nein" ... can this cause the problem ...

Hi together, since the last beta update the MQTT Broker Plugin Option "Prevent Loop" does not work properly any more ... After installing the latest update ... see below, there is no more echoing back of MQTT messages, that come in to "domoticz/in" and have to be echoed back out to "domoticz/out ...

It is important that you clear your browser cache after updates. Especially when you have user interface issues. Did you do that? Hi all! also after clearing the browser cache it is not possible to change the field "prevent loop" from "true" to false" ... after updating the settings and remarking ...