Hahaha! Same with me! It got down to 68 degrees in here before I started wondering what was going on!!
Fix for this in hot fix release today.
2 Likes
When I downgraded back to .126 the old fashioned thermostat took over. I can't get in to the thermostat controller app anymore so I'm just dialing it in manually for now.
In .129 I'm still getting
java.lang.NullPointerException: Cannot invoke method minus() on null object on line 39 (mainPage)
Should I try to remove the thermostat controller app and reinstall?
I get these same errors on 129.
1 Like
Just to add to the info. I was NOT getting errors on 128 but my controller was not properly controlling the t-stat. I'm now on 129 and I still do NOT have errors. I'm able to go in/out of the app and not seeing any errors in the logs.
Currently it looks like it is now controlling the zwave t-stat properly. Will know after a few cycles.
EDIT: Yes, seems to be controlling properly now.
Ah crap. This is a bug as to certain thermostat drivers. We will fix it!
3 Likes
Bruce, you are the man! Patiently waiting for 130?
Coming soon.
2.2.5.130 is out. Should fix these issues with Thermostat Controller.
2 Likes
Thank you!!!! This fix did it!! I love being able to control more than one thermostat with one controller!!
@bravenel Thank you! It's working here too. I am reminded again how nice it is to not have hot fixes waiting for approval...in S.Korea.
Confirmed crash and non-control issues fixed for me as well. Thanks @bravenel for playing whack-a-mole with the bugs (been there, done that)!
Installed the update, reinstalled everything, still getting an error. Setpoints will not update. I am using Hub Mesh on the controller hub. 1) Thermostat Physical 2) Thermostat Controller.
java.lang.NullPointerException: Cannot invoke method contains() on null object on line 571 (thermHandler)
Show the device page for the thermostat in question, on both the real thermostat and on the Hub Mesh device.
What driver are you using?
I'm also still getting the same error with .130. Zen thermostat. No hub mesh. I see "14 23 1/3 * * ?" down in the scheduled jobs, so I tried deleting the scheduler but still getting error.
I guess I should have checked my logs before commenting that I was good...setting it up went fine and error free and my first test seemed to work, now it is getting cold again and I have these errors.
The problem stems from this driver not having the attribute "supportedThermostatModes". That's what Thermostat Controller is looking for, and not finding it, blowing the error. So one fix is to add that to the driver, adding the attribute definition and in its updated method:
attribute "supportedThermostatModes", "JSON_OBJECT"
sendEvent(name: "supportedThermostatModes", value: ["heat", "cool", "auto", "off"])
Or whatever modes it supports in that list of modes.
The app isn't going to work correctly without that attribute being set.
