Release Asus ZenWiFi XT8 - New Firmware: 3.0.0.4.386_45934

[bradbort]

Well this is a puzzle. Around the same day that this mesh router updated to new firmware, my nest thermostat also updated its firmware. Since that date, the nest app has shown the thermostat to be disconnected about once a day. Rebooting the router does not help. Rebooting the thermostat does. Lots of chit chat on the google/nest forum about the firmware creating issues, some connectivity, but it seems to be limited to older nest learning thermostats 3, leading folks to suspect some chip differences over the years. No other IOT devices are showing issues, just the Nest thermostat. Nest protects and Nest doorbell are all fine.

So, is the problem with the thermostat’s firmware or the router’s firmware. I actually just set up a repeater, and linked the nest to that instead of directly to the router, and it has stayed stable since then.

Anyone who knows more about this stuff then me (practically anyone) have some thoughts about what is going on.

Nov 17 19:40:19 roamast: eth4: disconnect weak signal strength station [3e:5a:51:9d:7f:36]
Nov 17 19:40:19 roamast: eth4: remove client [3e:5a:51:9d:7f:36] from monitor list
Nov 17 19:44:03 wlceventd: wlceventd_proc_event(527): eth4: Auth 3E:5A:51:9D:7F:36, status: Successful (0), rssi:0
Nov 17 19:44:03 wlceventd: wlceventd_proc_event(537): eth4: ReAssoc 3E:5A:51:9D:7F:36, status: Successful (0), rssi:-52
Nov 17 19:51:06 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 0C:7A:15:68:B8:02, status: 0, reason: Unspecified reason (1), rssi:0
Nov 17 20:01:20 wlceventd: wlceventd_proc_event(527): eth5: Auth 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:0
Nov 17 20:01:20 wlceventd: wlceventd_proc_event(556): eth5: Assoc 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:-87
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(527): eth4: Auth DA:89:FE:28:70:8C, status: Successful (0), rssi:0
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(556): eth4: Assoc DA:89:FE:28:70:8C, status: Successful (0), rssi:-90
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind DA:89:FE:28:70:8C, status: 0, reason: 4-way handshake timeout (f), rssi:0
Nov 17 20:01:55 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
Nov 17 20:01:55 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
Nov 17 20:01:56 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 16:5D:B2:2D:8D:9E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:04:06 wlceventd: wlceventd_proc_event(527): eth5: Auth 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:0
Nov 17 20:04:07 wlceventd: wlceventd_proc_event(556): eth5: Assoc 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:-78
Nov 17 20:04:08 wlceventd: wlceventd_proc_event(527): eth5: Auth 7E:BC:20:95:8D:C4, status: Successful (0), rssi:0
Nov 17 20:04:08 wlceventd: wlceventd_proc_event(556): eth5: Assoc 7E:BC:20:95:8D:C4, status: Successful (0), rssi:-87
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 7E:BC:20:95:8D:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(527): eth5: Auth 7E:BC:20:95:8D:C4, status: Successful (0), rssi:0
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(556): eth5: Assoc 7E:BC:20:95:8D:C4, status: Successful (0), rssi:-64
Nov 17 20:13:18 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:13:18 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:16:24 wlceventd: wlceventd_proc_event(527): eth4: Auth 3E:5A:51:9D:7F:36, status: Successful (0), rssi:0
Nov 17 20:16:24 wlceventd: wlceventd_proc_event(537): eth4: ReAssoc 3E:5A:51:9D:7F:36, status: Successful (0), rssi:-42
Nov 17 20:31:22 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-54
Nov 17 20:31:22 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-54
Nov 17 20:31:23 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 16:5D:B2:2D:8D:9E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:01 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:01 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:02 roamast: [EXAP]Deauth old sta in 0 0: 3E:5A:51:9D:7F:36
Nov 17 20:32:02 roamast: eth4: disconnect weak signal strength station [3e:5a:51:9d:7f:36]
Nov 17 20:32:02 roamast: eth4: remove client [3e:5a:51:9d:7f:36] from monitor list

 

[GTLT]

updated the firmware and have lost access to internet.... needed to back rev to correct it

 

[bradbort]

