vortec4800 / homebridge-ecobee-away Goto Github PK

I have two ecobees. Is it possible to setup two HomeKit switches for the away mode (for each one) so I can control them separately?

How hard is it to change this plugin to control the HVAC fan. my setup includes an air exchanger that uses the fan from the air handler to exchange. Manually flipping this means I get more fresh air into the house when on.

Right now I have to use the Ecobee interface to control the fan. Automation and Siri control would be super cool.

Hey there :-)

saw the disclaimed limitations, and still installed the plugin. I have an ecobee 3, and an ecobee 4 with multiple sensors.

The switch actually still works - it just sets both thermostats into away mode, whereas I would love for it to be just the upstairs one. The end goal would be to create a simple 'when the last person leaves, set the upstairs thermostat to away' Homekit automation. I can't do that to the downstairs thermostat, as our dog would get extremely hot, ha ;-)

Would love it if you are open utilizing my use case to add a 'by device' type feature.

I'm on a TOU plan and have ecobee setup to keep that in mind for cooling purposes. I have this switch setup so that when the last person leaves, it puts ecobee into "Away" mode, and when the first person returns, it resumes the schedule. For some reason, when returning to normal schedule, if during a TOU time, it will disable TOU for the day, leaving the rest of eco+ operating. This causes more cooling than desired when power costs are high.

Hi,

I moved this plugin to a child bridge because it was slowing down Hombridge service. Every two hours the plugin throws the following error, which forces the child bridge to restart:

/usr/local/lib/node_modules/homebridge-ecobee-away/node_modules/axios/lib/core/createError.js:16
var error = new Error(message);
^
Error: Request failed with status code 500
at createError (/usr/local/lib/node_modules/homebridge-ecobee-away/node_modules/axios/lib/core/createError.js:16:15)
at settle (/usr/local/lib/node_modules/homebridge-ecobee-away/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/homebridge-ecobee-away/node_modules/axios/lib/adapters/http.js:260:11)
at IncomingMessage.emit (node:events:402:35)
at endReadableNT (node:internal/streams/readable:1343:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
[2/1/2022, 9:22:10 AM] [Ecobee Away] Child bridge process ended
[2/1/2022, 9:22:10 AM] [Ecobee Away] Process Ended. Code: 1, Signal: null
[2/1/2022, 9:22:17 AM] [Ecobee Away] Restarting Process...
[2/1/2022, 9:22:18 AM] [Ecobee Away] Launched child bridge with PID 26297
[2/1/2022, 9:22:18 AM] Registering platform 'homebridge-ecobee-away.EcobeeAway'
[2/1/2022, 9:22:18 AM] [Ecobee Away] Loaded homebridge-ecobee-away v1.0.2 child bridge successfully
[2/1/2022, 9:22:18 AM] Loaded 1 cached accessories from cachedAccessories.0EE6DDEA3D5B.
[2/1/2022, 9:22:18 AM] [Ecobee Away] Loading accessory from cache: Ecobee Away
[2/1/2022, 9:22:18 AM] [Ecobee Away] Renewing auth token
[2/1/2022, 9:22:18 AM] Homebridge v1.4.0 (HAP v0.10.0) (Ecobee Away) is running on port 58070.
[2/1/2022, 9:22:19 AM] [Ecobee Away] Restoring existing accessory from cache: Ecobee Away
[2/1/2022, 10:22:19 AM] [Ecobee Away] Renewing auth token