Domoticz

There is an silent() function. It would be nice to have a function that only changes the state (On/Off) of a device without 'firing' the RFLINK or RFXCOM.
Is such a function available?

what would be the purpuse of "simulating" a command that a dummy hardware device can't do?

Simpel. I have a master and slave Raspberry Pi.
On one Rasp. RFLink and on the other Rfxcom.
I would like to synchronize all the devices on both Raspberry's
Most of the devices, which are insight of both Rasp. are default synchronized, because they recieve each other signal.
A few devices do not receive the both Rasp. (at least not at all times). Fault are the concrete floors.
So for those devices the Rasp. are not synchronized.
If I find a way to do that, I would have a redundant system.
If 1 crashes or does not function properly I would have the other to control my devices.

ok, thaks for clarification.

what about a dummy pushbutton
edit it
in the onAction configure the http API for the remote button
http://<remoteIP>:<remoteport>/json.htm?type=command&param=switchlight&idx=<remoteSwitchIdx>&switchcmd=On

The problem is that one Rasp. fires a switch.
If you activate the other Rasp. with a json call then that switch gets activated and fires the hardware which could be recieved by the initial Rasp.
And then the cycle starts again.
The json call principle would work if it is garanteed that both Rasps would not recieve each other.
But for all the switches on the border of reception of the other Rasp. that creates a problem.

how would you identify a real switch by a virtual/test operation?

All the switches I use are real (KaKu) switches. There is no virtual/dummy switch involved.
So from master domoticz I have scripts that acts on those Kaku's, at least the ones out of range.
That script sets a variable in the slave domoticz with IDX and On or Off.
On the slave domoticz a script is triggered on the change of the variable.
That script read the variable and reads the content (IDX and On/Off).
Than that device (IDX) is set on or off.
Status of that device on the slave is now in sync with the master.
What I want to stop is that the change in status of the slave device is send to RFLink.
Because that sending operation might be catched by the Rfxcom in the master, and then you get into a loop.