Nov 17 19:40:19 roamast: eth4: disconnect weak signal strength station [3e:5a:51:9d:7f:36]
Nov 17 19:40:19 roamast: eth4: remove client [3e:5a:51:9d:7f:36] from monitor list
Nov 17 19:44:03 wlceventd: wlceventd_proc_event(527): eth4: Auth 3E:5A:51:9D:7F:36, status: Successful (0), rssi:0
Nov 17 19:44:03 wlceventd: wlceventd_proc_event(537): eth4: ReAssoc 3E:5A:51:9D:7F:36, status: Successful (0), rssi:-52
Nov 17 19:51:06 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 0C:7A:15:68:B8:02, status: 0, reason: Unspecified reason (1), rssi:0
Nov 17 20:01:20 wlceventd: wlceventd_proc_event(527): eth5: Auth 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:0
Nov 17 20:01:20 wlceventd: wlceventd_proc_event(556): eth5: Assoc 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:-87
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(527): eth4: Auth DA:89:FE:28:70:8C, status: Successful (0), rssi:0
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(556): eth4: Assoc DA:89:FE:28:70:8C, status: Successful (0), rssi:-90
Nov 17 20:01:47 wlceventd: wlceventd_proc_event(491): eth4: Deauth_ind DA:89:FE:28:70:8C, status: 0, reason: 4-way handshake timeout (f), rssi:0
Nov 17 20:01:55 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
Nov 17 20:01:55 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-89
Nov 17 20:01:56 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 16:5D:B2:2D:8D:9E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:04:06 wlceventd: wlceventd_proc_event(527): eth5: Auth 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:0
Nov 17 20:04:07 wlceventd: wlceventd_proc_event(556): eth5: Assoc 16:5D:B2:2D:8D:9E, status: Successful (0), rssi:-78
Nov 17 20:04:08 wlceventd: wlceventd_proc_event(527): eth5: Auth 7E:BC:20:95:8D:C4, status: Successful (0), rssi:0
Nov 17 20:04:08 wlceventd: wlceventd_proc_event(556): eth5: Assoc 7E:BC:20:95:8D:C4, status: Successful (0), rssi:-87
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 7E:BC:20:95:8D:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(527): eth5: Auth 7E:BC:20:95:8D:C4, status: Successful (0), rssi:0
Nov 17 20:05:24 wlceventd: wlceventd_proc_event(556): eth5: Assoc 7E:BC:20:95:8D:C4, status: Successful (0), rssi:-64
Nov 17 20:13:18 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:13:18 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:16:24 wlceventd: wlceventd_proc_event(527): eth4: Auth 3E:5A:51:9D:7F:36, status: Successful (0), rssi:0
Nov 17 20:16:24 wlceventd: wlceventd_proc_event(537): eth4: ReAssoc 3E:5A:51:9D:7F:36, status: Successful (0), rssi:-42
Nov 17 20:31:22 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-54
Nov 17 20:31:22 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 16:5D:B2:2D:8D:9E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-54
Nov 17 20:31:23 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 16:5D:B2:2D:8D:9E, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:01 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:01 wlceventd: wlceventd_proc_event(508): eth4: Disassoc 3E:5A:51:9D:7F:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 17 20:32:02 roamast: [EXAP]Deauth old sta in 0 0: 3E:5A:51:9D:7F:36
Nov 17 20:32:02 roamast: eth4: disconnect weak signal strength station [3e:5a:51:9d:7f:36]
Nov 17 20:32:02 roamast: eth4: remove client [3e:5a:51:9d:7f:36] from monitor list

One last update. For reasons I don't understand, having the nest thermostat on the guest network seems to have solved the "losing app connectivy 1x a day) issue.

 

[jmpr]

Anyone know if this fixes the IoT device disconnects? I'm finally stable on the beta 9.0.1.4_386_46197 beta firmware, and am feeling pretty risk averse at this point.

No problems at all. I have 8 IOT devices (mostly wifi plugs).

 

[bradbort]

No problems at all. I have 8 IOT devices (mostly wifi plugs).

Maybe. The router updated the same time as my nest thermostat. It then started to disconnect once a day. When I moved it to a guest network, it ceased disconnecting. Unclear if it was the router or the Nest firmware causing the issue. All my other IOT devices are working fine.

 

[h1berto]

