Reduce API calls

[CFenner]

To get a full picture of a system, today each device needs to be updated on its own.

https://documentation.viessmann.com/installationgatewayfeatures-featuresapi-mw-iot/v2#installationgatewayfeatures-featuresapi-mw-iot_Get_gateway_features

https://api.viessmann.com/iot/v2/features/installations/
  {installationId}/gateways/
  {gatewaySerial}/features{?regex,filter,skipDisabled,includeDevicesFeatures}

includeDevicesFeatures
indicates whether return or not devices' features; if this is set to true, the disabled features will be filtered out

Maybe this endpoint could be used to fetch the data point for all devices of a gateway and therefore reduce the number of requests that are needed.

[lackas]

I've analyzed this and tested the bulk endpoint against my own installation (Vitocal 300G with RoomControl).

Finding: Bulk endpoint returns significantly fewer features

Device	Bulk fetch	Individual fetch	Missing
gateway	2	3	-1
0 (heat pump)	92	188	-96
RoomControl-1	12	457	-445
HeatDemandControl	1	5	-4
Total	110	653	-548

The missing features include core functionality: heating.circuits.* (operating modes, schedules, heating curves, temperature sensors), and most RoomControl features.

The API docs say "if this is set to true, the disabled features will be filtered out" - but these aren't disabled features, they're actively used.

Test script and results

I've created a test script to reproduce this: https://gist.github.com/lackas/2bff2fdf48f0dfb3a4fd5f2520e8bae3

Questions

1. Is this the expected behavior of the bulk endpoint?
2. Do you know of another API parameter or endpoint that returns the complete feature set?
3. If no full bulk endpoint exists, would it still be valuable to use bulk fetch for initial device discovery (fewer features but lower API calls), then individual fetch for full data?