I have been having multiple issues with my TP-Link devices going offline in OpenHab. I would show 20 devices offline and the Kasa app would show them online. It got even worse after the last updates on OH4.1.2. But I finally tracked it down. I have a TP-Link Deco mesh network. There is overlap in the mesh to where the devices were hopping to a different mesh node and that is when the device would go offline in OH. To fix this, I went into the Deco app and specifically assigned each device to a specific node and band. I then turned off Mesh hopping for that device. Since I did this, I have not had a single device go offline.
Iāve had similar issues with my TP-link and other wifi devices on an asus mesh network. Whenever I restart the mesh network it takes some time for the devices to āsettleā on a given mesh node and until then their status in openhab can take some time to update.
I just wait it out after a restart 
I wait it out after a restart also. But this was much later after everything is clear. They would just start to build up and next thing I would have 20 or more offline. But this seems to have helped that. It may be a timing issue in the binding, since Kasa and Amazon show them online.
It depends on how aggressive your mesh system is at rerouting devices. My NetLink Orbi had a setting to determine if devices should hop quickly or hang onto the original access point for as long as possible.
Iāve also helped some people who had too many mesh APs in a small space, simply because their system came with all of the APs. It was too much of a good thing, and disconnecting a few helped a lot.
BTW, you could probably change the title to be āWiFi devicesā, because it doesnāt really have anything to do with your TP-Link devices themselves. Mesh hopping will affect any WiFi device thatās caught between two roughly equal AP signals.
1 Like
This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.