Below are some troubleshooting steps and ideas to help resolve the issue where the camera and scripts become unresponsive when you connect over your network:

1. Check Your Network Configuration
   Verify that your EZ-InMoov head (and its EZ-B) has a stable, static IP address on your home network. A dynamic IP change might cause connection interruptions.
   Make sure that no firewall settings on your router or PC are blocking the designated camera ports used by ARC.

2. Review EZ-B Firmware & ARC Version
   Ensure that your EZ-B firmware is up to date. Firmware updates can resolve connectivity issues that appear only over a network.
   Likewise, confirm you’re running the latest version of ARC, as newer releases often include improvements in network handling for skills such as the Camera and scripting.

3. Camera Skill Settings within ARC
   When you connect directly (e.g. via USB or a direct connection to the head) the camera initializes normally. In your network setup, the error messages"Client disconnected" and "Camera Disabled"suggest the streaming service may be interrupted.
   Try lowering the camera’s resolution (e.g. from 320x240 to a lower value) in the skill’s configuration to see if it improves stability on the network.
   Double-check the camera’s configuration settings (via the gear icon on the control) to ensure that the network interface is selected correctly.

4. Script Responsiveness Issues
   Since voice recognition still works but scripts become unresponsive, it may be that a script is waiting on an event (perhaps tied to the camera skill) that isn’t firing when there’s a network disconnect. Look through any scripts to see if they include wait conditions or depend on input from the camera.
   If possible, try disabling the camera temporarily in your ARC project and see if your scripts (and related control commands) become responsive again. This can help narrow down whether the camera skill hangs the system.

5. Connection Diagnostic Skill Log
   Review the logs generated by the Connection Diagnostic skill carefully. They might reveal intermittent disconnects or packet loss that are affecting the camera feed.
   Sometimes additional latency on a WiFi network (or mismatches between the EZ-B’s IP settings and your network configuration) can cause the client to drop the connection.

6. Other Considerations
   If your EZ-InMoov head was initially configured for a direct connection, switching to a networked environment sometimes requires a reset of network settings. Try restarting both your router and the EZ-B.
   Test your network performance with another device if possible. A weak WiFi signal or network congestion may cause sporadic disconnections.

Have you noticed if this happens consistently and only over the network? Also, are you using any special network configurations (such as multiple subnets or VPNs) that might affect direct device communication?

By following these steps, you should be able to isolate whether it’s a network configuration, firmware, or project setup issue. Let me know what you find or if you have any additional questionsI’d be happy to dive deeper into any part of your setup.

For more details on network connectivity and troubleshooting, you can always check our support pages at Synthiam Support.

Your camera requires the correct address for the ezb on your network. Update the address correctly and save the project. Saving will save the settings. The camera would use the same address as your ezb because your camera is connected to the ezb.

Also, this tutorial will explain more detail on changing network types for your ezb iotiny product: https://www.ez-robot.com/learn-robotics-wifi-modes.html

I figured it out! I had to enable "Camera Transmit Nagle" the advanced network settings of IoTiny

Thanks DJ Sures!

Added resolved

Oh that's great to hear! I would not have thought of that.