UnhandledPromiseRejectionWarning & SIGTERM errors keep shutting down HOOBS
No matter what I do, using the Harmony v1.5.1 plug-in, I get the following errors and my hub shuts down.

SIGTERM
EADDRINUSE

the newest error being 

UnhandledPromiseRejectionWarning

(I’ve discovered the terminal command “sudo killall -9 node” seems to fix EADDRINUSE, so that doesn’t seem to be an issue anymore. I just included it, in case it is important diagnostically).

When I install the harmony plugin, I only fill in the following fields:

Name of YourHub
IP Address of Your Hub (must be fixed)
Hub name in Your Harmony App 
Main Activity

I leave everything else to default.

I have 3 plugins installed:

Harmony (HOOBS certified) v1.5.1
Ring (HOOBS certified) v9.15.6
OnStar v1.5.1

I’m running:

HOOBS v3.3.5
Node v14.15.1

I have restored my HOOBS hub to factory defaults several times, trying to resolve the issues, but it never works.

I’ve followed the link for using the CLI Flag, but I don’t know anything about coding, therefore, I don’t understand what needs to be done or how to do it. I’m comfortable using the terminal, as long as I’m given commands that I can copy and paste.

Here is the latest error log (If I get a SIGTERM error, I’ll add it to this post. I get them weekly, sometimes daily.). 

UnhandledPromiseRejectionWarning: Error: SIP request made after call was destroyed
4/4/2021, 5:51:01 PM at SipCall.request (/home/hoobs/.hoobs/node_modules/homebridge-ring/lib/api/sip-call.js:117:35)
4/4/2021, 5:51:01 PM at SipCall.sendKeyFrameRequest (/home/hoobs/.hoobs/node_modules/homebridge-ring/lib/api/sip-call.js:188:21)
4/4/2021, 5:51:01 PM at SipCall.<anonymous> (/home/hoobs/.hoobs/node_modules/homebridge-ring/lib/api/sip-call.js:216:24)
4/4/2021, 5:51:01 PM at Generator.next (<anonymous>)
4/4/2021, 5:51:01 PM at fulfilled (/home/hoobs/.hoobs/node_modules/homebridge-ring/lib/api/sip-call.js:5:58)
4/4/2021, 5:51:01 PM (node:1525) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)

Thank in advance for any assistance.