vojtamolda / homebridge-ecobee3-sensors Goto Github PK

Got the plugin set up and running in HomeBridge. In homekit the sensors show in automations but not as accessories. Any idea what I missed?

Hi,

I'm wondering if you can help with the follow issue?

[1/2/2022, 4:06:50 AM] ERROR INITIALIZING PLUGIN homebridge-ecobee3-sensors:
[1/2/2022, 4:06:50 AM] Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/lib/node_modules/homebridge-ecobee3-sensors/node_modules/chalk/source/index.js from /usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js not supported.
Instead change the require of index.js in /usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js to a dynamic import() which is available in all CommonJS modules.
at Object. (/usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js:4:13)
at Plugin.module.exports [as pluginInitializer] (/usr/lib/node_modules/homebridge-ecobee3-sensors/index.js:11:18)
at Plugin.initialize (/usr/lib/node_modules/homebridge/lib/plugin.js:147:21)
at PluginManager.initializePlugin (/usr/lib/node_modules/homebridge/lib/pluginManager.js:91:26)
at PluginManager.initializeInstalledPlugins (/usr/lib/node_modules/homebridge/lib/pluginManager.js:83:24)
at async Server.start (/usr/lib/node_modules/homebridge/lib/server.js:106:9)
[1/2/2022, 4:06:50 AM] ====================

Thanks!

iPhone 6s Plus
iOS 10.2
Homebridge running on an Ubuntu
exclude_thermostat: true

I have an Ecobee3 with just 1 additional sensor. The temperature and occupancy sensor show up fine, and seem to work as expected.

However, the Details section on the first page of the Home app always says '2 accessories not responding' even though it also reports occupancy and temperature of the room correctly.

I deleted the persist folder and restarted homebridge, re-entered the key in MY APPS and it does not change anything.

My thought is that this may because I have exclude_thermostat to true, or because the items have no user changeable status (which may be why ecobee removed them)?

I was looking through this project and found you were using your developer api key for these calls. I was wondering if you maybe move that to the config file and have yours by default but easily allow others to change to their own key if they have one

This use to work in the past.

Any suggestions

[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [My ecobee]
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] Update equipments
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] Cached | Ecobee compCool1
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee compCool1]
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee compCool1] - true
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] Cached | Ecobee fan
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee fan]
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee fan] - true
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee compCool1] - true
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] [Ecobee fan] - true
[8/24/2023, 9:57:07 PM] [Ecobee 3 Sensors] Wait | 30 seconds
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] Update sensors
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [Downstairs]
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [Master Bedroom]
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [Office]
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [My ecobee]
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] Update equipments
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [Ecobee compCool1] - true
[8/24/2023, 9:57:38 PM] [Ecobee 3 Sensors] [Ecobee fan] - true

Not sure how to diagnose.

If I move a sensor to a different room or use them in automation, they disappear from my Home app. Everything else stays, and it even stays in the Homebridge Config UI, yet they don't appear in my Home app again until I reboot the server.

Do you have any suggestions for how I can go about resolving this?

Ecobee has a new thermostat with air quality sensor. It would be great if homebridge-ecobee3-sensors supported the new model . Thanks

Running homebridge on Raspberry Pi. The Ecobee sensor plugin had been working properly up until a few days ago, and now with it in my config, Homeridge crashes with this error:
SyntaxError: Unexpected token e in JSON at position 0
Apr 20 14:00:45 raspberrypi homebridge[25375]: at JSON.parse ()
Apr 20 14:00:45 raspberrypi homebridge[25375]: at EcobeePlatform. (/usr/local/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:87:24)
Apr 20 14:00:45 raspberrypi homebridge[25375]: at IncomingMessage.emit (events.js:327:22)
Apr 20 14:00:45 raspberrypi homebridge[25375]: at endReadableNT (_stream_readable.js:1220:12)
Apr 20 14:00:45 raspberrypi homebridge[25375]: at processTicksAndRejections (internal/process/task_queues.js:84:21)
Apr 20 14:00:45 raspberrypi homebridge[25375]: [4/20/2021, 2:00:45 PM] Got SIGTERM, shutting down Homebridge...

Any ideas?

Thanks,

Tim

With the recent Firmware Version 3.7.0.969 from Ecobee, sensors (Temperature and Occupancy) are exposed to homekit automatically. Only Humidity sensor is not enabled from Ecobee, which this plugin does. It would be great if we have a config option called humidity_only: true, which would disable the temperature and occupancy through this plugin and enable humidity.

