Gladys 4 Beta is available! 🚀

[pierre-gilles]

Hello everyone,

Last week, I deployed a new version of the Gladys site, focused on documentation.

Nouveau site & nouvelle documentation pour Gladys 4

Salut à tous ! Ca y est, le nouveau site pour Gladys 4 est en ligne Et il a un dark mode ! [screenshot-website-gladys-4-low] Le site est disponible comme avant: N’hésitez pas si vous avez des retours, je suis preneur

Today, I’m resuming the development of Gladys 4 itself.

Before diving headfirst into development, I reviewed the short-term goals of the project and the ongoing tasks. I would like to discuss this here so that we can also discuss it with you

My number 1 goal now is to launch Gladys 4 RC

To achieve this goal, I had to make choices. I took all the tasks on GitHub and asked myself, « Is this development necessary for the RC? » If my answer was « Yes, absolutely, » then I added the task to the milestone.

We therefore have 21 tasks remaining in the milestone:

The milestone on GitHub → GitHub · Where software is built

For these 21 tasks, I have estimated the time required to develop the feature:

• 13 tasks “low” = 13 * 2 hours = 26 hours / 8 hours = 3.25 days
• 5 tasks “medium” = 5 * 1 day = 5 days
• 2 tasks “high” = 2 * 4 = 8 days

This allows me to estimate the development time required to release the v4 RC:

3.25 + 5 + 8 = 16.25 development days (130 hours)

Note that these are « pure » development days.

Working part-time on Gladys, on my side, I am available Monday and Tuesday for Gladys (Wednesday, Thursday, and Friday I work for a client as a freelancer).

Knowing that on these 2 days of Gladys, I am not really available for 2 days, because there are many things that take time:

• Responding to community messages
• GitHub administration
• Gladys Plus maintenance
• Site maintenance
• Accounting
• etc…

By trying to compress these tasks enormously, I think I can have 1.5 days of development per week.

I need your help

If I were alone on Gladys, it would take me 11 weeks to finish this RC, which brings us to mid-October. And even that, I find it optimistic, not counting any possible breaks (I’m not a robot )

I therefore call on your help to help me finish this RC

All PRs are welcome, if they concern these 21 tasks.

Because, the bad news is that if we want this v4 to be released, it’s that I have to say « no » to everything else… I know, it’s very sad, there are so many great PRs waiting on GitHub, but I have to face the facts: it’s not possible to do 15 things at once. I just don’t have the bandwidth to do that, the days are so short.

Trying to do everything means doing nothing.

Let’s go!

On my side, I start the series of todos, and I will update my development estimates on this thread Thanks to your help, the v4 may be released earlier, I hope

[tiboys]

Hi @pierre-gilles, I really like your mathematical and pragmatic analysis of the remaining work to be done.
You’re already doing a lot, and I can hardly imagine what all this represents.
I also think we should prioritize a good stable base that can evolve in a plugin-like way ..
I don’t know much about programming, but if a little hand can contribute a small stone to the edifice .. don’t hesitate.
Good luck to you and all contributors.
Tiboys

[pierre-gilles]

@tiboys Thanks for your message!

I wouldn’t hesitate if there are any small tasks that can free me up to move forward

[gaetanb76]

Hello everyone,
Not being a programmer, I will offer my help to provide feedback.
I look forward to being able to test the creation of scenes to program my Z-wave heating and others to manage the opening of my shutters.
I also hope to be able to use my NodOn Z-wave remote control.
However, I see in

@pierre-gilles

The milestone on Github → GitHub · Where software is built

that RF-433 MHz is not planned for right now. I will therefore wait to use my temperature/humidity sensors.

Given the amount of work to be done, I completely understand .

Good luck to everyone.
Take care.

[pierre-gilles]

@julienL

Is the integration of the Zigbee2MQTT module not part of the RC milestone? Is it not planned?

This is not my area It seems that @Reno has been quite busy recently and does not have time to finalize this module for now.

I invite you to ask on the integration channel:

[V4] Intégration Zigbee2mqtt

Hello, Voila un petit retour de mes tests : Le process de configuration est top (après avoir passé la petite difficulté liée à la détection du stick Zigbee), par contre toujours besoin de faire un force refresh pour faire apparaître mes devices sur la page discover après qu’ils aient été détectés par le stick Si on navigue directement sur l’onglet discover (par exemple en tapant dans l’URL), les devices détectés n’apparaissent pas, il faut passer par l’onglet devices puis retourner sur l’ongl…

[VonOx]

Personally, I’ll be barely or not available until September. I had my second baby who arrived at the beginning of June and I’m using my leave to do some home improvements. The little time I have left is for sleeping.

Don’t hesitate to ping or message me so I get the notifications.

[pierre-gilles]

@gaetanb76

RF-433 MHz is not planned for now. I will wait to use my temperature/humidity probes.

I replied to that, are you talking about 433MHz via an Arduino + transmitter?

We have a PR ready made by @billona. I’m waiting for some changes from his side but otherwise the service can already be tested, there is a Docker image built from the PR

