Max Isom

That's odd, because in the screenshot it shows an error from OpenAPI (the old package that I replaced). I'd try removing and reinstalling @tuyapi/cli just to make sure everything is...

Did you try removing and reinstalling @tuyapi/cli to make sure the sub-dependencies were updated? (Shouldn't be necessary, but again not sure what else could be going on. v0.3.4 of @tuyapi/link...

That output looks really strange as well. Are you able to try inside a virtual machine so cached dependencies and anything else wouldn't affect it? You can also get keys...

@galvaof > All devices that you want to use must be registered in either the Tuya Smart app or the Smart Life app.

Hmm, that's the first instance of 3.4 that I've seen in the wild... so yes, that's probably the issue. If you send me a packet dump of when the app...

After taking a quick look at the provided packet dump, it does indeed appear to be significantly different than 3.3 / 3.1. I don't currently have plans to add support...

@harryzz that's great, thank you for taking the time to figure out the protocol! I don't have plans to implement it myself as I don't have any 3.4 devices to...

Check if the correct port is open on your target device with `telnet [ip] 6668`. Also, try running your script with the debug env var set (`DEBUG=*`).

Interesting. Do they appear as separate devices in the app? I would recommend setting `gwId` to your device ID, then `id` to `[id]_2`.

I believe the MD5 hash is the same as what's implemented in TuyAPI (see [here](https://github.com/codetheweb/tuyapi/blob/9d2e05594eadcc376661e85e9b5f440721b10c58/index.js#L248)), although I could be wrong.