Merge pull request #311 from meshtastic/remove_send_owner_interval

Remove send_owner_interval

docs/settings/power.mdx

@@ -29,7 +29,6 @@ For a description and more information on what exactly all of these mean, please
 |       phone_timeout_secs       |                                                                       `integer` (seconds)                                                                       |    `0`    |
 |         screen_on_secs         |                                                                       `integer` (seconds)                                                                       |    `0`    |
 |            sds_secs            |                                                                       `integer` (seconds)                                                                       |    `0`    |
-|      send_owner_interval       |                                                             `integer` (sent every x network pings)                                                              |    `4`    |
 |      wait_bluetooth_secs       |                                                                       `integer` (seconds)                                                                       |    `0`    |
 
 :::note
@@ -505,43 +504,6 @@ Configuring this setting is not yet available for the selected platform. If this
   </TabItem>
 </Tabs>
 
-### send_owner_interval
-
-This sets how often to send the database of node owner information with other nodes in the mesh (per mesh network ping).
-
-#### Configure send_owner_interval
-
-<Tabs
-groupId="settings"
-defaultValue="cli"
-values={[
-{label: 'CLI', value: 'cli'},
-{label: 'Android', value: 'android'},
-{label: 'iOS', value: 'iOS'},
-{label: 'Web', value: 'web'},
-]}>
-<TabItem value="cli">
-
-```shell title="Set send_owner_interval to default (every 4 network pings)"
-meshtastic --set send_owner_interval 0
-```
-
-```shell title="Set send_owner_interval to every 10 network pings"
-meshtastic --set send_owner_interval 10
-```
-
-  </TabItem>
-  <TabItem value="android">
-Configuring this setting is not yet available for the selected platform. If this is incorrect please update the documentation for this page.
-  </TabItem>
-  <TabItem value="iOS">
-Configuring this setting is not yet available for the selected platform. If this is incorrect please update the documentation for this page.
-  </TabItem>
-  <TabItem value="web">
-Configuring this setting is not yet available for the selected platform. If this is incorrect please update the documentation for this page.
-  </TabItem>
-</Tabs>
-
 For instance the default interval of 4 will send the node owner information for every 4 mesh network pings. This information is also transmitted after the node first boots up.
 
 ### wait_bluetooth_secs

docs/settings/router.mdx

@@ -70,7 +70,6 @@ Toggling `is_router` changes your device settings in the following ways.
 
 |          Setting          | `is_router` Default | Normal Default |
 | :-----------------------: | :-----------------: | :------------: |
-|   `send_owner_interval`   |          2          |       4        |
 | `position_broadcast_secs` |      12 hours       |   15 minutes   |
 |   `wait_bluetooth_secs`   |          1          |       60       |
 |  `mesh_sds_timeout_secs`  | NODE_DELAY_FOREVER  |    2 hours     |

docs/software/other/power.mdx

@@ -55,7 +55,7 @@ From lower to higher power consumption.
 - At cold boot: The initial state (after setup() has run) is DARK
 - While in DARK: if we receive EVENT_BOOT, transition to ON (and show the bootscreen). This event will be sent if we detect we woke due to reset (as opposed to deep sleep)
 - While in LS: Once every position_broadcast_secs (default 15 mins) - the unit will wake into DARK mode and broadcast a "networkPing" (our position) and stay alive for wait_bluetooth_secs (default 60 seconds). This allows other nodes to have a record of our last known position if we go away and allows a paired phone to hear from us and download messages.
-- While in LS: Every send*owner_interval (defaults to 4, i.e. one hour), when we wake to send our position we \_also* broadcast our owner. This lets new nodes on the network find out about us or correct duplicate node number assignments.
+- While in LS: Every one hour, when we wake to send our position we \_also* broadcast our owner. This lets new nodes on the network find out about us or correct duplicate node number assignments.
 - While in LS/NB/DARK: If the user presses a button (EVENT_PRESS) we go to full ON mode for screen_on_secs (default 30 seconds). Multiple presses keeps resetting this timeout
 - While in LS/NB/DARK: If we receive new text messages (EVENT_RECEIVED_TEXT_MSG), we go to full ON mode for screen_on_secs (same as if user pressed a button)
 - While in LS: while we receive packets on the radio (EVENT_RECEIVED_PACKET) we will wake and handle them and stay awake in NB mode for min_wake_secs (default 10 seconds)