cli
cli copied to clipboard
Troubles with Lohas devices
Hello, I have 4 spotlights and a bulb from Lohas:
I can control them using the Tuya app, and they appear in my Tuya developer portal. However, when I try to scan them, I mostly receive ECONNRESET errors across all protocols:
➜ ~ tuya-cli get --ip 10.6.9.69 --id <my device id> --key <my devce password> --protocol-version 3.1
node:events:496
throw er; // Unhandled 'error' event
^
Error: Error from socket: read ECONNRESET
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:26)
at Socket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on TuyaDevice instance at:
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:12)
at Socket.emit (node:events:518:28)
[... lines matching original stack trace ...]
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v20.11.1
➜ ~ tuya-cli get --ip 10.6.9.69 --id <my device id> --key <my devce password> --protocol-version 3.2
node:events:496
throw er; // Unhandled 'error' event
^
Error: Error from socket: read ECONNRESET
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:26)
at Socket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on TuyaDevice instance at:
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:12)
at Socket.emit (node:events:518:28)
[... lines matching original stack trace ...]
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v20.11.1
➜ ~ tuya-cli get --ip 10.6.9.69 --id <my device id> --key <my devce password> --protocol-version 3.3
node:events:496
throw er; // Unhandled 'error' event
^
Error: Error from socket: read ECONNRESET
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:26)
at Socket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on TuyaDevice instance at:
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:12)
at Socket.emit (node:events:518:28)
[... lines matching original stack trace ...]
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v20.11.1
➜ ~ tuya-cli get --ip 10.6.9.69 --id <my device id> --key <my devce password> --protocol-version 3.4
node:events:496
throw er; // Unhandled 'error' event
^
Error: Error from socket: read ECONNRESET
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:26)
at Socket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on TuyaDevice instance at:
at Socket.<anonymous> (/usr/local/lib/node_modules/@tuyapi/cli/node_modules/tuyapi/index.js:686:12)
at Socket.emit (node:events:518:28)
[... lines matching original stack trace ...]
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Node.js v20.11.1
If I nmap them, they all have the 668 TCP port open:
➜ ~ nmap 10.6.9.69
Starting Nmap 7.95 ( https://nmap.org ) at 2025-01-12 14:47 CET
Nmap scan report for ESP_B2D874.local (10.6.9.69)
Host is up (0.025s latency).
Not shown: 999 closed tcp ports (conn-refused)
PORT STATE SERVICE
6668/tcp open irc
Nmap done: 1 IP address (1 host up) scanned in 2.61 seconds
I briefly managed to communicate with 1 of them using protocol 3.1 and get a list of datapoints, but it stopped responding afterward. They all work fine in the tuya app. I find the whole Tuya stack very confusing, and that doesn't help.
Can someone help me find some clarity? and perhaps to fix my white problem?