Adding an event log

[Will_71]

I would like to propose adding an event log feature to Gladys Assistant.

Feature description: It would be a centralized log that would list all important events in the home, for example:

• Openings/closings of doors and windows
• Alarm activation/deactivation
• Motion detections
• Sensor state changes
• Gladys restart
• Stop or restart of a service launched by Gladys (zigbee2mqtt, mqtt…)
• Shutter openings/closings
• Heating on/off
• Errors
• Etc.

Use cases:

• A browsable history of security events
• Quickly check if a door/window was opened during my absence
• View the alarm activation history
• Get an overview of the home’s activity over a given period

Proposed features:

• Chronological display of events (most recent to oldest)
• Filtering by event type (doors, windows, alarm, etc.)
• Filtering by room or by device
• Search by period (today, this week, this month, custom period)
• Possible export of data (CSV, PDF)

Here’s a mockup to make it clearer:

@pierre-gilles: I hope I was clearer than for my first request.

[pierre-gilles]

@_Will_71

@pierre-gilles: I hope I was clearer than for my first request.

Perfect, thanks
Your first request was clear but as the topic evolved, it no longer was! Now it’s perfect

[prohand]

Very good idea

I’m at my vote limit but +1 from me ^^

[Chris75]

Excellent idea! Maybe in a first step, having the possibility to download the history of all events from all sensors in CSV format?

[pierre-gilles]

@Will_71 Where are you at with the event log development?

I think this is a fairly trivial feature to develop for an AI. So if you’re stuck or don’t have time, I can handle it by running Claude on it.

@Chris75

Is it possible to download the history of all events from all sensors in CSV format?

There’s actually another open request about this.

Exportation des données au format CSV

Bonjours la communauté, Pour reprendre l’idée de @Prof_Techno, serait il possible de créer une fonctionnalité permettant d’exporter les données au format CVS afin de les croiser avec d’autres données externes? Merci beaucoup.

Regarding the event log, I also remind you that to view the history of binary sensors, you can already add a Graph widget to the dashboard, which will display this type of output:

It’s not exactly an event log, but it can do the job to see the history of a door opening, for example.

[Will_71]

@pierre-gilles

Where are you at with the event log development?

I wanted to give you an update tonight but didn’t have the time, I’ll do it tomorrow night

Edit: here are some screenshots anyway

A complete preview of what I’ve added

The ability to filter by type

By date

Or a standard search

[pierre-gilles]

Thanks for your feedback and for working on this development

I see that you’ve chosen to mix information from sensors with more “system” information. Doesn’t that create a bit of redundancy with the “Background Tasks” view?

I know it’s possible to filter by type, but I’m afraid that, by default, this view might seem a bit too technical and deter some users. Given its location in the interface, I think it would benefit from being as user-friendly as possible, with information that’s truly useful and actionable on a daily basis.

I wonder if the very technical events wouldn’t be better placed in the “Background Tasks” view, so that this one remains more usage-oriented.

I really liked your first graphic mockup proposal. I’m wondering if I should have Claude start a first implementation, focusing solely on events related to sensors and what’s happening in the house. The idea would be to have a view centered on the core business and daily actions, rather than on Gladys’ internal mechanisms.

[Will_71]

@pierre-gilles

Doesn’t this create a bit of redundancy with the “Background Tasks” view?

It might, but in that case, we need to rework the page because, as it stands, I never use it.

After that, I can remove them to focus on the job and daily actions

@pierre-gilles

centered on the job and daily actions

@pierre-gilles

I really liked your first graphic mockup proposal

Regarding the mockup, aren’t the colors missing from the icons?
After that, I added the filtering functions, which are essential.

If you do something else, go ahead, you’ll probably be faster than me.

[pierre-gilles]

@Will_71

Yes, but in that case, the page needs to be revised because, as it stands, I never use it.

The « Background Tasks » page can also evolve, clearly

@Will_71

Compared to the mockup, are the colors missing from the icons?

I found the sensor display much clearer in the mockup. The title was customized by device name, for example, « Living room shutters closed, » vs. « Device state change, » which isn’t very descriptive

[Will_71]

@pierre-gilles

The sensor display was much clearer on the mockup, I think, the title was customized by device name, for example « Living Room Shutters Closed », vs « Device State Change », which isn’t very descriptive

It’s just formatting, and as explained, I’m just at the beginning, so there’s still work to be done.

[pierre-gilles]

I asked Cursor Agent in Auto to develop the feature, and it came up with this in one go:

We can iterate on it, but I find it very clean.

By the way, I also ran Fable 5 on it to compare the results

[pierre-gilles]

The version of Fable 5 is less „design“ but more integrated with the patterns we already have in Gladys:

[Will_71]

A mix of both would be ideal

[pierre-gilles]

Yes I agree! I think the Cursor version is cleaner and we can just ask it to add more elements:

• Be able to view specific dates
• Filter by device type

[pierre-gilles]

By date, it offers this:

[pierre-gilles]

Hyper clean the selection of device categories:

[pierre-gilles]

The big advantage is that since this view remains focused on the « business usage » part and not on Gladys’ internal logic, there’s almost no backend code in the PR, and no data model changes. It’s all frontend.

So it could go out quite quickly. We can iterate on it, or even completely change tack, without consequences, because the data remains the existing data!

I really like it anyway

[mutmut]

I prefer Fable 5, we have more « simple » info on screen, it’s more condensed and I find the flow more readable. Live filters are nice but they take up a lot of space, and if you have to swipe right for 10 seconds to get the right filter, it’s annoying.

[pierre-gilles]

The screenshots were not taken at the same resolution, so the amount of information displayed is not really representative.

For my part, I have a preference for Cursor!

[pierre-gilles]

Quick comparison of the two versions on my MacBook Air screen:

Fable 5

Actually, what helps a lot here is that Fable groups consecutive events.

It’s true that when I tested it myself, the Fable version is super pleasant

Cursor: