Make Gladys communicate with an external MQTT module?

[elfedagger]

Hello, I got a module to communicate with my Intex spa via MQTT. I created my MQTT commands on Gladys to control my spa and I therefore have these topics.
gladys/device/mqtt:Spa/feature/mqtt:Spa/state
gladys/device/mqtt:Bulle Spa/feature/mqtt:Bulle Spa/state
gladys/device/mqtt:Filtre Spa/feature/mqtt:Filtre Spa/state
gladys/device/mqtt:Chauffage Spa/feature/mqtt:Chauffage Spa/state
gladys/device/mqtt:Température désirée/feature/mqtt:Température désirée/state
gladys/master/device/mqtt:Température actuelle/feature/mqtt:Température actuelle/state
I need Gladys to subscribe to or publish to the module’s topics. I asked the module designer who gave me this answer.
« My system probably doesn’t work with ESPHome, it was coded in Visual Studio Code.
Why would you need to modify it?
Normally Gladys should listen to these topics and be able to converse with it!?!
The 2 topics are Pool/# and Wifi/# »

Can someone tell me how to make Gladys communicate with these topics?

[GBoulvin]

The only solution for you is to use Node-RED to convert the topics.
Or create a specific integration…

[elfedagger]

Thanks for your reply — I had that idea too in the meantime. I’m trying it on Node-RED. So there’s no simple solution to do it directly .

[GBoulvin]

Unfortunately…
The MQTT integration is really inflexible due to the lack of support for custom topics!

[cce66]

Hello @elfedagger

You can go through Node-RED and draw inspiration from the following tutorials to adapt them to your needs

Mini-tuto Piloter dans Gladys un appareil Zigbee2Mqtt qui n'est pas encore reconnu par Gladys via Node-red

