ECONNRESET || No HomeKit Notifications on Status change

[fatal1010]

Checking the logs, I see the following, is this a concern and what could be the cause?

0|homebrid | [11/17/2019, 00:54:28] [Garage Door] FetchError: request to https://api.myqdevice.com/api/v5/accounts/<Account_ID>/devices/<Device_ID> failed, reason: read ECONNRESET
0|homebrid | at ClientRequest. (/usr/lib/node_modules/homebridge-chamberlain/node_modules/node-fetch/index.js:133:11)
0|homebrid | at ClientRequest.emit (events.js:210:5)
0|homebrid | at TLSSocket.socketErrorListener (_http_client.js:406:9)
0|homebrid | at TLSSocket.emit (events.js:210:5)
0|homebrid | at emitErrorNT (internal/streams/destroy.js:92:8)
0|homebrid | at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
0|homebrid | at processTicksAndRejections (internal/process/task_queues.js:80:21) {
0|homebrid | name: 'FetchError',
0|homebrid | message: 'request to https://api.myqdevice.com/api/v5/accounts/<Account_ID>/devices/<Device_ID> failed, reason: read ECONNRESET',
0|homebrid | type: 'system',
0|homebrid | errno: 'ECONNRESET',
0|homebrid | code: 'ECONNRESET'
0|homebrid | }

Info

iOS Version: 13.2.2
Plugin Version: latest
HomeBridge Version: latest
Node/Npm Version: 12.13 / 6.12

Also, this is probably related to iOS 13 (HomeKit just acting weird), but, I don't get consistent notifications on my phone when garage opens/closes...I sometimes randomly get an Open or Close status, but, very very sporadic.

Let me know.

[iRayanKhan]

Is there a chance you may have mistyped your login info?

[fatal1010]

No, this is randomly scattered in the error log file, sometimes once a day, sometimes multiple times a day ... the std output has the normal garage state change log lines in it and the Home app opens/closes the garage as expected.

Don't know if this is an issue or not, just thought I'd point it out to you that my error log has these entries.

As a side note, I don't receive any Home app alerts anymore though (or, again, very randomly sometimes that the garage has opened or closed), but I think it is related to iOS 13 (was working well in iOS 12).

[iRayanKhan]

Is there a chance you may have enabled "DND" for the Home App? I did that once for messages on accident. In Settings > Notifications > Home it should show. It seems like since it's scattered the request just fails. Issue #51 had a similar issue, and an update fixed it. I'll keep track of this.

[fatal1010]

Hey, nope, nothing in listed under Settings -> Notification -> Home...chalk it up to random request failures.

[xDiavelS]

I am also this exact same error message throughout my logs. Sometimes it happens multiple times in a row, other times it can be hours in between. The door still opens through HomeKit and Siri, so doesn't seem to be a major problem though.

[iRayanKhan]

If notifications never show, it means something is really wrong. If it was just a request failure, then the status would also not report in HomeKit. But since the Status does poll in HomeKit (As far as I can tell), it may be a Home App issue. Maybe re-adding the accessories may help?

[iRayanKhan]

@kbardai In the Home App, top Left Corner (Home Image), tap "Home Settings", select your home, then go to "Notifications", then "Doors and Locks". See if they were disabled.

[fatal1010]

The "Doors and Locks" notification is enabled. I've tried turning it off and on again but the notifications are very sporadic, sometimes I get notifications/sometimes none.

I'll try your suggestion of removing homebridge and re-adding to see if that helps...dunno if I need to go all nuclear and clear accessories/cache from homebridge as well, maybe as last resort.

[iRayanKhan]

Hey @kbardai did anything work so far?

[fatal1010]

Hey,

Removed and re-added homebridge from home app, no success...still sporadic notifications for garage.
Removed accessories/persit, removed homebridge from home app, restarted, re-added homebridge to homeapp, setup all accessories again (PITA), still no success, sporadic notifications.

Imma chalk it up to iOS13 issues?

Edit: to clarify, garage is the only notification I have setup in Home app.

Take Care

[DMBlakeley]

I am seeing the same behavior, same iOS revision, random in occurrence. Just updated to nom version 6.13.2 and will monitor.

[fatal1010]

Just installed the Schlage Sense door (HomKit) and get alerts consistently and almost instantly (whether manually unlocking or through homekit or schlage app)...dunno why garage alerts are a hit/miss :/

Edit: to add, sometimes I get notifications when I open the Home App, notifications that should have gotten hour+ ago/etc.

