Feature Request
Heatpump model:
S series
Firmware version:
Any plans to support nibe local REST api Connection?
Point data is available at /api/v1/devices/0/points. Looks like data could be mapped against current model json file through modbusRegisterID. Assuming Nibe keeps REST and MODBUS api 1:1
Another approach would be to abandon Modbus ids for this connection type and use variableId.
"4": {
"title": "Aktuelle Außenlufttemperatur (BT1)",
"description": "",
"metadata": {
"type": "metadata",
"variableId": 4,
"variableType": "integer",
"variableSize": "s16",
"unit": "°C",
"modbusRegisterType": "MODBUS_INPUT_REGISTER", // <- Register type
"shortUnit": "°",
"isWritable": false,
"divisor": 10,
"decimal": 1,
"modbusRegisterID": 1, // <- Modbus register
"minValue": 0,
"maxValue": 0,
"intDefaultValue": 0,
"change": 5,
"stringDefaultValue": ""
},
"value": {
"type": "datavalue",
"isOk": true,
"variableId": 4,
"integerValue": 100,
"stringValue": ""
}
},
Feature Request
Heatpump model:
S series
Firmware version:
Any plans to support nibe local REST api Connection?
Point data is available at
/api/v1/devices/0/points. Looks like data could be mapped against current model json file throughmodbusRegisterID. Assuming Nibe keeps REST and MODBUS api 1:1Another approach would be to abandon Modbus ids for this connection type and use
variableId.