v22.07
Changelog
- Scenes #554, #557, #568, #565, #561, #555,
- working schedule (active hours) for access identifiers #514
- extend the possible gateway and door timeout to 2 minutes #535
- allow negative "added value" in electricity meters and impulse counters #536
- flow to re-register private instance in case the instance token in lost #465
- better support for humidity sensors #546, #571
- ability to download all user icon images in one request #564
- add link to public apps catalog in the Automation menu #552
- small bugfixes #172, #541, #538, #537, #540, #551, #554, #531, #567, #569, #570
- solve all NPM security vulnerabilities (at the time of the release)
- updated Github docs and API docs available at
/api-docs/docs.html
New versions scheme
From now on, the versions of the SUPLA Cloud, SUPLA Core, mobile apps and firmwares will be published as vYY.MM scheme. If multiple versions are published in the same month, they will consist of a third number, e.g. vYY.MM.bb. YY is a 2-digit year, MM is a 2-digit month and optional bb is a 2-digit subsequent version number published in the same month.
As for the API versions, nothing changes for now. This release introduces a new v2.4.0 API version with partial docs available at /api-docs/docs.html. The documentation is about to be completed in the upcoming releases.
Breaking API changes between v2.3.0 and v2.4.0
- drop support for API
v2.0.0; now all the queries are defaulted tov2.1.0, if not specified otherwise - new
v2.4.0API is available through/api/v2.4.0prefix - remove all arrays thtat contained identifiers of related collections like
channelsIds,accessidIds,locationsIds,iodevicesIdsfrom the responses; in order to find out the number of related entities, a newrelationsCountproperty is avaiable - do not send meaningless channel params through API for channels configuration; the API exposes a self-descriptive channel's config; all available channel's configuration options and the configs are listed here
- all IP addresses in API are now sent in decimal-dotted format instead of a long
- input/output feature of a subject is now declared on the function instead of a type #509, #572
possibleActionsarray is defined now in the first level of a channel/channel group/scene and is not tied to the function object- data fetched from
/measurement-logsendpoint are converted to numbers and are not returned as strings anymore