Added Ecobee action bundle.

[watou]

The new bundle adds ten new actions for use with the Ecobee binding.

Parameters in italics are optional, in which case each unused parameter must be replaced with null. Read the API documentation to be sure you know the rules for calling these functions.

• ecobeeAcknowledge(Item item, String thermostatIdentifier, String ackRef, String ackType, Boolean remindMeLater) - Acknowledge an alert.
• ecobeeControlPlug(Item item, String plugName, String plugState, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Control the on/off state of a plug by setting a hold on the plug.
• ecobeeCreateVacation(Item item, String name, DecimalType coolHoldTemp, DecimalType heatHoldTemp, Date startDateTime, Date endDateTime, String fan, Integer fanMinOnTime) - Create a vacation event on the thermostat.
• ecobeeDeleteVacation(Item item, String name) - Delete a vacation event from a thermostat.
• ecobeeResetPreferences(Item item) - Set all user configurable settings back to the factory default values.
• ecobeeResumeProgram(Item item, Boolean resumeAll) - Remove the currently running event providing the event is not a mandatory demand response event.
• ecobeeSendMessage(Item item, String text) - Send an alert message to the thermostat.
• ecobeeSetHold(Item item, DecimalType coolHoldTemp, DecimalType heatHoldTemp, String holdClimateRef, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Set the thermostat into a hold with the specified temperature.
• ecobeeSetOccupied(Item item, Boolean occupied, Date startDateTime, Date endDateTime, String holdType, Integer holdHours) - Switches a (EMS model only) thermostat from occupied mode to unoccupied, or vice versa.
• ecobeeUpdateSensor(Item item, String name, String deviceId, String sensorId) - Update the name of an ecobee3 remote sensor.

[buildhive]

openHAB » openhab #3192 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[teichsta]

Thanks @watou for this contribution! Hope to find the time for a review soon.

Can you confirm this Action is being shown in the Designer properly?

Best, Thomas E.-E.

[watou]

Hi Thomas, even though your comment prompted me to add the missing entry to feature.xml, I still cannot see the new actions in the Designer (on macosx). There must still be something missing or incorrect in my PR. Can you offer any suggestions?

[buildhive]

openHAB » openhab #3199 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[watou]

Added a note to issue #1403, which seems to be related to why the actions do not appear in the Designer.

[teichsta]

Hi Thomas, even though your comment prompted me to add the missing entry to feature.xml

that was my intention ;-)

Also saw your comment on #1403 … i've also investigated some time already but didn't find an explanation. @kaikreuzer any additional ideas?

[buildhive]

openHAB » openhab #3208 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[buildhive]

openHAB » openhab #3215 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[watou]

@teichsta, I'm thinking that I need to change the Integer parameter types in some of the actions to DecimalType before I test more, you review, etc. So I will comment here when I think this PR is suitable for your time. Thanks!

[buildhive]

openHAB » openhab #3239 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[teichsta]

ok, than give me a sign, when you think this PR is ready for review. Thanks, Thomas E.-E.

[watou]

@teichsta, this PR is ready for your review. Thank you!

[teichsta]

ok, great, thanks!

[watou]

Added testing discussion to the Google Group.

[watou]

squashed and rebased off master

[watou]

I will make changes that mirror those made in #2967 once it's merged, as well as rename the Java package org.openhab.binding.ecobee.internal.messages to org.openhab.binding.ecobee.messages. IMHO it would make the action bundle harder to use to require the user to specify the instance name and set of thermostats to target in the action call, since the user must already have a matching item binding, and all connection state is already maintained in the binding and is therefore dependent. Please let me know if this sounds acceptable in concept.