Rule 5.1 Throwing Error when Implementing a Thermostat Scheduler 2.0 Action

I Have 2 Thermostats, and have set each of them to use a separate Thermostat 2.0 Scheduler.

I am attempting to set the heat/cool temperature set points via Rule 5.1 using an Action to "Control HSM, Garage Doors, Locks Valves or Thermostats". I then select "Set Thermostat Scheduler" I then Check the box for "T6 Thermostat 1st Floor", I then select "Set Days/Times Setpoints" I then select one of the Preset Time Periods "Wake", and when I click anywhere in the Screen I then get:

Unexpected Error

An unexpected error has occurred trying to load the app. Check Logs for more information.

Error: Cannot get property 'heat' on null object

The logs show this error:
java.lang.NullPointerException: Cannot get property 'heat' on null object on line 5199 (method doActPage)

I cannot do anything to use Rule Machine with the Scheduler 2.0. I've deleted and created new rules, I've changes the name of the Thermostat Scheduler, but the same error is thrown at the same point making it impossible to set the Thermostat schedule in Rule Machine 5.1. I'm on platform version 2.3.3.130 on C-5 Hub.

Any advice?

I'm not able to reproduce an error with this. Could you show a screenshot of the Thermostat Scheduler you are trying to set with RM.

I Rolled back to Thermostat Scheduler Legacy, and now everything appears to be working as expected.

New 5.1 Rules do let me proceed on the legacy version.

I'll take a backup and then recover to the version that is using Thermostat Scheduler 2.0, and take some screenshots for you to see.

Here is a screenshot showing the 2 Thermostat Schedulers 2.0 that I have set-up:

Here is a snapshot of the Actual T6 Thermostat 1st Floor Scheduler Settings:

Here is the Screen adding a new Rule 5.1 rule, and going straight to setting the action:
1:

2;

3:

I then click off the selection box, anywhere on screen and receive this error.

4:

image

The Logs show this:

5:

I am using a custom driver for teh T6 Thermostat, that was originally published by djdizzyd.

When I roll my Hub back to a version where it has only Thermostat Scheduler Legacy, everything seems to work with without error...

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.