Attribute Default Value on Northbound side

During initialization of OCB entities, the library set some default attribute values based on type field. Here a snippet from deviceService.js file:

function getInitialValueForType(type) {
    switch (type) {
        case constants.LOCATION_TYPE:
            return constants.LOCATION_DEFAULT;
        case constants.DATETIME_TYPE:
            return constants.DATETIME_DEFAULT;
        default:
            return constants.ATTRIBUTE_DEFAULT;
    }
}

The value of constants.ATTRIBUTE_DEFAULT now is an empty string, what do you think about null value? In my opinion, semantically null is better: we are sensing something, so an empty string could be confused as real measure...

Start in deviceService.js at getInitialValueForType and inspect how constants.ATTRIBUTE_DEFAULT is used during OCB entity initialization. Determine whether the default should change from an empty string to null, then verify that initialized non-location and non-datetime attributes receive the intended value.