I have about 35 Tasmota devices in my home with my Google WiFi Mesh system. Things started out pretty good when I initially deployed the WiFi mesh system back in March 2020, but some time in December 2020 / early January 2021 I started having Tasmota connectivity issues. Analysis showed that the Tasmota devices on the mesh system were connected to an access point. Probably because the signal strength was stronger at the access point (and physically closer). In troubleshooting, I took the access points down, the Tasmota devices that were in overlapping wifi coverage area came back online in minutes. Some devices cannot come back online because they are outside of the coverage area. I’m at a loss as to why this is happening and what to do.
I have read this, Device disconnects from Wi-Fi often, and it appears that mesh networks with advanced features could be a problem. Does anyone else use Google WiFi Mesh network with Tasmota devices successfully?
With ESPhome you can hard code the Mac address of the access point that the device should connect to. I had issues with this as well when I used an unmanaged system with multiple access points. If it helps, I’m now using a TP-Link / omada deployment with a omada-controller container running that actively pushes clients off one and onto another access point when the signal is low. It also managed the coverage overlap by using different channels at each point. It works great and I no longer have these problems.
Thanks for your reply. I was hoping to keep my Google WiFi Mesh system, but the more that I read about it, the more it appears that I need to get rid of it if I want to keep my Tasmota devices.
I scored these access points for about $30 a piece and they are just as performant as the unifi stuff. The controller software is also super powerful but easy to use. As long as you have a docker host running somewhere, it can manage all kinds of complex wifi stuff like balancing, vlans, multiple ssid’s, etc. All in, I’m at like $150 for three access points and a managed switch.
Ive wired each of mine back to the main switch (so no mesh). Using the newer EAP-225v3 (like $60 each on Amazon) then yes you can set these up to mesh with no need to wire them in other than to power them up. The mesh requires you run the controller software though, so you’ll need an always on host (like a Linux server running docker, or the TP-Link cloud controller).
ok, all sounds good. I guess I am confused about how a wired access point is different from a wireless access point (what I believe is the cause of my Tasmota issues here).
Yeah it comes down to confusion around the term mesh. Typically, a mesh network means the access points don’t need to be wired together to handle the backhaul traffic. Instead, they use a separate wireless signal to send traffic back to the router. Wiring the access points together is not really a mesh in that sense, though the clients still may only see one ssid even though they can hop access points when moving around the house.
Edit: I’m not a networking specialist so I could be way off here.
And in terms of the difference, I think the magic is in the amount of control you will get over the system using a pro-sumer setup from unifi or omada. I think the systems are designed to manage these things better.
I have an issue with a flashed Sonoff RF Bridge. It worked fine with the Sonoff firmware, but after flashing with Tasmota and Portisch, it appears that it conflicts with my desktop (Win10 Pro).
If I disable my desktop network adapter, the bridge appears on the wifi (Asus mesh). It will happily stay on wifi for hours, but within minutes of turning my desktop back on, it gets kicked off the router.
It will come back on intermittently, but I can’t work out any pattern. Something on my desktop is affecting it.
I have two other Win10 machines - a server which is on the whole time and a laptop. Neither interfere with the bridge wifi. This is driving me nuts.
In a similar boat. I have around 35 tasmota devices in the home and switched over to a T-Link mesh network in November. Connected the DECO’s with an ethernet backhaul and disabled my modem’s wifi. My devices wouldn’t stay connected. Eventually renamed my wifi and everything went back to normal.
Until I installed fiber in Feb. Not much has changed, fiber modem runs a lan cable to my router. My router did move closer to the fiber modem but the rest is still the same, router has a lan cable to my main DECO as accesspoint 1, then there is another lan cable from deco1 to deco2. My devices started have issues staying on the network. I renamed my network again, nothing changed. reset and rebooted decos, replaced lan cables, played with the beam forwarding settings on the decos… nothing is working.
My automations pretty much work all of the time, but if I hit a light switch on sometimes it disconnects immediately from the network and HA doesnt see that the command went through, even though the light is on. Other times it takes a few on and offs to disconnect…
I’m not too sure what happened, but this issue just went away for me. (Well, mainly. I have 1 device that is just about outside of the Wi-Fi range that sometimes disconnects. Being patient and it works itself out.)
I did read elsewhere that there was an issue with one of the Google Wi-Fi software updates. I didn’t take note of the software version before the issue and after, so I unfortunately do not have any further details. One thing to note is that I had 3 Google Wi-Fi devices running (1 router and 2 access points). The router and 1 of the access points was using the same channel. So I took that access point down and was running 2 different channels. I have not turned that access point back on. So there is a bit of me that suspects that there was an issue with the duplicate Wi-Fi channel. I will have to keep this in mind for the future if coverage becomes an issue again.