deric.lts,

Since setting the temperature is not an emergency, my approach would be to establish a global temperature setting variable. If the user changes the temperature, increment or decrement a local copy of this global (displayed on the Pronto) -- don't issue any commands now, but schedule a function for future execution. Regardless of the number of increments or decrements, schedule the function only once. On execution, the future function will calculate an absolute temperature command and send the IR. At this point there is little risk of a user interface block for the single IR command.

This approach works around any syncronization issues because, regardless of any past or current settings, the user wants the temperature displayed on the remote and the absolute temperature commands will force this.