Good morning. I haven't found anything about this, but if the topic has been addressed, I apologize.
In version 4.11.36, when creating scenes, when transferring them to a frame, I can't find a way to enable the checkbox that previously existed to enable/disable scene intervention.
Am I missing a step?
.
Indeed. Since I left them all activated, I had nothing to add with the "+" and the screen appeared blank.
If, on the other hand, I left them all disabled in the configurator, I would have them all available with the "+" button.
As you rightly say, regardless of the scenes I create in the project, I like to leave them open so the client can generate them.
Thank you again for your help.
Best regards.
Hello,
I don't think that was the problem. I believe that you were confused by the UI change, which is perfectly fine.
When you add controls to the scene on the Configurator, it's up to you if you enable them or not right there on the Configurator. In fact, when you're creating a scene on the Configurator, when you add controls they are added enabled by default, which is the same that saying that those controls will be executed.
So basically you can choose what the scene will do, right there on the Configurator, you don't have to add the controls disabled, and then go and configure the scene on the app (unless it's for a client and you wish for them to create the scene instead of being you).
The same way, if you disable all the controls on the app for that scene, and you go and check on the Configurator, the controls will show up as disabled (you may have to exit and enter the scene, to see that the controls were disabled).
So enabling or disabling on the Configurator, doesn't matter. So you're free to add the controls on the Configurator (when you add them first, they will always be added as enabled).
Best regards
Another example, same scene, but with added shutters on the scene
(Please note that I had to add the shutters manually on the scene on the Configurator, as I only had lights there when I created the scene)
https://mega.nz/file/VvwyTTrI#hNbfAKJ2AxugFd0pePXTAyUi19JoyYWjFe7GzH--xcA
Best regards
Hello,
There has to be something wrong there. I have no problems with my scenes.
If you click add, and nothing else shows, then probably your scene doesn't have more circuits.
You have to check your scene first on Configurator, and make sure that the scene has all the circuits you want.
Otherwise nothing will show.
And then, go and check the scene again on the app.
I double checked, even created a demo scene, and it's working perfectly fine.
Check this video, with the configured scene:
https://mega.nz/file/8uBCkIaD#KxAVpxOeRwCmMNubkj7-D8uW6-hn_vf55Kpi8hXwCWc
Best regards
Ok, but my scene with multiple controls, when I press the + button, appears empty and I have nothing to select.
We agree that sometimes the list in the scenes was endless, but perhaps this radical change should have been documented in some way and even respected the old way of making scenes.
Hello,
The UI was changed, and now the scenes work differently.
On the previous UI iteration, all the circuits of the scene would show up on an eventual endless list, which in my opinion sucks, and you would check which ones were going to be executed.
This new UI is better in my opinion, so it only shows the circuits you actually want to execute. The remaining circuits are hidden. If you want to add up new circuits, just click under on the "+" button, and add what you want.
In my opinion this UI works better, because we don't get an endless and boring list of all the scene circuits, but rather only shows what was actually chosen to be executed. If you add new circuits, they will become visible.
Hope it helps.
Best regards
The ComfortClick team basically changed the UI for the scenes and timers, and I really think that this changes on the scenes make more sense.
Previously, we were presented with an eventual long list of controls (if we had many controls on the scene), and we had to go through that list and check / uncheck what we wanted to do.
In this new iteration, we are only shown what controls are executed, and they hide the not executed ones, and we simply just add more if we need them, but they remain hidden until then, to unclutter the view.
I was also intrigued when this new UI was changed, but as soon as I figured it out, then it makes all sense.
You're welcome