[2.4.3.164] issues controlling Thermostat Scheduler from RM (including EcoMode offset)

📐 Rule Machine®
,
1

While trying to help another user, discovered that there is an issue when setting a Thermostat Scheduler's EcoMode offset from Rule Machine.

The problem happens when the Thermostat Scheduler has EcoMode already set to on and the offset is changed via Rule Machine. It looks like the new offset is applied before first removing the previous offset currently applied to scheduled setpoints.

In the examples below, the offset is manually set to 2.4 in the TS config page and the RM rule sets it to -3.

Here is a sequence with EcoMode set to OFF (set in the TS config page) then changing the offset via RM (also note the RM action label for "Set EcoMode Offset" is completely weird):

image
image1596×656 164 KB

Here is the same sequence, this time turning EcoMode ON from the TS config page, then changing the offset via RM (note that the "Set EcoMode Offset" RM action also appears to turn on EcoMode as a side effect... which isn't great IMO):

image
image1602×576 143 KB

We see that the new offset (-3) gets applied on top of the already-offset setpoint. The last two logs are from controlling via the TS config page (where the EcoMode offset has been properly updated to -3). Turning EcoMode off returns the setpoint to... 15.6, which is not the scheduled setpoint, it corresponds to the previous EcoMode offset scheduled temperature. Pressing "Set Scheduled Temperatures" returns the setpoint to its correct scheduled temp.

Workaround: always set EcoMode to off before changing the offset.

I believe this is @bravenel's app but we haven't seen them here in months... @bertabcd1234 any ideas?

2

The @support_team can be pinged when RM issues are found.

1 Like
3

Thanks. It's not clear to me if the real issue is in Rule Machine (beyond the cosmetic issue the Thermostat Scheduler action seems to work) or in Thermostat Scheduler (my guess).

1 Like
4

To summarize, these are the issues encountered with controlling Thermostat Scheduler from Rule Machine:

  1. Rule Machine: action "Set EcoMode Offset": app state info is displayed instead of a more appropriate action label (see screenshot above). Other Thermostat Scheduler actions don't have this problem (I tried Set Days/Times Setpoints, for example, displays fine)
  2. Rule Machine: selection of Thermostat Scheduler by Thermostat is ambiguous when more than one Scheduler references a given thermostat - action label does not disambiguate which Scheduler is being controlled. Appears always the "first" Scheduler is picked (whatever "first" means... lowest app id ?)
  3. Rule Machine: selection of Thermostat Scheduler by App is not reflected in the action label, the action label still reads "Thermostat Scheduler for (thermostat name)". However the underlying action, when executed, controls the correct Scheduler, so seems to be a display issue only.
  4. Setting the EcoMode offset from Rule Machine when the Thermostat Scheduler EcoMode is ON gives unexpected results (see first post).

@support_team could we get an acknowledgement please?