Honeywell T6 Pro Z-Wave Programmable Thermostat (TH6320ZW2003)

Add-ons Bindings
,
41

Sorry to jump in on this thread, and I’m not sure whether you discovered how to enable AWAY and HOME modes or just came up with a workaround, but I did run across a somewhat obscure Honeywell document with some Z-wave implementation details that states:

Basic V1 (basic set command implementation):
• Value 0x00 Device goes to Energy saving setting (AWAY mode)
• Values 0x01-0x63 and 0xFF Device goes to Comfort setting (HOME mode)

I assume that sending 0x00 will put the thermostat into an “eco heat” setting when it would normally be in heating mode and “eco cool” when it would be cooling.

It also details how AWAY/HOME states are reported. Sorry I’m too noob to upload it but here is the link to Honeywell’s site: T6 Pro Z-Wave Programmable Thermostat SUBMITTAL SHEET

42

@chris Does this have anything interesting? It would be great if there was a way to send this command using the z-wave binding.

@steve_hoge I have not discovered a way to set Away mode, just eco heat and eco cool. The Thermostat just ignores the “AWAY” mode. There does not seem to be a way to set AWAY on the thermostat menu itself.

This SEEMS to suggest that this “V1 Basic” command could control a HOME/AWAY toggle, but @chris can let us know if this is in the wheelhouse of the z-wave binding or a manufacturer specific extension to the z-wave spec that cannot be realistically supported by the binding.

NOTES
Thermostat Mode V3:
• Some of the reported modes are manufacturer specific if not covered by the Z-Wave command class.
• The energy saving mode (Away state) is reported in “Manufacturer Data field 1” as follows:
0 = Energy Saving Auto. System mode is Auto, Away state is active
1 = Energy Saving EmHeat. System mode is EmHeat, Away state is active
Basic V1 (basic set command implementation):
• Value 0x00 Device goes to Energy saving setting (AWAY
mode)
• Values 0x01-0x63 and 0xFF Device goes to Comfort setting (HOME mode)
Notification V3:
• Notification V3 is enabled by default (Power management alarm handling). Notification Type: Power Management
(0x08). Notification Events: AC mains disconnected
(0x02), AC mains re-connected (0x03)
Security:
• All supported Z-Wave Command classes are supported securely (S2 unauthenticated), except Transport Service V2, Security 2 V1 and Z-Wave Plus Info V2 Association V2:
• Group ID: 1; Maximum Nodes: 1; Description:
• Z-Wave Plus Lifeline
• Command Classes reported: Multilevel Sensor, Thermostat Setpoint, Thermostat Mode
• Thermostat Fan Mode, Thermostat Operating State, Thermostat Fan State

43

Reading the spec, it looks like the manufacture data 1 is not a separate command or the Away mode.
Meaning on the send you have to select a “Manual or Manufacture specific Mode”
and a bit field for number of bytes.
and then those specific bytes.
I cant tell if the binding currently supports that or not.

No of Manufacturer Data fields (3 bits)
This field is used to advertise the length in bytes of the Manufacturer Data field in the command. This
field MUST be in the range 0..7.
This field MUST be set to 0 if the Mode field is not set to 0x1F (MANUFACTURER SPECIFIC).
This field MUST indicate the length in bytes of the Manufacturer Data field if the Mode field is set to
0x1F (MANUFACTURER SPECIFIC).
Mode (5 bits)
This field is used to set the thermostat mode at the receiving node

Below is from the binding
What is needed is not support for 13 away
but support for 31 (0x1F) followed by additional data


        OFF(0, "Off"),
        HEAT(1, "Heat"),
        COOL(2, "Cool"),
        AUTO(3, "Auto"),
        AUX_HEAT(4, "Aux Heat"),
        RESUME(5, "Resume"),
        FAN_ONLY(6, "Fan Only"),
        FURNANCE(7, "Furnace"),
        DRY_AIR(8, "Dry Air"),
        MOIST_AIR(9, "Moist Air"),
        AUTO_CHANGEOVER(10, "Auto Changeover"),
        HEAT_ECON(11, "Heat Econ"),
        COOL_ECON(12, "Cool Econ"),
        AWAY(13, "Away"),
        FULL_POWER(15, "Full Power"),
        MANUAL(31, "Manual");

image

44

@chris I’m following up about what @bernie_xg described. Do you have any comments?

45

Manufacturer specific addons here are not supported by the binding.

46

@bernie_xg Can you provide a link to where you found this?