RadiantLabs / modeling-api-docs

Official Modeling API documentation
0 stars 1 forks source link

Conflicting HVACHeatPumps IDs With Address-Only Requests #37

Closed lukeduran closed 8 months ago

lukeduran commented 8 months ago

We are getting an error when sending "address only" requests. It seems to relate to HVACHeatPumps.

Request

{
    "addressFull":"107 Ryan Dr, Hendersonville, TN 37075-2245",
    "addressComponents":{
       "addressLine1":"107 Ryan Dr",
       "city":"Hendersonville",
       "stateAbbreviation":"TN",
       "zipCode": "37075-2245"
    },
    "globalControls": {
        "includeTypical": true,
        "resolution": ["annual","monthly"],
        "timelineStartDate": "2023-09-01",
        "timelineDurationInYears": 1
    }
}

Response

{
    "errors": [
        {
            "in": [
                "timelines",
                0,
                "models",
                0,
                "appliedBaseBuilding",
                "systems",
                "hvac",
                "hvacHeatPumps"
            ],
            "message": "invalid type",
            "code": "invalid-type"
        },
        {
            "in": [
                "timelines",
                0,
                "models",
                0,
                "appliedBaseBuilding",
                "systems",
                "hvac",
                "hvacHeatPumps"
            ],
            "message": "There are one or more objects with conflicting IDs in HVACHeatPumps"
        }
    ],
    "globalControls": {
        "timelineStartDate": "2023-09-01",
        "resolution": [
            "annual",
            "monthly"
        ],
        "includeTypical": true,
        "timelineDurationInYears": 1
    },
    "addressFull": "107 Ryan Dr, Hendersonville, TN 37075-2245",
    "addressComponents": {
        "zipCode": "37075-2245",
        "addressLine1": "107 Ryan Dr",
        "stateAbbreviation": "TN",
        "city": "Hendersonville"
    }
}
kellyatradiantlabs commented 8 months ago

@lukeduran We just pushed some changes in our code repo and this issue is now resolved. I just retried this request and it is successfully modeling now.