Snap One is excited to announce the launch of OvrC Pro App v7.4.0, an engineering effort that features a number of updates to the back-end processes and infrastructure, and will provide noticeable, real-world improvements. This launch is a continuation of Snap One’s mission to provide the best, fastest, most powerful, and easiest to use tools for our Partners. For this OvrC update, engineering development focused on improving the Partner experience within OvrC, with special attention to Partner-requested enhancements.

The highlights for this update include:

• Improved Accuracy in Device State Reporting
  • More accurate ‘Connected State’ results with timing change for health check scans
  • More accurate device monitoring with MAC address validation checks for discovered devices

OvrC now validates the MAC address of discovered devices by matching the device list in the OvrC Pro agent. This provides more accurate monitoring on sites with frequently changing IP addresses.

Previous versions of the Pro Agent performed a health check every 5 minutes, regardless of the network size. As a result, small networks had a delay when notifying when the connected state changed. For larger networks, the health check scan may not have been completed before the next was triggered. This resulted in devices showing as disconnected when they were functioning as expected. OvrC Pro App version 7.4.0 now waits for the previous health check to complete before triggering the next one, for a more accurate connected state reading.

• Improved Network Speed Tests
  • Faster speed test results with multi-threaded runs of the Ookla speed test
  • Improved scan speeds for AN-520 routers, now comparable to the AN-310 router

• Improved Reliability
  • Resolved WebConnect issues with Onkyo, Integra, and Pioneer AVRs
  • Resolved issue where login credentials and SNMP community names were not being stored
  • Resolved memory leak issue in the OvrC Pro agent
  • Fixed data storage location in Pakedge WR-1. Persistent data for OvrC Pro was not being properly stored
  • Fix to accept x.x.x.254 addresses for static IP; previously this was not accepted by the OvrC Pro agent

• Improved Security
  • OvrC Pro interface that was used for the local UI (port 60000) has been removed from OvrC Pro agent devices
  • Local UI on the OvrC Pro Hub (port 80) has also been removed
  • This update has been applied automatically to all relevant devices

With these important features moving to the OvrC cloud, access to the local UI of the OvrC Pro agent will no longer be needed and will be removed in a future update to secure the local device and protect the privacy of the customer.  For the OvrC Pro Hub, port 80 was used. For devices like routers and Control4 controllers that are serving as the OvrC Pro agent, this interface was typically found on port 60000 when accessing the device directly. These agent devices also serve a local UI on port 80 (http) or 443 (https) and there will be no impact to that local interface.

COMING SOON

• Improved Device Claim Process
  • To streamline the steps to claim a device in OvrC, additional options will be added later in Q1
    • Press the ID Button: quick and easy way to claim a device that is powered and online
    • Scan the QR Code: allows Partners to claim an offline device still in the box
    • Manual Entry (current option): type in the Service Tag number for the device:
      • CORE: Service Tag is found on the box, and on the label on the bottom of the unit
      • CA/EA: found in the Device Properties for that driver in the System Design page in Composer Pro; the controller must be powered, online and identified)