get() timeout error after the result was successfully retrieved

[kardoka]

Greetings, I am getting a timeout error for the get() command after I successfully process the result of it. What could be the issue here? Would it be possible to handle this error?

The error message (note that I am hiding the device ids and full path to working directory):

node:internal/errors:478
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_UNHANDLED_ERROR]: Unhandled error. ('Timeout waiting for status response from device id: hidden)
    at new NodeError (node:internal/errors:387:5)
    at TuyaDevice.emit (node:events:502:17)
    at ./node_modules/tuyapi/index.js:411:12
    at Timeout._onTimeout (./node_modules/p-timeout/index.js:25:13)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ERR_UNHANDLED_ERROR',
  context: 'Timeout waiting for status response from device id:  hidden
}

The code itself:

const TuyAPI = require('tuyapi');
require('dotenv').config();

const device = new TuyAPI({
  id: process.env.GATEWAY_DEVICE_ID,
  key: process.env.LOCAL_KEY,
  version: 3.3,
  issueRefreshOnConnect: true,
});

(async () => {
  await device.find();

  await device.connect();

  let status = await device.get({
    cid: process.env.CHILD_ID,
    dps: 1
  });

  console.log(`Current status: ${status}.`);

  device.disconnect();
})();

EDIT: I am able to catch it using:

process.on('uncaughtException', error => {
  console.log('Caught it!');
})

But is there some more elegant way to catch it or to avoid this exception altogether?

[Apollon77]

Please start your ascript with DEBUG=TuyAPI* node myscript,js and provide the log. I assume that you have a 3.3 device which is special and returns and error for the normal get way and needs to be queried by "set" and then is not responding.

What you mean with "the exception is thrown after you processed the result"? (and in fact any "await" can throw an error)

[kardoka]

Sure thing, here is the log output:

 TuyAPI Finding missing IP undefined or ID HIDDEN +0ms
 TuyAPI Received UDP message. +9s
 TuyAPI UDP data: +2ms
 TuyAPI {
 TuyAPI   payload: {
 TuyAPI     ip: '192.168.1.155',
 TuyAPI     gwId: 'HIDDEN',
 TuyAPI     active: 2,
 TuyAPI     ablilty: 0,
 TuyAPI     encrypt: true,
 TuyAPI     productKey: 'HIDDEN',
 TuyAPI     version: '3.3',
 TuyAPI     lan_cap: 5000,
 TuyAPI     lan_seq: 10,
 TuyAPI     token: true
 TuyAPI   },
 TuyAPI   leftover: false,
 TuyAPI   commandByte: 19,
 TuyAPI   sequenceN: 0
 TuyAPI } +0ms
 TuyAPI Connecting to 192.168.1.155... +4ms
 TuyAPI Socket connected. +7ms
 TuyAPI GET Payload: +2ms
 TuyAPI {
 TuyAPI   gwId: 'HIDDEN',
 TuyAPI   devId: 'HIDDEN',
 TuyAPI   t: '1669902045',
 TuyAPI   dps: {},
 TuyAPI   uid: 'HIDDEN'
 TuyAPI } +0ms
 TuyAPI GET Payload: +3ms
 TuyAPI {
 TuyAPI   gwId: 'HIDDEN',
 TuyAPI   devId: 'HIDDEN',
 TuyAPI   t: '1669902045',
 TuyAPI   dps: {},
 TuyAPI   uid: 'HIDDEN',
 TuyAPI   cid: 'HIDDEN'
 TuyAPI } +0ms
 TuyAPI Received data: HIDDEN +10ms
 TuyAPI Parsed: +1ms
 TuyAPI {
 TuyAPI   payload: 'json obj data unvalid',
 TuyAPI   leftover: false,
 TuyAPI   commandByte: 10,
 TuyAPI   sequenceN: 1
 TuyAPI } +0ms
 TuyAPI Received DATA packet +0ms
 TuyAPI data: 10 : "json obj data unvalid" +1ms
 TuyAPI GET needs to use SEND instead of DP_QUERY to get data +0ms
 TuyAPI SET Payload: +0ms
 TuyAPI {
 TuyAPI   devId: HIDDEN,
 TuyAPI   gwId: HIDDEN,
 TuyAPI   uid: '',
 TuyAPI   t: 1669902045,
 TuyAPI   dps: { '1': null }
 TuyAPI } +0ms
 TuyAPI Received data: HIDDEN +6ms
 TuyAPI Parsed: +1ms
 TuyAPI {
 TuyAPI   payload: {
 TuyAPI     dps: {
 TuyAPI       '1': true,
 TuyAPI       '9': 0,
 TuyAPI       '17': 16060,
 TuyAPI       '18': 196,
 TuyAPI       '19': 230,
 TuyAPI       '20': 2290,
 TuyAPI       '21': 1,
 TuyAPI       '22': 129,
 TuyAPI       '23': 11332,
 TuyAPI       '24': 1354,
 TuyAPI       '25': 2657314,
 TuyAPI       '26': 0,
 TuyAPI       '27': 'off',
 TuyAPI       '28': 'relay',
 TuyAPI       '29': false
 TuyAPI     },
 TuyAPI     cid: 'HIDDEN'
 TuyAPI   },
 TuyAPI   leftover: false,
 TuyAPI   commandByte: 10,
 TuyAPI   sequenceN: 2
 TuyAPI } +0ms
 TuyAPI Received DATA packet +1ms
 TuyAPI data: 10 : {"dps":{"1":true,"9":0,"17":16060,"18":196,"19":230,"20":2290,"21":1,"22":129,"23":11332,"24":1354,"25":2657314,"26":0,"27":"off","28":"relay","29":false},"cid":"HIDDEN"} +0ms
Current status: [object Object].
 TuyAPI Disconnect +2ms
 TuyAPI Socket closed: 192.168.1.155 +1ms
node:internal/errors:478
   ErrorCaptureStackTrace(err);
   ^

Error [ERR_UNHANDLED_ERROR]: Unhandled error. ('Timeout waiting for status response from device id: bf27d70310e2f30aa0u8ws')
   at new NodeError (node:internal/errors:387:5)
   at TuyaDevice.emit (node:events:502:17)
   at /home/justas/Code/tuya-programming/node_modules/tuyapi/index.js:411:12
   at Timeout._onTimeout (/home/justas/Code/tuya-programming/node_modules/p-timeout/index.js:25:13)
   at listOnTimeout (node:internal/timers:559:17)
   at processTimers (node:internal/timers:502:7) {
 code: 'ERR_UNHANDLED_ERROR',
 context: 'Timeout waiting for status response from device id: bf27d70310e2f30aa0u8ws'
}

[kardoka]

I assume that you have a 3.3 device which is special and returns and error for the normal get way and needs to be queried by "set" and then is not responding.

I am not setting any values, I just want to retrieve the latest status.

What you mean with "the exception is thrown after you processed the result"? (and in fact any "await" can throw an error)

By this I mean that the error is thrown after I retrieve the device status and disconnect.

[Apollon77]

I think you found a bug :-)) When a "get" is issued but requires a refresh then the reponse is not matched correctly ... I will provide a PR

[Apollon77]

@kardoka please der in the created issue. And test my branch please!!

[Apollon77]

@kardoka Any update?