Unable to Reset XT8 Node

[Stach]

Hi all, I cannot for the life of me reset my remote XT8 v1 node. I was trying to upgrade to the latest Gnuton version (388.4_0-gnuton0_alpha1) and started, like I always do by upgrading the remote node first. That apparently failed as it never came back up properly and it does not even show as a down node in the GUI. It seemed to be in a funky state where it was pingable from the network and I could even connect via hard-wire to it and surf, but the node itself never showed as being connected in the GUI and if I tried going to the Admin page for the remote node, it said that it couldn't connect to the Parent AP (shown below).

After trying and failing MANY times to factory reset the remote Node, I tried the firmware restoration tool to restore the previous firmware (388.2_2_0-gnuton1). This finally got the IP address back to the shipping default IP of 192.168.50.1, but I still am not able to use the Admin page for it or fully factory reset the device as it still tries to connect to the Parent IP. I've tried a few more resets by powering on with the WPS button pushed, but it appears to be in a reboot loop as it becomes active for about 1 minute, pingable and admin webpage "works" and shows the above screenshot, but then reboots.

Does anyone have advice for getting my unit fully reset so that I can see the following screen and rejoin my Parent node (screenshot from a different unlinked node)?

 

[L&LD]

I'm not sure about the Zen products, but I wouldn't be accessing the node's GUI to connect it to the main router.

Use the main router to 'add' an AiMesh node instead. AFTER you have fully reset the node and haven't tried to access it at all via its GUI.

 

[Stach]

Thanks for your reply but unfortunately the node needs to be in that reset state before I can join it, as it currently only looks to join what was the previous mesh network and can’t.

 

[hwagenle]

Is there a solution here? I can't manage to reset a mesh node either, for a short time I see the default IP 192.168.50.1 but then it reconnects to the main router. I have used reset method 6 and also tested other methods, but I cannot reset the node. Firmware is 3.0.0.4.388_24621
greetings

 

[Tech9]

for a short time I see the default IP 192.168.50.1 but then it reconnects to the main router

So it does reset, but reconnects to the main router as AiMesh node after. This is a known behavior for paired mesh sets. What's the purpose of resetting this node? If you want to run it in AP Mode instead you have to power down the main router temporarily and configure the second router first the way you want it, then power up the main one. Once the second router's operation mode has been changed it won't reconnect as AiMesh node automatically.

 

[hwagenle]

I would like to use the node as a bridge. In principle, this also works as a mesh node, but I'm irritated that I can't reset the node.
When I switch off the main router, I get (from my brain memory) that the parent router cannot be reached.
Greetings
Holger

 

[Tech9]

I would attempt connecting it to something else first (mobile hotspot for example), power up the main router and reconnect the bridge to it. What I know is you have to change the operation mode to prevent automatic reconnection as AiMesh node after reset. Or set it as Router first and change the mode to Media Bridge after, this may work too. Test and it will work one way or another. It's done this way for "convenience", expected use case is AiMesh.

 

[hwagenle]

Logging in via another network helped and now it works. Many thanks for your help!
Holger