Have you considered the possibility that Hubitat doesn't want to create a support nightmare for itself with a large influx of users attracted by a highly discounted price-point ($99)?
You cannot be local. And this is exactly the sort of reason that it is in Hubitat's best interests for people who migrate to this platform to be fully aware of:
- Devices that are Hubitat compatible
- Cloud integrations that are Hubitat-created (and therefore Hubitat supported)
- Cloud integrations that are community created and therefore not supported by Hubitat personnel.
I moved from Wink to Hubitat in late March of 2019. I spent an entire month before that carefully cataloging my devices that worked with Hubitat using built-in drivers, versus the devices that required community drivers (I also downloaded copies of these to use when needed). I realized the one of my cloud integrations was Hubitat-created (ecobee), whereas the other (MyQ) was written by a community member.
I spent at least a week asking questions here about unsupported devices - and received very helpful responses from members of the community (@waynespringer79, @zarthan, @ogiewon, @JasonJoel, @bertabcd1234, @SmartHomePrimer, @Cobra, @bptworld among others). But doing all this requires time and patience (realizing that those responding to you are doing so out of the goodness of their heart, and have plenty of other things on their plates). That cannot happen when a large influx of users feels compelled to migrate in the span of a week.
Instead of the good experience I had, a large number of users rapidly migrating from Wink to Hubitat who are unaware of the community-support model that Hubitat relies on will:
- Guarantee a poor user experience for themselves (which Hubitat doesn't want)
- Overwhelm Hubitat support with questions about community integrations (which Hubitat staff shouldn't have to deal with).
