IPX800 integration

Hi @cce66,

I’m replying to your message in a dedicated thread.

Thanks for your comments, I’ll be able to work on a new version :slight_smile:

Thanks @cce66 for the test and screenshots, it’s very useful!

What you see is intentional: by default, all relays arrive read-only, because a controllable relay obeys all « turn everything off » commands (scenes, Google, Alexa…) and you don’t want to accidentally turn off a pump or an HRV. To control one:

  1. Integrations → IPX800 → Configuration, field « Relays controllable by Gladys »: enter the codes, for example R1, R2 (or R1:light to make it a light), then save.
  2. Discovery tab: your relays display a « Update » button. Click on it: the functionality changes from « Status (read-only) » to a real switch.

For X-4FP zones: Off and Frost Protection work immediately; Eco and Comfort require checking « Allow Eco and Comfort from Gladys » in the Configuration.

You’re right, it’s not visible enough. In the next version, the integration will say itself when no relay is controllable, and the guide will explain it from the installation. I’m also checking your repository to verify the V5 API.

And thanks for the test proposal: having a V4 and a V5 on hand is precious, the integration had never run on a real IPX800 before. Let me know if the relays switch to a switch with these two steps.

@cce66 v0.1.2 is out: Release v0.1.2 · LM1LC3N7/gladys-ipx800 · GitHub

  • The integration status now shows how many relays are read-only, and which ones are waiting for « Update » in Discovery.
  • The guide now lists the relays to control before creating the devices: they then appear directly as switches.
  • Thanks to your repository (thank you!): outputs X-8R with a large number, like your 4784128, could not be made controllable; this is fixed. And a faulty X-THL sensor no longer publishes a measurement.

If you have time to test, here’s what would help the most:

  1. After listing R1, R2 and clicking « Update »: does the command from Gladys work in both directions? Does a change made on the IPX page appear in Gladys within about ten seconds?
  2. On your X-4FP: after Stop and Frost Protection sent from Gladys, does the IPX page only show the last mode? Does the integration status sometimes display « Unreadable Mode »?
  3. If you have an X-THL: is the temperature displayed correctly (21.5 and not 215)?
  4. On your V4: is everything found (relays, inputs, pilot wire zones)?
  5. Have the new status messages been enough for you to understand what to do?

For the V3, the Eco-Devices, and the X-Pool: they have a different API, it would be a separate integration. For the Eco-Devices, there is already GitHub - LM1LC3N7/gladys-ecodevices · GitHub if you want to try it.

for the moment it’s ok in both directions at the relay level in a quasi-immediate way (less than 1s)


for the x-thl and the x-4fp I have to reconnect them, I’ll get back to you later
following update
everything is ok for v5
for v4, I had to modify the ip and the apikey and then it commands the v4 relays (but with the v5 parameters) but they don’t find anything from v4 itself

I think we need to integrate per device to make it simpler (you can have a v5 and a v4 or even a v3 in a house)

the repository I gave you all the html with an api are autonomous devices reachable on the LAN so each with an ip (the x-thl, the x-4fp, x-4vr etc are devices connected with a cable to the ipx)
so we would need a separate integration for
ipx800 v3
ipx800 v4
ipx800 v5
ecodevices
ecodevices RT2
ecodevices ED3

The ipx 800 V5 and the ecodevices ED3 are controllable via API and MQTT
That’s it, I have the 6 devices available for testing at the moment