-
|
Bug description: Constantly getting: Provided:
|
Beta Was this translation helpful? Give feedback.
Replies: 17 comments 23 replies
-
|
Bug description: Constantly getting: Provided: device id (also tried w/ uuid) device link: https://www.lazada.com.ph/products/i2894646694-s14066635798.html?urlFlag=true&mp=1&tradePath= |
Beta Was this translation helpful? Give feedback.
-
|
Previous issues may have some clues about what others have encountered;
|
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error on the logs:
I uninstalled smart life app just to make sure.. do I have change the ip address for this device? |
Beta Was this translation helpful? Give feedback.
-
|
This looks like #408. Do not set your IP address to "Auto" if you have localtuya installed, it will not work as the mechanism to find tuya IP addresses on the network is already in use by localtuya. Instead, set it to the actual IP address of the device. |
Beta Was this translation helpful? Give feedback.
-
I tried to add the ip address and i'm still getting the same issue. Do I need to completely remove local tuya? Because right now it's just disabled. also got a different log now:
|
Beta Was this translation helpful? Give feedback.
-
|
Seems like I am having an issue with a specific device. I was able to add the same device brand/model on a different part off the house. I just not seeing all the entities. What else can I check if that's the issue? |
Beta Was this translation helpful? Give feedback.
-
|
The log message "Detected blocking call to sleep" only comes when the protocol is set to Auto. You may need to restart HA after changing the config to flush out the old connection. |
Beta Was this translation helpful? Give feedback.
-
|
seems to be working now. thanks! I think the other integration is interfering with this one. |
Beta Was this translation helpful? Give feedback.
-
|
So must we assign static IPS to all devices? Auto use to work but yes now I am having issues once the IPs have changed. |
Beta Was this translation helpful? Give feedback.
-
|
If you have localtuya installed, Auto IP detection will not work (or vice versa - if it works for this integration, it will break localtuya). This is even with different devices configured in the different integrations, as the address detection uses a broadcast discovery protocol, which can only have a single listener on each IP address. |
Beta Was this translation helpful? Give feedback.
-
|
Tried everything - seems latest update from TUYA has somehow removed the ability to control devices locally. Can provide logs/info if needed @make-all |
Beta Was this translation helpful? Give feedback.
-
|
If you can get any logs from the device, then it may be worth providing them. The firmware update may have changed the protocol version, or it may have changed the dps layout. It seems unlikely that Tuya would remove the local control completely, as the mobile app also uses local control when it is on the local network, so it would affect the user's perception of performance to force them to go via the cloud. |
Beta Was this translation helpful? Give feedback.
-
Sadly, I think you're right. |
Beta Was this translation helpful? Give feedback.
-
|
I have a similar problem to the one I had a few posts earlier with the Tuya socket. More specifically, the problem with not being able to add it to tuya-local. What's interesting is that it's not added to Local Tuya either, but it is added to the standard integration. When adding through this integration, I get the following error in the logs:
I take the device_id and local_key from iot.tuya.com. In HomeAssistant itself I get an error Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect. The socket itself is known to work in the Tuya ecosystem; in the standard integration it is defined as smart plug (4ntsx9vymmfcwi7y) and it is possible to control the socket itself from the HA, to see the U, I, P values, as well as the child lock switch, on/off indicator and setting the last state. Get Device information on this socket at iot.tuya.com gives the following information (I have closed some of the private information) { |
Beta Was this translation helpful? Give feedback.
-
|
In 2023.5.1 version of tuya-local the socket was added. On default setup. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @make-all I'm having issues with the Bluetooth gateway and Tuya lights. I have Bluetooth gateways of versions 3.3 and 3.4, as well as 19 CCT lights. When using Tuya local, I can only connect three lights to one gateway. When I try to add more, I receive an error messages: However, if I remove one of the lights and try to add another, it successfully connects. For example, let's say I have light 1, light 2, light 3, and light 4. If I add lights 1, 2, and 3, and then try to add light 4, I receive an error. But if I remove light 3 and try to add light 4, it works successfully. In a previous discussion or related tickets, you mentioned that Tuya devices can only support up to three connections. Could this be the issue? Since the gateway and each light are treated as separate devices when added via the gateway, we have a situation where the gateway only supports three connections to Tuya local. A possible solution could be allowing the "node ID" to include all 19 light IDs, creating a single connection between the gateway and Tuya local. Are there any other alternatives? |
Beta Was this translation helpful? Give feedback.
-
|
After writing the message, I thought of another scenario. I tried not to remove light 3 but instead disabled it and then added light 4, which was successful. Then I attempted to enable light 3 again, which allowed me to, however its status became unavailable. As soon as I disabled light 4, light 3 immediately became accessible. |
Beta Was this translation helpful? Give feedback.
-
|
Its probable that the gateway only supports 3 simultaneous local connections. The subdevice support is quite simple and does not try to reuse connections between devices on the same hub, so a connection is opened for each device. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your response. Yes, it seems that the issue is indeed related to the limitation of the gateway supporting only up to three connections. However, do you think that the problem lies specifically with the three connections of the gateway I have? Because, as I mentioned, I have two different gateways (nous and moses) with the exact same situation. If this is a restriction imposed by Tuya, then the use of the gateway essentially becomes pointless. Both of my gateways can support up to 50 devices. If tuya local can only handle up to three connections, then essentially, if I have 50 BLE devices, I would need to purchase an additional 17 BLE gateways just to connect all of them to tuya local. Perhaps you have encountered BLE gateways yourself that support as many internal connections as the number of devices that can be connected to the gateway? |
Beta Was this translation helpful? Give feedback.
-
|
Gateway support is relatively new in tuya-local, and the implementation is simplistic, making a connection per subdevice the same as if they were separate devices on WiFi. So we are still getting to know about what limitations there are in the hubs. It may be possible to share connections, so in future more devices can be supported within these limitations, but that is not high on the priority list at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
I've come across a "Smart Wired Multi-mode Gateway ZigBee WiFi Bluetooth Mesh Hub" that appears to support BLE device connections beyond the three-device restriction. This gateway seems capable of efficiently managing more devices simultaneously, which could offer an alternative for those looking to expand their smart home ecosystems without the additional gateways. Here is a link to the device for reference: https://moeshouse.com/products/moes-gateway-mhub-ms Additionally, there seems to be another issue arising from the use of the gateway where a separate connection is created for each lamp between the gateway and home assistant. This approach could quickly become unwieldy, so I'll create a separate issue to allow for future consideration of this area's development when time permits. |
Beta Was this translation helpful? Give feedback.
-
|
I have a 6 smart plugs that won't connect to this integration, and 4 that will. The 6 that won't integrate have the "Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect." error message. I've discovered that I cannot ping the devices that have this error from the terminal window in Home Assistant. Why would some of the plugs communicate, and some will not? Is there a way to enable this communication between the plugs and Home Assistant? |
Beta Was this translation helpful? Give feedback.
-
|
Don't know if this has been answered before, but i followed the first 10 advices in this discussion without succes.. |
Beta Was this translation helpful? Give feedback.
-
|
same here, got a switch back to life by blocking it inside the deco app and unblocking a few seconds after. |
Beta Was this translation helpful? Give feedback.
-
|
There are 8 light tracks that work as children with their own gateway PRO X2P (a special wireless protocol, not WiFi!). I wrote a converter for tuya-local and was able to add 3 devices following the instructions (gateway ID + key + sub node ID) - they work excellently , but the remaining ones are not getting added, no matter which protocol I choose. I have also tried restarting (the light bulbs work fine in the mobile application). The error in the logs is as follows: subdevices{
"result": [
{
"active_time": 1688218790,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bf759f2bad7e38237evnwz",
"name": "lamp 5",
"node_id": "01e14c5bf2",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488910
},
{
"active_time": 1688218792,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bfae12c3ed86ba9906svro",
"name": "lamp 6",
"node_id": "01e14c60f9",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488910
},
{
"active_time": 1688218783,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bf98c965eac8d5e59fzuqn",
"name": "lamp 3",
"node_id": "01e14c53c8",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488909
},
{
"active_time": 1688218795,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bfe25f3477c0964b17wbsn",
"name": "lamp 7",
"node_id": "01e14c608e",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488909
},
{
"active_time": 1688218786,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bf4fc94f35e6197d28osdm",
"name": "lamp 4",
"node_id": "01e14c60e3",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488909
},
{
"active_time": 1688218798,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bf629db68416b1b9a1qkzk",
"name": "lamp 8",
"node_id": "01e14c6376",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488909
},
{
"active_time": 1688218181,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bf981d173f64bb664bejln",
"name": "panno",
"node_id": "0120139a04",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488908
},
{
"active_time": 1688218184,
"category": "dj",
"icon": "smart/program_category_icon/dj.png",
"id": "bfc189bbe2f98dfd26vxaj",
"name": "work desk",
"node_id": "012213de36",
"online": true,
"owner_id": "36487050",
"product_id": "fkxcslivaluonzdp",
"update_time": 1709488908
}
],
"success": true,
"t": 1709489619341,
"tid": "c28b5dd9d98911ee9a28e612834bce39"
} |
Beta Was this translation helpful? Give feedback.
-
|
This is issue #1054, caused by a limit on the number of connections the hub will accept |
Beta Was this translation helpful? Give feedback.
-
|
We are eagerly awaiting the fix. |
Beta Was this translation helpful? Give feedback.
-
|
I have several https://www.aliexpress.com/item/1005002877713892.html There are still minor problems with aubess_1gang_switch.yaml:
I've also fixed # 1 and # 2 in my local config. But I don't know what to do with the protocol issue and how to manage # 3 and # 4 (not ordinary types). Query Things Data Model List of DPS from diagnostics |
Beta Was this translation helpful? Give feedback.
-
|
Dear community I have a Wifi Sensor that is installed in a water tank measuring water level I receive from time to time this kind of errors Indeed the water tank is making the wifi connection sometimes unstable (depending also on weather as the tank is underground) So there is no bug, just the reality of life. My question is. Is there a way to configure the integration so that:
Indeed a water level is not moving every 15 seconds... so most of the errors could be removed / Have no functional impact I know within HA i can already keep the last read value by using a sensor template so this is already great (do not know if this could be automatically proposed as an option/configuration in the integration) Thanks for your answers (and sorry if my question is basic for you) |
Beta Was this translation helpful? Give feedback.
-
|
As long as the sensor is not set to |
Beta Was this translation helpful? Give feedback.
-
|
Many Thanks for your answers. So i understand from your answer that errors are not coming from a bad/intermittent wifi connection but more with a problem in the messages sent from the sensor ? correct ? |
Beta Was this translation helpful? Give feedback.
-
|
I tried to understand why i get errors in debug mode i see the following log. Does anyone has a clue to what is happening ? 2024-04-23 19:04:33.010 ERROR (MainThread) [custom_components.tuya_local.device] Failed to fetch device status for Niveau cuve - Eau de Pluie - E0 - Jardin |
Beta Was this translation helpful? Give feedback.
-
|
I continue to investigate on my own my issue (WIFI sensor that is not 100% available due to physical position and coverage) I noticed this error earlier in the logs 2024-04-28 14:40:39.310 WARNING (SyncWorker_0) [custom_components.tuya_local.device] Niveau cuve - Eau de Pluie - E0 - Jardin protocol error 905: Network Error: Device Unreachable seems that this is coming from tiny tuya error code 905 - Network Error: Device Unreachable then i get the recusrive error every 15 second It is hard to believe that it is coming from the device itself (because the device is unreachable). Anhone can help me in my investigation ? My question is. Is there a way to configure Home assistant so that:
I know within HA i can already keep the last read value by using a sensor template so this is already great (do not know if this could be automatically proposed as an option/configuration in the integration) Thanks for your answers (and sorry if my question is basic for you) |
Beta Was this translation helpful? Give feedback.
-
|
Happy Friday, I can use some help please. I have looked at all the pinned issues and still cannot get some devices to link. The first Test protocol error 901 was with IP address or hostname set to: auto
What's odd is I bought a 2-pack of the same floodlights and the first two have a different image in Smart Life and a also have different product_id's & product_name's.
The two that worked/linked auto selected rgbcw_lightbulb.yaml and they have all functions via HA. These are the lights: https://www.amazon.com/gp/product/B0BZ46Z2CG
Thank you in advance. Walter (Sandy) |
Beta Was this translation helpful? Give feedback.
-
|
Did you try all protocol versions? |
Beta Was this translation helpful? Give feedback.
-
|
Also some issues here:
It seems to find Device id and Local key just fine. But connecting is an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Have tha same trouble! (( Has several WiFi devices connected with LocalTuya, but last time some of them very often fall off for 1-2 minutes. Try to test Tuya Local. Connected one of them without any problems. And I noticed that the number of dumps has decreased several times with Tuya Local. But when I try to connect at least some other device - I always get the same error (( |
Beta Was this translation helpful? Give feedback.
-
|
I have the same error when setting up the integration - I cannot add the device, even though all the settings match. The device_id and local_key are taken from Tuya IoT, the IP is assigned by the router, and I have tried all protocol versions. |
Beta Was this translation helpful? Give feedback.
-
|
FYI one solution I found is if the device's ip has changed and you cannot change it on the UI and getting the unable to connect issue. Under homeassistant's .storage folder edit and change the IP address in the "core.config_entries" file and then restart home assistant and viola it connects fine i.e. under /.storage/core.config_entries Find your tuya device ip and edit it both data and options host ips e.g. hope this helps edit: unsure why this happens maybe something during init when it fails to connect cc @make-all |
Beta Was this translation helpful? Give feedback.
-
|
The problem is similar. I have an RSH Star Projector. I'm sure the device data is good. It gives the error as soon as I press the key. |
Beta Was this translation helpful? Give feedback.
Previous issues may have some clues about what others have encountered;