search

TuyaAPI / cli

🔧 A CLI for Tuya devices
MIT License
267 stars 43 forks source link

tuya-cli get command results in socket error write EPIPE unhandled error event #79

Closed cdprince closed 4 years ago

cdprince commented 4 years ago

Bug is repeatable I tried to run the tuya-cli get command and an error occured and a message was thrown: Update available 1.13.0 → 1.13.3 I Just performed a apt-get upgrade then updated my npm i @tuyapi/cli -g $ tuya-cli -V 1.13.3 $ npm -v 5.8.0 I was able to do use tuya-cli get yesterday no problem.

$ DEBUG=* tuya-cli get --ip '10.0.0.212' --id 73328546dc4f22eb3795 --key 153e749667XXXXXX -a TuyAPI IP and ID are already both resolved. +0ms TuyAPI Connecting to 10.0.0.212... +11ms TuyAPI Socket connected. +24ms TuyAPI GET Payload: +3ms TuyAPI { gwId: '73328546dc4f22eb3795', TuyAPI devId: '73328546dc4f22eb3795', TuyAPI t: '1595466643', TuyAPI dps: {}, TuyAPI uid: '73328546dc4f22eb3795' } +0ms TuyAPI GET Payload: +20ms TuyAPI { gwId: '73328546dc4f22eb3795', TuyAPI devId: '73328546dc4f22eb3795', TuyAPI t: '1595466643', TuyAPI dps: {}, TuyAPI uid: '73328546dc4f22eb3795' } +0ms TuyAPI Error event from socket. 10.0.0.212 { Error: write EPIPE at WriteWrap.afterWrite [as oncomplete] (net.js:789:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write' } +7ms events.js:174 throw er; // Unhandled 'error' event ^

Error: Error from socket at Socket.client.on.err (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:350:30) at Socket.emit (events.js:198:13) at errorOrDestroy (internal/streams/destroy.js:107:12) at onwriteError (_stream_writable.js:436:5) at onwrite (_stream_writable.js:461:5) at _destroy (internal/streams/destroy.js:49:7) at Socket._destroy (net.js:614:3) at Socket.destroy (internal/streams/destroy.js:37:8) at WriteWrap.afterWrite [as oncomplete] (net.js:791:10) Emitted 'error' event at: at Socket.client.on.err (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:350:16) at Socket.emit (events.js:198:13) [... lines matching original stack trace ...] at WriteWrap.afterWrite [as oncomplete] (net.js:791:10) pi@raspberrypi:~ $ pi@raspberrypi:~ $ pi@raspberrypi:~ $ DEBUG=* tuya-cli get --ip '10.0.0.212' --id 73328546dc4f22eb3795 --key 153e749667XXXXXX -a TuyAPI IP and ID are already both resolved. +0ms TuyAPI Connecting to 10.0.0.212... +11ms TuyAPI Socket connected. +21ms TuyAPI GET Payload: +3ms TuyAPI { gwId: '73328546dc4f22eb3795', TuyAPI devId: '73328546dc4f22eb3795', TuyAPI t: '1595466680', TuyAPI dps: {}, TuyAPI uid: '73328546dc4f22eb3795' } +1ms TuyAPI GET Payload: +21ms TuyAPI { gwId: '73328546dc4f22eb3795', TuyAPI devId: '73328546dc4f22eb3795', TuyAPI t: '1595466680', TuyAPI dps: {}, TuyAPI uid: '73328546dc4f22eb3795' } +0ms TuyAPI Error event from socket. 10.0.0.212 { Error: write EPIPE at WriteWrap.afterWrite [as oncomplete] (net.js:789:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write' } +6ms events.js:174 throw er; // Unhandled 'error' event ^

Error: Error from socket at Socket.client.on.err (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:350:30) at Socket.emit (events.js:198:13) at errorOrDestroy (internal/streams/destroy.js:107:12) at onwriteError (_stream_writable.js:436:5) at onwrite (_stream_writable.js:461:5) at _destroy (internal/streams/destroy.js:49:7) at Socket._destroy (net.js:614:3) at Socket.destroy (internal/streams/destroy.js:37:8) at WriteWrap.afterWrite [as oncomplete] (net.js:791:10) Emitted 'error' event at: at Socket.client.on.err (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:350:16) at Socket.emit (events.js:198:13) [... lines matching original stack trace ...] at WriteWrap.afterWrite [as oncomplete] (net.js:791:10)