the n-way things are a bit tricky. Z-Wave is not a "bus", so only the addressed devices see commands. The code usually adds an association for the regular switches and dimmers. So when they are operated locally, like the merten ones, they also send a command to the core, as we are in group 1. When they are operated remotely, they don't send a command to their group 1 associated peers.
Solution: Read out the association of the remote switch and store them in the DB (the new code already manages the child devices on its own and stores e.g. capabilities for each device, learned from the node info frame at association). We then put the dongle of the core into all groups of the remote switch. So every button press sends a command to the core, too. We then have to traverse the association list and send commands to request the actual levels from the devices. This was already implemented as proof of concept for the ACT remote switches, but abandoned as it forced me to read all associations at every startup in the past. You cannot do that for battery powered remote switches. There is also a new remote switch device template in 0810, so this will work on the long term. For now, the network is polled after 30 seconds of no activity, so you still have the correct floorplan status when you use the orbiter to check if you left the lights on in a room for example.. and you seldom toggle a light and then instantly jump to the orbiter to see if the status is correct (except for testing :-) )
best regards,
Hari