From what I've read, the Carrier Cor (corSmart) is essentially a rebranded Ecobee. I was able to get this plugin installed on Homebridge, successfully add the authorization code in my "Apps" on the Cor login page (everything is basically the same as ecobee).. but when launching homebridge, I get
Not supported thermostat | My home (corSmart

I don't have sensors, just trying to get the Cor setup with homebridge. It's the TP-WEM01 Model which doesn't have native Homekit compatibility. The TP-WEM01-A (which came out years later) is what has native compatibility.

Is this something we can tweak to make work, or am I barking up the wrong tree?

After successfully adding the app on ecobee.com, the following is logged and Homebridge restarts:

[12/8/2016, 7:30:17 PM] [homebridge-ecobee3-sensors.Ecobee 3 Sensors] Authorization successful :-)
[12/8/2016, 7:30:17 PM] [homebridge-ecobee3-sensors.Ecobee 3 Sensors] Update sensors
/usr/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:221
if ((this.config.exclude_thermostat === true) && (sensorConfig.type !== 'ecobee3_remote_sensor')) continue
^
TypeError: Cannot read property 'exclude_thermostat' of null
at EcobeePlatform.sensors (/usr/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:221:23)
at EcobeePlatform.<anonymous> (/usr/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:185:16)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
homebridge.service: main process exited, code=exited, status=1/FAILURE
Unit homebridge.service entered failed state.
homebridge.service holdoff time over, scheduling restart.
Stopping Node.js HomeKit Server...

Hello - I'm really enjoying this HomeBridge plugin!

There is one thing I am having issues with: having to re-enter a new authorization code every time I restart Homebridge (when I restart my computer, when the terminal crashes, power loss.. etc.). When I re-launch I get the following message:

[Ecobee] Token has been deauthorized by user. You must re-request authorization. Re-requesting authorization!

Is there any way to set this up as one-time authorization? I've already set-up Homebridge to start up again in any of these conditions, but since there is this authorization step the whole thing is hanging until I get a chance to update it in the ecobee portal.

Thanks!

If you have an early Ecobee3 or SmartSi and want to have unofficial HomeKit support, upvote 👍 this comment.

If your thermostat has the following logo on the box, then it's already HomeKit enabled and you don't need to read any further. Here is a way to check if you don't have the box anymore.

Please, keep in mind that you'll have to permanently run a HomeKit server on a computer (i.e. Raspberry Pi) that's connected to your home network to get HomeKit to work.

I run home bridge. I get code and enter into ecobee. It creates app. All works fine.

I have to reboot system or update so I stop home bridge

I start it back up and it asks me to register again. Is there no way to have it remember the registration???

thanks,

Jeff

...so other developers won't see node_modules/*files as changes!

I am getting this error. I have an Ecobee3 with homekit support but want to get sensor data so using your plugin.

Error: Accessories must be created with a non-empty displayName.
    at new PlatformAccessory (/usr/local/lib/node_modules/homebridge/lib/platformAccessory.js:15:27)
    at EcobeePlatform.sensors (/usr/local/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:235:33)
    at EcobeePlatform.<anonymous> (/usr/local/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:187:16)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

I used your exact sample code. I have about 10 sensors which could be an issue but none have a blank name. Only difference I can see in your examples are that I have a lot more sensors. Unless I have to I would rather not have to deactivate all of them and try 1 x 1

Also after the error when I run it again it thinks its the first run again and I have to deactivate the ecobee app and add it again with the new code.

Currently, the plugin asks for full read-write access (scope=smartWrite) during the Ecobee API authorization process. I don't think this is necessary since we never issue any POST request that would change anything on the thermostat. I think some people may not be willing to grant the write access It's easy to imagine Terminator-like scenario where some crazy piece of software is literally messing with their house.

At the moement all the functionality is a bit "dumb" and the plugin merely forwards the values to be displayed in HomeKit. Read-only privileges (scope=smartRead) should be enough to get the sensor values and we should take advantage of it to make things a bit more secure.

More details about the authorization API can be found in the documentation.

Got an Ecobee 4 and it says Not Supported. Its basically a 3 with alexa built in

Currently my homebridge log gets about a dozen lines from the ecobee every 30 seconds. This makes it tricky to find the actual useful information in the log. It would be nice if I could set the plugin to only log errors.

