IoT Devices falling off nodes (only) always requires reboot to fix

[Tech9]

it is (should be) specifically designed to work as an integrated system

It's designed to sell more ASUS routers to low knowledge users who already have one ASUS router by advertising "AiMesh Compatible" without specifiying details. Some more advanced users like you may notice the issues and complain, most won't. This type of business works well on the consumer market.

 

[jksmurf]

It's designed to sell more ASUS routers to low knowledge users who already have one ASUS router by advertising "AiMesh Compatible" without specifiying details. Some more advanced users like you may notice the issues and complain, most won't. This type of business works well on the consumer market.

Yeah, the concept is fantastic, the reality, not so much. To be fair there are simply too many variables for a one size fits all auto smart everything solution to work effectively, even with supposedly GNP and VLAN compatible groups of hardware.

Again, to be fair they do provide the tools to tweak it (and RMerlin does too) so you can get there, but for the average user I think it’s a step too far.

 

[Tech9]

Some of the limitations are hardware related. Even if you had per device power adjustment - you know ASUS routers with Broadcom hardware reboot on every change. Imagine your nodes totally disappearing for few minutes on every change during your tuning process, one by one. How long it will take and how precise it will be with this type of constant network disturbance? Your wireless clients will go crazy. With Qualcomm hardware you can do it on the fly and some home mesh systems self-adjust dynamically. Your observations are correct - with AiMesh add-on software you get higher number of check box features and lower overall user experience.

 

[jksmurf]

[EDIT1] Forgot to add, for some reason vertically orientated external antennas on the two RT-AX86U Pro nodes worked better than my normal setup of central antenna vertical and the outside ones at 45 degrees (first click). I’m neither qualified nor experienced enough to offer any explanation for this.

Couldn’t add to post above as too long ….

[EDIT2] A recent reboot had me scrabbling to get the IoTs latching on again, so I went with 2.4GHz Roaming Assistant @ -70dBm, in the Wireless Professional Tab and I also changed the 2.4Ghz control channel from channel 11 to channel 6 in the hope it was less crowded.

[EDIT3] Changed “Enable TX Bursting” from default Enable to Disable.

[EDIT4] VERY IMPORTANT. Bound specific Shelly Devices to the AiMesh Nodes that are closer and clearly have a much better RSSI. I have done tests before and after for my Shelly TRV Gateways. What seems to be happening (I have no way of proving this) is that on an Aimesh Setup with various Nodes (even Wired which mine ALL are), when the system comes up (i.e. a SYSTEM Reboot from the AiMesh Tab) the Shelly's (only on a 2.4Ghz Network) latch on to the Main GT-AX6000 Router first (which wakes up first) with a weak signal, rather than the closer RT-AX86U Pro wired AiMesh nodes; and they never seem to relinquish this connection. This happens even with roaming assist (RA) enabled @ -70dBm. If I try +65 or -67, they don't connect at all despite this being a totally reasonable figure on the MB Node (as shown by the results). So AiMesh seems to be falling down here.

Some of you may recognise that if you reboot AiMesh Main or Nodes separately, depending on that sequence, you get a different set of devices connecting with better, or worse, RSSI; or not connecting at all. I believe the reason is as above.

Before and After Results:

Master_BRM_GW (B0:81:84:E6:0D:14):
Before: -78 dBm (on Kitchen node)
After: -40 dBm (on MB node)

Living_RM_GW (B0:81:84:E3:91:00):
Before: -74 dBm (on Main router)
After: -50 dBm (on MB node)

[EDIT 5]I had to UNBIND all my bound Shelly devices (which worked super well), because they do not appear in the Shelly Cloud App anymore, despite Asus showing they are all connected and have strong signals. I am researching, but it seems a known issue with Shelly Devices. Unbinding them brought them all back (in the Shelly App). So infuriating. Like whack-a-mole.

These are the additional changes to the long post above. It’s seems all very sensitive TBH. I am concerned it just isn’t robust and the more tweaks there are the more potential for things to go awry.

 

[Tech9]

Antennas have to be vertical for one-level houses or apartments. May also work better in multi-level homes in specific environments with objects reflecting the signal.

 

[jksmurf]

I am editing and adding as I go (see above EDITs), but thought I would repeat an observation from a recent edit (EDIT4) above, as it might help other folks who are struggling to understand why AiMesh may be running them around in circles.

[EDIT4] VERY IMPORTANT. Bound specific Shelly Devices to the AiMesh Nodes that are closer and clearly have a much better RSSI. I have done tests before and after for my Shelly TRV Gateways. What seems to be happening (I have no way of proving this) is that on an Aimesh Setup with various Nodes (even Wired which mine ALL are), when the system comes up (i.e. a SYSTEM Reboot from the AiMesh Tab) the Shelly's (only on a 2.4Ghz Network) latch on to the Main GT-AX6000 Router first (which wakes up first) with a weak signal, rather than the closer RT-AX86U Pro wired AiMesh nodes; and they never seem to relinquish this connection. This happens even with roaming assist (RA) enabled @ -70dBm. If I try -65dBm or -67dBm, they don't connect at all despite this being a totally reasonable figure on the MB Node (as shown by the results). So AiMesh seems to be falling down here.

Some of you may recognise that if you reboot AiMesh Main or Nodes separately, depending on that sequence, you get a different set of devices connecting with better, or worse, RSSI; or not connecting at all. I believe the reason is as above.

Before and After Results:

Master_BRM_GW (B0:81:84:E6:0D:14):
Before: -78 dBm (on Kitchen node)
After: -40 dBm (on MB node)

Living_RM_GW (B0:81:84:E3:91:00):
Before: -74 dBm (on Main router)
After: -50 dBm (on MB node)