Ce mini-tuto propose de connecter un appareil reconnu dans zigbee2mqtt mais dont l’intégration n’existerais pas encore dans Gladys en utilisant node-red comme intermédiaire ! Plus d’excuse pour ne pas utiliser Gladys ! Pour cela on va créer un appareil virtuel (ou virtual device) dans l’intégration MQTT de Gladys et un flow Node-red qu’il suffit d’importer et il faudra juste paramétrer en fonction de l’appareil à controler et de vos paramètres (IP de votre instance Gladys, mot de…

as well as

Mini Tuto - Interaction Gladys - IPX800V5 via node-red

Le but de ce tuto est de montrer comment piloter des relais de la plate-forme domotique IPX800V5 de GCE avec Gladys Allez dans l’onglet « Système » [image] Cliquez sur « MQTT » [image] Paramétrez comme suit, avec pour « Serveur: " l’ip du broker mosquito (IP du raspberry ou du Nuc sur lequel est installé Gladys, en « Client ID » le nom que vous voudrez (j’ai mis ici IPX800V5 c’est important pour les paramétrage des Topic dans Node-red) [image] Ensuite on va dans l’onglet « Liens » [image…

Mini-Tuto pour avoir la valeur Tempo EDF (+Nb Jour BBR) dans Gladys via Node-red avec scène envoi Telegram

Créer un appareil virtuel comme suit dans Gladys dans l’intégration MQTT [image] Avec les fonctionnalités suivantes [image] [image] [image] Importer ce flow dans node-red Code du Flow (inspiré depuis Couleur EDF TEMPO dans Node Red) Vous devez avoir cela maintenant dans Node-red [image] Adapter les paramètres du broker Mqtt à vos paramètres [image] [image] Créez dans le dashboard de Gladys [image] Voila maintenant le TEMPO EDF est affiché dans votre dashboard. [image] Pour…

https://community.glad

[pierre-gilles]

Hi @elfedagger

You can absolutely communicate with custom MQTT topics in Gladys without using Node-RED!

We have scene actions that allow receiving MQTT messages / and sending them.

Example of a trigger:

Example of an action:

I have the impression this feature is little-known

[elfedagger]

I tinkered with this last night and it works very well. I get the temperature of my spa, all the commands work. The only thing that’s a bit off is adjusting the desired temperature with the + and -

[GBoulvin]

@pierre-gilles

I have the impression that this feature is little known

That’s true! I had completely forgotten it existed. I think it was added later to the feature set and I had given up on using my temperamental devices.
The instinct is to create a device to integrate it into Gladys. Going through scenes is not intuitive because the received message can change the state of a virtual device and, forgive me if I’m wrong, you need two scenes for a simple switch: one scene to receive the state and one to control it
Well, I’ll have to take a closer look at that!

[pierre-gilles]

Indeed, since it’s custom we really have to do it that way — it’s the same on the Node-RED side, you need different triggers

Even though I’ll admit that in Node-RED it feels like less work since you can have several scenes on the same ‹ flow ›.

[elfedagger]

I managed to send my on/off commands for all functions of my spa. But I wasn’t able to retrieve the current temperature or send the desired temperature by sending and receiving an MQTT message.

[pierre-gilles]

To retrieve the current temperature, I’m not sure that’s possible via Gladys alone (it’s possible via Node-RED)

However, to send the desired temperature, you create a virtual MQTT device in Gladys, then you make a scene where you send the value of that device over MQTT every time its state changes

Do you see what I mean?

[elfedagger]

Yes that’s what I did, I created an MQTT device « desired temperature » which corresponds to the desired temperature widget.
![Capture d’écran (49)|690x387](upload

[pierre-gilles]

[quote="elfedagger, post:

[Will_71]

As a trigger, I’d use the current temperature of your spa! Right?

[elfedagger]

Since version 4.41 I’ve solved my problem. The ability to listen to a custom MQTT topic allowed me to retrieve the current temperature of the water in my spa. For two days Gladys has been controlling my spa without going through Node-RED. The only remaining problem is that my scenes that turn the spa and the filtration on and off in the morning and evening send the MQTT on and off messages directly to the module’s topics in my spa, and so on my dashboard I don’t see the on/off buttons change state. I don’t know if my spa is on or off remotely.

[pierre-gilles]

@elfedagger Awesome Glad that fixes your issue.

@elfedagger

The only problem I still need to fix is that my scenes that turn the spa and filtration on and off in the morning and evening send the MQTT on and off messages directly to the module’s topics in my spa, and so on my Dashboard I don’t see the on/off buttons change state.

In your scene, you can control these devices so that it’s also reflected in Gladys

[GBoulvin]

I’m reviving this topic…

I tinkered with a module to connect my Intex spa as well, and instead of playing with custom topics (which listen to maps but don’t control), I directly modified the program, which must be the same as yours, to send and listen to Gladys topics as well as Gladys values (1 and 0 instead of on and off).

If you’re interested, I can share the modified firmware (and even the setup, although it’s on GitHub).

Here’s the result:

[elfedagger]

Hello, I solved my problem by going through Node Red to transform Gladys’ 1s and 0s into on and off for my spa. I bought the card from Patitan who manufactures and sells his cards via the Home Assistant forum. The firmware is his and he told me it was coded in Visual Studio Code. I have no idea what that is and how to modify it. I see that you pick up the Wi-Fi signal, that’s interesting.

[elfedagger]

How can I find that on GitHub?

[GBoulvin]

I’ve seen this PaTiTan thing pop up a lot in my research, but I’m not sure what hardware he put in his box. I thought you had gone straight to the source, the guy who did the original coding (GitHub - jnsbyr/esp8266-intexsbh20: MQTT WiFi remote control for the Intex PureSpa SB-H20 and SJB-HS whirlpools · GitHub), because the topics you showed in the screenshot earlier match that development.

I’m not going to ask you to disassemble your module to flash it (even though a wireless update topic is included by default), or suggest we go any further in general until we know what board your module’s firmware is installed on.

We’ll see if your current solution works for you or if you’re ready to tinker (it’s technical but not impossible)!

@elfedagger

How can I find that on GitHub?

Oh yeah, another thing I need to do… Update my GitHub

@elfedagger

you retrieve the Wi-Fi signal

The topic to listen to is wifi/rssi, exactly like that as a custom topic in your virtual MQTT device