Hello @Hizo, sorry for the sleepless night, and thanks for the report.
No, the message in Gladys has not disappeared: it is still written in the conversation (you should see them). The SMS comes in addition, it does not replace anything. When a messaging integration is installed, Gladys broadcasts each message on all configured channels, so all existing scenes start sending SMS without having been modified. This is exactly what you describe.
And you didn’t miss anything: there was indeed no option « only in the Gladys conversation ». The « Send via » selector allows you to choose a specific channel, but not to choose none.
I propose a correction: an option « Gladys Conversation Only » should arrive on the blocks « Send a Message », « Send a Message with Camera » and « Ask the AI » (the latter had no selector at all: it sent the response on all channels, even when you just want to store it in a variable).
In the meantime, to cut off SMS immediately: clear your credentials in the « My Account » block of the SMS Free integration. Without configured identity, sending fails silently, and you keep the integration installed.
For the SMS that continue despite disabled scenes, two leads:
A disabled scene remains executable if it is called by the action « Run a Scene » of another active scene: only the triggers check the enabled/disabled state. Check your active scenes that launch others.
Some system notifications go through the same channel and have nothing to do with your scenes: low battery, Gladys update, backup, weekly digest.
@pierre-gilles a question on point 1: scene.execute does not check scene.active, unlike the triggers. Is this intentional (a disabled scene remains usable as a subroutine) or should a disabled scene never run, even if called by another? I can make the change, but it will have an impact on those who rely on the current behavior, and at least the editor should warn when an action « Run a Scene » points to an inactive scene.
Thanks for the PR! It is currently being merged and will be included in the next version of Gladys.
Yes, it is intentional
Just like a deactivated scene can still be launched manually, scene.execute does not take scene.active into account. Deactivation only affects automatic triggers.
After that, if several feedbacks show that this behavior is not the most relevant, we can of course question it. But as it stands, it is not a bug
