Launch of Gladys Assistant 4.12 Tuesday, November 1 at 10:00 live on YouTube!

Hello everyone!

I’ll see you on Tuesday, November 1 at 10:00 AM French time for the launch of Gladys Assistant 4.12 :rocket:

Some hints about the topics covered in the YouTube thumbnail :innocent:

:bell: Remember to click « Notify me » on YouTube to receive a notification when the live starts :bell:

See you on Tuesday!

11 Likes

It’s going to be one hell of a version again :heart_eyes:

2 Likes

I’m a fan of the new version of the device name management / features!!! :+1:
I can finally tell my 4-channel switches apart, thank you very much for all your work!

1 Like

Superb presentation as always!!

1 Like

Thank you!

The replay is available on YouTube:

The launch article is available on the blog:

Thanks to everyone who contributed to this release, I’m thinking of @bertrandda, @VonOx, @cicoub13 and @AlexTrovato :folded_hands:

Feel free to share any feedback on this version

5 Likes

Thank you very much for all the improvements you’ve made! The project is progressing well, it’s really great! Can’t wait to see the Zigbee2Mqtt heaters!

1 Like

Good evening @pierre-gilles,

I just watched the replay of the live stream (couldn’t follow it live, masonry work to open a window in my workshop required!).

Very good…

For 45 minutes the Gladys 4.12 update has been applied on my server.

Very good, especially at the dashboard level the

Good evening,
@VonOx replied to you on the other forum thread with some pointers to move forward. You can certainly look into it and check whether the current development will be compatible with your case.
The goal of each integration is to cover the majority of use cases (in this case

2 Likes

but I documented myself, as evidenced by the elements I added to my initial post.
but the response given revolves around the Lixee solution which is not compatible (a module with 3 connectors like the Linky… whereas pre-Linky meters only have a 2-wire teleinfo output); as for the other solution clamped onto the electrical cabinet and the USB-C port, it’s …
the ESP and teleinfo2mqtt approach seems more coherent with the Gladys approach

Another great update! I don’t know where to turn :laughing:

Congratulations to everyone on this great work

Great :slight_smile: Glad it’s working for you!

Can you create a thread on the forum dedicated to your request so we can help you with that? It’s really a completely separate topic so it’s complicated to mix that with the discussions about the Lixee TIC part and Enedis.

Thanks @Mastho :folded_hands:

@pierre-gilles Really interesting in the replay, but we can’t see the comments posted during the

1 Like

Too bad the Lixee TIC is out of stock at Domadoo…

Otherwise, great work :muscle:, thanks to everyone who made it possible :pray:.

1 Like

No, unfortunately not possible in Gladys. It would require a specific aggregation of the energy features that always increase in value (I only have that via InfluxDB/Grafana).

arf it’s a shame for this kind of sensor not to be able to do it natively in Gladys ^^
I’ll wait a bit longer to see if it’s added via the feature PG is working on :slight_smile:
Thanks for your reply

1 Like

That could be done at the Zigbee2mqtt integration level; we could create a « derived » feature that would be the current index minus the previous one.

2 Likes

Hello/Good evening,
I’m going to be blunt…
Since the update, this appears in the graphs…


Whereas before, there was no problem…
These are Tasmota devices from different rooms.
I thought I had tested the Gladys Plus version, though?

1 Like