Thanks, cracker! My last clock did that too, before updates broke it utterly
I would guess it is because your wifi next by the INST has inconsistent positions, meaning some fire a frame late and some a frame early (when they happen in succession, the spark is ignored). Try making the different temp wifi's use the same position around the INST. It might not be the only issue though.