Jump to content
C4 Forums | Control4

Thermostat


smarch

Recommended Posts


1 thing to consider before removing it, that was the best zigbee radio they made....so you could have some zigbee mesh issues depending on how strong it is. 

"Best" integration will always be c4 produce and their new tstat is nice. Honeywell/nest work well. Nest is a free driver Honeywell cost like $200

Link to comment
Share on other sites

4 hours ago, koxkp said:

@Dave w @msgreenf I really like my ecobee and use the app now. I've kind of been itching to integrate it with C4, but not liking the driver cost

Has it been worth it to you? I'm sure I'll bit the bullet eventually

I have only used the driver a few times...not sure it's 100% worth it, but it does let me finish the UI, so it's worth it to me. lol

Link to comment
Share on other sites

On 11/22/2016 at 7:32 AM, msgreenf said:

I have only used the driver a few times...not sure it's 100% worth it, but it does let me finish the UI, so it's worth it to me. lol

I really like it and use the driver a lot.  But I have 4 thermostats in my project, So maybe more useful than with just one, 

Link to comment
Share on other sites

Unless you need the "cool" factor of Nest, I would recommend against using it with C4 and at that point might as well use their own app. The C4-THERM UI is very feature-rich and the t-stat works reliably. The Nest driver is quite limited, so much so we have a KB dedicated to much of its limitations such as:

* Control4 Thermostat UI:

- The 'Permanent Hold' / 'Hold Off' are mapped to Away / Home commands of the thermostat.

- There is no way to show the 'Leaf' on / off value

- There is no way to indicate that the Nest thermostat is online / offline, and not receiving commands

- The API does not send status messages of the state of the system. The heat, cool, and fan icons on will always be greyed out on the Control4 UI

- There is no way to indicate that the thermostat is not receiving commands due to rate limiting (See Additional information about Too many requests)

- There is no scheduling support through the Control4 UI

- You cannot change the Temperature scale (F/C) from Navigators

- When in Celsius mode, only full degrees will be shown and used on the Control4 UI

* Control4 Composer Thermostat Properties Page:

- There is no button lockout functionality supported in the driver

- There is no remote temperature sensor support

- You cannot change the Temperature scale (F/C) from Composer Pro

* Nest API / System:

- Scale (Celsius/Fahrenheit) can only be changed from the Nest side, not from Control4

- If the home is in 'Away' mode, any thermostat commands will silently fail. Away / Home states can still be adjusted.

- If the thermostat is offline (not communicating to Wi-Fi for any reason), any thermostat commands will silently fail

- If the thermostat is low battery, any thermostat commands will silently fail

Additional Information:

*Too Many Requests*

The Nest API only supports up to 10 requests in any given hour from Control4. Every additional request after the limit has been reached will be rejected and result in a “Too Many Requests” Error. The thermostat can still be controlled directly from the thermostat, the Nest App or the Nest Web interface, but it locks out commands sent from a Control4 UI.

Since there is no way to show errors on the current UI, there is a 'NESTERROR' variable provided, and a NestError event. When the NestError event fires, you can use the NESTERROR variable in a popup or status message to display the error to the user.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.