Unhandled errors in promises

[BobFrankston]

I'm getting fatal errors because of unhandled failures in promises.

[samuraitruong]

hi @BobFrankston can you share your connection code? maybe your device is new model and this code was not updated for awhile

[BobFrankston]

It shouldn't matter what the device is doing, your code needs to handle errors in promises because Node will terminate the app when there is such an error.

[BobFrankston]

I just upgraded from 1.0.5 to 1.1.0. I will see if it fixes the problem.

[BobFrankston]

I've upgraded, but I still get

2022-08-12 13:28:08.832 [fail] Error: connect ECONNREFUSED 172.20.0.245:55443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)

I presume there is a missing error handler in the TCP connection.

[BobFrankston]

Could be my error -- I just added (.on('error"). to the connection and it seems to have fixed it.

[samuraitruong]

I think we should handle if no error listener in client. THanks, I will update it when have some time

…

________________________________ From: Bob Frankston ***@***.***> Sent: Saturday, August 13, 2022 3:50 AM To: samuraitruong/yeelight ***@***.***> Cc: Truong Nguyen ***@***.***>; Comment ***@***.***> Subject: Re: [samuraitruong/yeelight] Unhandled errors in promises (Issue #47) Could be my error -- I just added (.on('error"). to the connection and it seems to have fixed it. — Reply to this email directly, view it on GitHub<#47 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJA3IXKYT4NXFYQVGIWSKDVY2FHTANCNFSM54PAQDHQ>. You are receiving this because you commented.Message ID: ***@***.***>