Support for Emerson Sensi wifi Thermostat

[rayg]

Has anyone looked into creating an interface to this popular wifi thermostat?

 

http://www.emersonclimate.com/en-us/products/thermostats/sensi/pages/sensi-wifi-thermostat.aspx

 

Its very affordable and has a nice APP to go with it but integration with ISY would be grand

 

Thanks

 

...Ray

[Michel Kohanim]

Hi Ray,

 

We are currently working on Honeywell WiFi thermostats. Once that's done, we'll take a look.

 

With kind regards,

Michel

[Harvvm]

I have one also and recently received an email saying Sensi is now supported by Echo.

[JCDinPGH]

I second this. It would be great to control/monitor my Sensi thermostat from my ISY. Unfortunately the echo integration is very minimal. One thing they left out what the ability to query the thermostat from the echo, like "Alexa, ask thermostat what is the current temperature?"

[carealtor]

Just curious if any progress had been made on this.  I'm looking at the Sensi thermostat because I'm looking at the Ecovent system.  Ecovent is most closely integrated with Sensi, tho' they say other integrations are coming.

[rayg]

Yes I would also like to know if you plan on adding this functionality.  This is a very popular thermostat too but the lack of ISY integration especially queries for Temprature and humidity  is a limitation for me.

[rayg]

4 Years seems like a long enough wait for a reply from UDI.

Any idea if this can/will be added?

Thanks

 

[lilyoyo1]

4 hours ago, rayg said:

4 Years seems like a long enough wait for a reply from UDI.

Any idea if this can/will be added?

Thanks

 

Does it have an open api?

If there's an open api, you may be better off asking in the nodeservers forum along with a link to the API in hopes that a developer is willing to do something

Edited December 29, 2020 by lilyoyo1

[simplextech]

2 hours ago, lilyoyo1 said:

Does it have an open api?

Not that I can find or am aware of.

I have tried before and they don't respond to me about integrations.  Simplex Tech isn't big enough for them to care.  Maybe if UD contacts them....

[rayg]

Thanks for the suggestion about the nodeServer forum.  I gather there is an API because of what I've seen in terms of integration with SmartThings and the code projects on GitHub containing Java and Ruby implementations.  One guy referred to the API as now being a paid one which may actually stand a better chance of being supported longer term.

But I think you are correct that we need this request to come from higher up and not just the hobbyistes. 

[lilyoyo1]

1 hour ago, rayg said:

Thanks for the suggestion about the nodeServer forum.  I gather there is an API because of what I've seen in terms of integration with SmartThings and the code projects on GitHub containing Java and Ruby implementations.  One guy referred to the API as now being a paid one which may actually stand a better chance of being supported longer term.

But I think you are correct that we need this request to come from higher up and not just the hobbyistes. 

There's an API. It's whether or not it's open or closed. Unfortunately, the fact its working with Smartthings doesn't say much as they could've released their own device handler for it vs a 3rd party person doing it.

If it's a paid API, I have a hard time seeing UDI footing the bill.... especially if it's reoccurring for a small segment of their users to gain access. Not when there are other options which do not require payment such as ecobee, honeywell, zwave, and Nest (potentially) thermostats.

[rayg]

4 hours ago, lilyoyo1 said:

There's an API. It's whether or not it's open or closed. Unfortunately, the fact its working with Smartthings doesn't say much as they could've released their own device handler for it vs a 3rd party person doing it.

If it's a paid API, I have a hard time seeing UDI footing the bill.... especially if it's reoccurring for a small segment of their users to gain access. Not when there are other options which do not require payment such as ecobee, honeywell, zwave, and Nest (potentially) thermostats.

I agree totally.  I was suggesting that they may charge end users - who want the added functionality - a fee to access the service via API  (As UDI charges for access to its own Networking module) via assigned credentials / tokens / oAuth but I am no expert in this.  As would be the case for certain Weather services I have used recently.

Edited December 29, 2020 by rayg