Edit2:
https://github.com/KhaosT/HAP-NodeJS/issues/543
homebridge/homebridge#2160

[seldridge1]

I’m also having similar results re: status change notifications. Would estimate I’m only receiving a notification about 10% of the time the door is opened or closed whether I’m on WiFi or cellular.

[fatal1010]

Here are some debug log info when I opened/closed the garage...received no notifications on any device. The IPs listed below are homepods and/or iphones/macbook. Also, let me know if this is getting off topic from the original post I made.

Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":10,"ev":true},{"aid":2,"iid":11,"ev":true}] +0ms Accessory [Homebridge] Registering Characteristic "Current Door State" for events +0ms Accessory [Homebridge] Registering Characteristic "Target Door State" for events +1ms EventedHTTPServer [::ffff:192.168.1.6] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":0}]} +11s EventedHTTPServer [::ffff:192.168.1.151] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":0}]} +1ms EventedHTTPServer [::ffff:192.168.1.7] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":0}]} +1ms EventedHTTPServer [::ffff:192.168.1.246] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":0}]} +0ms EventedHTTPServer [::ffff:192.168.1.167] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":0}]} +1ms [12/7/2019, 15:59:49] [Garage Door] doorstate changed from closed to open EventedHTTPServer [::ffff:192.168.1.6] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":0}]} +2ms EventedHTTPServer [::ffff:192.168.1.151] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":0}]} +1ms EventedHTTPServer [::ffff:192.168.1.7] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":0}]} +1ms EventedHTTPServer [::ffff:192.168.1.246] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":0}]} +1ms EventedHTTPServer [::ffff:192.168.1.167] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":0}]} +0ms EventedHTTPServer [::ffff:192.168.1.6] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":1}]} +2m EventedHTTPServer [::ffff:192.168.1.151] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":1}]} +1ms EventedHTTPServer [::ffff:192.168.1.7] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":1}]} +1ms EventedHTTPServer [::ffff:192.168.1.167] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":1}]} +0ms EventedHTTPServer [::ffff:192.168.1.246] Sending HTTP event '2.10' with data: {"characteristics":[{"aid":2,"iid":10,"value":1}]} +1ms [12/7/2019, 16:05:17] [Garage Door] doorstate changed from open to closed EventedHTTPServer [::ffff:192.168.1.6] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":1}]} +2ms EventedHTTPServer [::ffff:192.168.1.151] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":1}]} +1ms EventedHTTPServer [::ffff:192.168.1.7] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":1}]} +0ms EventedHTTPServer [::ffff:192.168.1.167] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":1}]} +1ms EventedHTTPServer [::ffff:192.168.1.246] Sending HTTP event '2.11' with data: {"characteristics":[{"aid":2,"iid":11,"value":1}]} +1ms [12/7/2019, 16:05:17] [Garage Door] desireddoorstate changed from open to closed

[iRayanKhan]

Personally I'm a few revisions behind of this plugin on my main setup since it works for me (pretty sure it goes as far as the last V4 Api version I updated) so I can try this version with the V5 Api and see if there's more to it.

[twentyNoise]

Edit: to add, sometimes I get notifications when I open the Home App, notifications that should have gotten hour+ ago/etc.

These are all the same issues I’ve been seeing since I installed this plugin a few years back. It may be worse in iOS 13 but always been an issue. I first posted about it here: #40

Been trying to get to the bottom of it for a while.

[joker1138]

Same issues, same iOS. Usually early in the morning will get the error in home bridge. On Homekit, if I press all the items that are "no response", they eventually reconnect. Of course, restarting home bridge clears everything up.

[hepcat72]

