Unknown device, IP not found

[franzudev]

Hi, I'm having trouble trying to use the music mode from Home Assistant on two lamps.

I have two ambient lamp, they acts like a led strip and it works fine in Home Assistant, but I can't use the music mode in HA, but in the Smart Life app yes.
I imagined that I can use tinytuya to make a script and/or an integration for HA, but given that I have all the infos of the devices, I can't use it, am I doing something wrong?

Scanning doesn't get me any device, but force scanning does, the problem is that for my two devices the result is:

Logs of the force scan

  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044fa82dabcef7497df4d645112e0fe06e317604e5668d52b044ba17f3ae3a12a61401fe9ac8f265df1dc1f25145aea5cf56a8d56133ac396b6a91fb63845dbd0d50000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961624fbdfc4dff5e1d671aec6eef0a241d813b068857c67b3a0aac80b1778030667300009966'
  DEBUG:Force-Scan Found Device 192.168.178.69
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044287ce327baf71a962493935260bc80598500f9b3bff010b902a6ee0bf3b97bfecf461ea3c26a84df8c094740b55cf97671e0f6770d2e6d8a0c5c3042356723700000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c30313233343536373839616280a14996859e8fea1cbec15d3ca23c53379b03187071c2bb19d902d09f3f807500009966'
  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044e48f686d2b1b00f4f7918a9c9d7ef80ff7136b762708a582e4f375a6b56ea9d7a1c3b165dc5f208eaa62733c3d27b95a6c223ee543e5eb84027f3608393f9faa0000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961620f3333fb3ed491fb0fb899674213c4094773b0e16ecd9906f06ee0d53ff9219600009966'
  DEBUG:Force-Scan Found Device 192.168.178.69
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044fa82dabcef7497df4d645112e0fe06e317604e5668d52b044ba17f3ae3a12a61401fe9ac8f265df1dc1f25145aea5cf56a8d56133ac396b6a91fb63845dbd0d50000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961624fbdfc4dff5e1d671aec6eef0a241d813b068857c67b3a0aac80b1778030667300009966'
  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044117059d8d2d8e9bd64551d1d6e8f779c7db16cdccb7fa00472d3e464342a547707a35869b4ac443277c1708a2f16696e86bf64f228676a2c59d984b561b854e70000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961621bdd7c4034c20d330255b6627c7997a26726a63be42cc510ce07dbd1dde19e6d00009966'
  DEBUG:Force-Scan Found Device 192.168.178.69
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044e48f686d2b1b00f4f7918a9c9d7ef80ff7136b762708a582e4f375a6b56ea9d7a1c3b165dc5f208eaa62733c3d27b95a6c223ee543e5eb84027f3608393f9faa0000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961620f3333fb3ed491fb0fb899674213c4094773b0e16ecd9906f06ee0d53ff9219600009966'
  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa00000001000000030000004489922fbc28cebf4a80acf359cb0be110c559df4b9e128eb9205c4fe6f9ac3846396fbd334996d19203f428684b58c35fe058126c4e77083a1957199fc5de41270000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c303132333435363738396162376999dcdcaa0767050e0485a0d522d08df762ac6d1f46789853c8d65f47959900009966'
  DEBUG:Force-Scan Found Device 192.168.178.69
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044117059d8d2d8e9bd64551d1d6e8f779c7db16cdccb7fa00472d3e464342a547707a35869b4ac443277c1708a2f16696e86bf64f228676a2c59d984b561b854e70000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961621bdd7c4034c20d330255b6627c7997a26726a63be42cc510ce07dbd1dde19e6d00009966'
  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044287ce327baf71a962493935260bc80598500f9b3bff010b902a6ee0bf3b97bfecf461ea3c26a84df8c094740b55cf97671e0f6770d2e6d8a0c5c3042356723700000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c30313233343536373839616280a14996859e8fea1cbec15d3ca23c53379b03187071c2bb19d902d09f3f807500009966'
  DEBUG:Force-Scan Found Device 192.168.178.69
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa00000001000000030000004489922fbc28cebf4a80acf359cb0be110c559df4b9e128eb9205c4fe6f9ac3846396fbd334996d19203f428684b58c35fe058126c4e77083a1957199fc5de41270000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c303132333435363738396162376999dcdcaa0767050e0485a0d522d08df762ac6d1f46789853c8d65f47959900009966'
  DEBUG:Force-Scan Found Device 192.168.178.68
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload encrypted=b'000055aa000000010000000300000044fa82dabcef7497df4d645112e0fe06e317604e5668d52b044ba17f3ae3a12a61401fe9ac8f265df1dc1f25145aea5cf56a8d56133ac396b6a91fb63845dbd0d50000aa55'
  DEBUG:final payload: b'0123456789abcdef'
  DEBUG:payload [3] encrypted=b'00006699000000000002000000030000002c3031323334353637383961624fbdfc4dff5e1d671aec6eef0a241d813b068857c67b3a0aac80b1778030667300009966'
  Scan completed in 12.1125 seconds
  Unknown v3.4 Device   Product ID = ?  [Failed to Force-Scan, FORCED STOP]:
      Address = 192.168.178.68   Device ID =  (len:0)  Local Key =   Version = 3.4  Type = default, MAC =
  Unknown v3.4 Device   Product ID = ?  [Failed to Force-Scan, FORCED STOP]:
      Address = 192.168.178.69   Device ID =  (len:0)  Local Key =   Version = 3.4  Type = default, MAC =