After I reset all 3 nodes, very stable no issues and I have a performance increase on the Wifi.
So far so good.

 

[Blowsor]

After I reset all 3 nodes, very stable no issues and I have a performance increase on the Wifi.
So far so good.

When you say reset, exactly what kind of reset did you do?

 

[h1berto]

Hard reset.
Press WPS button and turn on the router. When green light goes off, just restart the router.

 

[Blowsor]

Hard reset.
Press WPS button and turn on the router. When green light goes off, just restart the router.

Thank you for your quick answer!

 

[ThatGuyinNC]

After I reset all 3 nodes, very stable no issues and I have a performance increase on the Wifi.
So far so good.

When you say performance increase are you talking about speed or coverage, or even both? This is with this firmware?

 

[Kapet]

Hard reset.
Press WPS button and turn on the router. When green light goes off, just restart the router.

Reset for node:
1. Turn of node
2. Hold down WPS Button, keeping it pressed
3. Turn on node
4. Node will light white, then turn off light
5. Keep holding WPS Button
6. Node will start to blink green
7. Keep holding WPS button
8. Node will turn off light again
9. Turn off node
10. Turn on node - and it will be reset (at least mine did)

Xt8 Hard Factory Reset

I would like to confirm the correct way to do a hard factory reset on my XT8s, is this the correct procedure? - 1. Turn the router off. 2. Press and hold the "WPS" button and turn the router on. 3. Power light is on (keep holding the WPS button). 4. Release the WPS button after the power...

www.snbforums.com

 

[bradbort]

I am reverting as I was losing even more devices and receiving the kernel errors on this update. Having to revert and factory reset is not ideal but would like to use the devices as intended.

I just reverted as well. After I noticed my nest thermostat was dropping once a day, I also noticed that my govee water sensors were doing the same thing. I"m going to revert for 24 hours and see if they both clear up. Strangely, moving the nest over to the guest network seemed to have stopped the dropping issue on the newest firmware.

 

[bradbort]

Anyone know if this fixes the IoT device disconnects? I'm finally stable on the beta 9.0.1.4_386_46197 beta firmware, and am feeling pretty risk averse at this point.

Where did you get the beta software? I'd like to give it a try!

 

[robgbc]

Where did you get the beta software? I'd like to give it a try!

I haven't tried it myself, but It's in this thread http://www.snbforums.com/threads/asus-zenwifi-xt8-new-firmware-3-0-0-4-386_45898.75102/post-720718

 

[Dodgydrains]

Where did you get the beta software? I'd like to give it a try!

https://www.asuswebstorage.com/navigate/a/#/s/63ED1D87CF9E40448ACDDD24AE0BBD59Y

 

[Lars]

https://www.asuswebstorage.com/navigate/a/#/s/63ED1D87CF9E40448ACDDD24AE0BBD59Y[/

This version i like is the best so far,9.0.1.4.386_46197_gfc5aa34_nodpi,have a many/lots of device,my line is 350/350 and no dropp outs in weeksmy wife havent complain ones doesnt have Parental Controls but i dont need that

 

[Dodgydrains]

This version i like is the best so far,9.0.1.4.386_46197_gfc5aa34_nodpi,have a many/lots of device,my line is 350/350 and no dropp outs in weeksmy wife havent complain ones doesnt have Parental Controls but i dont need that

This was sent to me by Asus engineers to test issues I had with Teams. It was rock solid for me but I need parental control which is why I reverted to stable version after couple of days testing. I gave feedback and have chased Asus to find out when the changes in beta 46197 will be implemented in stable.

 

[h1berto]

When you say performance increase are you talking about speed or coverage, or even both? This is with this firmware?

On my case it's speed. I have a fiber gigabit connection and the Wifi6 devices never went above 500Mbps. Now it's normal to reach 750Mbps.

 

[ThatGuyinNC]

On my case it's speed. I have a fiber gigabit connection and the Wifi6 devices never went above 500Mbps. Now it's normal to reach 750Mbps.

that is fantastic, and this is with the latest firmware?

 

[slikr]

On my case it's speed. I have a fiber gigabit connection and the Wifi6 devices never went above 500Mbps. Now it's normal to reach 750Mbps.

which firmware version is this?