Elements of a single serial driver are all showing a delay between sending out a command, and receiving/processing the response. All elements using the driver show the same behavior, also across different clusters.

The delay is pretty much exactly the same as the configured element time-out time. Confirmed by modifying the time-out time.

After manually checking the response, it seems to match with the structure defined in the protocol <Response> tag, and also the development logging does not indicate any mismatches. The elements are also not in a time-out state, and parameter values are all filled in.

Any ideas about what could cause this, based on the description above?