tsightler
commented
3 years ago The error noted is from TuyAPI (the underlying API that this script uses) and indicates that there's no active connection to the device. Debug output would be helpful, and I should probably trap the error scenario, but since you mention that you are already running tuya-mqtt on a different device, my first guess might be that you didn't stop it there before starting it on the new device. Most Tuya devices only support a single concurrent local connection and will reject all other attempts to connect to the device locallt, so, if another instance of the script (or the Tuya app for example) is already connected to the device, then running a second instance will not be able to connect.
This should be clearly visible when running with debug output as reconnect attempts will happen every 30 seconds or so.
palsbo
Flip76
When trying to install on RS914 (npm install) I get the following:
`ash-4.3# npm install audited 322 packages in 17.975s
45 packages are looking for funding run
npm fundfor detailsfound 2 vulnerabilities (1 low, 1 high) run
npm audit fixto fix them, ornpm auditfor detailsash-4.3#`
running npm audit, I get the following: `ash-4.3# npm audit
┌──────────────────────────────────────────────────────────────────────────────┐ │ Manual Review │ │ Some vulnerabilities require your attention to resolve │ │ │ │ Visit https://go.npm.me/audit-guide for additional guidance │ └──────────────────────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ Low │ Prototype Pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Package │ minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Patched in │ >=0.2.1 <1.0.0 || >=1.2.3 │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Dependency of │ @tuyapi/cli │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Path │ @tuyapi/cli > http-mitm-proxy > optimist > minimist │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ More info │ https://npmjs.com/advisories/1179 │ └───────────────┴──────────────────────────────────────────────────────────────┘ ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ High │ Prototype Pollution in node-forge │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Package │ node-forge │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Patched in │ >= 0.10.0 │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Dependency of │ @tuyapi/cli │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Path │ @tuyapi/cli > http-mitm-proxy > node-forge │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ More info │ https://npmjs.com/advisories/1561 │ └───────────────┴──────────────────────────────────────────────────────────────┘ found 2 vulnerabilities (1 low, 1 high) in 322 scanned packages 2 vulnerabilities require manual review. See the full report for details. ash-4.3#`
Running npm audit fix, I get the following: `ash-4.3# npm audit fix up to date in 15.732s
45 packages are looking for funding run
npm fundfor detailsfixed 0 of 2 vulnerabilities in 322 scanned packages 2 vulnerabilities required manual review and could not be updated ash-4.3#`
Sending command from MQTT prints the following:
(node:7616) UnhandledPromiseRejectionWarning: Error: No connection has been made to the device. at TuyaDevice._send (/volume1/homes/admin/tuya-mqtt-master/node_modules/tuyapi/index.js:269:13) at pTimeout._setResolver (/volume1/homes/admin/tuya-mqtt-master/node_modules/tuyapi/index.js:242:14) at new Promise (<anonymous>) at /volume1/homes/admin/tuya-mqtt-master/node_modules/tuyapi/index.js:238:46 at run (/volume1/homes/admin/tuya-mqtt-master/node_modules/p-queue/dist/index.js:153:104) at PQueue._tryToStartAnother (/volume1/homes/admin/tuya-mqtt-master/node_modules/p-queue/dist/index.js:101:38) at /volume1/homes/admin/tuya-mqtt-master/node_modules/p-queue/dist/index.js:167:18 at new Promise (<anonymous>) at PQueue.add (/volume1/homes/admin/tuya-mqtt-master/node_modules/p-queue/dist/index.js:148:16) at TuyaDevice.set (/volume1/homes/admin/tuya-mqtt-master/node_modules/tuyapi/index.js:238:27) (node:7616) 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: 2) (node:7616) [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.Any idea? Thanks for the greate work - it works fine on my Raspberry pi but not on Synology. I have checked the configurations files and the cli.