Yes Im seeing drops too, my graph seems to keep going but the device list is flashing with devices showing online then greyed out offline.
A lot of the ones that are dropping are Ring security camera’s and also an android phone. It also seems to be focused on my AP that’s in mesh mode, the devices connecting to that AP keep dropping and re-joining.
The other issues I was having with multicasting and all that seem to still be fixed.
@WhyAydan sorry to hear about the troubles. Did you reach out via chat? Matt and I have replicated this internally, and we’re digging into it further.
I’m not going to be able to do this at scale, but I can help a some people revert if you need an immediate temporary fix, and there are technically options. Please reach out via DM or chat here on the forum.
Obviously this is very high priority for us; we’re on it.
It does not seem to be limited to the AP on mesh after looking a bit longer.
I downgraded mine back to the older build and then upgraded them back to 2.0a to see if there is any difference but still seeing the same.
I also set the SSID to only 2.4ghz to see if maybe they were bouncing back and forth off 2.4 and 5ghz between AP’s and that’s not it same devices are showing the same on 2.4ghz only.
I think both 2.0a and 1.1q-4 are both affected, but I haven’t actually cofirmed the latter yet. Not sure which you’re trying. I think the last good dev build may have been 1.1p-dbg2 (aka 1.1p-dirty), at least for one that includes multicast improvements.
If you guys ping @Alta-MikeD a message he will then be able to drop the firmware version for you. Don’t think the downgrade path has been publicly released just yet.
Since the new firmware i have dropped connections and teams errors due to connection. Can i revert the firmware? If i am pitching a new customer on IT cases and my wifi disconnects… uhhh bad story. so please were can i revert the firmware because is was stable before,
I’ve reached out to a few of you directly, but we believe we’ve resolved an issue that has occurred on a small percentage of sites, particularly those with shorter DHCP lease times. Please reach out to me if you’d like to try out the next release that addresses these issues, but it should be going out soon, either way.
It can definitely (and very likely will) still impact those with longer DHCP lease times, but it seems to cause more issues especially with those with shorter lease times. Those “No such r0 nor r1” error messages are innocuous when fast roaming is disabled, and will be removed in the next test release.
Yes, I can. We’re preparing the updated build for release, and it should be out later today. I can upgrade you to 2.0b RC1 now if you’d like to see if it fixes your case, or if you want to wait for the final tag to be ready, it probably will be out later this afternoon.
So far it’s fixed it for other affected users who we’ve worked with.
Came here because I was having dropped wifi issues over the last two days. When I logged into my Pro unit it showed 2.0a and had 2.0b ready to download/reboot.