Hi everyone, are you encountering the same bug as me on the device « shutter state »?
When I click the buttons, there’s no reaction from the shutters. Example of shutters:
When a scene sends a value to these shutter devices, it works. For example these buttons that send values to the relevant shutters:
It’s been a few days, at most two weeks, since they stopped responding like this.
I admit I’m having trouble understanding everything! 
Do you have screenshots of your setup? Virtual device + scene
Sorry, identifying the problem is actually simpler following additional tests. I’ll edit my post.
It’s hard to help you with so little information
For example these buttons that send values to the relevant shutters:
How?
To understand the bug
OK, sorry again, I summarized too much 
The shutter buttons are configured with the values -1, 0 and 1 for the three commands.
For some of my shutters with a 433MHz module, I use Node-RED which is subscribed to the different topics and which, depending on the value, sends the 433 code that corresponds to the values/shutters.
Here is an excerpt of my Node-RED flow:
For two others using the Somfy sub-protocol, I use an ESP8266 that is subscribed to the topic and which, depending on the received value, sends the code that corresponds to the values/shutters.
No image except the ESP code.
Testing the buttons for these two types of shutters does nothing at all.
However, with my scene examples, for example closing the living room shutters, the relevant shutters do close properly.
A test of injecting a value into the MQTT button topics also makes them react.
Node-RED flow injecting value into button topic:
Here is the scene that triggers the closing of the living room shutters:
I tested this scene to receive a message if the office value -1 is obtained but I don’t receive any message when I press the button.
However I receive it if I inject the value via Node-RED:
I hope this time I provided enough. 
Everything seems to indicate that it’s the buttons that do not « react » to clicks.
Did you run tests without any condition (« bureau (volet-bureau) < 1000 » for example, something bogus) to see which value was sent when you click the button?
I’m not sure I understood your proposed test.
Here is the scene I set up :
I also tested a return to Node-RED with display of
@tiboys I confirm that I can reproduce the bug, it doesn’t work on my side either!
Can you create a GitHub issue? 
It’s done.
I hope I did that properly because I’m not very familiar with it ..
Thanks! I’ve renamed the issue
I found the source of the issue, the bug comes from the new « Devices » widget, it simply never worked 
If you use the old « Room devices » widget, it works normally
The fix is here:
It’s true that this coincides with my widget setups that replaced my old boxes.
I’ll revert to my old widgets.
I didn’t fully understand the code but thanks a lot.
[quote="pierre-gilles,
@Lokkye The bug was only present with « shutter » devices. We use a debounce so that if you move the slider gradually, it doesn’t send 15 requests, but only 1 when the user has finished moving the slider
The fix is live in Gladys Assistant v4.25.1:
