Dialogflow + Adventurebot Wifi Setup

Yes - for AdventureBot + DialogFlow, the most reliable setup is usually EZ-B v4 in Client mode, with your PC also on the same home network for internet access.

Recommended networking setup

Best practice

• EZ-B v4 in Client mode
• ARC on your laptop connected to:
  • the same WiFi/router as the EZ-B
  • and also the internet for DialogFlow

This avoids the "two network interfaces fighting each other" issue you ran into with AP mode + bridge setups. That setup can work, but it’s often less stable than simply putting the EZ-B on the router.

Why AP mode causes trouble

In AP mode, your laptop is directly connected to the robot’s WiFi, and depending on the adapter/routing setup, Windows may stop sending internet-bound traffic correctly. That’s why DialogFlow can work one moment and then fail once ARC is tied to the EZ-B network.

You can read more about the networking side here:

• Two Network Interfaces: https://synthiam.com/Support/Tips-to-Make-a-Robot/Two-Network-Interfaces
• Connecting EZB Over Internet: https://synthiam.com/Support/troubleshooting/Connecting-EZB-Over-Internet

About the lag you’re seeing

A 1-2 second delay between intent and movement usually points to one of these:

• WiFi congestion or weak signal
• Router roaming / power-saving behavior
• Video stream bandwidth competing with command traffic
• Script logic waiting on something before motion starts
• DialogFlow processing latency on the cloud side

Things to try

1. Use a clean 2.4 GHz network

AdventureBot / EZ-B v4 generally performs best on a dedicated 2.4 GHz SSID.

If your router offers it:

• Separate 2.4 GHz and 5 GHz SSIDs
• Connect the EZ-B only to the 2.4 GHz one
• Keep the laptop on the same 2.4 GHz network if possible

2. Keep the signal strong

• Stay close to the router
• Avoid mesh nodes that may roam aggressively
• Try a different router location if possible

3. Reduce competing network load

• Limit video streaming resolution/fps if the camera skill allows it
• Avoid heavy downloads on the same WiFi during testing
• Disable bandwidth-heavy devices temporarily to compare performance

4. Avoid Windows network bridging

You already found the common problem: bridging can be flaky with ARC and WiFi devices. In most cases, it’s better to:

• use the router/client mode approach
• or use two separate adapters without bridging, if necessary

ARC configuration tips

DialogFlow execution pattern

Yes - using DialogFlow’s On Response / script execution to route recognized intents to robot actions is the preferred pattern.

That’s the normal ARC workflow:

• DialogFlow recognizes intent
• ARC stores the response / parameters in globals like:
  • $APIIntent
  • $APIComplete
  • $APIParameters[...]
  • $APIResponse
• Your script checks the intent and triggers actions

That’s exactly how you should drive AdventureBot from voice commands.

Example: intent routing script

If your intent action is something like drive.forward, you can keep the script simple:

if (getVar("$APIIntent") == "drive.forward") {
  if (getVar("$APIComplete")) {
    Movement.forward();
    sleep(1000);
    Movement.stop();
  }
}

Or if you want multiple commands:

if (getVar("$APIComplete")) {
  var intent = getVar("$APIIntent");

  if (intent == "drive.forward") {
    Movement.forward();
    sleep(1000);
    Movement.stop();
  } else if (intent == "drive.reverse") {
    Movement.reverse();
    sleep(1000);
    Movement.stop();
  } else if (intent == "drive.left") {
    Movement.left();
    sleep(500);
    Movement.stop();
  } else if (intent == "drive.right") {
    Movement.right();
    sleep(500);
    Movement.stop();
  }
}

For smoother driving

If you want less "one command = one timed move," consider:

• start/stop style intents
  • "drive forward"
  • "stop"
• and separate intents for direction / speed / duration

That tends to feel more responsive than waiting for a full sentence + timing parameter every time.

Best overall recommendation

For AdventureBot:

1. Put EZ-B v4 in Client mode
2. Put ARC laptop on the same router
3. Use a clean 2.4 GHz network
4. Keep video quality modest
5. Route DialogFlow intents through scripted intent handlers in ARC

Helpful ARC docs

• DialogFlow skill: https://synthiam.com/Support/Skills/Artificial-Intelligence/DialogFlow?id=15882
• EZ-B Connection skill: https://synthiam.com/Support/Skills/Communication/EZB-Connection?id=16041
• AdventureBot info: https://synthiam.com/Support/Hardware/AdventureBot

If you want, I can help you build a clean DialogFlow intent map for AdventureBot - for example:

• drive.forward
• drive.reverse
• turn.left
• turn.right
• drive.stop

and show you the exact ARC script to go with it.