By default, an Octave edge device is configured to be in Developer Mode. This keeps a connection open with the Octave servers continuously, so that the device's configuration can be delivered immediately. Developer Mode is useful when writing, testing, and debugging edge applications, but should be disabled prior to deployment.

In Developer Mode, the device frequently transmits its hierarchy of Resources to the Octave servers, so that the latest information about the device is available to the user. By default, Developer Mode will remain enabled so long as the device configuration is being pushed to the device.

Enabling/Disabling Developer Mode

Developer Mode is enabled/disabled by accessing the /cloudInterface/developer_mode Resource, setting the Resource's enable property, and clicking Apply.

Automatically Suspending Developer Mode

Developer Mode can also be configured to automatically suspend itself after a period of inactivity, to avoid sending the excess data associated with Developer Mode:

1. Navigate to Device > Resources.
2. Locate /cloudInterface/developer_mode.
3. Click on the menu and select Configure Resource.
4. Enable close_on_inactivity. This configures the device to suspend Developer Mode after the time specified in the inactivity_period field.
5. Enable inactivity_period and set the inactivity time period, in seconds.
6. Click Apply to send the settings to the device.

Minimizing Message Consumption on Your Device

The following parameters must be disabled in order to disable all system-generated messages. Doing so will help to minimize message usage and keep billing costs down:

• Developer mode must be disabled:

  • through the Octave Dashboard as described above; or
  • programmatically set /cloudInterface/developer_mode/enable to false) using an Edge Action or Cloud Action

• Diagnostic mode must be disabled:

  • set the /diagnostic/logs/enable Resource to false

📘

Note

Beware that opening the Edge Action “Console” screen on a device automatically enables Diagnostic mode

• CloudInterface “heartbeat” must be optimized or disabled:
  • set the /cloudInterface/store_forward/heartbeat_on_empty Resource to false if you do not need a keep-alive on your device.
  • if you need a HeartBeat, set it to a value optimized for your needs

Once these are disabled, the device will only report Messages related to:

• Observations you have defined
• Data sent to the Cloud or Store & Forward from an Edge Action