The ecobee-influxdb from bradjc

ecobee-influxdb's People

Contributors

Watchers

ecobee-influxdb's Issues

Start date/time logic seems flawed

I gave this an attempt since I am still on Influx 1.x. Seems that it is trying to pull data that would never exist in the ecobee API, and that I am instead killing their servers for no reason. The db structure appears to properly write to influxdb,

Any thoughts? Note that I am using the Dockerfile for this
docker run -v /mnt/user/appdata/ecobee-influxdb/config.json:/config/config.json --name ecobee -it test/ecobee

Config.json:

{
  "api_key": "hvmcGVoWxxxxxxxxx6JQ",
  "work_dir": "/home/ME/.ecobee_influx_connector",
  "thermostat_id": "52xxxxxxx18,52xxxxxxx00",
  "influx_server": "http://influx.home:8086",
  "influx_database": "ecobee",
  "influx_user": "",
  "influx_password": "",
  "influx_health_check_disabled": false,
  "always_write_weather_as_current": false,
  "write_heat_pump_1": true,
  "write_heat_pump_2": false,
  "write_aux_heat_1": true,
  "write_aux_heat_2": false,
  "write_cool_1": true,
  "write_cool_2": false,
  "write_humidifier": false
}

Log:

End:   0001-01-16
Pin is "xxxx-xxxx"
Press <enter> after authorizing it on https://www.ecobee.com/consumerportal in the menu under 'My Apps'

writing
runtime write good
writing
runtime write good
Start: 0001-01-17
End:   0001-01-31
writing
runtime write good
writing
runtime write good
Start: 0001-02-01
End:   0001-02-15
writing
runtime write good
writing
runtime write good
Start: 0001-02-16
End:   0001-03-02
writing
runtime write good
writing
runtime write good
Start: 0001-03-03
End:   0001-03-17
writing
runtime write good
writing
runtime write good

Recommend Projects