on 2.3.3.125 on c5 hub
did not work on 2.3.3 but figured id wait for an update too see if a bug was fixed
thermostat scheduler brings up a similar error
Looks like the driver will need to be updated to support the supportedThermostatModes and supportedThermostatModes attributes, which I don't see it generating an event for at all right now. I don't think these are new, or at least not recent, so it likely always should have been doing this, but some additional clarity was recently provided surrounding the data type this excepts (a JSON list, not a Groovy list as a string like many drivers used to do), and some apps like the new Thermostat Controller 2.0 do expect this, though I think most/all are supposed to work around this with the "old" format for a while, too. But nether is possible with this driver since it doesn't look like it does it at all.
You can verify this by looking at the "Current States" section at the top of the device detail page for the thermostat. If you don't see these attributes there, that is indeed the problem. The best solution would probably be to fix the driver. I'm not sure where you found it (presumably not directly from GitHub) or if the author is still active in the forums or eve rmade a post about it, but if so, that is probably best. But as a workaround, you'd likely be able to temporarily switch to the Virtual Thermostat driver and run the setSupportedThermostatModes() and setSupportedThermostatFModes() commands yourself, providing a JSON list like ["auto", "off", "heat", "cool"] and ["auto", "on"] yourself with the appropriate values for your device/setup.
Same issue on Fibaro Heat Controller with the internal driver. However the issue is that there are no cooling states. this is correct as it is a radiator controller so can't cool. Can we have an option to remove cooling settings for heating only devices? then we can move to the new controller. I realise this is a US/UK problem
Worked like a charm. thank you. I found it sometimes still errored out on creating the new controller but allowed me back in to work with it after that. thank you for taking the trouble to respond.
Please remove that instance of the app (from its App Status page -- gear icon), and start over. Please take a screenshot of just before this problem happens.
I am not able to reproduce any problem at all with adding a thermostat to Thermostat Controller.
If you still have this problem, then I would recommend that you roll back to whatever you prior release was, and then update again to 2.3.4.114.
You can roll back by going to [hub-ip]:8081. There you can do Restore Previous Version. You will need the MAC address from Settings / Hub Details to open the :8081 page.
What I did is go back to 2.3.3.140, I got the same problem.
I try 2.3.2.141 and this version work , but I have only “Thermostat Controller” not the version “Thermostat Controller2.0” with child, but it’s work.
With this version I lost a lot of improvement for . “Thermostat Scheduler”
I decided to go back to 2.3.4.114 and I hope the next version will fix it.
Thanks for you time
I copy the error below
Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: No signature of method: java.lang.String.call() is applicable for argument types: (java.math.BigDecimal) values: [20.0] Possible solutions: wait(), any(), wait(long), each(groovy.lang.Closure), take(int), any(groovy.lang.Closure)
Log:
groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.math.BigDecimal) values: [20.0] Possible solutions: wait(), any(), wait(long), each(groovy.lang.Closure), take(int), any(groovy.lang.Closure) on line 326 (method mainPage)