Is Anybody Supporting this? Can We Add Ecobee4? Thanx

After installing the plugin, I am never able to see a pin that I can enter on the ecobee site to authorize homebridge.

I am getting this in the logs. Using the readme default config JSON object.

[1/21/2021, 5:32:31 PM] [Ecobee] Update sensors
[1/21/2021, 5:32:31 PM] [Ecobee] Not supported thermostat | Downstairs (nikeSmart)

how can i change the read out of this info to F instead of C?

found some references to it in the code but unfamiliar with how to change it to read Fahrenheit stats.

THANKS for any assistance!

First thank you for the plug-in. Just installed and happy to see my sensors in HomeKit now. However I noticed when I changed the "update_frequency": 30 value to something else (I can live with 5+ min updates so changed to 300 and rebooted) that the plug-in still is polling ever 30 seconds per the log ("wait | 30 seconds").

I'm not a coder but I see in the code (platform.js) the following line of code:
this.updateFrequency = this.config.update_frequency || 30;

Is the JSON value (update_frequency) not getting correctly read by the program?

Updated (added JSON & log capture):

JSON:
"exclude_equipment_sensors": false,
"update_frequency": 600,
"log_level": 1

LOG
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [Main Floor]
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [Master Bedroom]
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [Basement]
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [My ecobee]
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] Update equipments
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [Ecobee auxHeat1] - false
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] [Ecobee fan] - false
[28/01/2024, 13:18:09] [Ecobee 3 Sensors] Wait | 30 seconds
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] Update sensors
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [Main Floor]
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [Master Bedroom]
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [Basement]
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [My ecobee]
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] Update equipments
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [Ecobee auxHeat1] - false
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] [Ecobee fan] - false
[28/01/2024, 13:18:39] [Ecobee 3 Sensors] Wait | 30 seconds
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] Update sensors
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [Main Floor]
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [Master Bedroom]
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [Basement]
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [My ecobee]
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] Update equipments
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [Ecobee auxHeat1] - false
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] [Ecobee fan] - false
[28/01/2024, 13:19:09] [Ecobee 3 Sensors] Wait | 30 seconds

Thanks,
David

i contacted ecobee a few months ago about fixing their homekit implementation to show the sensors as seperate accessories, but they've yet to push an update. so, this plugin is a great idea.

however: the README file mentions bluetooth/arduino in a few places, which leads me to suspect that there was a cut-and-paste that wasn't entirely reviewed!

best,

/mtr

I have the latest Ecobee and needed to add the vulcanSmart model to get it to work

