Bug or regression? Variables now incorrect

Hi @pierre-gilles,

This morning I created a new scene for « Gladys starts » and I took the opportunity to update my « intrusion detection » scene.
But to my great surprise, my variables were turned into text and therefore no longer appear in the final message sent on Telegram.

The last line allows comparison of what should have been displayed:

I went through Gladys Plus and reloaded the page several times just in case. A trigger test also confirms that the variables here are in error.
Same behavior locally.

Wouldn’t you just need to add a space in the variable’s syntax? I find it surprising that it’s displayed like this :

{{0.11.lastvalue}}

Should be :

{{ 0.11.lastvalue }}

It’s a scene that has existed for several months and was working.
I don’t know since when it was « modified », maybe because of the update?

I’ll admit I don’t know anything about that… :confused:

Hence my message :sweat_smile:
Either I’m the only one and it’s just bad luck, or there was a bug or a regression in the library update or in part of the core?

I just checked on my side, the scenes where I use a message that contains variables are still OK, the variable is still formatted as it should be.
Sorry for not being much help ^^
We’re waiting for the boss!

Thanks, at least you’re providing some context!

1 Like

For my part I had the same kind of issue, but only with a single variable.
As for how long, no idea, though

You must have modified the scene order, each variable is identified by its position in the scene (0.1.1 are the coordinates of the variable in the scene)

If you change the order, it indeed re-creates the variables’ positions and breaks the functionality!

That’s interesting — could this be implemented as a dev task so that the variables and their coordinates are updated when the position changes in the scene?

That’s it, I added a « if the alarm is armed » block as a condition.

I understand better why it’s « broken », but to me that’s rather a bug in that case. As a user I would expect Gladys to update the references automatically, as is the case with retrieving the latest values if I change one of the sensors.

Yes, that’s true, we’d need to recalculate all the references! Are you creating a GitHub issue?

1 Like
1 Like

DAMN I just created an issue too… ^^ @pierre-gilles I’ll let you delete it :wink:

You can close it, can’t you?

Ah yes, sorry — I didn’t think I had the option to close. It’s done!