Connecting bug getting UnhandledPromiseRejectionWarning when using example code

[domanows]

While running example code with the following configuration
var elk = new Elk(
2601, // port
'192.168.39.6',
{
secure: true,
rejectUnauthorized: false,
secureProtocol: 'TLSv1_method'
}
);

I am getting UnhandledPromiseRejectionWarning even though connection appears to be successful.
connected
(node:7967) UnhandledPromiseRejectionWarning: Timout occured before Arming Status (as) was received.
(node:7967) 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(). (rejection id: 1)
(node:7967) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[sgentry]

Which version are you using?

[domanows]

Shane, Thanks so much.  I am using elkmon@1.2.2 The ELK system is listed as System Type M1G Hardware Version 0.11 Boot Version 3.3.2 Firmware 5.1.8 Port 2601 I do know that I have to keep a Windows 7.2 copy around as the latest Windows Wouldn't run the Elk RP software.  It has something to do with an SSL deprecation. When I called Elk they recommended not updating the firmware on the Elk M1 Gold unless necessary. Is it possible that this has something to do with it? Thanks, Matt

…

On 11/26/19 3:44 PM, Shane Gentry wrote: Which version are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=ACRFNFIZVA5EG5ZSO5JQCXDQVWDCFA5CNFSM4JPT7X72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHMCXI#issuecomment-558809437>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRFNFL7CD2AA3ZFEMMTP2DQVWDCFANCNFSM4JPT7X7Q>.

-- Matt Domanowski www.neumonics.com 716-870-6873

[sgentry]

Sorry for the delay. Busy time of year and I forgot to come back to this.

I've been using the elkmon beta version (2.0.0-beta.1) but that shouldn't have anything different that would affect connecting to the M1XEP. I'm guessing your suspicions are correct and it has something to do with SSL. I'm assuming you can connect without using SSL, correct? Here's my system info.

System Type M1G
Hardware Version: .13
Boot Version: 3.3.6
Firmware: 5.3.10
M1XEP Firmware: 2.0.42 (Updated to 2.0.44 today)

I've been running the Elk RP Software on Windows 10 for several years now with no issues. Looks like you need to make sure to update your M1XEP, for Win 10 compatibility. Are you able to able to connect to port 2601 using the RP software?

[domanows]

Shane, Thanks so much.  I will try without ssl and see what happens.  I was afraid to upgrade the firmware in the M1EXP unless necessary. Although entertaining, the warning on the Elk Products website of "*WARNING:  *As with any device firmware update there is a small risk of an update being unsuccessful which could render the device inoperable."  deterred me from upgrading. BTW, the link for the M1XEP firmware is https://www.elkproducts.com/m1xep-version2-firmware.  I am not sure where to check it on the actual system either. Have a great holiday.

…

On 12/14/19 12:22 PM, Shane Gentry wrote: Sorry for the delay. Busy time of year and I forgot to come back to this. I've been using the elkmon beta version (2.0.0-beta.1) but that shouldn't have anything different that would affect connecting to the M1XEP. I'm guessing your suspicions are correct and it has something to do with SSL. I'm assuming you can connect without using SSL, correct? Here's my system info. System Type M1G Hardware Version: .13 Boot Version: 3.3.6 Firmware: 5.3.10 I've been running the Elk RP Software on Windows 10 for several years now with no issues. Looks like you need to make sure to update your M1XEP <https://www.elkproducts.com/elk-m1xep-and-windows-compatibility>, for Win 10 compatibility. I'm not finding where to check which firmware I have on my M1XEP, but I've updated it several times in the past. Pretty sure it's 2.x.x since it shows the M1Cloud tab from RP Software. Are you able to able to connect to port 2601 using the RP software? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=ACRFNFP3YDRIKN2VH2PN2BDQYUI5RA5CNFSM4JPT7X72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4HEIY#issuecomment-565735971>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRFNFIRBZRC4QN7VSFAB4DQYUI5RANCNFSM4JPT7X7Q>.

-- Matt Domanowski www.neumonics.com 716-870-6873

[sgentry]

I'm not sure why they discourage updating like they do. I prefer to keep my system updated.

If you're wanting to verify which M1XEP firmware is installed, you can check that from RP Software after you have successfully connected.

Send/Rcv --> Enroll Update Control and Devices

[domanows]

Holiday really slowed me down. It works without SSL.  Honestly since the alarm system is on a private network inside a home, not having SSL isn't the end of the world. Thanks again!

…

On 12/14/19 12:22 PM, Shane Gentry wrote: Sorry for the delay. Busy time of year and I forgot to come back to this. I've been using the elkmon beta version (2.0.0-beta.1) but that shouldn't have anything different that would affect connecting to the M1XEP. I'm guessing your suspicions are correct and it has something to do with SSL. I'm assuming you can connect without using SSL, correct? Here's my system info. System Type M1G Hardware Version: .13 Boot Version: 3.3.6 Firmware: 5.3.10 I've been running the Elk RP Software on Windows 10 for several years now with no issues. Looks like you need to make sure to update your M1XEP <https://www.elkproducts.com/elk-m1xep-and-windows-compatibility>, for Win 10 compatibility. I'm not finding where to check which firmware I have on my M1XEP, but I've updated it several times in the past. Pretty sure it's 2.x.x since it shows the M1Cloud tab from RP Software. Are you able to able to connect to port 2601 using the RP software? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=ACRFNFP3YDRIKN2VH2PN2BDQYUI5RA5CNFSM4JPT7X72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4HEIY#issuecomment-565735971>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRFNFIRBZRC4QN7VSFAB4DQYUI5RANCNFSM4JPT7X7Q>.

-- Matt Domanowski www.neumonics.com 716-870-6873