I a working on a problem with a large system - 2 miniservers working together, 31 dimmers, 3 DIs, etc. There are many touchpads which connect back to inputs on the dimmers and DIs.
Each touchpad is assigned 4 inputs on the Loxone system, but many have more than 4 buttons (they can have up to 6 plus a motion sensor). Buttons can be multiplexed by setting them to output a pulse train (from 1 to 4 pulses), simulating a human tapping the button quickly.
Typically the less frequently used buttons are set to use pulses (e.g. room exit), and the more frequently used buttons are connected directly (e.g. lights), with 3 touchpad outputs wired direct to buttons, and the 4th used for the (up to 4) pulse patterns.
The timing of the pulses can be set and at the moment is 0.2 sec high, 0.2 sec low with a guaranteed 0.4 sec gap between consecutive pulse trains. The pulse timing is perfect, I've checked on an oscilloscope.
In the config, a multiclick block is wired to the touchpad output that is associated with pulses. It detects single, double, triple, and quad pulses.
This all worked perfectly in v8. It is unreliable in v10 following a recent upgrade.
I found one issue: half the multiclick blocks were using a max-time-between-pulses value of 0.22s, the other half were using 0.35s. I saw some improvement when I set all to 0.35s, but it is still unreliable. Note that I'm not trying to push one button followed closely by another, so this isn't about the 0.4s gap mentioned above.
Grateful for any suggestions!