-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReferenceError: timeout is not defined #9
Comments
Try to update to the latest. |
Any luck? |
pls. add tag node-red to package.json, update version |
The package is not yet published to npm. I’ll sort that out during the week. I need to make sure is working properly. Did you update the node to latest and is it working ? |
node-red crashes at start 13 Aug 10:04:26 - [red] Uncaught Exception: |
I cannot reproduce this, did just update? are you using the commandByte filter? |
Just add extra check
next issue is: (node:73782) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of undefined |
The second error is tuyapi, nothing we can do there. I cannot reproduce the first one, not an expert in this. What node version is this ? |
node v12.4.0 |
Just tested with v12.4.0 and is working fine. Did you maybe duplicate the node with same ip address? |
(node:63079) UnhandledPromiseRejectionWarning: ReferenceError: timeout is not defined
at TuyaDevice. (/Users/apopov/.node-red/node_modules/node-red-contrib-tuya-local/tuya-local.js:74:17)
at TuyaDevice.emit (events.js:200:13)
at Socket. (/Users/apopov/.node-red/node_modules/node-red-contrib-tuya-local/node_modules/tuyapi/index.js:367:16)
at Socket.emit (events.js:205:15)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1040:10)
(node:63079) 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:63079) [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.
The text was updated successfully, but these errors were encountered: