Is this a V3 or V4 EZ-B? What does the Debug in ARC report when attempting connection?

Edit: Questions answered as I asked...

Is that the correct IP for the EZ-B? Type that IP address (without the :23)in to your browser and see what comes up to check.

Please watch the connection video for the EZ-B v4 Wi-Fi. You are attempting to connect to something over Wi-Fi that is not the EZ-B v4.

When attempting to connect, this pops out in the debug console

172.20.129.140 is not a valid IP Address for an EZ-B v4. Where did you get that IP Address from?

Is it possible for you to reply to Rich's questions please?

Here is the connection instructions video:

Personally I would scan for EZ-Bs again if the EZ-B is in client mode.

DJ shows how in this video;

The EZ-B will chime when it is detected too so you can be sure it's an EZ-B that's detected not a printer, router, access point, thermostat, PC or anything else that's on the network.

Once it picks it up, select it and click on the small circular icon (kinda like the Chrome icon) to the right. This will open the web page for the device, this should let you be 100% sure it is the V4 you are trying to connect to.

Once you are 100% sure, try connecting to it. You should find no errors in the debug if you have done it correctly.

@DJ just a thought and I don't know if it's feasible or not but perhaps adding in a pop up message for when users connect to something that's not an EZ-B may be of benefit? Something like "This is not the droid you are looking for". While this is only the second time I've seen this "problem" it still amounts to 2-3% of V4 users

Hi everyone. Thanks for the help, I thought that the IP address was my own IP address.

So I would physically need to have the robot, is that right? Are there any ways of using the ARC without a robot on hand?

Do you have an EZ-B v4? If not, then you can still use ARC to experiment. Simply do not use the CONNECT button because there is no robot. You can add controls and experiment with features.