Skip to content

@fracz fracz released this Feb 12, 2019 · 35 commits to master since this release

  • Direct links
    • generating a link for a channel or group of channels
    • determining what actions can be done using the link
  • User icons for channels and channel groups
    • in the channel details you can upload your set of icon files
    • icons are assigned to the function, i.e. you can use the set once sent in several channels
  • New channel features
    • electricity meter
    • water meter
    • gas meter
  • Controlling channel groups in schedules
  • Delete the measurement history from the channel details page
  • Authorization of external applications in accordance with OAtuh 2.0
    • proprietary OAuth Broker mechanism, allowing for the authorization of public applications on the users' servers https://github.com/SUPLA/supla-cloud/wiki/OAuth-SUPLA-Broker-workflow
    • the mechanism for registering private instances on cloud.supla.org, which enables the above functionality
    • abandoning the authentication mechanism in SUPLA Cloud based on the session
    • transparent authentication with CORS (i.e. users will always remain in cloud.supla.org)
    • catalog of public applications
    • determining access to the SUPLA API divided into functionalities (scope)
    • creating your own OAuth applications
    • generating personal access tokens
    • removing the current way of granting access to the API, maintaining compatibility for existing integrations
    • Providing external applications integrating SUPLA with Amazon Alexa and Google Home
  • GUI / UX
    • a clearer way to select channels in groups and schedules
    • a clearer way to change the channel function
    • "with function" filter in the channel list
    • redirecting to the target page after logging in
    • translation into Slovak
  • Cloud management
    • command to delete a selected user
    • command to set the limits of the selected user
    • API (details will appear in the new version of the Swagger documentation)
    • possibility of collecting the state of the channels from the list of devices and channels collectively
    • response status 401 instead of 400 when authentication is required
  • Fixes
    • the link to the original device location indicates the correct location
    • the possibility of reversing the logic for the channel with the "Window opening sensor" function
    • Incorrect email language with notification of password reset
Assets 3
You can’t perform that action at this time.