v23.05.01

• fix disabling and enabling schedules from supla-server perspective
• fix exporting measurements history for channels with special characters in their names

v23.05

• complete rewrite of measurement logs charts for all supported channel functions #668 #673 #691 #693
• new formats for logs download (CSV, ODS, XLSX, HTML) #672
• ability to choose a value separator in CSV logs download #671
• add ability to enable or disable schedules from scenes, direct links and action triggers #548
• a new Security panel in accout dropdown with compact summary of all active sessions, tokens and applications that can use your account #701
• ability to add a delay at the end of the scene #688
• configuration options for Alexa/Google integration for scenes (hiding, pin, acknowledgements) #663, #664
• improve appearance of register forms #665
• smaller fixes and improvements #641 #679 #689 #692 #700 #680

v22.12

• voltage aberrations logs improvements
  • load the whole voltage aberration history with inifinite loading while browsing (fixes bugs: #657, #659)
  • ability to delete logs from selected phase only #640
  • clearing voltage aberration logs older that configured lifetime (in public clouds the default is 180, in Docker instances - 1000) #643
  • fix the problem with setting low and high thresholds #644
• ability to hide unused phases for electricity meters
• ability to hide scenes from client's devices (smartphones) #661
• add configuration panels for Google Home and Alexa integrations (availability, action confirmation) #428, #654, #655, #660
• support for storing measurement logs in another database #656
• OAuth2 improvement: expire refresh token only after its access token has been used successfully
• Docker only: add appropriate healthchecks for supla-cloud that will prevent supla-server from starting before the database is ready

Be careful when upgrading with Docker!

If you are upgrading your private instance with Docker, make sure you meet the new version requirements of Docker and Docker Compose before the upgrade.

• miminum version of Docker is now 17.09.0, check with docker -v command, the previous requirement was: 17.06.0, see upgrade instructions
• miminum version of docker-compose is now 1.25, check with docker-compose -v command, the previous requirement was: 1.17, see official upgrade instructions or installation with pip (for Raspberry)

v22.11

• Automatic closing for gates #128
• Add recording of voltage aberrations in electricity meters #511
• Ability to choose gate state verification method #611
• Allow to wait for scene execution before proceeding with the actions #576
• Support for devices in sleep mode #622, #623
• Fix smaller UI bugs #616, #609, #621 #528, thanks @jaku2019 for reporting
• Technicial improvements
  • Replace moment.js with Luxon (results in more than 2x less webapp entrypoint size)
  • Provide unit tests and E2E tests for frontend

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 to v2.1.0, if not specified otherwise
• new v2.4.0 API is available through /api/v2.4.0 prefix
• remove all arrays thtat contained identifiers of related collections like channelsIds, accessidIds, locationsIds, iodevicesIds from the responses; in order to find out the number of related entities, a new relationsCount property 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
• possibleActions array 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-logs endpoint are converted to numbers and are not returned as strings anymore

v2.3.37

• Separate number of attempts for opening and closing gates #519
• add Include energy corrections in new measurements history checkbox for intitial values (renamed to Added values) #526 #527
• improve default levels for error logs #520
• ability to define a custom webhook for user (only local instances) #525
• small bugs fixed #523, #530

v2.3.36

• new COPY action that allows to copy state from one channel to another #484
• new SHUT_PARTIALLY action (as opposed to already existing REVEAL_PARTIALLY)
• new roller shutter actions (SBS, SHUT_PARTIALLY, MOVE_DOWN_OR_STOP, MOVE_UP_OR_STOP) #483 #489
• e-mail notifications
  • panel for managing e-mail notifications in user account settings
  • new notification: new IO device connected #141
  • new notification: new client app connected #140
• initial values for electricity meters #493 #497
• ability to enter device configuration mode from cloud (firmware update required) #507 #448
• setting the number of retries for open or close the gates #492 #495
• new Access Triggers' actions #490
  • publish to integrations (MQTT and webhooks)
  • disable local function
• GUI improvements
  • better (hopefully) buttons for executing actions #517
  • lifting of details pages
• add support for pairing measurement channel with staircase timer #474
• increase the range of setting the rollershutter closing / opening time from 300 to 600 seconds #383
• improve performance of generating CSV measurement logs #499
• redirection to your own server when update is in progress #516
• bug fixes and other small UI improvements

v2.3.35

• Action Triggers #206 #475
• use current user languange to set automatic name for new locations and access identifiers #341
• fix direct links history display #476
• expose supla-server status in API #455

v2.3.34

• more flexible schedules #322, #200, #152, #232
  • new schedule modes
  • advanced crontab input
  • multiple actions in single schedule
  • 1-minute interval for planning
• support for more calibration modes of roller shutters #464, #466, #449
• add ability to reset counter state #456
• new flow for changing channel function in GUI
• UI improvements #468, #462,
• add supla-server status check #471

v2.3.33

• fix: display measurement history for impulse counters #463
• fix: detect changes of relay time for staircase timer