No IP found #290
Replies: 9 comments 13 replies
-
|
Is it a battery operated device? If so, it will only connect and be visible on the network for a few seconds when it has something to report. The rest of the time it will power down and sleep. There are a few ideas discussed in #264 and #214 to get events from these devices, but none of them are particularly great. |
Beta Was this translation helpful? Give feedback.
-
|
No is a battery device. Is a breaker switch. "AT-Q-SY1 WiFi/ ZigBee Din Rail" In the 'devices.json' result of "python -m tinytuya wizard" there is none 'ip' key. Any ideas? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Are you connected to the same network as the devices, and are broadcast packets allowed on the network? If not, you can try force-scanning for the devices with |
Beta Was this translation helpful? Give feedback.
-
|
i am having the same issue with new version of smart plug with power monitoring older devices worked. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting. I wonder if these are devices with a new firmware version that doesn't broadcast UDP discovery packets the same way or just has issues on the local network. I see you did a force scan and it identified two devices that it couldn't identify: 192.168.86.183 and 184. Could these be the devices? 
You could try debug mode as well: python -m tinytuya scan -force 192.168.x.y/24 -d |
Beta Was this translation helpful? Give feedback.
-
|
Correct 183 and 184 are the devices. i have reserved them ips. I was also able to get device ids and local keys from raw json file. I will try debug mode when i am back at home. anything else you need these are new devices they even appear slightly different on the tuya smart app. |
Beta Was this translation helpful? Give feedback.
-
|
What version of TinyTuya do you have? |
Beta Was this translation helpful? Give feedback.
-
|
its latest i updated to v1.12.9 and tried, also tried from another windows machine was the same |
Beta Was this translation helpful? Give feedback.
-
|
here is debug log hope i masked all that i need to --##maskedmasked## this is what i have replaced where its empty it was empty DEBUG:TinyTuya [1.12.9] DEBUG:Python 3.11.4 (tags/v3.11.4:d2340ef, Jun 7 2023, 05:45:37) [MSC v.1934 64 bit (AMD64)] on win32 TinyTuya (Tuya device scanner) [1.12.9] [Loaded devices.json - 5 devices] Scanning on UDP ports 6666 and 6667 and 7000 for devices for 18 seconds... DEBUG:Listening for Tuya devices on UDP ports 6666, 6667 and 7000 DEBUG:Received valid UDP packet: {'ip': '192.168.86.185', 'gwId': '##maskedmasked##', 'active': 2, 'ablilty': 0, 'encrypt': True, 'productKey': 'keyjnuy4s3kre7m7', 'version': '3.4', 'token': True, 'wf_cfg': True} Scan Complete! Found 6 devices.
DEBUG:Scan complete with 6 devices found |
Beta Was this translation helpful? Give feedback.
-
|
It looks to me like the device isn't broadcasting and the brute-force version detection in the scanner isn't working. Since it is accepting connections I suspect it will work if you pass the correct version to the |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing exactly the same thing with newer firmware plugs. Thinking I might have to write my own code to supplement the json with fixed IPs, unless there's a chance this will get fixed? |
Beta Was this translation helpful? Give feedback.
-
|
Fix what? If device broadcasts aren't being sent/received and the device isn't responding to force-scans then there really isn't anything we can do in TinyTuya. You're going to need to contact the device manufacturer and see if you can get them to fix their firmware. At this point I suspect it is an incompatibility between the device and the WiFi router. I bought both of the devices linked to by @demonreeper (as well as a 3rd in a different listing from the same seller) and all 3 have been working fine for me without issue for over a month; I'm running a UniFi UAP-AC-Pro access point (running an older firmware as all the newer ones are horribly broken for IoT devices) and a generic Linux box handling DHCP and gateway/router duties. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, perhaps I should have said "resolved" rather than fixed; wasn't trying to suggest tinytuya was at fault! I've actually realised it was user error on my part; I use Node-RED and it seems my newer plugs ("Defender Mini Plug") don't broadcast or accept secondary connections unlike my earlier Teckin SP27 plugs which both broadcast and accept additional connections. Thanks for the great software, I'm just going to have to switch a few plugs around so I can do what I need with the ones that play nicely. |
Beta Was this translation helpful? Give feedback.
-
|
I'm running 6.2.49.14111 on everything as I've found 6.4.x and 6.5.x to all have major issues with devices dropping offline for no apparent reason. I've seen posts in Ubnt's forums and on Reddit saying others are seeing the exact same issue, so it's not just me. The UAP-AC-Pro and U6-LR also seem to be a bit more reliable for IoT devices than the UAP6MP. Do you have a link for those plugs? I'm always interested in picking up "problematic" devices to poke at. |
Beta Was this translation helpful? Give feedback.
-
|
I got them off Amazon in the UK: Defender Mini Smart Plug They are physically bigger than the Teckin plugs I've used previously, so don't fit in a four-way extension lead, and as I put in my updated post they just don't broadcast or support second connections when my Node-RED is connected to them, which is frustrating but I can probably get round it. Interesting on the Unifi firmware. Now you mention it, the Teckin plugs do have a habit of losing their minds once in a while (flashing orange) and I need to readopt them, but I don't know if that's caused by Wi-Fi issues, I'll have to try downgrading one of my APs and pinning the plugs to that. |
Beta Was this translation helpful? Give feedback.
-
|
I don't suppose anybody has found a solution to this? Just picked up a switch that has the behavior. No IP or Version is found. {
"name": "BR Switch",
"id": "ebb1a838262de95b89glbe",
"key": "--------",
"mac": "a8:80:55:84:73:5b",
"uuid": "956cb19ca1b75dee",
"sn": "100103513001B0",
"category": "kg",
"product_name": "WIFI Smart Switch",
"product_id": "dn7fpj6lcz3krzbv",
"biz_type": 18,
"model": "NH-\u7f8e\u5f0f\u5355\u706b\u6309\u952e\u4e00\u8def",
"sub": false,
"icon": "https://images.tuyaus.com/smart/icon/ay1554975589161DYAhk/76f66b4c3a3ce2567c60ee4f736ae57d.png",
"mapping": {
"1": {
"code": "switch_1",
"type": "Boolean",
"values": {}
},
"7": {
"code": "countdown_1",
"type": "Integer",
"values": {
"unit": "s",
"min": 0,
"max": 86400,
"scale": 0,
"step": 1
}
},
"14": {
"code": "relay_status",
"type": "Enum",
"values": {
"range": [
"power_off",
"power_on",
"last"
]
}
},
"15": {
"code": "light_mode",
"type": "Enum",
"values": {
"range": [
"none",
"relay",
"pos"
]
}
}
},
"ip": "",
"version": ""
} |
Beta Was this translation helpful? Give feedback.
-
|
You can try |
Beta Was this translation helpful? Give feedback.
-
|
Yeah unfortunately that does not seem to be doing the trick for me. I've pinged the manufacturer and will cross my fingers that they will care enough to do something about it, but I have my doubts. |
Beta Was this translation helpful? Give feedback.
-
"python -m tinytuya wizard" founds my 2 devices but can't found the devices IP. Then, I can't work locally.
Beta Was this translation helpful? Give feedback.
All reactions