Gladys by the end of 2026: big news and an ambitious plan 🚀

Great news!

Enjoy all the wonderful moments this new adventure will bring you.

Well done

Congratulations! Take the time to enjoy it
 it goes by too fast


Wow, what wonderful news! Congratulations. In my case, as part of my transition from HA to Gladys, I’m trying to replicate the nightlight mode I have for my child in Gladys, and I can confirm that smart home dads are better than regular dads!

For my part, virtual thermostats and even extended heating management to prioritize certain areas without exceeding the maximum power provided, in the same way that GitHub - jmcollin78/versatile_thermostat: A full featured Thermostat for Home Assistant: presets, window, motion, presence and overpowering management · GitHub does, would be fantastic and I think that would add a big asset to Gladys. +1 for thermostats then!

What about the ongoing requests that are in « in-progress Â»?

Hello @pierre-gilles,

Congratulations to you. And of course, congratulations to the mom too, because let’s not forget that she does most of the work.

Warning: a new life begins!!! All happiness but, of course, a lot of worries (especially for the first one) but the joys still outweigh the fears. When I had my first child (it’s been quite a few years now), home automation didn’t exist (at least I wasn’t interested in it) but I had invested in an automatic rocking cradle. No doubt that now, the process can be greatly improved (start the rocking at the first cry). I think that being a dad will give you ideas for home automation projects.

For the rest, I think that everything that will facilitate the work of those who develop external integrations should be the priority. Then, I would see an improvement aimed at giving everyone the possibility to manage, more finely, their dashboards. It may seem anecdotal to prioritize the visual aspect, but I find it important to have beautiful dashboards: it makes you want to use them more.

Best wishes for your new life with the arrival of the smurf!!!

Hi Pierre-Gilles,

Already: congratulations :tada: Great news, enjoy these first months, they are magical.

On the roadmap, I find the order just right and I wouldn’t change anything. Priority 1 is the one with the best leverage effect: as long as an external integration cannot display its own widgets or expose scene actions and triggers, we are stuck.

I started a sort of alarm revamp here, but that can wait for your return in 2027.

And on the 2027 goal: being able to live off Gladys is also what secures the project in the long term for all of us. I will switch from HA to Gladys by the end of October (the comeback) and I will be very happy to support this project again :rocket:

Cyril

Hi Pierre-Gilles,

That’s fantastic news! I wish you both so much happiness and love, and the fact that you get to enjoy it for such a long time (I still remember my 11 days of paternity leave) is truly amazing :slight_smile:

Regarding priorities, I get the feeling there’s a consensus for the thermostat, but for my part, I would have loved to see the multimedia player arrive, as I think it could be useful for several services and integrations already in place: Airplay, Android TV remote, Subsonic, Apple TV, Denon/Marantz, Google Cast, Immich SLideshow, LG Web OS, Plex, Samsung Smart TV, Sonos, Spotify.

That’s quite a list that could benefit from it. And if this is combined with the ability to have widgets associated with external integrations, then I think it’s a winning combo.

See you soon for an intensive final stretch on the project!!

Thank you all for your messages :slightly_smiling_face: We can’t wait!

On the thermostat

A quick important reminder: the feature has already been developed by @Will_71 :backhand_index_pointing_right: here

What’s missing today isn’t development, it’s testers and feedback on the PR. So far, there’s only been one tester in a month, which explains the current prioritization.

So if the thermostat interests you, now is the time to act: go test it and give Will your feedback on his work! :folded_hands:

If the tests are done, the result is great, and it suits a good majority of users, all I’ll have left to do is validate it and click on « Merge ». Under these conditions, it can definitely move up in my priority list :slightly_smiling_face:

On my time before the end of the year

If the delivery happens at the beginning of November, I only have 17 working days left. And out of these 17 days, some will inevitably go to administration, support, and infrastructure, so there’s less left for pure development.

That’s why I want to focus this time on what has a multiplier effect, and today it’s the work on external integrations that has this effect: each door opened allows the entire community to build on it, even during my absence.

Yes, of course, in 2027! :slightly_smiling_face:

Here I’m only talking about my last working days before my paternity leave.

@Chris75 For this last sprint before my paternity leave, I prioritize what has a multiplier effect, and for me, those are the external integrations :slightly_smiling_face:

The goal is simple: for the project to move forward without me, and for me to no longer be the bottleneck.

If I manage to get through my list (let’s be honest, the chances are slim), I will of course take up these topics before my departure.

Otherwise, don’t worry: all ongoing topics will be picked up again upon my return. Nothing is abandoned, it’s just a matter of order!

Congratulations to you and your partner!
They talk about change with a newborn, so yes, it changes, but a lot :sweat_smile:
Enjoy it, it goes fast!

No kidding, it really goes too fast. For me, it feels like it was just yesterday, and my son is already 17 years old.

Congratulations to the future parents. It’s the discovery of the reversal of the scale of priorities.

I take this opportunity to say that V5 is great. Quite a boost in a short time.

Congratulations to the future parents, and above all, lots of happiness, children grow up so fast, enjoy all these special moments. Warm regards

Hi @pierre-gilles,

Congratulations to the future parents, I wish you all the happiness in the world as a family!

For the priorities, I completely agree with @cicoub13’s remark:

This is clearly a structuring point for external integrations.

But I must also admit that the thermostat is tempting for me: it would allow me to remove about ten scenes that I always struggle to remember the overall logic and how I built them.

Thanks for your messages! :slightly_smiling_face:

The first development is ready to be tested. I’m open to your feedback, especially from integration developers, by Monday so that we can deploy this feature as soon as possible.

We’re discussing it in this topic:

The second development is ready to be tested :smiley:

Also taking feedback from integration developers!

We discuss it in this topic:

Hi Pierre-Gilles,
How will future PRs be validated that you currently validate?

Congratulations and best of luck

I will be a grandpa for the second time at the end of the year, and with my wife, we have 6 children and 5 grandchildren

I especially think we should ask for the instruction manual because these children always arrive without one!

(Otherwise, I don’t really know how to help the community as a novice user)

Very good question :slightly_smiling_face:

First, that’s exactly the purpose of the work I want to do in this last sprint: to minimize the things that go through the core.

With external integrations (integrations, widgets, scene triggers and actions, energy contracts, etc.), the community can create and evolve entire features without a single line of code passing through my hands. No PR to merge, no release to wait for. In this model, the project moves forward without me.

Then, there’s the real question: core fixes during my absence.

There, I don’t have an answer yet. We could imagine that I delegate the rights to a trusted maintainer, but I don’t know yet what form that would take, or who could take on that role.

It’s a big responsibility: you have to know the code, understand the philosophy of the project, know what we accept or not, and assume the consequences of a merge. Gladys is running today in many users’ homes, including beginners and starter kit customers. A regression is a home that no longer responds, without necessarily someone on the other end capable of diagnosing the problem.

This is a topic we can explore in the meantime, if you have ideas on how to organize it, or if you want to get involved, I’m all for it! :smiley:

Me, I’m not at all at the right level :sweat_smile:.
But a word to enthusiasts, or rather to the pro :wink:,
Here I’m preaching to the choir, but making a request for a function that doesn’t appear in Gladys, even though it does appear in Zigbee2mqtt for example, does that fall under core fixes?
In any case, enjoy all these future parental moments.

Indeed, we need to find a solution because if a problem occurs and causes Gladys to be stuck for 2 months, that would not be « acceptable Â» and very bad for new users 

But, during these 2 months of paternity leave, you won’t be available at all to intervene in an emergency?