One L535 involves a local smart action, but other L535 exact same version and firmware does not
Automation 1: When motion (T100 + H200) detected, turn on a L535 => local action
Automation 2: When motion (T100 + H200) detected, turn on other L535 => NOT local action ¿why could this be?
I even tried using the same T100. It is never a local action.
Editing "Automation 1" using the same T100 as "Automation 2" is still a local action.
The only difference is which light bulb they are tuning on.
I don't understand what's happening, because both L535 have the same hardware version, the same firmware, and they even were bought together. Why for this particular L535 its automations are never local?
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
When creating a local smart rule, all the involved devices must be connected to the same network (subnet). If any device is located in a different network, the local smart rule cannot be created successfully.
Are there two bulbs connected to the same WiFi? Pay attention to the guest WiFi, iot network, or the WiFi signals created by network extension devices. For example, it will be a problem if one device is in the main network while the other is in an isolated guest wifi.
- Copy Link
- Report Inappropriate Content
>Are there two bulbs connected to the same WiFi
Yes. Actually, one is physically next to the other.
I thought rebooting everything (router, hub h200, and turned off and on again the light bulbs) would fix the issues… but the effect was the exact opposite.
Now all the configured actions, except for one, are no longer local, and I can't create or update any new local actions. I have no idea what's happening here. It just rebooted, and now, not only is that single action wrong, they are all wrong! (except for one). This is for everything, not only the L535 light bulbs.
- Copy Link
- Report Inappropriate Content
What's the firmware version of your Tapo H200? How many H200 do you have? Do you have other Tapo hubs?
- Copy Link
- Report Inappropriate Content
>How many H200 do you have?
Two
>What's the firmware version of your Tapo H200?
Both the same latest firmware: Version:1.6.0 Build 20250915 rel.33520
>Do you have other Tapo hubs?
No. Only the two H200
Now, some automations that were flagged as 'local actions' since the beginning are no longer local. It involves a motion sensor turning on an L520 light bulb. I don't know why the action is no longer local. Every automation, including this L520, isn't local anymore. However, nothing has changed in the network.
- Copy Link
- Report Inappropriate Content
To assist with this case, a specialist will help to follow it up through email. Please check your inbox later to confirm.
If the email you used to register for the TP-Link community is not your contact email or you cannot access it, please send me your contact email through private message.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@hhh3 so its supported only by h100 hub and with beta firmware, h200 doesnt support multiple triggers or if you put anything in if. The engineering team told me it will be implemented, but who knows when, maybe never.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 83
Replies: 7
Voters 0
No one has voted for it yet.