Add a verbose mode (Logs) to Gladys

I think Gladys is missing a verbose mode

Would it be possible to add a « Logs » field between « Service » and « System »?
We could put interesting events for the user there such as:

Timestamp- Gladys : Update/restart
Timestamp- Containers : Update/restart
Timestamp- Scene : Start/end at step
Timestamp- Devices (lights/switches) : off/on
Timestamp- Alarm : off/on, wrong code entered, etc
Timestamp- Network loss

To avoid this causing a large overload, it might be possible

To avoid overconsumption, could verbose mode be temporary?

« Activate for XX minutes »

@cce66 I deleted your message in the other post since it didn’t have a link :slight_smile:

I agree there’s a problem, but I think we can implement the solution differently.

The « Background tasks » tab already exists.

That tab is indeed missing some data:

  • Restarting Gladys
  • Running a scene

For devices, there’s already a request:

:+1:

Indeed that could work if the events mentioned above were integrated into that tab, but it should be possible to filter by events and date because it would quickly become hard to find a specific event

Indeed, I think we should ultimately merge these two requests, I may add my request as well

The ideal for me:

  • a place where we can check the general state of the system (backend: updates, stop/restart containers, network status, key status, data aggregation…)
  • a place where we can check the status of user-facing features (frontend: scenes, devices to see device state changes during scene execution, etc)
    Currently, you can design scenes but you almost have to verify them live to be sure they’re OK

Indeed, or a FIFO log for 24 or 48 hours or based on a size allocated to logs

@pierre-gilles, if you want you can attach this post to the other one and delete this one which is more of a complement than a new request

1 Like

On the contrary, I prefer to have very specific requests rather than a single very vague, « catch-all » request :slight_smile: