Thanks for the quick fix, am able to add zones now.
Question about the ecobee zone controls — when I go into that menu this only option is null — do I need to be running a specific device handler for my ecobee for this to work?
What device handler are you using. I am using yivies. If you point me to the other device handler I can take look at comparability.
I too am working now as well, although the Ecobee properties are null as well for me (I use the built in Smart Things device handler I believe).
Jeff
The new features I have added is Ecobee Climate Zone control, enable and disable keenectZones using what active climate ecobee is running.
In your thermostat driver do you need a driver that exposes capability showing the running ecobee climate.
Right now I am using Yives ecobee driver. The capability is called currentprogramNameForUI, in my app I take this in as the running climate. I also leverage currentClimateList to generate a list of available climates during the setup process.
I will look into the default driver and see whats exposed.
I’m using the default one currently as well.
So, I just want to make sure I understand the setup properly.
I’ve left the default options for the most part, used my Ecobee thermostat as the main thermostat in the first screen as well as the second field (since it’s a sensor as well).
The second screen I created a zone, called Bedroom with my Keen Vents #1 and #2, and used the Bedroom Sensor I have (Ecobee Sensor). I set the temperature control to a static temperature (since I enjoy a very specific set of temperatures) - 70* for heat, and 72* for cooling.
This means that the vents should close if the temperature rises above 70* when heat is running correct? (and they should close at 72* if in cooling if I understand correctly - here’s a catch 22, I use the auto mode versus heat/cool on my ecobee, is this going to be a problem? (I use it because for example it’s 18* this morning, and going to be 60* this afternoon).
Eric
Correct setup, auto mode on the thermostat is not a problem, the system will take the inputs you have for the zone and adjust accordingly.
In addition the vents will close proportionally as you get close to the setpoint.
Fantastic! I haven’t seen them move yet or heard them move yet.
Is using the built in device handler for Ecobee going to be a problem with the temperature/occupancy sensors?
Thank you again!
It will not be a problem.
Just tried installing, can’t get it to work,
Getting java.lang.NullPointerException: Cannot invoke method toFloat() on null object @ line 80
in logging
I tested some more, it only happens when I say the system is AC compatible.
and more testing
So I had my nest set to heat only (for the winter) and Kennect fails when set to AC Capable. So I went into my nest and set it for Auto switch between Heat and Cool, now Kennect works
Megan
Nice find.
I have seen this before with nest, especially with new nest units connected to smart things. When in heat or cool only nest does not send smartthings setpoints for heating and cooling hence the error. After the zones are installed you can set back to heat or cool only.
FYI, Megan your correct both line 80 and 465 reference the cooling setpoint.
I had V1.2 installed but it would not control any vents, I removed it and installed this version, and although everything appears to work, the vents never change settings no matter what temp the room is and what the thermostat is set at. I have an ecobee3 with 3 room sensors. Even if I set the zone temperture to say 60, and the temperature is 70 the vents remain at 100% open, or whatever position I manually set them at. They do open and close from the smartthings app manually.
Any help would be appreciated,
Can you post the log file from a zone when the heat is on and you receive a temp update from the associated zone temp Sensor.
I have moved V2.5 from BETA to stable, please post any bugs or errors, log files are helpful for diagnosing errors.
I’m having the same issue. Old version 1.1.0 was working until I changed my old z-wave thermostat to the Ecobee3. Now the app won’t control the vents. Updated to 2.5 and same problem. Ecobee shows system is running (in heat mode) but Keenect app shows system idle.
I am using the stock ST DH for Ecobee3.
John
I will look into the issue with the stock st dh for ecobee3.
Brian