search

maccoylton / esp-homekit-wired-thermostat

Homekit Firmware for Wired Thermostat BHT-002
Apache License 2.0
8 stars 1 forks source link

Existing functionality - Schedules #1

Open ckpt-martin opened 3 years ago

ckpt-martin commented 3 years ago

Sorry for using the issues to get in touch. But I have such a BHT-200 thermostat and am very interested in flashing it with a HomeKit firmware. Is this firmware in a working state? If so, what functionality exists today?

maccoylton commented 3 years ago

It should work, you can set see the current state and temperature and you can set the state and target temperature. I have not implemented any functionality to store schedule as I intend all that to be managed with homekit automation. Give it a go and let me have your feedback.

ckpt-martin commented 3 years ago

Thanks. Which version of code should I use? The debugging-startup or which one?

ckpt-martin commented 3 years ago

About scheduling: are schedules stored in the MCU? Because you can switch between auto and manual mode from the panel. I understand the thinking that automations would typically be done from HomeKit. But there are sometimes advantages to the built-in automation functionality in some devices. For instance, my shades in the house are integrated into HomeKit via HomeBridge and I could do automations via HomeKit. But these shades also have a physical button to enable/disable schedules. This is practical for instance in a guest room where the guest can decide whether they want to manually adjust the shades or leave the pre-defined schedules active. Typically the pre-defined schedules are active when there is no guest. The shade panel also shows whether manual or auto mode are active. This only applies to the schedules stored in the device and would not work for automations created within HomeKit. So, automations in HomeKit have advantages, but also disadvantages depending on the device being controlled.

maccoylton commented 3 years ago

Sorry at the moment I have not implemented schedules. This is tricky to do, and wasn't required for my uses case. On my list of future enhancements but not a priority.