Experience report Gladys 4 beta

Hello,
I have been following the project for a few months now and I must say I like it.
For my part, I had never tested home automation before, but being a bit of a geek and a DIY enthusiast, I thought I should give it a try. So I don’t have many connected objects yet, but I still encounter some problems, so I come to share them.

My first integration is a SonOff module (which I put on Tasmota firmware). This allows me to control an air extractor for the bathroom. But here, I wanted to couple it with a homemade module based on an esp8266 to measure humidity, but the scenarios are not yet very complete so impossible to use it except for the lamps. So I thought no problem as I use MQTT instead of using the integration module for Tasmota I will use the MQTT module and put that it is a lamp while waiting for the integration in the scenarios. But it is impossible to force a specific topic in Gladys and I have not found how to completely change the topic on the SonOff module either. So never mind, I will wait for the integration in the scenarios. But I find it a shame that we do not have the possibility to change the path of the topics.

I saw that recently it has been added the possibility to see the path of the topic as well as the possibility to copy it, really a very good idea. However, the copy function does not work for me. I have an installation with the Raspi image of Gladys v4 and I use Brave as a browser which is based on Chromium.

2nd integration: a homemade module that allows me to control my tension while keeping the basic buttons of the latter. The integration in MQTT is going well, I have switches that appear and I can control my module. However, I try to call my switches differently, they all take the name of the device instead of the names given in the features unless I put them in « it’s a sensor sending data to Gladys only » mode but in this case I only have the state of my switches but not the control.

In addition, I would like to have the state of my physical buttons when it changes but I send my switches to Gladys and my switches do not move.

The features in the MQTT module are not all very clear, it would be great to have a description of what they can be used for.
Still in the MQTT module, the possibility to change the external_id of the device even after registration.

In the Home tab, the ability to move a card from column to column without having to delete it. To readjust the order of the devices in the « device in room » card, or to be able to delete some of them whose data you do not want to see.

I assume it is planned but a user manager would be nice.

That’s it, I think I have covered everything I had to say for now.

In any case, congratulations on the work done, I find Gladys on a very good path and I will continue to follow all this closely.

Good evening

Sylvain

Hello Sylvain,

Welcome here :wink:

@link39 created a pull request to address this gap: Scenes : Add turnOn/Off the Switches function by link39 · Pull Request #670 · GladysAssistant/Gladys · GitHub

I had noticed that too but hadn’t created the issue. It’s done now: MQTT Service : copy function doesn't work · Issue #756 · GladysAssistant/Gladys · GitHub

I like this idea!

For the rest, I haven’t looked. If ever, you can go create the issues found on Github. It could be fixed for the release candidate :slight_smile:

Thanks for all this feedback @SylvainL!

To complement what @PhilippeMA said:

Indeed, I think we’re going to change the selector and put more explicit feature names, currently it’s not great.

I created an issue →

I’m not sure about that though. In Gladys, the external_id is what defines a device, if you update the external_id, it’s simply no longer the same device… It has big implications on the Gladys side, what would be your use case?

It’s planned! There is a card on GitHub that talks about it →

Yes! Handle multi-user usage in Gladys · Issue #637 · GladysAssistant/Gladys · GitHub

Thanks again for your feedback! :slight_smile: