Might as well add « show me the %room% », no?
It won’t hurt :-p
Thank you @cicoub13 aka Lucky Luke for the PR 
I just merged it and the fix will be included in the next Gladys release!
I think I just found a small one too…
When you click on ‹ save now ›, you get this:
Shouldn’t it be ‹ il y a ›?
Or is that normal?
There must be a slight offset (even 10 ms is enough) between your Raspberry Pi’s time and your browser’s time, which causes the generated timestamp to be in the future relative
2 Likes
Good evening everyone,
I’m having a problem with injecting variables into a scene and I can’t manage it.
Explanation: In a scene that I had already created and that was working correctly, I modified a sensor in zigbee2Mqtt. I wanted to update my scene, so I deleted the part that no longer worked and then recreated it.
So I retrieve the last state of my sensor « magnet buanderie » and then I create a message where I inject the variable, to display its state in my message. The problem is that when I type ‹ {{ › Gladys suggests a different sensor than « magnet buanderie »; in this scene I repeat this piece of scene 5 times, so 5 different sensors.
see image, it explains more:
I’ve tried changing browsers, Firefox, Chrome, the problem remains the same and it’s always that sensor « magnet porte d’entrée » that is shown instead. Is this a bug or am I missing something?
thanks for your help
ps: the thread « injection d’une variable dans une scène » is closed, that’s why I’m writing here
In another scene that uses the same principle, I get strange values in this scene:
I think there is a problem
Remove the quotation marks first, since they’re not necessary. The syntax requires that you put a space after the {{
Does that change anything?
Hello @GBoulvin
Thanks for your reply — I should have waited until this morning to post; sleeping on it helped. This morning I had the revelation, then I read your reply. Indeed, that’s exactly what
2 Likes