Zigbee2mqtt: Request to integrate Develco IOMZB-110 module

Good evening, with the aim of adding a wireless programmable thermostat to my electric heating installation it has become essential for me to add to Gladys a Zigbee module that has physical inputs. I found a Develco module, model IOMZB-110, that should be perfect except that this module integrated into Gladys appears only with 2 outputs while the 4 inputs are ignored. I am very surprised because in Zigbee2mqtt this module is complete: 4 inputs and 2 outputs and everything is functional.

Is it possible to modify this integration to access the inputs of this module or is that not possible?

It’s possible if someone takes care of adding the features to this device!
Unfortunately it won’t be me — I absolutely don’t know how to do it, I don’t know how to develop.

Hi @Zebulon :slight_smile:

Is this the device?

Would it be the « input_l1 », « input_l2 », « input_l3 », and « input_l4 » that are missing?

We’re in agreement — if I understand correctly, these 4 inputs should just be sensors in Gladys; they aren’t controllable?

If it’s just a matter of reading the exposes, that can be done easily. However, where I have a question is about the line To read (/get) the value publish a message to topic ..... I think you have to send this command when you want to read this expose, but I don’t know whether this command is implemented in Gladys.

I think /get is if you ever want to query the state in Zigbee request mode, but otherwise the state is also published we change it to: " Value can be found in the published state on the input_l1 property."

So it’s exactly like what we’re doing right now, with just 4 attributes to read that we’re not currently reading.

In that case I could open a PR over the weekend and create an image if needed for testing.

2 Likes

Great, thanks!

Hello, this is indeed the module I would like to use because I didn’t find any other for Zigbee and it is sold by Domadoo so it’s easy to find and delivered quickly.
Thank you for the quick reply.
Alain.

@pierre-gilles, here is the PR.

I only tested with an MQTT device but not with a real device.

image
image

@Zebulon, if you’re up for testing with your device, here is a Gladys test image: willde71/gladys-test:develco-IOMZB-110

Good evening, after struggling a bit to test a Gladys image I tried but I must have made a mistake because it’s not going as it should.
In PuTTY I sent the following command with the output and the error at the end:

docker run -d \
–log-opt max-size=10m \
–restart=always \
–privileged \
–network=host \
–name gladys-test:develco \
-e NODE_ENV=production \
-e SERVER_PORT=8001 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladys-test:develco:/var/lib/gladysassistant \
-v /dev:/dev \
-v /run/udev:/run/udev:ro \
willde71/gladys-test:develco-IOMZB-110

Unable to find image ‹ willde71/gladys-test:develco-IOMZB-110 › locally
develco-IOMZB-110: Pulling from willde71/gladys-test
83d624c4be2d: Already exists
d0ddb100d04a: Already exists
2aef2c99b54e: Already exists
12af688d404f: Already exists
82d4419d4908: Already exists
4dc0af8162f4: Pull complete
68a50a3fdc45: Pull complete
4f4fb700ef54: Pull complete
a919a5678706: Pull complete
016d5003aaf5: Pull complete
c96d8bc4222f: Pull complete
Digest: sha256:ef3ecac3f613603ab9a5616a267828026de81447129b38d2f58ae86fb7d8bc76
Status: Downloaded newer image for willde71/gladys-test:develco-IOMZB-110
docker: Error response from daemon: Invalid container name (gladys-test:develco- IOMZB-110), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed.
See ‹ docker run --help ›.

You cannot put a : in the container name. Try with gladys-test-develco

That’s fine, thank you very much.
Alain

Good evening, I tried several times on an Rpi 3B+ to test the installation which was done correctly but I couldn’t get the test to work.
All I managed was to break my Gladys installation on that board and to put everything back in order I had to take a basic course on Docker commands.
I’m sorry I didn’t succeed but at least Docker is less mysterious to me.
Alain

Thanks for trying. So, did you manage to get your installation working again?

Hello, yes I put things back in order by stopping the Docker containers one by one, then I removed them with the command docker container rm and the ID of each container, and I restarted the Gladys installation from the beginning without the Docker install since it was already there.
There was no problem getting Gladys running again.
Thank you.
Alain

Good evening, I just restarted my test by changing the Zigbee dongle, using a minimal Docker setup and the PR works, but the Develco module is still fine in ZigbeeMQTT and only the outputs appear in Gladys’ Zigbee integration.
Screenshots :



Thanks for the reply.
Can you take a screenshot of the State tab of your device in zigbee2mqtt?

Yes, here is the screenshot

I put a jumper on the pins of input « input_11 »; it is active compared to the other three.

Correction to my previous message: it’s « input_I1 », not 11