pjczx / homebridge-thermostat Goto Github PK

Hey,

Using your code as a base I've gotten the HomeKit UI to update to say cooling or heating using setCharacteristic(Characteristic.CurrentHeatingCoolingState, value)

The problem is it only makes a difference to the temperature wording, not the Off/Heat/Cool/Auto mode switch.

Do you have any insight into this or how to fix it? I assume you see the same thing?

Thanks!

Luke

When using a Home Assistant server, coupled with homebridge-homeassistant, this thermostat accessory doesn't work. To provide a compatibility layer, I created a proxy between your thermostat accessory and the API in Home Assistant.

https://github.com/jharmn/homebridge-homeassistant-thermostat
https://hub.docker.com/r/jharmn/docker-homebridge-homeassistant-thermostat/builds/

Feel free to close the issue and ignore, I just thought you might want to share the option for Home Assistant users.

Hi there,

I've had a lot of fun with this project, however, I am having a problem both with this plugin: every now and then, when I open the Home app, all devices appear as No Response. I believe other people have had similar problems with this plugin #17). All it takes is closing and re-opening the app for the messages to reset.

This problem is becoming increasingly annoying however, and this is why I am seeking help. Note that this problem only occurs when using this plugin; furthermore, when this plugin is isolated on my test "Home" with no other plugins, the issue does not occur. Thus, it seems the problem only occurs when in the same "Home" as multiple other accessories, and, at that, only every now and then (I'd say 1 in 5 times or if I haven't opened the Home app in a few minutes).

After running Homebridge in debug mode (DEBUG=* homebridge -D), something strange happens. Whenever I get the No Response error in the Home app, the following 5 lines always appear at the end of the debug log (where 192.168.1.36 is the local IP of my iPhone):

  EventedHTTPServer [::ffff:192.168.1.36] HTTP Response is finished +3ms
  EventedHTTPServer [::ffff:192.168.1.36] Writing pending HTTP event data +1ms
  EventedHTTPServer [::ffff:192.168.1.36] Client connection closed +113ms
  EventedHTTPServer [::ffff:192.168.1.36] HTTP connection was closed +2ms
  EventedHTTPServer [::ffff:192.168.1.36] HTTP server was closed +1ms

These lines never appear in this order anywhere else as long as there is no No Response error (the first 2 lines appear frequently by themselves elsewhere, but the last 2/3 only appear during this error). Any ideas on what might be causing the plugin to make this happen?

Thank you in advance for your help,

Kind regards, Tom

README States:

• GET /targetHeatingCoolingState/{INT_VALUE_0_TO_3}

But index.js appears to accept:

action = "/off";
action = "/comfort"; // Looks like heat
action = "/auto";
action = "/no-frost"; // Looks like cool

Which is correct?

Hello,
First of all thank you for the plugin.
After installing the plugin I have an error in the log files
See log
Can you help me?

{ Error: connect EALREADY 192.168.1.244:3310 - Local (192.168.1.241:48890)
Aug 30 13:00:15 sdomotica homebridge[3810]: at Object._errnoException (util.js:1003:13)
Aug 30 13:00:15 sdomotica homebridge[3810]: at _exceptionWithHostPort (util.js:1024:20)
Aug 30 13:00:15 sdomotica homebridge[3810]: at internalConnect (net.js:967:16)
Aug 30 13:00:15 sdomotica homebridge[3810]: at net.js:1067:9
Aug 30 13:00:15 sdomotica homebridge[3810]: at process._tickCallback (internal/process/next_tick.js:150:11)
Aug 30 13:00:15 sdomotica homebridge[3810]: at Function.Module.runMain (module.js:703:11)
Aug 30 13:00:15 sdomotica homebridge[3810]: at startup (bootstrap_node.js:193:16)
Aug 30 13:00:15 sdomotica homebridge[3810]: at bootstrap_node.js:617:3
Aug 30 13:00:15 sdomotica homebridge[3810]: errno: 'EALREADY',
Aug 30 13:00:15 sdomotica homebridge[3810]: code: 'EALREADY',
Aug 30 13:00:15 sdomotica homebridge[3810]: syscall: 'connect',
Aug 30 13:00:15 sdomotica homebridge[3810]: address: '192.168.1.244',
Aug 30 13:00:15 sdomotica homebridge[3810]: port: 3310 }
Aug 30 13:00:15 sdomotica homebridge[3810]: { Error: connect EALREADY 192.168.1.244:3310 - Local (192.168.1.241:48890)
Aug 30 13:00:15 sdomotica homebridge[3810]: at Object._errnoException (util.js:1003:13)
Aug 30 13:00:15 sdomotica homebridge[3810]: at _exceptionWithHostPort (util.js:1024:20)
Aug 30 13:00:15 sdomotica homebridge[3810]: at internalConnect (net.js:967:16)
Aug 30 13:00:15 sdomotica homebridge[3810]: at net.js:1067:9
Aug 30 13:00:15 sdomotica homebridge[3810]: at process._tickCallback (internal/process/next_tick.js:150:11)
Aug 30 13:00:15 sdomotica homebridge[3810]: at Function.Module.runMain (module.js:703:11)
Aug 30 13:00:15 sdomotica homebridge[3810]: at startup (bootstrap_node.js:193:16)
Aug 30 13:00:15 sdomotica homebridge[3810]: at bootstrap_node.js:617:3
Aug 30 13:00:15 sdomotica homebridge[3810]: errno: 'EALREADY',
Aug 30 13:00:15 sdomotica homebridge[3810]: code: 'EALREADY',
Aug 30 13:00:15 sdomotica homebridge[3810]: syscall: 'connect',
Aug 30 13:00:15 sdomotica homebridge[3810]: address: '192.168.1.244',
Aug 30 13:00:15 sdomotica homebridge[3810]: port: 3310 }

