Cool, Iâll test that tonight.
What modification needs to be made to the Zigbee models?
All my Xiaomi switches are currently detected as plugs. I can take care of testing and making a PR 
Today, in Gladys, switches are displayed as outlets. You canât tell the two apart.
Currently, we are using power outlets instead of lights in the scenes.
Okay, weâll wait for a potential update on this in the future then
@VonOx and @pierre-gilles, I finally made the PR to update the list of equipment compatible with Gladys (Zigbee2mqtt).
Well, the list is still small but it will grow over time!
Hello @VonOx,
Iâm unable to sync my opening sensors with Gladys on my end.
I tested on about ten of them but nothing on Gladysâs side.
I pressed for 5 seconds to put it in pairing mode.
Did I miss something?
Everything is green on the configuration side.
Hello. Are you on the latest version of Gladys?
Can you see the devices in Zigbee2mqtt (port 8080, same IP as Gladys)?
Do you have any logs in Gladys regarding these devices?
Hello, I also no longer have the ability to insert my Zigbee devices since the update to 4.2.3⊠Here are the details on a brand new installation.
Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2021-04-13T00:01:52+0200 <info> init.js:47 () Zigbee2mqtt USB dongle attached to /dev/ttyACM0
2021-04-13T00:01:52+0200 <info> installMqttContainer.js:25 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...2021-04-13T00:01:52+0200 <info> installMqttContainer.js:26 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:2 image...
2021-04-13T00:01:58+0200 <info> installMqttContainer.js:30 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2021-04-13T00:01:58+0200 <info> installMqttContainer.js:36 (Zigbee2mqttManager.installMqttContainer) Creating container...
2021-04-13T00:02:22+0200 <info> installMqttContainer.js:50 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2021-04-13T00:02:30+0200 <info> installMqttContainer.js:56 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...
2021-04-13T00:02:31+0200 <info> installMqttContainer.js:69 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2021-04-13T00:02:37+0200 <info> installMqttContainer.js:73 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started and configured
2021-04-13T00:02:37+0200 <info> installZ2mContainer.js:24 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2021-04-13T00:02:37+0200 <info> installZ2mContainer.js:25 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2021-04-13T00:03:58+0200 <info> installZ2mContainer.js:29 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2021-04-13T00:03:59+0200 <info> installZ2mContainer.js:40 (Zigbee2mqttManager.installZ2mContainer) Configuration of Device /dev/ttyACM0
2021-04-13T00:03:59+0200 <info> installZ2mContainer.js:43 (Zigbee2mqttManager.installZ2mContainer) Creation of container...
2021-04-13T00:04:25+0200 <info> installZ2mContainer.js:46 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed and configured as Docker container
2021-04-13T00:04:25+0200 <info> installZ2mContainer.js:65 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2021-04-13T00:04:33+0200 <info> installZ2mContainer.js:71 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2021-04-13T00:04:35+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2021-04-13T00:04:35+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2021-04-13T01:53:44+0200 <info> gateway.checkIfBackupNeeded.js:27 (Gateway.checkIfBackupNeeded) Not backing up instance to Gladys Gateway, last backup is recent.
2021-04-13T03:53:44+0200 <info> gateway.checkIfBackupNeeded.js:27 (Gateway.checkIfBackupNeeded) Not backing up instance to Gladys Gateway, last backup is recent.
2021-04-13T05:53:44+0200 <info> gateway.checkIfBackupNeeded.js:27 (Gateway.checkIfBackupNeeded) Not backing up instance to Gladys Gateway, last backup is recent.
2021-04-13T07:53:44+0200 <info> gateway.checkIfBackupNeeded.js:27 (Gateway.checkIfBackupNeeded) Not backing up instance to Gladys Gateway, last backup is recent.
2021-04-13T09:36:31+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:37:21+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:37:43+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:37:47+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:38:23+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:38:44+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d0004024e18 not configured in Gladys.
2021-04-13T09:42:00+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d0004024e18 not configured in Gladys.
2021-04-13T09:42:34+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:42:37+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:50:05+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:50:08+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:50:09+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:50:10+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:50:34+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:53:31+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:53:43+0200 <info> gateway.checkIfBackupNeeded.js:27 (Gateway.checkIfBackupNeeded) Not backing up instance to Gladys Gateway, last backup is recent.
2021-04-13T09:54:51+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
2021-04-13T09:55:45+0200 <warn> handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device 0x00158d00041d439f not configured in Gladys.
pi@raspberrypi:~ $ docker logs gladys
As you can see, they are indeed on the Zigbee interface
Yes
I have the same thing as @Jean34 but not all the time.
I entered 192.168.1.31:8080 but I get a 404 error
Iâll check this evening.
You should check the zigbee2mqtt FAQ, there are many reasons why you might not be able to pair (channel / serial port issue / device not very Zigbee compliant like Aqara).
Gladys only connects to the MQTT broker, it does not manage the zigbee2mqtt container. So pairing is not at all on the Gladys side.
I also reproduce this via G+ / on LAN / Mobile or PC
EDIT: There is a cache issue because by forcing a page refresh, I got my discover to work
I just realized that the issue occurs when Iâm on Gladys +, locally via the IP address, I have no problems
And of course, before coming to you, I did several hard refreshes and even ran CCleaner to be sure
I have often noticed connection losses related to the websocket (no connection to the Zigbee2mqtt service). But as the device reporting during the scan uses this protocol, sometimes it is necessary to reload the page to reconnect the websocket.
For Gladys Plus, I have not been able to test it, but the events should be reported in the same way as locally.
Could you check in the browser console if there are any specific errors?
Well, the pageâs responsiveness isnât great either ^^
@cicoub13 what does this message « Gladys is not accessible » correspond to? As it is, it gives the impression that Gladys is down, and I imagine thatâs not the case, maybe the wording should be improved
Are you sure the issue only appears in Gladys Plus and never locally? From the messages I read, it looks more like an instability issue that sometimes works and sometimes doesnât, regardless of whether itâs local or Gladys Plus (my impression)
@VonOx have you managed to get the Zigbee2mqtt integration to work at least once on Gladys Plus?
I confirm what @Jean34 said, it works locally but not via Gladys Plus
I donât know if it worked because my z2m configuration was done locally and via laptop for more comfort.
Devices already added work on the dashboard via G+.
No errors in the console
In our tests, we realized that sometimes the socket used would no longer respond and thus cause the scan to fail after several seconds.
To better manage this error, while waiting to resolve it definitively, I imagine, this error message was put in place to ask to reload the page and restore the socket.
Ah! Ok, Iâll investigate. What exactly isnât working?
I often have the same problem, but it seems to me that this problem only appears locally due to the serverâs hot reload. Do you have the same problem in production? (in which case, itâs not normal :p)
Ok thanks Iâll check
Ok, I found it. The Zigbee2mqtt integration code is based on an attribute not implemented on the Gladys Plus front end, it couldnât work.
Iâll code the thing!
I can confirm that this problem only occurred when restarting the Gladys container in my tests.
It has never happened to me since it has been in production, as far as I remember.