Not looking to turn this into a local vs cloud debate thread, or to talk about cloud pro/con, security, changing proprietary protocols, new hardware, hubs, bridges, or any of that...
just a couple of ideas to make things better I think would work with existing hardware with just firmware updates
I know that if the internet goes down for 3 minutes, the vents just open until they can get a connection again. Is it not possible with a firmware update to also allow it where if you have a puck, and the temp sensor reads 78 and the set point is say 74, the vents open, if the temp says 68 and the set point is 74, the vents close. That's it, no automation, no ecobee, no integrations, nothing like that, just basic open/close based on temp and set point. You could then control the primary thermostat manually and the vents would still kind work for you until the internet came back.
That shouldn't require any new hardware or anything complicated
Further idea that would make some happy, is to allow each puck to have a local REST API, so if you get the IP address of each puck, you have a basic REST API to:
GET vents (returns id's, status boolean open/close)
POST vents (take id, boolean for open/close)
POST setpoint (change set point)
That's it, nothing more, when connection is down no automatons, or ecobee control, etc... just this basic REST API... Then others could integrate into that very easily to control things if the internet goes down, tie it into home automation systems, all with Flair just supporting a basic REST API in the firmware and nothing more
just a couple of thoughts
Post is closed for comments.