Gladys 4 - Développement du service Arduino

Bonjour à tous Afin de rendre compatible Gladys 4 avec mon installation (principalement constituée de 433 MHz), je suis en plein développement du service Arduino. Page des intégrations : [Screenshot_2020-01-06 Gladys Assistant] Pages du service Arduino : [Screenshot_2020-01-06 Gladys Assistant(1)] [Screenshot_2020-01-06 Gladys Assistant(2)] Pour l’instant l’interface est simple et pas encore fini, mais je suis en train d’y travailler. Il faut aussi que je m’occup…

[gaetanb76]

Hi Pierre-Gilles,
Actually, no, I don’t use an Arduino for 433 MHz. I have an RFXtrx433E transceiver from RFXCOM.

It is connected to my Raspberry PI via a USB hub.
This is more like it:

[V4] Dev service RFlink

Bonjour , J’ai commencé a developper le backend du service RFlink (pas encore de PR car j’ai un mauvais niveau en JS et je ne pensais pas arriver a le faire) et je cherche quelqun qui voudrait faire le frontend . Je ne peux pas m’en occuper moi même, je n’arrive pas a apprendre React et je ne sais meme pas vraiment développer en JS. Le front serait simple , un onglet setup qui liste les ports usb et un onglet pour les devices. Si personne ne peux aider , j’essayerai de copier collé les pag…

However, I have a project to make a weather station with an Arduino connected via Wi-Fi. So what @billona does interests me. I already took a look at it.

[pierre-gilles]

New Release: Gladys v4.0.0 Beta 6

Well, already almost 1.5 days of work done this week, and I take this opportunity to release a new version: Gladys v4.0.0 beta 6. Yes, now beta releases have their version number!

This version number is visible in Gladys, so that we can easily know which version of Gladys you are running. Normally, you should be on Gladys v4.0.0-beta-6:

A New Raspbian Image

I took advantage of this tagged version to release a new Raspbian image, which will directly install the latest version v4.0.0-beta-6.

The Raspbian image is available for download on the Gladys site => Commencer avec Gladys | Gladys Assistant

Goodbye DarkSky, Long Live OpenWeather

You may have seen the news, but Apple acquired DarkSky, our old weather API. So, we had to find another API and recode the service (we could have done without it :D)

Thanks to the work of @pizza6, we have now migrated to OpenWeather!

I have updated the documentation: OpenWeather | Gladys Assistant

CalDav Synology, Google

I merged the work of @bertrandda on CalDav, it is now possible to connect CalDav from Synology NAS, as well as from the Google API.

A New Video Tutorial

I filmed it at Christmas, but never released it, it is now online: a new tutorial on YouTube to simply explain how to install Gladys 4 on a Raspberry Pi

[gaetanb76]

I saw in the early afternoon that I was on beta-6.
However, Dark Sky is still there and OpenWeather is not offered.
The help is very clear
Bravo!
I correct myself: Logout + Login and it’s good, OpenWeather is there!
However, I don’t have the weather image next to the temperature. I’ll wait to see if it arrives.

[pierre-gilles]

@gaetanb76

However, I don’t have the weather image next to the temperature. I’ll wait to see if it appears.

It’s possible that not all cases are handled, could you quickly check in your browser’s console for the result of your weather?

You do « Right-click on the page » => « Inspect element » => « Network », and you look for the request /api/v1/house/:house/weather

It should look like this:

And you give us the API response here

(Don’t hesitate to hide your latitude/longitude, what interests us is the weather)

[gaetanb76]

Here is what I get:

[pierre-gilles]

@gaetanb76 Thanks! I added the missing icons in this PR:

https://github.com/GladysAssistant/Gladys/pull/841

It will go out in the next release

[gaetanb76]

Hello,
The weather icon appeared after I logged out and back in.

[pierre-gilles]

The weather must have changed Some icons were indeed missing, but they will be fixed in the next release!

[Albenss]

@pierre-gilles

I need you

Hi @pierre-gilles, I’m a junior dev but I’ll try to train quickly to lend a hand

[pierre-gilles]

Hello everyone!

A quick update to let you know that I’m on track with the schedule, even a bit ahead having been very productive last week

Here’s the current milestone:

There are 12 issues left, including:

6 « low » issues * 2h = 12h / 8h = 1.5 days
4 « medium » issues * 1 day = 4 days
2 « high » issues * 4 days = 8 days

That’s 13.5 days of development left!

[pierre-gilles]

Et Gladys v4.0.0-beta-8 en cours de build avec les améliorations de la semaine

I tried to merge PR #745 from @AlexTrovato and @VonOx which allows to automatically launch an MQTT container but for now I’m stuck on conflicts related to changes by @bertrandda on the CalDav service!

[AlexTrovato]

Hi, yes I had to modify some caldav tests because there was a side effect, but that’s probably ancient history. I’ll take a look but I don’t know when

[pierre-gilles]

Hello everyone

It’s Monday morning, back to work to progress on the todos

@AlexTrovato I’ll check it out right away!