Hi, thanks for authorising my pull request. However, it looks like you overwrote it:

Note the Merge branch 'master' of https://github.com/PJCzx/homebridge-thermostat

You can see this simply if you compare my README with yours. But this also applies to the index.js. Shall I make a new pull request?

Best, Tom

First of all great plugin, but I have a few things I would like to have included :) First of all the humidity seems to not be passing through to homekit. I don't see the value showing up while it is included in the script output. Below the current output. It also returns the air pressure which can be ignored.

{ "targetTemperature": 19, "temperature": 20, "humidity": 48.4, "pressure": 104546 }

Currently for one thermostat there are at least four exactly the same requests.

Below log:
[19.02.2019, 18:29:11] [Thermostat] getTargetHeatingCoolingState from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getTargetRelativeHumidity: 0.5
[19.02.2019, 18:29:11] [Thermostat] getTemperatureDisplayUnits: 0
[19.02.2019, 18:29:11] [Thermostat] getHeatingThresholdTemperature : 25
[19.02.2019, 18:29:11] [Thermostat] getCurrentTemperature from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getCurrentHeatingCoolingState from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getTargetTemperature from: http://localhost:9010/REST/homekit/status

So in above example there are four calls to http://localhost:9010/REST/homekit/statusw which is very inefficient

First of all great plugin, but I have a few things I would like to have included :)

It would be great if I could just point to a local script instead of an URL for this to work

Hey

Should the "heatOnly" Option remove the "COOL" option in Home App?
If yes it looks like its not working.

TargetTemperature, CurrentTemperature, TargetHeatingCoolingState, and CurrentHeatingCoolingState values are being logged properly to the console (with correct values), but the actual numbers in the Home app are not showing up correctly.

I'm still able to control my Proliphix ethernet thermostat with this if I monitor the screen on it while I do so (or watch the console output), but the reported values in the Home app are significantly off.

For example, I see in the console that the queried temperature from the thermostat is 72.0 degrees Fahrenheit, but the Home app reports 162 degrees Fahrenheit. The numbers displayed in the interval when sliding to adjust also are affected (I've set values 62.0 and 86.0 in my config.json for minTemp and maxTemp, but in the Home app they range from 144 to 187). Sliding to adjust the temperature still sends the correct values to the console, however (I just can't accurately tell what they are without checking). temperatureDisplayUnits in config.json is set to 1 (without quotes).

I am running the latest build of iOS 13 (the numbers are the same across all my devices, however, including a HomePod, iPad, and a couple Macs). homebridge-thermostat itself is running on Ubuntu 18.

Thanks in advance, and happy to help debug this!

Is there any way to pass username and password to url when connecting to accessory?
I found username and password params in httpReques but I don't know how to pass them.
Does httpRequest function is used anywhere?

Hello,

I think it would be great if we can turne on/off thermostat devices with just one click in Home App. It has been done in the homebridge-daikin-local plug-in, and working very well for me :
(cbrandlehner/homebridge-daikin-local#15)

The way it has been done in this plugin was adding this characteristic :

    this.heaterCoolerService
      .getCharacteristic(Characteristic.Active)
      .on('get', this.getActive.bind(this))
      .on('set', this.setActive.bind(this)); 

With the 'setActive' action, the thermostat is powered up / powered down with just a click on the icon in Home app.

Do you think it's possible to implement it?

Regards

Id like to use your plugin, but i'd like to know if it's possible to overide the 38°C?

SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse (:null:null)
at Thermostat. (/usr/local/lib/node_modules/homebridge-thermostat/index.js:93:27)
at Request._callback (/usr/local/lib/node_modules/homebridge-thermostat/index.js:65:15)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-thermostat/node_modules/request/request.js:185:22)
at Request.emit (events.js:198:13)
at Request. (/usr/local/lib/node_modules/homebridge-thermostat/node_modules/request/request.js:1161:10)
at Request.emit (events.js:198:13)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-thermostat/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:286:20)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)

My thermostat does not have a humidity sensor. Is there something I can return for the humidity value to make it ignore it?

Hi, I have this working with my home thermostat and it is great, but my thermostat only has temperature control, so is it possible to have the Home App just control temp and not humidity and mode?

I have a a Proliphix Thermostat that has an http API and would like to see if this will work with it. Do you have any documentation on this project?

Good afternoon!
I really liked your plugin, I apologize for my English.
I can not understand in any way, I plan to use php to process the values received from the plugin, but for the GET request in the address bar there should be a "?" and in your example I see / targetTemperature / {FLOAT_VALUE} tell me how to get this value in my PHP script?

if headonly = true, maybe i want to have the following:

off - boiler is off permanently
on - boiler is allways on
auto - based on temperature threshold if currTemp < targetTemp - start heating, if currTemp > targetTemp - stop heating

update code:

if (this.heatOnly) {
this.service.getCharacteristic(Characteristic.TargetHeatingCoolingState)
.setProps({
minValue: 0,
maxValue: 3, < 0...3
validValues: [0,1,3] <<< add 3, ignore 2 (cooling)
});

Thank U. I'm new here, and i have setup my AC to HomeKit this awesome plugin successfully. And i want to know more about the thermostat in homeKit, but it's seem to be ambiguous in develop document. so...i am here to ask for help...

CurrentHeatingCoolingState is a read only Characteristic in HAP-NodeJS, so the setCurrentHeatingCoolingState entry doesn't really serve a purpose

Hi,
Nice job. Can you please make this also compatible with Dantherm Units?
I would like only control my Fan speed (Register 40325)
Forwarded THX!
Dantherm UVC Controller - Modbus TCP IP HCC2 HCV300400500700.pdf

Current temperature value displayed in HomeKit only displays whole number temperature values by rounding down I.e 22.8DegC is displayed as 22.0DegC.

Hi, thank u for uploading. I have a nodejs server running on raspberry pi and i want the homekit to send targetTemperature request and get the data from it.I have added app.get route('/status'... ,but homebridge says it doesnt get any data. I have copied the JSON body what i should return on /status from your readme ,but it shows this error. Any idea what im doing wrong?

Thanks,
Levi

First of all great plugin, but I have a few things I would like to have included :)

Homekit has the option to set the mode to Off, Heating, Cooling or Automatic. It would be great if I could set this through homebridge-thermostat. This way I can make my script decide what to do with the targetTemperature. This also has the added benefit of the targetTemperature being displayed in the status text within homekit.

Hi,
I'm pleased with your plugin, but the pollInterval doesn't seem to work.

Thanks.

I'm getting a "no response" in iOS home app. Logs are showing that my API is correctly returning all the values.

First of all great plugin, but I have a few things I would like to have included :)

Homekit seems to have the option to indicate if the heating is actually running based on the targetTemperature and temperature. I have this information and can also supply it to homebridge-thermostat. It would be great if this was added.

Not really an issue, but I've put together https://github.com/SupraJames/homebridge-heatmiser in the hope that someone finds it useful. It's a server based on your fake.js which implements the API for heatmiser thermostats, using command line calls to https://github.com/thoukydides/heatmiser-wifi.

Hi,

I am trying to use this project with the Fake.js setup with x2 Raspberry pi's; one with Homebridge (192.168.0.150) and the other pi running the fake.js (192.168.0.160), but am not getting any communication between the two.

Is this an issue with my setup somewhere or an issue with the code?
Homebridge is configured with the following and has a Thermostat appearing in Homekit

        "accessories": [{
                "accessory": "Thermostat",
                "name": "Thermostat",
                "apiroute": "http://192.168.0.160:12000"
        }]

The other pi has the fake.js running with the only change being the port number, as follows:

var server = app.listen(12000, function () {
  var host = server.address().address;
  var port = server.address().port;
  console.log('Global : app listening at', host, port);
});

The fake.js prints the following when executing: Global : app listening at :: 12000 - which doesn't seem to specify a host prior to the port, but not sure if this is normal.

I can't see any other configuration/setup I am missing, could this be a code issue?

Thanks
James

I found that when the humidity reaches higher than 31 percent the thermostat device in the home kit app shows up as unresponsive. Once I lower it back down it begins to work again. Looks like everything outside the the plugin is working properly.

I have a Stelpro STZW402+ thermostat and was wondering if I can use this pluggin?

From the documentation of the device (http://www.stelpro.com/sites/default/files/fr-CA/guide_utilisateur/INS_STZW402_1215_EN_0.pdf)

Z-Wave Association
The Z-Wave Association Command Class is supported by the thermostat.
The thermostat supports the lifeline as Group1 and only one Node Id is supported in this group (the
Z-Wave controller).
The following reports are sent via the Lifeline :

• Basic Report
• Device Reset Locally Notification
• Thermostat Mode Report
• Thermostat Setpoint Report
• Sensor Multilevel Report
• Thermostat Operating State Report

Z-Wave Basic command class
The Z-Wave Basic command class is supported by the thermostat in the following way:
To trigger the Eco mode on the thermostat: Send it a Basic SET (0x00) command (Energy Saving Mode)
To trigger the Comfort mode on the thermostat: Send it a Basic SET (0xFF) command (Comfort Mode)

I set this all up over a year ago - but at some point something broke - I could no longer use Siri to set the desired temperature of my heating.

I found today that there is a difference in how Siri and the Home app work. On my iPhone running iOS 12.1.2 I can use the Home app to set the temperature and it works fine:

Jan 16 20:13:40 smartie homebridge[20463]: Wed, 16 Jan 2019 20:13:40 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics
Jan 16 20:13:40 smartie homebridge[20463]: Wed, 16 Jan 2019 20:13:40 GMT Accessory [Homebridge] Processing characteristic set: [{"aid":17,"iid":13,"value":21}]
Jan 16 20:13:40 smartie homebridge[20463]: Wed, 16 Jan 2019 20:13:40 GMT Accessory [Homebridge] Setting Characteristic "Target Temperature" to value 21
Jan 16 20:13:40 smartie homebridge[20463]: [2019-1-16 20:13:40] [Heatmiser] setTargetTemperature from: http://localhost:4321/targetTemperature/21
Jan 16 20:13:40 smartie homebridge[20463]: [2019-1-16 20:13:40] [Heatmiser] response success

However, if I ask Siri to 'set the temperature to 21 degrees' then HomeKit seems to use a different Characteristic, which is not implemented:

Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics
Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT Accessory [Homebridge] Processing characteristic set: [{"aid":17,"iid":17,"value":5}]
Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT Accessory [Homebridge] Setting Characteristic "Heating Threshold Temperature" to value 5
Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT EventedHTTPServer [::ffff:192.168.100.143] Sending HTTP event '17.17' with data: {"characteristics":[{"aid":17,"iid":17,"value":5}]}
Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT EventedHTTPServer [::ffff:192.168.100.176] Muting event '17.17' notification for this connection since it originated here.
Jan 16 19:54:15 smartie homebridge[476]: Wed, 16 Jan 2019 19:54:15 GMT EventedHTTPServer [::ffff:192.168.100.176] HTTP Response is finished

So, short story, Home app uses "Target Temperature" and Siri uses "Heating Threshold Temperature".

I have no idea when this change, presumably in iOS, occurred. Editing index.js for homebridge-thermostat and commenting out the following lines fixes the issue:

                this.service
                        .getCharacteristic(Characteristic.HeatingThresholdTemperature)
                        .on('get', this.getHeatingThresholdTemperature.bind(this));

We then don't register this characteristic with HomeKit, and it doesn't get called. Siri starts to work again.

I'm opening this as an issue, I think the simple fix would be just to delete these lines but don't want to break anything.

I'm trying to get this hooked up to an Infinitude implementation to gain control of my Bryant thermostat. I've got Infinitude up and running (which gives me local web-based control of the thermostat), but I'm pretty new to this and I'm not sure how to set up the API call to get it working.

I tried to look at the Heatmiser API example but I'm having trouble translating that to my specific implementation. Do you have any other examples I could look at? Or any experience with getting it hooked up with Infinitude?

Sorry for the newbie question, but any help would be greatly appreciated!
Guthrie

Hi,

How can add a dummy thermostat in Homebridge? I want use it to set the target and use rules in EVE app

Hi, I've been struggling with this for hours. I wrote custom software to control the heating/cooling in our home. It was simple to implement the homebridge-thermostat HTTP API in my code, so I did that:

{"targetHeatingCoolingState":3,"targetTemperature":22.77777777777778,"currentHeatingCoolingState":0,"currentTemperature":23.059999999999995,"targetRelativeHumidity":30,"currentRelativeHumidity":30}

With Homebridge 0.x, I was able to set up homebridge-thermostat using the following settings:

 "accessories": [
        {
            "accessory": "Thermostat",
            "name": "Nursery Thermostat",
            "apiroute": "http://127.0.0.1:9269/api/nursery",
            "temperatureDisplayUnits": 1,
            "minTemp": 19.444444444,
            "maxTemp": 25.555555556
        },
        {
            "accessory": "Thermostat",
            "name": "Bedroom Thermostat",
            "apiroute": "http://127.0.0.1:9269/api/bedroom",
            "temperatureDisplayUnits": 1,
            "minTemp": 19.444444444,
            "maxTemp": 25.555555556
        },
        {
            "accessory": "Thermostat",
            "name": "Living Room Thermostat",
            "apiroute": "http://127.0.0.1:9269/api/living-room",
            "temperatureDisplayUnits": 1,
            "minTemp": 19.444444444,
            "maxTemp": 25.555555556
        },
        {
            "accessory": "Thermostat",
            "name": "Office Thermostat",
            "apiroute": "http://127.0.0.1:9269/api/office",
            "temperatureDisplayUnits": 1,
            "minTemp": 19.444444444,
            "maxTemp": 25.555555556
        }
    ],

This kinda worked. At first, all 4 accessories showed the proper temp and state, but said No response below the temperature. Sometimes, inexplicably, the No response would go away, and it would say Set to 74º or whatever. My wife, who is also a member of this HomeKit home, also saw the same behavior. We were happy, though confused about the No response.

However, a few hours later, the accessories stopped working on my phone. Then they stopped working on her phone. Then, no matter what I tried – restarting homebridge, re-pairing – it never worked again.

After poking around the Homebridge forums, I saw that Homebridge 1.0 was out, and it claimed to fix some issues with "No response" and multi-user homes. So I upgraded to Homebridge 1.1. Unfortunately this did not help. In fact, now I can't even pair Homebridge with my Home at all. I've tried everything they suggest – wiping the persist directory, etc. It turns out I can only get pairing to work if I remove the homebridge-thermostat accessories from config.json.

Here's what homebridge debug logging says when I try pairing with homebridge-thermostat accessories:

  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /pair-setup +82ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: POST /pair-setup +1s
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair step 2/5 +1ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +1s
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /pair-setup +9ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: POST /pair-setup +1s
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair step 3/5 +2ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair step 4/5 +7ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair step 5/5 +143ms
  HAP-NodeJS:Accessory [Homebridge A854] Paired with client FB7C4E9B-6733-44AB-8CA1-B1B83C487B6C +3m
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +233ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] Client connection closed +11ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP connection was closed +3ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP server was closed +0ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] New connection from client +3ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP server listening on port 44213 +1ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /pair-verify +3ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: POST /pair-verify +104ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair verify step 1/2 +2ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +103ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /pair-verify +9ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: POST /pair-verify +109ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pair verify step 2/2 +2ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Client FB7C4E9B-6733-44AB-8CA1-B1B83C487B6C verification complete +84ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +90ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /accessories +8ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: GET /accessories +11ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +9ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP request: /pairings +25ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] HAP Request: POST /pairings +35ms
  HAP-NodeJS:HAPServer [0E:A1:1A:10:A8:54] Pairings: successfully executed REMOVE_PAIRING +6ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP Response is finished +8ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] Client connection closed +12ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP connection was closed +1ms
  HAP-NodeJS:EventedHTTPServer [::ffff:192.168.0.165] HTTP server was closed +1ms

I found an ancient Homebridge issue homebridge/homebridge#1245 (comment) where the authors claim that a plugin is "malfunctioning" and causing pairing to fail. This makes sense to me, as pairing seems to work, but then the Home app decides it "cannot connect" after getting the accessory list.

Any advice? Am I using the wrong settings?

Api expectations should be corrected

Would be nice to add Honeywell home t series thermostats. Or a guide if this would work with them.