Hello
\[following my scene issue and certainly a loop that can’t be found \]
I’m redoing my heating scenes rather than writing everything out, which isn’t my strong suit; so here’s an algorithm of what I’d like to do — I’m open to any ideas.
So I started positioning it in a scene — I’ve already made the 7 states in the bottom right and it looks like this
I find that the layout causes some difficulties: we’re stuck on the sides and don’t use the full width, which is a shame. (after checking in the inspector, if you modify the CSS class: container mb-8 to the width of your screen this fixes the issue until the page is reloaded)
The numbering also becomes complicated to manage in practice.
A suggestion had already been mentioned, but it would be useful to add visible or written comments to make it easier to find your way.
Similarly, the numbered A2 blocks that are imposed automatically are not always practical. It would probably be more sensible to have a button to add them only when you need them. That would give more freedom in the layout and avoid ending up with unnecessary blocks.
Hi @Prof_Techno, quite the diagram!
I couldn’t make out your scene because the screenshot resolution is too low (even when clicking « view original image »)
If I could give you one piece of advice, it would be to use the « Start scene » action which would allow you to split your large scene into small blocks, and thus factorize some actions:
For example, at the bottom of your diagram, you have cases that are always the same (target temperature reached or not → turning the pilot wire on or off).
Couldn’t this small block be its own scene?
One advantage of this strategy is that it lets you test each part of your scenes separately, and above all have smaller, more readable scenes.
Be sure to properly name each scene, with a description, and tags so you can find them easily.
You’re right!
On the « dashboards » and « scenes » views, we could increase the max-width.
I’ll look into that.
Edit: Discussion sur la largeur de la page "tableau de bord" et "Scène"
I think your scene is too complex; it should be split into smaller scenes in my opinion 
Don’t hesitate to create a feature request; I didn’t find an existing request on this topic, but it’s true that it’s not the first time we’ve talked about it!
Why not! Don’t hesitate to create a feature request
1 Like
Hello
No more than 15 minutes of work (I’ve already spent 2 hours doing it in the scenes and it’s not finished)
For the image I’ll redo something tonight on an external host because otherwise it hits the forum’s limit
I thought of that but for that you would need variables that pass from scene to scene otherwise the benefit wouldn’t be obvious (for the variables concerned this would be temperature but also the device involved for example). I’ll add the info on the graph tonight
My goal was to limit the number of scenes (currently more than 40 scenes to manage the heating while I only have 6 radiator zones to manage) because otherwise it quickly becomes difficult to manage (personal opinion even if tags have started to make it easier)
Personally I find the scene still simple because it doesn’t yet take into account my outdoor movements or movements within the house
I’ll prepare something when I get home with the help of AI to rephrase my sentences given my difficulties.
Thanks for your reply
I’ll add to this message at the end of the day with new images to better document the work already done.
It’s entirely possible
You create a device in the MQTT integration, and you give it a function, it’s a so-called « virtual » device, and in the scenes you assign it a value before moving to another scene.
Many of us use these virtual devices to store information between scenes
You can create a wide range of devices like « Setpoint temperature », « Heating on/off », etc…
In my opinion, with virtual devices you can greatly reduce that number, while keeping a separation between actions.