Hi Chris,

It sounds like you're having trouble with the network scan detecting your EZB IoTiny when it’s configured in client mode. I’d like to offer some insights and troubleshooting steps:

1. Client Mode & Broadcast Behavior
   The EZB IoTiny, when operating in client mode, may not always broadcast its presence in the same way as some other EZB devices. This can make it harder for the EZB Connection skill’s network scan to pick it up automatically. It isn’t necessarily a flaw in the skillit’s more about how the device is configured and how it interacts on your specific network.

2. Network Environment Considerations
   Ensure that your computer running ARC and the IoTiny are on the same subnet.
   Check your router or any network firewall settings. Sometimes these can block broadcast or discovery messages.
   In some cases, devices in client mode rely on manual IP configuration rather than advertising themselves by default.

3. Manual IP Entry is Expected in Some Cases
   Since the IoTiny may not be advertising itself strongly over the network in client mode, many users end up manually entering the IP address using the router’s device list. This is a common workaround.

4. Double-Check IoTiny Configuration
   Review the IoTiny’s settings (via its web configuration page) to see if there is any option related to network discovery or broadcast.
   It may not have an explicit "broadcast" checkbox, but verifying that its network settings (such as IP, subnet, and gateway) are correctly set can help ensure it’s reachable by ARC.

5. Further Troubleshooting Options
   Try temporarily disabling your computer’s firewall to see if the scan then detects the IoTiny.
   Ensure that any network isolation or security settings on your router aren’t blocking the discovery process.
   If possible, test with a different network segment or even a direct connection to help narrow down the cause of the issue.

For more detailed hardware information on the IoTiny, you can check its Synthiam support page here:
https://synthiam.com/Support/Hardware/EZ-B-IoTiny

Have you already verified that both your ARC PC and the IoTiny are on the same network and that no firewall is interfering? Let me know if any of these suggestions help or if you need further details on a particular step. I'm here to help!

Ezb iotiny from ezrobot should broadcast itself. You’ll see the option in the webserver settings. It uses the word broadcast in the option.

if your router is disabling broadcasts it won’t work. Check your router to make sure it’s not doing some crazy filtering internally. Sometimes it’s called AP isolation.

Hi there,

DJ_Sures makes a good point. The EZ-B IoTiny does indeed have an option in its webserver settings that enables broadcast. Here are a few steps and considerations based on that:

Verify the Broadcast Setting:
Open your IoTiny’s web configuration page and look for an option that mentions broadcast. This setting should be enabled so that your device sends out its presence on the network.

Router Settings and AP Isolation:
Even with the setting enabled on the IoTiny, if your router is filtering broadcast messages or has AP isolation enabled, then your device won’t be detected by ARC’s network scan. Double-check your router’s configuration to ensure that it isn’t blocking these broadcasts.

Network Environment:
Make sure both your ARC computer and the IoTiny are on the same subnet. Any internal router filtering or advanced security settings might be interfering with the discovery process.

Manual Entry as a Workaround:
Although the IoTiny is meant to broadcast itself, some environments will still require a manual IP entry if network broadcasts are being filtered. This is a common workaround many users employ.

Could you check your IoTiny’s broadcast option in the webserver settings and verify that your router isn’t set to use AP isolation or any similar broadcast filtering? Let me know what you find so we can further narrow down the issue.

For more information, you can check out the EZ-B IoTiny support page here:
https://synthiam.com/Support/Hardware/EZ-B-IoTiny

Feel free to ask if you have more questions or need any additional help!

Also, there's a popup built into Windows when a server is started in an application. This window would have popped up when you opened the scan utility. The window is not part of synthiam or has any relationship to synthiam as it's built into windows. It is a standard prompt to notify users that a server will listen on your port. If that window is closed or not accepted, the Windows firewall will block the server. If so, it will never work unless you manually enable the feature.

In addition, if your network device is configured for PUBLIC instead or PRIVATE, windows will disable certain network scan features. This is a feature of Microsoft windows and not Synthiam ARC. Becuase windows is your operating system, it has features to enable and disable network access based on the configuration.

Hi there,

Synthiam_Support makes some important points regarding Windows' built-in network security prompts that can affect server functionality when scanning. Below are some key areas to check and consider:

1. Windows Firewall Popup Prompt

   • When you use the scan utility, Windows may display a popup asking if you allow a server to listen on a specific port.
   • If you close or deny this prompt without allowing it, Windows Firewall could block the server.
   • Make sure you accept the prompt so that the required port remains accessible.

2. Network Profile Settings

   • Windows differentiates between network types (PUBLIC vs. PRIVATE).
   • If your device is set to a PUBLIC network, Windows might disable certain network scan features to protect your security.
   • Verify that your network connection is set to PRIVATE if you plan on using these scan utilities. You can check this in Windows Settings under Network & Internet > Wi-Fi or Ethernet > Manage known networks > your current connection’s properties.

3. Firewall and Security Software Adjustments

   • Beyond the built-in popup, ensure your firewall settings or any third-party security software aren’t interfering with the network scan.
   • You may need to manually configure your Windows Firewall to allow incoming connections on the specific port used by ARC’s EZ-B Connection skill.

4. Impact on Broadcast Detection

   • Since Windows network policies can block certain server functions and broadcasts, even if the IoTiny is correctly set to broadcast its presence, Windows security settings may prevent ARC from detecting it.
   • Double-check that you’ve accepted the prompt and adjusted your network profile accordingly.

Have you had a chance to review the Windows Firewall prompt when opening the scan utility and checked your network profile? Let me know if adjusting these settings helps or if there are any other issues. I'm here to help as you work through this!

For a bit more on Windows network settings, you might also review Microsoft’s documentation on network profiles and the firewall settings, which can provide additional details on how to switch between Public and Private networks.

Make sure nothing else is connected to the ezb. If you're computer is connected from a previous connection you need to disconnect. Only one connection works.