Control IPX800-v5 in Gladys

cce66 · January 12, 2022, 3:31pm

Is it not possible to directly control a device (command and status feedback) in Gladys? For example, I have an IPX800v5 to control my home automation. It is possible to control it from Node-RED on Home Assistant, but I can’t do it on Gladys? In the IPX, there is a push object that sends the status of relay 1 and a subscribe that allows controlling relay 1 (details Mini-Tuto Liaison MQTT IPX800-V5 Node-red (sur Home-Assistant) - Cartes Ethernet IPX800 - GCE Electronics). But I would like to control everything from Gladys, how can I do that?

pierre-gilles · January 12, 2022, 7:22pm

Hello @cce66!

I don’t know the IPX800-v5, is it a relay that works with MQTT?

If I understand correctly, you want to publish to a specific MQTT topic to control this relay?

In Gladys 4, there is an MQTT API:

Example: MQTT | Gladys Assistant
Documentation: MQTT API | Gladys Assistant

After that, this API is fixed by Gladys, and I don’t know if your relay doesn’t specifically expect a specific MQTT topic and a specific message format, which we don’t handle in Gladys currently.

cce66 · January 12, 2022, 8:55pm

It’s a bit of home automation to NFC15100 standards, it goes into the electrical panels, it’s like having all the equipment like dio sockets, dio switches in a module on a DIN rail

Actually, all commands go through the existing wires (VR, Lamps) and all the sockets can also be controlled from this central point, it’s widely used in home automation (also industrial) there are 8 relays, 8 digital inputs and 4 analog ones

And I would like to be able to control it from Gladys and (I wanted to do it by voice command but not yet on v4 ) there is a RESTful API but in MQTT it’s more responsive!!!

pierre-gilles · January 13, 2022, 7:38pm

Go through the REST API in the meantime

Otherwise, you can use Gladys + Node-RED

cce66 · January 13, 2022, 10:25pm

The ideal in Gladys would be to have more flexible MQTT configuration like in the IPX, here the broker part, so we put the MQTT broker address on the network as a parameter

Then we have « publish » and « subscribe » objects

Here a subscribe linked to the command of relay 1

Configured as follows

And in Node-RED I have

At the MQTT configuration level

In Gladys, this seems much more complex to me (but maybe I haven’t yet understood the way it works!). I understood that Gladys offers the possibility to deploy a mosquito container, mine runs in a container under openmediavault for the moment, so I go through the mosquito broker hosted on home-assistant, so in Gladys I would like to have in the MQTT devices a relay type (it is missing in the devices) with boolean values and a configuration type like in the IPX, for the relay I link it to an MQTT publish to change the state in the IPX and a subscribe to know its state, that’s all. And there, in Gladys, I’m stuck unless I develop a module like the one for Tasmota (I think), but I looked at your tutorial on this and it’s not easy For RESTful APIs, it’s not as reactive as MQTT… On the IPX forum, many people would like to couple their IPX with a home automation solution and are mainly faced with the problem of external connection (which Gladys now has, unlike Home Assistant, Domoticz, or Jeedom). Control modules have been developed on Jeedom and HA, but the interaction with Jeedom and HA is poor… I’ll try to dig into the matter…

pierre-gilles · January 14, 2022, 9:07am

There is « outlet » → « switch » which is made for that

cce66 · January 22, 2022, 10:55am

Hello @pierre-gilles,
I managed to control one of the ipx800 relays via node-red, but I can’t get the switch status back from the ipx800 in gladys

I still have a debug that seems correct to me
22/01/2022, 00:32:11node: f14f85a92afafbeb

IPX800_V5-1 : msg.payload : string[25]

« { »[IPX]Relay cmd 1":true}"

22/01/2022, 00:32:13node: f14f85a92afafbebIPX800_V5-1 : msg.payload : string[28]

« { »[IPX]Relay state 1":false}"

22/01/2022, 00:32:13node: cf703754e8389474msg.payload : string[3]

« off »

22/01/2022, 00:32:13node: 89b610539bda7d0dmsg.payload : string[3]

« off »

22/01/2022, 00:32:13node: e4dc354cc2860d26msg.payload : number

0

22/01/2022, 00:32:13node: 8f8275c29bb036c5gladys/device/mqtt:lampe/feature/mqtt:lampe/state : msg.payload : string[1]

« 0 »

22/01/2022, 00:32:13node: 4678ca9e7131d24cgladys/device/mqtt:lampe/feature/mqtt:lampe/state : msg.payload : string[1]

« 0 »

22/01/2022, 00:32:13node: 471e3ac46dc6fb17gladys/device/mqtt:lampe/feature/mqtt:lampe/state : msg.payload : string[26]