# Gladys Assistant 4.84.4: OAuth over HTTPS and value selector in scenes

**URL:** <https://community.gladysassistant.com/t/gladys-assistant-4-84-4-oauth-en-https-et-selecteur-de-valeurs-dans-les-scenes/10450>\
**Category:** Actualités\
**Created:** [August 4, 2026, 7:27pm UTC](https://community.gladysassistant.com/t/gladys-assistant-4-84-4-oauth-en-https-et-selecteur-de-valeurs-dans-les-scenes/10450 "2026-08-04T19:27:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [August 4, 2026, 7:27pm UTC](https://community.gladysassistant.com/t/gladys-assistant-4-84-4-oauth-en-https-et-selecteur-de-valeurs-dans-les-scenes/10450/1 "2026-08-04T19:27:35Z")

</div>

Hi everyone!

A small evening release, following directly from yesterday’s feedback: the real Spotify OAuth fix (via HTTPS), the alarm bug during arming, and some very concrete UX improvements 😃

* * *

## External Integrations: OAuth2 via [my.gladysassistant.com](http://my.gladysassistant.com)

Spotify (and modern OAuth providers in general) no longer accept a `redirect_uri` in HTTP on a local IP (`http://192.168.x.x`). Result: most self-hosted installs were getting a `redirect_uri: Not matching configuration`.

This is fixed: Gladys now uses an **official HTTPS redirect page** :

`https://my.gladysassistant.com/redirect/oauth`

Same principle as Home Assistant, Freebox, Synology, and many others:

- you declare **this URL** on the Spotify side (no need for a certificate at your end)
- after authorization, the page redirects you to your local instance
- the page is **static** : no tokens / credentials pass through our servers

On the Gladys config side, the URL to copy is now clearly displayed (with a copy button).

Available for **all** OAuth2 external integrations, without changes on the integration side.

Thanks to @l.dolle for the report, and to @Will_71 for the end-to-end testing 🙏

* * *

## Alarm: Disarm during arming

Forum feedback from @bob: a scene triggered by “alarm in the process of arming” that disarms the house if a door is still open… it did cancel the delay, but the UI remained stuck on the countdown at 0, without any disarm event / trigger.

Cause: during the arming delay, the house is still `disarmed` in the database → the disarm raised a `ConflictError` (“already disarmed”) before emitting anything.

This is fixed: disarming (or entering the code on a tablet) **during** the countdown properly cancels the arming, and the triggers / events are sent.

* * *

## Scenes: Value selector in “Continue only if”

For features with fixed values (binary sensors, pilot wire, fan, etc.), no need to type `0` / `1` / “Closed” blindly: a **list selector** offers the possible values, translated.

 ![Screenshot 2026-08-04 at 20.58.13](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/a/e/aef9e69961d7d39e54428b34d84f3a732a228d39.png)

You can still switch to a custom / variable value if needed.

* * *

## System: UX for update verification

Following yesterday’s thread (@spenceur): the “Check for updates” button now has real feedback:

- dedicated loading state (without graying out the entire card)
- success message if you are up to date
- error message if the check fails
- display of the version number when an update is available

* * *

## Other fixes

- **External Integrations** : “Force update” always refreshes the index + compares with the repo manifest (no more false “already up to date” due to cache)
- **Devices / Features** : Duplicate names automatically generate a unique selector (`-2`, `-3`, …) instead of failing on creation

* * *

As usual, Gladys will update automatically within 24 hours if you use Watchtower, otherwise you can do it with one click in the settings.

[View full release notes on GitHub](https://github.com/GladysAssistant/Gladys/releases/tag/v4.84.4)