These are the additional changes to the long post above. It’s seems all very sensitive TBH. I am concerned it just isn’t robust and the more tweaks there are the more potential for things to go awry.

[EDIT 5]I had to UNBIND all my bound Shelly devices (which worked super well), because they do not appear in the Shelly Cloud App anymore, despite Asus showing they are all connected and have strong signals.

 

[Tech9]

The reasons for this are (as I understand it) due to the GT-AX6000 main router having much higher TX power than RT-AX86U Pro nodes

Not sure what you have edited, but this assumption is incorrect. There is FCC ID registration data for reference. In addition to AiMesh limited network tuning options ASUS doesn't even tell in GUI what the Tx power actually is. The adjustment steps are region dependent and may have up to 10x difference. For example Performance on 2.4GHz band in Europe is up to 20dBm, in North America is up to 30dBm.

 

[jksmurf]

Not sure what you have edited, but this assumption is incorrect. There is FCC ID registration data for reference. In addition to AiMesh limited network tuning options ASUS doesn't even tell in GUI what the Tx power actually is. The adjustment steps are region dependent and may have up to 10x difference. For example Performance on 2.4GHz band in Europe is up to 20dBm, in North America is up to 30dBm.

Ok so do you know what GT-AX6000 TX Power is vs RT-AX86U Pro and if it’s the same whether the Antenna arrangement would explain what I’m experiencing please?

 

[Tech9]

Both have exactly the same 4-stream radio IC with similar low-gain dual-band dipole 2-3dBi antennas (gain depending on frequency) and up to slightly below 30dBm EIRP (depending on region). The only obvious difference is the number of external antennas (RT-AX86U Pro has 3x external + 1x internal). The expected range and performance from the same location and in the same environment is expected to be pretty close, confirmed by available online reviews/tests (with devices purchased in the same region).

 

[Dedel66]

OK, I'm desperate enough; what were those recommended settings again?

Since I assigned static IP addresses to all my Tasmota smart plugs (IP, gateway, subnet), their connection has been rock solid. I haven't configured any bindings, and the plugs automatically find their "best" access point. I have reserved the IPs in the DHCP list.

 

[mrric]

About the RT-AX86U Pro and TX Power Adjustment, what is the default value... Power Saving?

 

[Tech9]

The default setting is Performance.

 

[bennor]

About the RT-AX86U Pro and TX Power Adjustment, what is the default value... Power Saving?

As indicated by Tech9, the default setting on a RT-AX86U Pro (Asus-Merlin 3006.102.6) for Wireless - Professional > Tx power adjustment (both 2.4Ghz and 5Ghz) is Performance. Example from an RT-AX86U Pro:

 

[jksmurf]

Both have exactly the same 4-stream radio IC with similar low-gain dual-band dipole 2-3dBi antennas (gain depending on frequency) and up to slightly below 30dBm EIRP (depending on region). The only obvious difference is the number of external antennas (RT-AX86U Pro has 3x external + 1x internal). The expected range and performance from the same location and in the same environment is expected to be pretty close, confirmed by available online reviews/tests (with devices purchased in the same region).

Thank you. Despite wired BH, possibly just down to my mesh setup or router placement, that it seemed the preferred router for my Shelly 2.4GHz clients to attach to; although that might very well be down to boot order as noted above, which is what I am seeing (and the reason for some Shellys to choose the Main on a lower RSSI).

[EDIT 5]I had to UNBIND all my bound Shelly devices (which worked super well), because they do not appear in the Shelly Cloud App anymore, despite Asus showing they are all connected and have strong signals. I am researching, but it seems a known issue with Shelly Devices. Unbinding them brought them all back (in the Shelly App). So infuriating. Like whack-a-mole.

 

[jksmurf]

Since I assigned static IP addresses to all my Tasmota smart plugs (IP, gateway, subnet), their connection has been rock solid. I haven't configured any bindings, and the plugs automatically find their "best" access point. I have reserved the IPs in the DHCP list.

Thanks, yes, I have used Static Assignments on the 35 odd Shellys for quite a while. It helped, but does not make them move to a better RSSI node.

 

[Tech9]

that it seemed the preferred router for my Shelly 2.4GHz clients to attach to

There is a different story for 2.4GHz radio. GT-AX6000 has better and newer BCM6715 4-stream radio. RT-AX86U Pro has whatever was cheap and available at the time... BCM6710 3-stream radio. It was actually not popular troubled Broadcom product with support issues upstream. Remember I recommend AiMesh with identical units? Now you know another reason why - there is less chance for preferred AP due to hardware/software factors outside of your control. All my business (Cisco) and residential (UniFi) networks have the same model APs for the same reason.

 

[jksmurf]

There is a different story for 2.4GHz radio. GT-AX6000 has better and newer BCM6715 4-stream radio. RT-AX86U Pro has whatever was cheap and available at the time... BCM6710 3-stream radio.

Fantastic info. Thank you. Thant would explain a fair bit. So my understanding (assumption) was correct, just poorly defined and backed up with actual facts, which you have now kindly supplied . In terms of definition, I probably should have said the assumption was for 2.4GHz only, as my IoT Network is only 2.4Ghz and the Shelly's attach on that band.

It was actually not popular troubled Broadcom product with support issues upstream. Remember I recommend AiMesh with identical units? Now you know another reason why - there is less chance for preferred AP due to hardware/software factors outside of your control. All my business (Cisco) and residential (UniFi) networks have the same model APs for the same reason.

Yes, it's like 'sorry boyo, it;s not enough just to have VLAN-capable and GNP-compatible units, it is best to have all the same units', which seems to me to a bit pointless as you may only need the "lighter" ones to plug the gaps. Yes, AiMesh ... great for single Router environments ...

 

[degrub]

Sums it up succinctly
"Yes, AiMesh ... great for single Router environments ..."