From the point that the plugin changes the ModeStatus (HeatOn, CoolOn, AutoChangeOver, and Off), the intervening time before the status poll reflects the change in the ModeStatus device variable, attempts to change setpoints will not perform correctly because the plugin needs to know the current ModeStatus. The most practical fix would be to cache the ModeStatus change immediately when it's set, instead of waiting for the next status poll. Otherwise, attempts to change setpoints for the next 5 seconds or so won't work.
From the point that the plugin changes the ModeStatus (HeatOn, CoolOn, AutoChangeOver, and Off), the intervening time before the status poll reflects the change in the ModeStatus device variable, attempts to change setpoints will not perform correctly because the plugin needs to know the current ModeStatus. The most practical fix would be to cache the ModeStatus change immediately when it's set, instead of waiting for the next status poll. Otherwise, attempts to change setpoints for the next 5 seconds or so won't work.