Notifications

On the Notifications page, you can see information about the Customer and Location the device is installed, as well as the device's current state displayed in green, yellow, or red. Click the Go To Device button to quickly navigate to the device's Details page.

Pro Tip: -_Provide the event's Reference ID when directing another technician to a device event.

Click the accordion icon to expand the list of events generated from the device.

To remove notifications from the page, either select a device(s) and click Acknowledge. To clear all notifications click the box in the upper left to select all, then click Acknowledge.

Note: -__.Clearing your notifications does not affect other users.

Managing notifications

Notifications are managed at a Global, Customer, Location, and Device level.

Global Notification Settings are managed on the User page. They allow each user to decide how they receive notifications (email, app, or both) and what device statuses send notifications.

Note: -__.Global Notification Settings are specific to each user on the account. Customer, Location, and Device level settings affect every user on the account.

You can turn notifications off for an entire Customer or Location from the Customer List page by clicking the icon in the appropriate row.

Device notifications can be turned off/on in the Location's Device tab or Rooms tab. Click the box to enable/disable device notifications in the Notification column to the far left.

Note: -__.Voltage, current, and wattage notifications are managed on each WattBox's Power Performance Notification page. These must be set for each WattBox at the location.

Best practices

Think before you turn on notifications. Before turning the notifications on, evaluate how devices perform. By design, many devices disconnect from the network to conserve power when not in use.

Examples include:

  • Mobile devices and tabletop touchscreens disconnect when not in use.

  • Smart TVs often disconnect from the network when the TV turns off.

  • Wi-Fi light bulbs disconnect when the light switch is powered off.

  • AppleTVs power off after 30 minutes of inactivity by default.

How notifications function

OvrC handles notifications differently based on the level they're set, the user who set them, and the device classification.

Note: -__.Users invited to your account from another OvrC account have different notifications. Meaning, if you invited a tech from a different OvrC account to share a Customer, the notifications enabled on your account do not affect the notifications on their account.

Device type classifications

There are three device classifications in OvrC:

  • OvrC-enabled devices – Devices that connect directly to the OvrC cloud servers without the need for any additional equipment. These are typically Snap One products and can be sold in a stand-alone application. (eg. WattBox, Luma, and Episode). These devices do not provide any access or visibility for other devices on the network.

  • OvrC Pro devices – Devices embedded with the OvrC Pro agent that scan the entire network to monitor all the connected devices. See the list of OvrC Pro Devices.

  • Discovered devices – Devices that are connected to the same network as an OvrC Pro agent and are not OvrC-enabled devices. These devices are typically made by manufacturers other than Snap One, with a few exceptions (eg. Cisco switches, Furman PDUs, or Control4 touchscreens).

Notification bells

Notification bells enable/disable monitoring at customer, device, and location levels. Each level is handled differently to allow a customized experience for each user on the account.

Customer level notifications

  • Notifications set at the Customer level only affects the user who enables/disables them.

  • Enabling/disabling Customer level notifications affects all the Locations for that customer.

  • Notification modifications on the Customer level do not modify device level notifications for other users.

Location level notifications

  • Notifications set at the Location level only affects the user who enables/disables them.

  • Location notifications are turned on by default.

  • Enabling or disabling location notifications does not modify device level notifications for other users.

Device level notifications

  • Notifications set at the device level affects all users on the OvrC account.

  • OvrC-enabled devices have notifications enabled by default.

  • Third party discovered devices have notifications disabled by default.

How OvrC processes events to trigger notifications

OvrC processes event types differently to avoid sending too many notification messages.

Connect and disconnect events

The device must be continuously disconnected for fifteen minutes. If the device reconnects after five minutes, then disconnects again, the timer restarts.

Limited events

Limited events refer to specific device states. Below is a list of each:

  • Limited connectivity — The OvrC-enabled device is discoverable by the OvrC Pro agent, but is not connecting to the OvrC servers.

  • Over Current Protection — The WattBox has detected a high current demand on a particular outlet and has turned the outlet off to prevent damage to the device.

  • Over/Under voltage or current — The WattBox has identified a defined threshold for the incoming voltage or current draw.

  • Wireless Access Point is underpowered — The wireless access point is detecting a power connection lower than PoE++. The access point will continue to operate but is running in a limited state.

How OvrC monitors different device classifications

OvrC-enabled and OvrC Pro devices initiate and maintain a connection to the OvrC servers. If the connection is lost it is the device's responsibility to establish a new connection.

If an OvrC-enabled or Pro device is operational but appears as disconnected in OvrC for an extended period, a restart of the device should resolve the issue.

Discovered device's connection status are determined by the recurring Network health checks performed by the OvrC Pro agent. Network health checks use Address Resolution Protocol (ARP) and Internet Control Message Protocol (ICMP) to discover devices. If the discovered device responds to either protocol it is considered connected.

When does OvrC send the notification?

OvrC uses a sixty-second aggregation timer to batch notifications together to reduce the number of emails you receive. This timer starts over each time a new notification of the same type (connected, disconnected, or limited) is generated. If the aggregation timer is unable to complete after five minutes a notification email is sent with the notifications currently queue.