Hi @StephaneB ![]()
I was waiting for some feedback before making my own so as not to monopolize the discussion, but if no one jumps in, I’ll go ahead ![]()
Dashboard
Could this be solved by an easier drag & drop that would « compress » the size of widgets, like we do on mobile for example?
I see two things:
- First, we could set default settings instead of leaving quite a few parameters « empty »
- Indeed, we could save the last settings of the last chart, that doesn’t bother me!
That’s totally possible!
On one hand I agree, but on the other I struggle to see how we can fit that in such little space. If we add a search bar + a filter-by-device-type bar, that adds quite a bit of height
But it’s worth investigating, I agree with the comment!
Why not!
I think the opposite: it should be automatic, indeed currently we don’t handle refresh when you come back to the application, and we could handle it fairly easily. I vote for it!
Why not, but then we lose the last hour?
I’m really not against changing it but we need to gather the needs of other Gladys users.
Okay to start the debate on a specific topic.
Why not change that indeed (as far as possible, we use ApexChart, I don’t know if it’s configurable)
Scenes
You’re not the first to complain, I created a GitHub issue, it’s a bug:
The problem with that is that the title then becomes the « selector » (unique identifier of the scene), and so you’ll end up with scenes called « copie-de-detection-mouvement-entree », instead of the proper name of your scene. Knowing that the selector is immutable.
Afterwards, it’s a choice, we can say we don’t care about the selector, but then it creates little points of frustration, for example if you use the Gladys API to trigger scenes, then to identify your scene you’ll have this title which doesn’t correspond to the current name of your scene.
Now, which point of frustration is stronger?
Why not!
As a result, we lose screen width on the scene view which is often already compressed! To be seen, I’d welcome a mockup ![]()
Other scenario creation software can be a source of inspiration (eg: Zapier, Apple Shortcuts)
I’m afraid that would complicate the scene creation interface a lot, which in my opinion is already complicated…
I’d like you to check if this is something that’s possible in other scenario-creation softwares, and if so how they do it (Apple Shortcuts, Zapier)
Yes! There’s already a feature request for that I believe (I think it was @lmilcent who created it but I don’t remember). I’d like you to find it and upvote ![]()
I know, and I’m the first to find this limitation inconvenient ^^
For now, no one has found a solution.
I’d be keen to know how other scenario-creation softwares do it (Apple Shortcuts, Zapier)
Zigbee2Mqtt
I understand the problem, but I’m not a fan of that solution.
Maybe that view could be simplified so that logging is more visible at a glance?
Indeed, I don’t think the synchronization is done both ways / nor that the current implementation supports the new pairing mode with expiration that appeared in Zigbee2mqtt after Gladys integration