Having all the infos, makes a difference?
Here's the snippet I'm trying to use:

import tinytuya

d = tinytuya.Device(
    dev_id="XXXXXXXXXXXSXXX",
    address="192.168.178.69",
    local_key="XXXXXXXXXXXXXX",
    version=3.4
)

print(d.status())

Tried with classes Device and BulbDevice but receiving this with version 3.4+:

{'Error': 'Check device key or version', 'Err': '914', 'Payload': None}

and this with version <3.4:

{'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}

There's a way I can try to send the command to set the music mode?

[uzlonewolf]

Most devices don't accept more than 1 or 2 connections, so make sure HA is stopped and the SmartLife app is closed before doing the scan. If you are running HA and TinyTuya on the same machine then they will fight over who gets to receive the device broadcasts as well.

That said, what are you expecting music mode to do? Most bulbs do not have built-in microphones and so the light show is generated by the app using the phone's microphone and sent to the bulb via a sequence of DP 28 updates. The bulbs/strips which do have a microphone usually activate it by switching to a special scene (the strip controller I have sets DP 25 to "000e0d0000000000000000c80000").

[franzudev]

Thanks for the response, I've closed the SmartLife app, but didn't stopped HA, maybe that was the cause. I'll get it a try.

[franzudev]

I've managed to solve the issue by closing the SmartLife app, stopping HA, and running the following script (after a scan, since devices.json is needed for the local keys):

import json
import tinytuya

IP = "192.168.178.69" # the IP of your device
VERSIONS = [3.3, 3.4, 3.5]

with open("devices.json","r") as f:
    devs = json.load(f)
if isinstance(devs, dict) and "devices" in devs:
    devs = devs["devices"]

def try_one(dev_id, key, name, ver):
    d = tinytuya.Device(dev_id, IP, key)
    d.set_socketPersistent(False)
    d.set_socketTimeout(3)
    d.set_version(ver)
    r = d.status()
    ok = isinstance(r, dict) and "dps" in r
    return ok, r

for ver in VERSIONS:
    print(f"\n=== Testing IP {IP} with version {ver} ===")
    for dev in devs:
        dev_id = dev.get("id")
        key = dev.get("key")
        name = dev.get("name", "")
        if not dev_id or not key:
            continue
        ok, r = try_one(dev_id, key, name, ver)
        if ok:
            print("\nMATCH FOUND")
            print("name:", name)
            print("id:", dev_id)
            print("key:", key)
            print("version:", ver)
            print("status:", r)
            raise SystemExit(0)

print("\nNo match found.")

Thanks to this script I found out that my devices use protocol version 3.5 instead of what TinyTuya reported during the scan. From that point on it was straightforward to send commands to the devices, since all properties are available in the Tuya Cloud API Explorer, and mapping them in HA is trivial thanks to the integration xZetsubou/hass-localtuya.

[jasonacox]

Nice! Thanks @franzudev - Did you see the wrong verion in the scan / wizard setup?

[franzudev]

@jasonacox Yes, all the logs are in the first post, but to keep it short, the scan found 3.4 unknown devices.

[jasonacox]

Thanks for reporting this! You're absolutely right - the scanner output was misleading when it couldn't determine the actual protocol version.

What was happening:

When the scanner sent unencrypted queries and the device accepted the connection but then immediately closed it (3 times), this is characteristic behavior of v3.4/3.5 devices that require encrypted session key negotiation. However, the scanner was incorrectly reporting these devices as "v3.4" even when it never got a response to confirm the actual version.

The fixes:

Corrected v3.5 detection priority - When testing both v3.4 and v3.5 protocols, the code now checks for the v3.5 prefix (0x00006699) first, then v3.4 (0x000055aa). This fixes cases where v3.5 devices were being misidentified as v3.4.

Accurate version reporting - Devices that never respond will now show version 0.0 (displayed as ??) instead of falsely claiming to be v3.4.

Clearer error messages - When version can't be confirmed, the output now includes context like "likely v3.4 or v3.5" to explain why we couldn't determine the exact version.

I'm opening an issue to track improving the scanner messaging and will submit these changes as a PR shortly.