Added the following to platform.js

  for (var thermostatConfig of reply.thermostatList) {                                                                                                                                                                                                                     
    if ((thermostatConfig.modelNumber != 'vulcanSmart') && (thermostatConfig.modelNumber != 'athenaSmart') && (thermostatConfig.modelNumber != 'apolloSmart') && (thermostatConfig.modelNumber != 'nikeSmart')) {                                                          
      this.log.info("Not supported thermostat | " + thermostatConfig.name + " (" + thermostatConfig.modelNumber + ")");                                                                                                                                                    
      continue                                                                                                                                                                                                                                                             
    

Anyway to expose ventilator [ERV] state to homekit with this plugin?

I tried running Homebridge without a config but it appears there is some issue with the plugin since it can't even get past loading the plugin. I would appreciate fixing this fast, due to it totally having shut down my Homebridge.

Load homebridge-ecobee3-sensors.Ecobee 3 Sensors
/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:21
  this.excludeSensors = config.exclude_sensors || false;
                              ^
TypeError: Cannot read property 'exclude_sensors' of null
    at new EcobeePlatform (/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge-ecobee3-sensors/source/platform.js:21:31)
    at Server._loadDynamicPlatforms (/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge/lib/server.js:315:30)
    at Server.run (/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge/lib/server.js:82:8)
    at module.exports (/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/Users/applegeek/.nvm/versions/node/v5.9.1/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:142:18)
    at node.js:939:3

I am getting the following error after instalation..

[12/12/2021, 8:01:27 AM] ====================
[12/12/2021, 8:01:27 AM] ERROR INITIALIZING PLUGIN homebridge-ecobee3-sensors:
[12/12/2021, 8:01:27 AM] Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/lib/node_modules/homebridge-ecobee3-sensors/node_modules/chalk/source/index.js from /usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js not supported.
Instead change the require of index.js in /usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js to a dynamic import() which is available in all CommonJS modules.
at Object. (/usr/lib/node_modules/homebridge-ecobee3-sensors/source/sensor.js:4:13)
at Plugin.module.exports [as pluginInitializer] (/usr/lib/node_modules/homebridge-ecobee3-sensors/index.js:11:18)
at Plugin.initialize (/usr/lib/node_modules/homebridge/lib/plugin.js:147:21)
at PluginManager.initializePlugin (/usr/lib/node_modules/homebridge/lib/pluginManager.js:91:26)
at PluginManager.initializeInstalledPlugins (/usr/lib/node_modules/homebridge/lib/pluginManager.js:83:24)
at async Server.start (/usr/lib/node_modules/homebridge/lib/server.js:106:9)
[12/12/2021, 8:01:27 AM] ====================

Post a link with some screenshots and try to attract users, testers & possibly contributors from this Slack channel

Just wondering if you can expose the AUX setting for the Ecobee? I would like to be able to have a trigger to AUX function when I have a power outage and not use my heat pump. HomeKit does not show it.

Guess you would need to expose the HEAT, COOL, and AUTO as well even though HomeKit does.

For some reason ecobee does not expose humidity separately in HomeKit as it does temperature, motion, and occupancy.

This prevents the Home app UI from displaying the humidity under the temperature.

This very useful homebridge plugin resolves that for my older thermostats but not my newer ones.

Is it possible to add support for the newer thermostats if even just for humidity (which I believe is the only item ecobee hasn’t addressed since this plugin was created)?

Would it be possible to add support for newer sensors?
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Not-supported measurement type | airQualityAccuracy
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Not-supported measurement type | airQuality
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Not-supported measurement type | vocPPM
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Not-supported measurement type | co2PPM
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Not-supported measurement type | airPressure
[11/27/2022, 11:20:17 AM] [Ecobee 3 Sensors] [My ecobee] Initialized | 531657384941

So, I would really like my house humidity to show up as a sensor, can you help me with the configuration I would need in config.json for this? Otherwise, I don’t want to add anything else.

Seems I'll get it working, authorize with Ecobee, and then after a few hours I get the "waiting for user to authorize application" message in the log again, complete with a new authorization code. Is this expected?

Related but not specifically- Has anyone created their own ecobee sensors using an Esp8266 and bme280 that somehow integrates with ecobee? I did a quick (really quick) google and didn’t see anything.

I am trying to get these two contact accessories to not show up in homebridge. I cannot figure out how to remove/stop them from appearing... I have excluded thermostat and equipment sensors but they still show up...

"platform": "Ecobee 3 Sensors",
"name": "Ecobee",
"exclude_sensors": true,
"exclude_humidity_sensors": false,
"exclude_occupancy_sensors": false,
"exclude_temperature_sensors": false,
"exclude_thermostat": true,
"exclude_equipment_sensors": true,
"update_frequency": 30,
"log_level": 1

In iOS 16, I can not seem to find a way to show the sensors as tiles. Is it possible to report sensors as a thermostat so that there is a tile? I am assuming this would cause issue with actual thermostats, and probably cause HomeKit errors if I try and adjust the temp. But if I could see the temp at a glance of a tile on my main page that would be great.

I have cleaned out persist, changed username and removed my Homebridge accessory from Home and restarted homebridge. When I try to add the accessory again Home says "Couldn't add Homebridge" and I get the following in the log:

[12/8/2016, 7:52:17 PM] Homebridge is running on port 51826.
[12/8/2016, 7:52:17 PM] [Ecobee] These are the steps authorize this application to access your Ecobee 3:
[12/8/2016, 7:52:17 PM] [Ecobee]   1. Go to https://www.ecobee.com/home/ecobeeLogin.jsp
[12/8/2016, 7:52:17 PM] [Ecobee]   2. Login to your thermostat console
[12/8/2016, 7:52:17 PM] [Ecobee]   3. Select 'MY APPS' from the menu on the top right.
[12/8/2016, 7:52:17 PM] [Ecobee]   4. Click 'Add Application'
[12/8/2016, 7:52:17 PM] [Ecobee]   5. Enter the following authorization code:
[12/8/2016, 7:52:17 PM] [Ecobee]    +------+
[12/8/2016, 7:52:17 PM] [Ecobee]    ¦ x23e ¦
[12/8/2016, 7:52:17 PM] [Ecobee]    +------+
[12/8/2016, 7:52:17 PM] [Ecobee]   6. Wait a moment.
[12/8/2016, 7:52:18 PM] [Ecobee] Waiting for user to authorize application. Retrying in 30 seconds.
[12/8/2016, 7:52:49 PM] [Ecobee] Authorization successful :-)
[12/8/2016, 7:52:49 PM] [Ecobee] Update sensors
[12/8/2016, 7:52:49 PM] [Ecobee] Create | Great Room | QRYQ
[12/8/2016, 7:52:50 PM] [Ecobee] [Great Room] Initialized | QRYQ
[12/8/2016, 7:52:50 PM] [Ecobee] [Great Room] Vacant | 21.3°C
[12/8/2016, 7:52:50 PM] [Ecobee] Create | Family Room | K52Q
[12/8/2016, 7:52:50 PM] [Ecobee] [Family Room] Initialized | K52Q
[12/8/2016, 7:52:50 PM] [Ecobee] [Family Room] Vacant | 22.1°C
[12/8/2016, 7:52:50 PM] [Ecobee] Create | Bedroom | undefined
[12/8/2016, 7:52:50 PM] [Ecobee] [Bedroom] Initialized | undefined
[12/8/2016, 7:52:50 PM] [Ecobee] [Bedroom] Vacant | 37% | 20.9°C
[12/8/2016, 7:52:50 PM] [Ecobee] Create | Guest Bedroom | MG4Y
[12/8/2016, 7:52:50 PM] [Ecobee] [Guest Bedroom] Initialized | MG4Y
[12/8/2016, 7:52:50 PM] [Ecobee] [Guest Bedroom] Vacant | 22.5°C
[12/8/2016, 7:52:50 PM] [Ecobee] [Bedroom] Vacant | 34% | 22.1°C
[12/8/2016, 7:52:50 PM] [Ecobee] Wait | 30 seconds
[12/8/2016, 7:52:50 PM] [Ecobee] Tokens
Fri, 09 Dec 2016 00:53:04 GMT EventedHTTPServer [::ffff:192.168.1.71] New connection from client
Fri, 09 Dec 2016 00:53:04 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP server listening on port 33227
Fri, 09 Dec 2016 00:53:04 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pair-setup
Fri, 09 Dec 2016 00:53:04 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pair-setup
Fri, 09 Dec 2016 00:53:04 GMT HAPServer [CD:00:2D:F3:CE:32] Pair step 1/5
Fri, 09 Dec 2016 00:53:06 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:09 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pair-setup
Fri, 09 Dec 2016 00:53:09 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pair-setup
Fri, 09 Dec 2016 00:53:09 GMT HAPServer [CD:00:2D:F3:CE:32] Pair step 2/5
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pair-setup
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pair-setup
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Pair step 3/5
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Pair step 4/5
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Pair step 5/5
Fri, 09 Dec 2016 00:53:11 GMT Accessory [Homebridge] Paired with client 868C2787-2FEA-4BB5-84CA-3B5B32AA522F
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] Client connection closed
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP connection was closed
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP server was closed
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] New connection from client
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP server listening on port 37815
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pair-verify
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pair-verify
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Pair verify step 1/2
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pair-verify
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pair-verify
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Pair verify step 2/2
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] Client 868C2787-2FEA-4BB5-84CA-3B5B32AA522F verification complete
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /accessories
Fri, 09 Dec 2016 00:53:11 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: GET /accessories
Fri, 09 Dec 2016 00:53:11 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:12 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP request: /pairings
Fri, 09 Dec 2016 00:53:12 GMT HAPServer [CD:00:2D:F3:CE:32] HAP Request: POST /pairings
Fri, 09 Dec 2016 00:53:12 GMT HAPServer [CD:00:2D:F3:CE:32] Removing pairing info for client
Fri, 09 Dec 2016 00:53:12 GMT Accessory [Homebridge] Unpairing with client 868C2787-2FEA-4BB5-84CA-3B5B32AA522F
Fri, 09 Dec 2016 00:53:12 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP Response is finished
Fri, 09 Dec 2016 00:53:12 GMT EventedHTTPServer [::ffff:192.168.1.71] Client connection closed
Fri, 09 Dec 2016 00:53:12 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP connection was closed
Fri, 09 Dec 2016 00:53:12 GMT EventedHTTPServer [::ffff:192.168.1.71] HTTP server was closed