I have the same log errors, however I disabled the notifications (they're reliable from the MyQ app). I ended up here to figure out what I needed to do to quiet the errors.

[iRayanKhan]

Seeing as this is becoming more widespread and splitting into more issues here's what I propose:

For the lack of notifications can you please confirm the following:

• Notifications aren't silenced by iOS:
  Settings -> Notifications -> Home
  Ensure everything is as expected, and there is a special tab in blue text called "Home Notification Settings), make sure your Doors, Locks, Windows, and Garages are either on/off to your liking.

I would like more logs please. If possible in your current environment, run home bridge with the debug flag.

Homebridge -D

I would like a reply of the most recent debug output.
I also would like:

• Node Version:

Node -V

• NPM version:

 Npm -v

Also the current home bridge version.

I would like more logs and more environment info from other people to see if I can isolate a common variable or condition.

Also please let me know what your environments are, like the platform and hardware you are running this on. I want to see if y'all can rollback your installation version as a temporary fix since an older version works for me. (Away from home atm, but will report back my version).

I appreciate y'all for bringing this to my attention and I am working as hard as I can to fix this for y'all.

Enjoy y'alls new year!

[hepcat72]

I would like more logs please. If possible in your current environment, run home bridge with the debug flag.

Homebridge -D

I would like a reply of the most recent debug output.

It may take awhile to get the error, so it's not like I can stop homebridge, and manually run that on the command line and see the error. I've been wanting to regularly run homebridge with the -D flag for awhile for other reasons, but if you run homebridge using pm2, like me, I don't know how to supply that flag and have the process managed (i.e. restart if it quits, start up on boot, etc). I would need that if I'm going to be running it this way long enough to get that error in this debug mode.

(I'd paste current non -D logs, but I'm VNC'd in ATM and the clipboards aren't linked.)

I also would like:

• Node Version:

Node -V

>node -v
v11.12.0

• NPM version:

 Npm -v

>npm -v
6.13.4

Also the current home bridge version.

>homebridge --version
0.4.49

I would like more logs and more environment info from other people to see if I can isolate a common variable or condition.

Can you be more specific?

Also please let me know what your environments are, like the platform and hardware you are running this on.

rPi 3
jesse

I want to see if y'all can rollback your installation version as a temporary fix since an older version works for me. (Away from home atm, but will report back my version).
I appreciate y'all for bringing this to my attention and I am working as hard as I can to fix this for y'all.

Enjoy y'alls new year!

Happy New Year to you as well.

[dqtech]

I have the same ECONNRESET issue and also experience sporadic HomeKit Notifications when opening and closing the garage door.

IOS Home App Notifications:
Using iOS 13.2.2. I checked this an I have notifications enabled for the garage door. I also have a Schlage Sense Lock and it notifies me consistently. The big difference here is the lock is native HomeKit compatible and not using homebridge.

Hardware
I am running CoreELEC v9.2.1 on an X96 Android Box. The X96 uses an Amlogic S905X (arm64v8) with 1GB RAM.

Environment:

/homebridge # uname -a
Linux CoreELEC 3.14.29 #1 SMP Wed Nov 27 06:02:54 GMT 2019 aarch64 GNU/Linux

Versions:
Homebridge is running in a docker container (oznu/homebridge) with host networking setup.

/homebridge # node -v
v12.14.0
/homebridge # npm -v
6.13.4
/homebridge # homebridge --version
0.4.50

Log File:
Here is a standard log file showing lots of examples of this ECONNRESET error.
I am running homebridge with the debug (-D flag) as I reply to this post, but the ECONNRESET error hasn't popped up yet. I will reply with the log file once the error occurs.

homebridge.log

Originally I first tried out the homebridge-myq2 plugin to connect to my Chamberlain Smart Garage Door Hub. Myq2 functions to open/close the door in the Home App, but notifications didn't work reliably. This is how I came across this plugin -I wanted to see if the homebridge-chamberlain plugin would give me consistent notifications.

Scanning through the attached log file, it appears that myq2 also suffers from ECONNRESET issues even though it looks like they are using v4api.

One last thing to note. I also have an old iPhone 5c running iOS 10. The garage door open/close notifications are consistent. Strange eh?!

[iRayanKhan]

Two things I can think of at the moment.
(Please read the whole thing before doing any of this as there's multiple workarounds for each workaround.)
When I get home I will supply the version of the plugin I am using for my main setup.
The fact it works on iOS furthers my theory about HomeKit no response issues.

If possible, clear Persist and cachedAccessories, unpair bridge from HomeKit, make a new HomeKit Home, see if notifications show there.
If you can't remove the bridge from your HomeKit home due to having multiple plugins, make another instance of this plugin. Steps here:

mkdir GarageTestBridge
cd GarageTestBridge/
nano config.json 
(If on non command line systems, drag and drop your config.json file here with only the chamberlain plugin in the config).
Then start this new instance of HomeBridge by doing: homebridge -U ~/GarageTestBridge/ 
(Cases Matter)
Add this new HomeKit bridge to your new HomeKit home, and see if you can get notifications. 

Be sure to change the homebridge Username, port, and name, (set-up pin code is fine as default) for the new Config file.

Reasoning:
I had a HomeKit home created in iOS 11.4 and users I shared the home with started having major issues where they couldn't control accessories locally or remotely. My assumption, was that with big HomeKit app changes with new iOS updates, something didn't convert properly for a iOS 13 version home. Also I recommend staying away from older iOS devices for your HomeKit home. I had tried to use an old iPad (runs iOS 10.3.3 max), as a HomeKit hub instead of the Apple TV's or HomePods, and it converted my light switches to Garages, and swapped all accessory states and ended up breaking my home. So If Making a new HomeKit Home works and the notifications along with it, it means it just have been a migration issue Apple is yet to fix in iOS for new Home.app versions.
I fixed my issues by making a new HomeKit home, and factory resetting All HomeHubs and it's been flawless so far. I plan to raise a feedback ticket with Apple to address this since I had an open Support case for now 7-8 months regarding HomeKit instability. Sorry to the mini rant, but here's a

tldr; iOS migration issues cause home.app to not make HomeKit's core functions work, and making a new HomeKit home worked for me.

[iRayanKhan]

Thanks for the logs @dqtech I noticed that you have homebridge-tplink-smarthome, I have this plugin too and you have to declare something for that plugin or this method to add a new homebridge instance won't work. I have a config just for this I will send in 4 or so hours.

I am doing more research on ECONNRESET, but since it's not that major as compared to Garage notification states, the priority is the notifications.
Edit:
I noticed that this error as stated happens every once in a while and at max happens 3 times a day, or once every day within the same time span. Do the times in the logs mean anything to you like, do you check the Home App during this time, or have anyone arrive then? I want to see if this is just background polling that fails, and the request just re-requests it's self.

[iRayanKhan]

Hey @hepcat72, thanks for the reply.

but if you run homebridge using pm2, like me, I don't know how to supply that flag and have the process managed

I also run PM2 on my environment too, I managed to get pm2 to run homebridge using the -U flag (specified folder), using a shell script to start PM2 in that certain instance, I'll send the file (it's 2 lines long), and how to have PM2 use the -D Flag. I know the -U flag works, -D should too.

[rajbala]

I also have the ECONNRESET issues sporadically through the logs.

/homebridge # node -v
v12.14.0
/homebridge # npm -v
6.13.4
/homebridge # homebridge --version
0.4.50
/homebridge #

I am running Homebridge in a Docker container on a RPi4 with 4GB of RAM. Happy to help debug this if I can.

[iRayanKhan]

So I was working on some tweaks for this plugin to make getting the version info and such easier, anyways I am using V1.0.6 of the plugin. I will upgrade to V1.0.8 and get back with y'all tonight and see if notifications work.

Also thank you everyone for replying and providing logs and such I appreciate it a lot.

I am hoping to have this issue resolved within a week, it also seems to be non-severe (the ECONNRESET) since it's just seems like an API call back failure and it resend a request. But the notifications thing is a big deal 'cuz that's a big integration part in HomeKit. V1.0.9 will maybe suppress this error if that's what fixes it, and V1.10.0 or may just call it V2.0 will add Accessory info in the Home App to report plugin version (good for debugging), and add light controller support if I can make it info one plugin and not 2 branches, will still release the other branch.

[iRayanKhan]

Has anyone tried making a new Home and trying notifications?

[DMBlakeley]

What I am finding when trying to understand the inner workings of the Homebridge plugins is to look at the HomeKit Characteristic Types to see how the HomeKit accessory characteristic is defined.

For a door / garage door there is both HMCharacteristicTypeCurrentDoorState as well as HMCharacteristicTypeTargetDoorState. So, both are legitimate characteristics.

[TheEngineerGuy]

Correct, both are legitimate characteristics. One seems to notify and update switch state, but the other seems to request and trigger a change if 'desired state' does not match the 'current state'.

EDIT: And I am just thinking that if we send both, it may cause homekit to not send out a notification, as the requested state matches the change state.

[iRayanKhan]

I don’t know how correlated this is, but these are my findings.

I recently got some eero’s for HomeKit secure router, and after re-adding my devices to the MyQ app, I get consistent notifications now.

I am considering learning TypeScript and rewriting this plugin, but this is not confirmed yet.

Also I looked at those node implementations and they seem viable. Just waiting for school to ease up a little bit so I can tinker with them and see if I can implement a better protocol.

[TheEngineerGuy]

And @iRayanKhan Do take a look at the iobroker.myq link I posted above. They have implemented every single MyQ state in it. The most comprehensive MyQ implementation I have seen till date, but it is for IOBroker and not homebridge.

[iRayanKhan]

I am considering re-writing this plugin from scratch to be based off that broker, but unsure at the moment. School ends this month so I should get some time to do more work on this plugin, as school is the priority at the moment.

I hope everyone is staying safe.

[iRayanKhan]

I sent some emails out to some people and right after I sent the email I found some answers.

This plugin exposes switches for ioBrokers. That means you will have to setup the broker then the plugin which isn't ideal. So I may have to combine several repos to achieve a full integration. This may or may not work, but hey it's worth a shot. This will/should add obstruction detection, proper states, notification fixes, etc. If anyone knows a better way to link ioBrokers into home bridge please link it.

[TheEngineerGuy]

Hi @iRayanKhan I was thinking that we could look at its source code and see how it queries the myq servers, handles the timers, handles the states etc. Not suggesting we should use it, just learn from it and implement it here. The logic that it has is quite different from our implementation. It uses a different URL as well, myqexternal.myqdevice.com.

[mbierman]

This is not a homebridge problem. ECONNRESET is a TCP reset generated by Server being contacted, which in this case is MyQ server.

Yes, we need to gracefully handle this error, and retry when this error is generated, but updating homebridge is not going to fix it.

Ah, just saw your reply. Am I understanding correctly that this is purely on the MyQ server side and not an indication of any issue on my LAN?

[gamertyke]

I am seeing the same behavior with sporadic notifications accompianied by

"FetchError: request to https://api.myqdevice.com..."

Additionally, a lot of the time when I ask Siri to open/close a door, she'll hang, then say "I tried however the Garage Garage Door didn't respond," but then it will actually work a few seconds later. Just thought I'd add my experience if it helps at all.

[beyerjp]

I am seeing the same behavior with sporadic notifications accompianied by

"FetchError: request to https://api.myqdevice.com..."

Additionally, a lot of the time when I ask Siri to open/close a door, she'll hang, then say "I tried however the Garage Garage Door didn't respond," but then it will actually work a few seconds later. Just thought I'd add my experience if it helps at all.

I am also seeing the same thing since upgrading to the newest version of Homebridge. Did you just upgrade as well?

Thanks!

[gamertyke]

Yes, it worked quite well for a while, but recently started doing that. I actually just noticed a new new version of Homebridge is out, so I'm going to upgrade and see if that helps.

[TheEngineerGuy]

This is not a homebridge problem. ECONNRESET is a TCP reset generated by Server being contacted, which in this case is MyQ server.

Yes, we need to gracefully handle this error, and retry when this error is generated, but updating homebridge is not going to fix it.

[mbierman]

It is worse now.

Module	Version
Node.js	12.16.3
NPM	6.14.5
homebridge	1.1.0
Alpine Linux (running in a Docker on a Synology)	3.11.6
homebridge-chamberlain	1.6.0
homebridge-nest	4.4.6

[5/18/2020, 9:16:28 AM] [Garage Door] FetchError: request to https://api.myqdevice.com/api/v5.1/Accounts/***/devices/***failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/homebridge/node_modules/homebridge-chamberlain/node_modules/node-fetch/lib/index.js:1455:11)
    at ClientRequest.emit (events.js:310:20)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:310:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

Many in a row this morning. I am happy to provide any additional information you need if I left something important out or run any tests you like to help.

[mbierman]

I am seeing the same behavior with sporadic notifications accompianied by

"FetchError: request to https://api.myqdevice.com..."

Additionally, a lot of the time when I ask Siri to open/close a door, she'll hang, then say "I tried however the Garage Garage Door didn't respond," but then it will actually work a few seconds later.

I've seen the same.

[dinof40]

Hi, just to add to this thread a thought. I too am receiving the ECONNRESET errors frequently and am not receiving alerts. But I also regularly get errors using the actual Merlin/Chamberlin app "Garage Door is not responding, Please try again." but most of the time the app still works. Do you think this is the same issue and it's actually something their end?

Rasberyy Pi Zero W - Raspbian GNU/Linux Buster (10)
node v12.16.2
npm 6.14.4
homebridge 1.1.0
homebridge-config-ui-x v4.19.0
homebridge-chamberlain v1.6.0

iOS 13.4.1

[iRayanKhan]

I have been contacted beyond Github by several people that they had their garages not respond in either HomeKit, the app, or both. It eventually fixed itself after a while, but it could be on their end.

Can someone try PR #100 to see if that resolves their issue? I will be able to push that PR to npm later if you need to install it that way.

[gamertyke]

Hey Ryan, happy to help test, but I'm a bit of a noob. I'm running Homebridge in docker, what's the best way to pull this test version of the plugin?

[iRayanKhan]

Looks like the official MyQ homebridge product to add native HomeKit support also has delayed notifications. Reddit Discussion

[TheEngineerGuy]

Till @iRayanKhan is working on getting this app recoded, as he suggested, we should give hime some space.

In the meantime we can use MyQ2 plugin, I have been using it for over a month now and notifications are pretty much immediate.

[TheEngineerGuy]

Looks like the official MyQ homebridge product to add native HomeKit support also has delayed notifications. Reddit Discussion

yes, the official MyQ homebridge sucks. I gave mine away a few weeks ago.

[iRayanKhan]

I haven’t looked into the source code of that plugin as deeply, I can see what it is doing differently with notifications and try it here.

[iRayanKhan]

Just published with tag rc3

The version is 1.6.2-beta.1

Please report any feedback from this beta release and reply here.

[hdcola]

Checking the logs, I see the following, is this a concern and what could be the cause?

0|homebrid | [11/17/2019, 00:54:28] [Garage Door] FetchError: request to https://api.myqdevice.com/api/v5/accounts/<Account_ID>/devices/<Device_ID> failed, reason: read ECONNRESET
0|homebrid | at ClientRequest. (/usr/lib/node_modules/homebridge-chamberlain/node_modules/node-fetch/index.js:133:11)
0|homebrid | at ClientRequest.emit (events.js:210:5)
0|homebrid | at TLSSocket.socketErrorListener (_http_client.js:406:9)
0|homebrid | at TLSSocket.emit (events.js:210:5)
0|homebrid | at emitErrorNT (internal/streams/destroy.js:92:8)
0|homebrid | at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
0|homebrid | at processTicksAndRejections (internal/process/task_queues.js:80:21) {
0|homebrid | name: 'FetchError',
0|homebrid | message: 'request to https://api.myqdevice.com/api/v5/accounts/<Account_ID>/devices/<Device_ID> failed, reason: read ECONNRESET',
0|homebrid | type: 'system',
0|homebrid | errno: 'ECONNRESET',
0|homebrid | code: 'ECONNRESET'
0|homebrid | }

Info

iOS Version: 13.2.2
Plugin Version: latest
HomeBridge Version: latest
Node/Npm Version: 12.13 / 6.12

Also, this is probably related to iOS 13 (HomeKit just acting weird), but, I don't get consistent notifications on my phone when garage opens/closes...I sometimes randomly get an Open or Close status, but, very very sporadic.

Let me know.

I had the same problem on my raspbian system.

homebridge-chamberlain v1.6.1

[iRayanKhan]

Working on updating the debugger. Will implement this in the next update, before V2.0/2.1.

I may have a debug beta within 3 or so days

[hdcola]

Thank you very much and looking forward to the new release!

[SidShetye]

On 1.6.1 I'm seeing a lot of

[8/6/2020, 10:53:41 AM] [Garage Door] FetchError: request to https://api.myqdevice.com/api/v5.1/Accounts/*****/devices/************ failed, reason: connect ENETUNREACH 13.83.97.206:443
    at ClientRequest.<anonymous> (/homebridge/node_modules/homebridge-chamberlain/node_modules/node-fetch/lib/index.js:1455:11)
    at ClientRequest.emit (events.js:315:20)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  type: 'system',
  errno: 'ENETUNREACH',
  code: 'ENETUNREACH'
}

errors just like the others. I tried 1.6.2-beta.1 but that gives other errors like

[8/6/2020, 11:27:41 AM] [Garage Door] Error: invalid response, got HTTP 400: {
    "SecurityToken": "",
    "ReturnCode": "0",
    "ErrorMessage": "please contact customer care, supportID: " **************",
    "CorrelationId": ""
}
    at /homebridge/node_modules/homebridge-chamberlain/src/api.js:26:15
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

I didn't update the plugin configuration (user/pass etc) during the update and when reviewing it, I see the right values.

I also see 2.0.3-beta.1 at npm.

What's the deal with 2.0.x series? Perhaps update the root readme.md here in this repo for 1.x and 2.x changes/awareness?

[iRayanKhan]

Closing: This plugin is now being deprecated. Please use this plugin.