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.
