Oh but wait, youâre not on Raspberry Pi! Youâre not using the official Raspbian image then.
You simply lack watchtower, itâs a container to launch alongside.
I invite you to check out the Gladys documentation:
PS: Be careful about the architecture youâre using, make sure to launch the right tag of the Docker Watchtower image. On Raspberry Pi we use armf, not sure if thatâs what you need.
Iâm posting here because Iâm not sure if itâs useful to create a new topic for this.
I find that the dashboard lacks clarity regarding the amount of information displayed.
To explain myself, I photoshopped a part of my dashboard to be clearer:
I would find it a bit more logical for each device to be separated from the next within the same room, as I also have Fibaro motion sensors that provide: brightness / presence / temperature / movement / battery / etc⊠If in the same room I have another device that gives me the temperature or if there are many features, I get lost ^^
I therefore imagined a card-header (Iâm talking as if the interface used bootstrap) of a different color and a list separated according to the devices.
Does this seem relevant to you?
I agree with you, Iâve been using V4 for testing since yesterday and I must say that I donât like the « Devices in room » widget.
The others are nice, but this one really looks rough (unfinished):
Your suggestion refreshes it, but Iâm not convinced by the design..
In case some people donât know, Dribbble is great for inspiration 
:
Are you using the official Gladys 4 or the zigbee2mqtt built branch? Itâs unfinished because youâre using an unfinished branch I think
The goal of the « device in rooms » box is to look like this:
Indeed, what you present is not clear, it will be changed before being integrated into master
I put my answer on the zigbee2mqtt topic here:
https://community.gladysassistant.com/t/tutoriel-zigbee2mqtt/5097/123?u=pierre-gilles
For the battery display on the dashboard, itâs a debate we have every time 
I put my opinion here: the battery, as long as the battery is good, the user doesnât care to see it on the dashboard, itâs information without added value. The only use of having feedback on the battery is when the battery is low. There, the user should receive a notification telling them « warning, battery below X% on sensor XX in the kitchen ».
For the story of having a display of devices « grouped », I agree that it would be great!
We talked about it at length this summer in another topic, I invite you to read the debate we had:
For now, no design has really appealed to me, but Iâm sure we can come up with something beautiful!
Small remark, if you have feedback on work still in development, do it on the topic of the branch concerned, or on the PR, itâs more practical
So all my apologies, as a newcomer I realize that I have missed a lot of debates and I speak without knowledge of the facts ^^
I absolutely agree with the fact that we donât care about the battery unless it goes below a certain level 
Got it, boss 
Hello everyone!
I would like to discuss an important topic: the official release date of Gladys 4, or at least the release date of the first RC!
I made a post to talk about it, and I would like your opinion
Read it here 
Indeed, I am currently on the zigbee2Mqtt container,
I will check out the official one then.
I find the rendering more pleasant but perhaps a bit too sober in your sceen
This is an ARM architecture, thereâs a difference with armf.
I ran the command from the documentation, and I think I crashed everything.
@Tlse-vins Which image are you running, Gladys? If youâre running the arm64 image, then you should run the arm64 image of Watchtower ^^ Iâm redirecting you to the Watchtower documentation that explains all this
I have installed the latest version of Gladys, I confirm that Philips Hue are recognized and working.
Iâm coming back to this because the image Iâm using is indeed the official one that I downloaded from the Gladys website.
The only difference is the implementation of Docker, after that I followed the documentation.
Could it be that Watchtower is not running?
Is it possible to add this option in the Gladys image for Respeaker?
I leave it to you @pierre-gilles.
I didnât manage to run the command to update, I completely reinstalled Gladys but I wouldnât want to have to do that every time.
To view running Docker containers, use this command:
docker ps
I think someone has already mentioned this: Is it possible to differentiate the different lines in a box?
@Tlse-vins: Can you create a specific topic to talk about this issue? I feel like weâre not understanding each other ^^ Iâm talking about Raspbian image, and I think youâre talking about Docker image.
Hello @pierre-gilles.
I wanted to know what you thought about the self-detection that HomeAssistant performs.
After installing and setting up the user, HomeAssistant seems to launch a scan of the devices that the user seems to own (in my example, it found a Chromecast, my Philips Hue, and my Sonos).
Since Gladys has the services in its core, couldnât it be smarter by performing a scan (local, no data sent of course) and thus make integration simpler for a user?
Thatâs great and itâs exactly the goal I have with Gladys 4! Itâs one of the advantages of having the code of the services internally
For now, we donât have many services that scan the network (only Philips Hue I think), but as soon as we have more, we can make a more complete configuration assistant!
I think we can already normalize the case with the few services we have. The sonoff / tasmota and future zigbee2mqtt also offer this. Bluetooth and its sub-services already plan for this.
But I love this idea!!!
Hello @pierre-gilles
Congratulations on this new version, Iâve been following the project from afar for a few years now and Iâve just taken the plunge with v4 
A quick question (which may have already been asked, sorry): is it normal that I donât see the interface to create scenarios at all? I tried to look a bit on the forum but I donât see anything.
Thanks and keep up the good work
Yes, thatâs normal, itâs not developed yet
@deep Thanks for your message! The scene view is under development, weâre actually discussing it in this topic: