Gladys 4 Beta is available! 🚀

[deep]

@VonOx @pierre-gilles thanks for your responses.

So in the meantime, do I need to switch back to version 3 to have all the features? Because I love v4 but without the scenarios I can’t do anything with it.

Thanks and good luck with the development.

[pierre-gilles]

@deep

So in the meantime, do we need to go back to version 3 to have all the features? Because I love v4 but without the scenarios I can’t do anything with it.

Indeed! We’re moving as fast as we can, but there’s a lot of work to be done, and time is limited

@beatrice

My issue is with the TRADFRI

Thanks! I’ve created a GitHub issue so it can be included in future developments:

Add IKEA TRADFRI lights

If someone can integrate them, that would be great!

[pierre-gilles]

@beatrice

The issue isn’t that: she doesn’t understand French I suspect everyone knows that… but just in case…

In this beta, the translations haven’t been done; we’ll do them for the RC release

[pierre-gilles]

I just deployed Gladys 4 beta with the scenes! For those who have Watchtower, your installations should already be up to date

There are very few triggers/actions available for now, but it’s a first draft!

I’m open to any feedback on the functionality of the scenes.

Note: For those using Gladys Beta on x86 with Docker + Watchtower, I pushed a container earlier with a small startup issue (my bad), and I noticed that as the container restarts continuously, Watchtower can no longer update it. A docker pull + a new docker run fixes the issue Don’t hesitate if you have any questions about this, it’s my fault! This kind of problem won’t happen in production, here as we build on master without tag during the beta it’s not always easy to test.

[Hamtaro]

A bit annoying to find the right device… Probably poor organization on my part, I should take the time to name them properly.

[link39]

Good point is that it works via the « start » and via my trigger !

Point that bothers me:

• I agree with @Hamtaro as it’s complicated to find your way around. Would it be possible to use device:feature instead of just the feature?
• Are there only the light switching, wait and message for now? What else have you planned?
• To save, you have to go back to the top of the page while you are at the bottom. A « Save » button at the bottom of the page would be welcome
• There are too many « add new action », it’s easy to get lost. The one in green below could simply be called: « Add »

• « Add new action » adds an action in the current block if it is not empty, otherwise a new block. This is the point that bothers me the most.

That’s it for my feedback.

[jean_bruder]

Hello everyone

Quite busy, I have put Gladys aside for the moment due to the lack of visibility of this v4. This remark is not to be taken negatively, as I know all the commitment of the community of developers around the project (thank you all!). Have you by any chance posted somewhere a list of « feature proposals » and what is already integrated/functional (scenarios, supported hardware, etc.)?

On a different subject: do you think it would be feasible for this v4 to offer a template system to quickly add new connected objects? I indeed have WiFi-controlled sockets, controllable via URL, that I would like to be able to add, but I don’t know how…

Looking forward to reading you,
Jean

[pierre-gilles]

@Hamtaro

A bit annoying to find the right device… Probably bad organization on my part, I should take the time to name it properly.

@link39

I agree with @Hamtaro because it’s complicated to find your way around. Is it possible to put device:feature instead of just the feature?

I agree it doesn’t drive you crazy! Maybe the solution is something like:

• Device name (Color)
• Device name (Battery)
• Device name (On/Off)

With (Color/Battery/On/Off) a data extracted from the type/category of the deviceFeature.

@link39

Is there only the lighting, wait and message for now? What else have you planned?

I’ll give you the link to the current task on GitHub →

As a user, I can create/list/edit/delete a scene in Gladys

For now there are few things, after I’m open to any suggestions to iterate in the future

And I’m open to any PR to code new types of actions, it’s super simple to code ^^

@link39

To save, you have to go back to the top of the page while you are at the bottom. A « Save » button at the bottom of the page would be welcome

Mmmm not bad I’ll think about it. Otherwise simply a button at the bottom « Back to top ».

@link39

There are many « add new action », you get lost quickly. The one in green below could simply be called: « Add »

Or « Add action »

I’m afraid that « Add » alone might be a bit confusing in relation to the group of actions..

@link39

« Add new action » adds an action in the current block if it is not empty, otherwise a new block. That’s the point that bothers me the most.

It always adds an action in the current block!

@jean_bruder

Have you by any chance put somewhere a list of the « feature proposal » and what is already integrated/functional (scenarios, supported hardware, etc. …)?

All ongoing developments are organized on GitHub Projects →

https://github.com/orgs/GladysAssistant/projects/2

@jean_bruder

Completely different subject: do you think it would be possible for this v4 to offer a template system to quickly add new connected objects? I have Wi-Fi controlled outlets, controllable via URL, that I would like to be able to add, but I don’t know how …

Yes why not

Another solution is that I would like to have a « Device HTTP » service that allows you to add devices controllable by HTTP request, and without coding a service

[Terdious]

Hello @pierre-gilles!!

First of all, congratulations on launching the Scenes!!

However, I have a question: why only have the ‹ turn on › for the lamps and not the ‹ turn off ›? Could you easily and quickly implement this? Because for my part, the test phase would mainly focus on this aspect with automatic extinction, with the ‹ wait ›. I still can’t control 99% of my devices via the mqtt service, but I just invested in Philips hue.

Second point, have you planned in the triggers to manage the « AND » in addition to the « OR » because that was my main problem in V3 where you had to go through the script for this operation - knowing that the goal is to target a wider audience, less tinkerer or who is looking for more simplicity.

Third and final question about the scenes: on the dev side, for the server/front update, could you indicate what the manipulation is? Do we lose the database? (Should I save it with TablePlus - thanks by the way, I got this from one of your replay of conv-call, it’s great!!^^ - to restore it after the update).

Finally, last question, after a big thank you, I saw that you had unlocked the limit of 20 rooms on the Dashboard editing view, so I can see my 57 rooms. However, hoping not to be too « heavy » in my requests, would it be possible to have the same layout as on the services with the rooms sorted in alphabetical order but by house first with the names of the houses in bold and indented. I tried to take back the code of the mqtt service in dev mode, but as I am in initiation, I did not succeed…

Voili voilou, in any case for a first feedback as such, I find it aesthetically pleasant and clear to configure. I think simple for the uninitiated, so accessible.

Looking forward to testing the « Turn light off », I will come back with more feedback for the next steps.

Thanks in advance for your answers.

[pierre-gilles]

@Terdious

However, I allow myself a question: why only include ‹ turn on › for the lamps and not ‹ turn off ›? Would you have a way to implement it easily and quickly? Because for my part, the test phase would mainly focus on this aspect with automatic extinction, with the ‹ wait ›.

I am developing it gradually I prefer to release actions gradually as needed!

The ‹ turn off › wasn’t so hard to implement, I added it, it will be in the next merge →

@Terdious

I still can’t control 99% of my devices via the MQTT service

There is still some reflection on the « MQTT Device Control » part, we want to do things well in Gladys 4 and take the time to think carefully about each feature before launching it. Here it touches on a much broader subject, the « Gladys Core/Gladys Pod » architecture, and I would like to have this debate before diving headfirst into development!

@Terdious

Second point, have you planned in the triggers to manage the « AND » in addition to the « OR »?

Yes, there will be a conditional block in the scenes, « Only continue if » which can have a set of AND/OR conditions. I am inspired a lot by Zapier for this.

See the GitHub issue where I talk about the subject:

As a user, I can create/list/edit/delete a scene in Gladys

@Terdious

Third and last question about the scenes: on the dev side, for the server/front update, could you indicate what the manipulation is? Do we lose the database?

When you develop under Gladys, the only thing to do is to do a git pull to get the latest version of the Gladys code. Then you can run the database migration in the server folder with the command npm run db-migrate:dev. You will not lose your dev database.

@Terdious

However, hoping not to be too « heavy » in my requests, would it be possible to have the same layout as on the services with the rooms sorted in alphabetical order but by house upstream with the names of the houses in bold offset.

Yes it will be done In fact I fixed the bug of the 20 rooms without even seeing your issue, I am focused on the development of the scenes and I did not have time to unstack my GitHub notifications. I will look into it when I have time.

@Terdious

Voili voilou, in any case for a first return as such, I find it aesthetically pleasant and clear to configure. I think simple for the uninitiated, therefore accessible.

Great! That’s the goal, glad it’s fulfilled.

[pierre-gilles]

@Hamtaro @link39 What do you think about a device display like this?

It’s a « Device Name (Feature Description) » combo, with « Feature Description » being a text from these translations.

[link39]

It seems much better indeed!

[Hamtaro]

Not bad, we’ll see how it goes.

[Terdious]

Why not display the name of the DEVICE_FEATURE for more clarity. Or take into account that:

1. the DEVICE contains only 1 DEVICE_FEATURE, display the name of the DEVICE,
2. the DEVICE contains several DEVICE_FEATURE, display a first line a bit like the name of the ROOM with the name of the DEVICE then below the names of the DEVICE_FEATURE.

I take my personal example, in my case all the DEVICE_FEATURE are named, but in the end whether it is on the Dashboard, or in the Scene now, this name is not used.

Finally, thank you for the PR with the new actions. I just programmed the use case for ‹ Turn off the Light ›.

[pierre-gilles]

Hello everyone!

I pushed all the work I did this week to the beta on Friday, namely the scenes with the conditions (AND/OR), it was a nice big chunk of work!

Looking forward to your feedback

@Terdious

Why not display the name of the DEVICE_FEATURE for more clarity.

That was actually the case before, but as you could see on @Hamtaro’s screens it wasn’t very clean ^^

[VonOx]

I’m starting to play with the scenes

Hot:

Is it possible to add a filter to find an icon quickly?

And I don’t think we can modify it once the scene is created.

I just noticed something else! Bug?
The poll does not work for the hue service?

I am on in Gladys for a lamp but not in reality (nor in the hue app).

I keep tinkering…

[Pasdesushi]

Super arrival of the scenes
Super job

However, I think there’s a small bug, I need to refresh the page for a new scene block to appear.

Overall, it’s all super

[pierre-gilles]

@VonOx

Is it possible to add a filter to quickly find an icon?

What kind of filter are you thinking of?

@VonOx

And I don’t think we can modify it once the scene is created.

Not a bad idea, yes it’s true that neither the name nor the icon are editable. I’ll change that.

@VonOx

The poll doesn’t work for the hue service?

That’s strange, it was working at one point, but I noticed the problem at my end! I’ll fix that.

@VonOx

I keep tinkering…

Great, don’t hesitate if you have more feedback!

@Pasdesushi

By the way, I think there’s a small bug, I have to refresh the page for a new scene block to appear.

Huh? That’s strange, everything works on my end. What browser and browser version are you using?

[pierre-gilles]

Hello everyone!

Quick message to keep you updated on the progress of Gladys 4

Here are the different ongoing projects:

• I have been working on scheduled scenes since last week, a nice piece but really worth it! Read my latest progress report here.
• @Terdious and @AlexTrovato are working on the French translation of Gladys 4, see the GitHub pull request.
• @link39 worked on an action box « Turn on the outlets », see the topic.
• @Boimb started a debate about the Gladys 4 MQTT API, particularly to think about the format of the new outgoing topics. Read the debate on the forum.
• Thanks to the update of Linux Alpine on the Docker Node.js 12 image, Gladys now uses OpenZwave 1.6, compatible with more Z-Wave devices!
• @AlexTrovato improved the UX of the MQTT service, including error management, see the GitHub PR.
• @bertrandda is working on the CalDav service which is starting to look really nice! See the PR on GitHub.
• @joeypic is working on the RFLink service, in order to be able to manage 433Mhz and Milight devices (via RFLink) See his last message on the forum.

This is just a small glimpse of all the work done, but believe me, Gladys is being worked on hard right now! Thanks to everyone who contributes, it’s thanks to everyone’s effort that Gladys is moving forward