Hello everyone, here we go, I’ve taken the plunge. First installation of Gladys, I’m testing before leaving HA.
Small issue with the installation of this box in the topic, in MQTT, pairing successful but I only have one entity and I don’t have the one for the button to open or close the door.
Any ideas?
For info, on HA, HA MQTT I have all my entities and it’s functional, but on ZHA, I only have one entity and no button, and of course I’m on ZHA.
Thanks in advance for your help
Hi @Husky14 and welcome to the world of Gladys 
I’m not sure I fully understand your need. You mention MQTT, but your module is Zigbee, right?
To work in Gladys, this module needs to be compatible with zigbee2mqtt.
If it is and if not all features are available in Gladys, then we need to integrate them, nothing too complicated.
However, you would need to provide us with the z2m page with all the features to see which ones are missing.
I took these screenshots in HA via z2mqtt because it’s the only place where I have all the entities.
For information, I use Proxmox with several VMs, one HA with ZHA, another HA with MQTT, and a third one with Gladys.
Hi and welcome to Gladys.
And in zigbee2mqtt, if you press the button, it works, because I have doubts about your screenshots.
Because we can see the Offline status of your device and N/A values on some exposes.
Can you take a screenshot of zigbee2mqtt in the State tab of your device?
I deleted and re-paired it, it’s online and the trigger opens and closes the door.
So, on HA Z2MQTT it works.
How to make it work on Gladys?
Thanks again 
The first (exposition) and last (state) screenshots are indeed the most useful. And so I think it’s not yet integrated into Gladys (I’m not a developer and I could be wrong, but it looks very much like it given the behavior).
Happy to see that you managed to pair it correctly.
As @mutmut pointed out, this device’s reports are not yet supported by Gladys.
I’ll look into it this week as soon as I have 5 minutes to integrate them.
Great, thank you so much.
I’ll wait for your feedback to try it out when it’s ready 
Oh, forget it. I’ll stick with Home Assistant. I’ll reinstall everything in MQTT to get my garage door working again.
Thanks anyway
It’s a shame because it’s exactly this device that a friend wants to buy and integrate into Gladys.
Hi @Husky14,
I owe you an apology. You came with a real migration project, the community welcomed you, the problem was well diagnosed, and then nothing for 9 days. That’s my responsibility, not the responsibility of those who helped you here. It’s my job to ensure that a request like yours is followed up, and it slipped through the cracks. I’m in the process of changing how we track these topics so this doesn’t happen again.
Now, let’s get down to business, in two steps.
1. Unblock your garage door today (5 minutes)
While waiting for native support, you can control the door with a scene:
zigbee2mqtt/YOUR_DEVICE_NAME/set (the exact name of your device in Zigbee2MQTT){"trigger": true}2. The real fix
Your device exposes trigger and garage_door_contact, and these two exposes are not yet in our Zigbee2MQTT mapping table. That’s why you only saw one entity. I’m adding it natively (button + door state sensor): it will be in the next release, by the end of the week. I’ll repost here as soon as it’s online so you can test it by simply updating Gladys.
I would completely understand if you stay on HA after this experience. But if you want to give your Gladys install another chance by the end of the week, your garage door will be fully supported, and I would love to have your test feedback.
Sorry again for the silence, and thanks for reporting the problem with so many details, that’s exactly what allows us to fix it. 
La PR :
@Husky14 It’s good, it’s available in Gladys Assistant 4.84:
Great, thanks Pierre-gilles, I’ll try that as soon as possible and I’ll get back to you
++
Hello everyone,
Test and validate
Bravo and thank you, it worked on the first try
