Mediola2mqtt: Simple Mediola to MQTT bridge with HA support

The Mediola Gateway is a multi-protocol, mult-transceiver networked gateway available as Mediola AIO Gateway or OEM product. It is the only gateway that supports my blinds (Elero) and it is widely available in my region (the Elero Centero home gateway is a rebranded Mediola gateway; there is an alternative for Elero blinds based on the Centero transmitter stick, but the Mediola gateway is cheaper).

The gateway has an HTTP API and reports important changes via UDP broadcasts. I created a simple MQTT gateway with HA auto discovery to make use of the Mediola features.

Limitations:

  • Only limited device support
    • Elero blinds
    • Somfy blinds
    • Intertechno remotes
  • Tested and developed on a v4 and a v4+ device

There is now rudimentary support for v5 and v6 gateways. For the v6, you need to map the UDP port 1901 to 1902 since it broadcasts on a different port.

When running standalone, also several Mediola gateways are supported.

See GitHub - andyboeh/mediola2mqtt: Mediola MQTT Gateway for instructions and details.

2 Likes

Thanks for your contribution.
I tried your code on my new V6 today. It work flawless with elero blinds.

Thanks for the feedback, good to know that it works on newer models as well!

Today, I played a bit with code, and moved configuration from file to configuration tab inside addon

:smiley:

Any contributions are welcome, so I’d appreciate a pull request. However, as I cannot run it as an addon, I will only accept changes that do not break running it as a systemd service (that’s the reason for the external configuration file, but with a few adaptions, both should be possible).

Can I use this to open and close my elero blinds?

That’s what it was written for - provided that you have a Mediola Gateway.

I think I need help with the settings.

mediola:
  host: is this the mediola gateway? can I use the IP?
  udp_port: 1902
  password: is there a password?
mqtt:
  host: the homeassistant ip?
  port: 1803
  username: homeassistant
  password: somepassword
  discovery_prefix: homeassistant
  topic: mediola
  debug: false
blinds:
  - type: ER
    adr: '1'
    name: Kueche
buttons: []

Maybe you can help? :slight_smile:

  host: is this the mediola gateway? can I use the IP?

Yes, the gateway. Of course you can use the IP.

  password: is there a password?

If you didn’t set one, there is none. That’s the password of your Mediola.

  host: the homeassistant ip?

Depends on your setup, could be the same IP address. You need to find out how you can reach the MQTT server.

Hey @andyboeh,

Thanks for all your work on making this really simple and easy!
What i noticed is, when autodiscovery does not work and i manually entered all my elero blinds from a Gateway 6, that the addresses are now in hex, which means after 08 it goes on with 0A. This seems not to be supported yet as you parse them as int always.
For myself, i removed that part in the script and use directly the adr field and it works flawless.
Maybe this is worth a consideration in the future to also fully support gateway 6.

It only affects people with more than 8 elero blinds on a gateway 6

No, the addresses are in hex on the v4 gateway as well. I stumbled upon this when I added my tenth blind a few weeks ago and it should be fixed since then (there are internal conversions hex <-> int).

Could you check if you run the latest version?

Regarding the v6, there is an ongoing discussion to better support this gateway. If you like, you can join the conversation at Behaviour of v6 gateway · Issue #4 · andyboeh/mediola2mqtt · GitHub.

Hi!
Thanks for your fast reply.
Yes, i will join the discussion.

I took the state of the master branch 3 days ago. Can you tell me, which commit you used to fix it or if it is merged there?

Hi Andy,

Thanks for this initiative

Do you know if it also works on the rebranded “Centero Home Gateway”.

Rob

Ja

Sorry, I don’t know - if you try it please let us know your results.

Is it possible to install that integration on Home Assistant Container? Probably it has some dependencies as 3rd party apps/libraries. I will be pleasure for some short instruction. I’ve tried to install via HACS and pasting github URL like in other integrations, but HA says “Repostitory structure for master is not compliant”

You are confusing add-on and integration. This is not an integration but a bridge to MQTT. It runs completely independently from HA, hence you can’t install it in HACS. Add-Ons can only be used on HassOS and allow the usage of independent applications without requiring access to the underlying operating system.

If you are containerized, you probably have access to the host operating system. If that’s the case, then you just need to clone the repository, adapt the configuration file and run it on your host operating system. You need to add the MQTT integration to Home Assistant, a new Mediola device will then show up within the MQTT integration. This is exactly the way I’m using it and the reason why there is also a PKGBUILD for Arch Linux and a systemd init script.

You can, probably, run mediola2mqtt also on docker. However, you have to figure out yourself how to create the docker container.

Hi Andy !

Your Addon is really cool and easy to configure.
My Somfy Device is working perfect.
But I a have a lot of Blinds with WAREMA EWFS
I tried to configure same way, but there is no action by the blinds.
Is there a Solution for WAREMA EWFS ?

Tom

No, only Somfy RTS and Elero blinds are supported, plus InterTechno switches. The reason is simple: I don’t have any other devices.
However, we can come up with a solution: You need to figure out which commands are sent to the Mediola gateway in order to control the blinds. Then, we can integrate that with mediola2mqtt.

Thank you for your work.

If I understand correct I can create a proxmox container with e.g. ubuntu und install there your script. This will “transfer” the mediola signals to any mqtt broker I have?

That’s right. The container needs to have a UDP port (1901/1902, depending on the Mediola version) forwarded so that it receives events.
Depending on your operating system, you don’t need any container at all (I run it natively on Arch Linux, without a container).

1 Like