Connection Schedule Repeat Interval conflict between protocol spec and Device Profile.

[GCoxCasey]

In section 2.1.4 Conneciton Scheduling the protocol document says

Repeat Interval
The repeat interval indicates the period in milliseconds at which the FD must re-attempt to contact the Broker, starting at the Start Time. A repeat interval of zero indicates that the scheduled connection is once per week or month. Scheduled connections repeat at the same time each week. For example, a connection at the start of Tuesday and Friday is achieved using a boundary of a week, a start time of 24 hours, and an interval of three days.
Repeat Count
The number of repeat connections that are made during the startBoundary interval after the initial connection has been made. For example, if the repeat count is two, then there would be three connection attempts (one initial connection plus two repeats). These would be spaced by the repeat interval.

The key point here being:

A repeat interval of zero indicates that the scheduled connection is once per week or month
Which as an aside needs to include Daily.

The default Device Profile:
https://github.com/LucidProtocol/Lucid-Specification/blob/master/Field%20Device%20Profile.json
Is not currently compatible with this:

`"repeat": {
"displayName": "Repeat",
"description": "The number of milliseconds between the start of each connection attempt.",
"type": "integer",
"min": 1,
"max": 604800000,
"group": "commsSchedule",
"order": 2
},

      "count": {
        "displayName": "Repeat Count",
        "description": "The number of repeats during the startBoundary interval.",
        "type": "integer",
        **"min": 1,**
        "max": 10000,
        "group": "commsSchedule",
        "order": 3
      },`

The 'min' fields are both set to 1, based on the current spec they should both be zero.

This would give the logic if Repeat Count AND/OR Repeat Interval are zero then FD connects ONCE per Start Boundary.

It could be argued that the special zero value for Repeat Interval is not really required if Repeat Count can be set to zero but it also makes little sense to force the user to configure a non-zero Repeat Interval if the intention is not to repeat.