I’d be very wary of trying that one out right now. Anyone that does should really test the temperature setpoints while physically present to be sure that they work as expected. If I’m remembering correctly, the issue is that the temperature scale (C/F) isn’t currently available in Edge, or perhaps the scale that is available isn’t reliable. I’m running my own thermostat driver with no issues, but I’ve hard-coded the fact that my thermostat and I both measure temperature like good Americans. The beta ST driver has this comment in the code that sums up the current makeshift logic used - it could be that this works just fine for a thermostat running in the normal livable range, but definitely test.
-- under 40, assume celsius
The post below deals with this very topic. I’ve only skimmed it, but it’s the right approach. It requires using the CLI and editing JSON files so it looks scary, but it’s not too terrible a process.
This is also controlled in the device presentation, so while following the steps in the linked topic you would delete the sections pertaining to the fan.
the device’s fingerprint needs to be included in the driver (There’s a generic fingerprint included, which may work for your device if it doesn’t match a specific fingerprint. Though I haven’t seen whether the generic fingerprints will pull a device into Edge)
the device’s fingerprint cannot be included on any custom DTH in your account (you can either delete the DTH or comment the fingerprint out of the DTH by typing // at the beginning of that line)
the device needs to be excluded and then included back into the network
The test folder has routines to test the driver by emulating the behavior of the real device. It isn’t indicative of whether or not a particular device is supported.