# Zigbee discovery malfunction ("Gladys is not accessible"). Related to Node-red service change? **URL:** \ **Category:** Configuration\ **Created:** [January 7, 2024, 9:11am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673 "2024-01-07T09:11:11Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\ **Post date:** [January 7, 2024, 9:11am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/1 "2024-01-07T09:11:11Z")
Hello, I need your help to fix a small issue in my Gladys-Zigbee-MQTT setup. Thanks in advance 😉 The Zigbee devices already configured work fine, but I can no longer add new Zigbee devices. The « Zigbee Discovery Â» page ([http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/discover](http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/discover)) shows the error « Gladys is not accessible Â». Yet all the indicators on the « Zigbee2mqtt service configuration Â» page ([http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/setup](http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/setup)) are green. The problem seems to coincide with a recent change: I switched from the Node-RED I initially set up (accessible at [http://192.168](http://192.168). **.** :1880) to the one now integrated into Gladys (accessible at [http://192.168](http://192.168). **.** :1881). Could my issue be caused by that? What can I do to resolve it? ---
**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\ **Post date:** [January 7, 2024, 9:30am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/2 "2024-01-07T09:30:12Z")
I should mention that the Zigbee page ([http://192.168](http://192.168). **.** :8080) is accessible, and that I was able to see the new Zigbee device I want to retrieve in Gladys displayed there. I also notice from the page [http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/discover](http://192.168.0.105/dashboard/integration/device/zigbee2mqtt/discover) which shows this error « Gladys n’est pas accessible Â» that a click on the « Autoriser l’association Â» button does have an effect on the Zigbee service, because the notifications « Zigbee : allowing new devices to join Â» and « Zigbee : disabling new devices Â» are indeed displayed on the page http://\_\_\_:8080 ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [January 7, 2024, 12:29pm UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/3 "2024-01-07T12:29:06Z")
Hello. The problem has been known for a few days (latest zigbee2mqtt update). I think we’ll fix that on Monday (if we can do a Gladys release). You have the details here [Zigbee2mqtt 1.35 - Erreur affichage devices - #4 par cicoub13](https://community.gladysassistant.com/t/zigbee2mqtt-1-35-erreur-affichage-devices/8670/4?u=cicoub13) ---
**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\ **Post date:** [January 7, 2024, 1:19pm UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/4 "2024-01-07T13:19:00Z")
Thanks @cicoub13. I had done some research but didn’t come across this topic. So I’ll wait until it’s fixed. ---
**Author:** ![Jluc](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jluc/32/12397_2.png) [@Jluc](https://community.gladysassistant.com/u/Jluc)\ **Post date:** [January 8, 2024, 11:10am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/5 "2024-01-08T11:10:08Z")
Hello, I have never used Node-RED and I encountered the same problem again around noon today. ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/8/8db4cfdc3ddaebfffcc586fa8d98172764aaf8bd.png) ---
**Author:** ![Einstein8854](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/einstein8854/32/9474_2.png) [@Einstein8854](https://community.gladysassistant.com/u/Einstein8854)\ **Post date:** [January 8, 2024, 12:37pm UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/6 "2024-01-08T12:37:13Z")
hello, on Zigbee network discovery the same message also « Gladys is not accessible Â», while in the configuration and settings menus of the zigbee2mqtt integration everything is green! but couldn’t the problem come from the koenkk/zigbee2mqtt container? it was apparently updated 6 days ago? ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [January 8, 2024, 2:27pm UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/7 "2024-01-08T14:27:25Z")
The error is mentioned here [Zigbee2mqtt 1.35 - Erreur affichage devices - #4 par cicoub13](https://community.gladysassistant.com/t/zigbee2mqtt-1-35-erreur-affichage-devices/8670/4?u=cicoub13) A fix has been made, now we just have to wait for the release. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [January 9, 2024, 8:03am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/8 "2024-01-09T08:03:57Z")
FYI Gladys Assistant v4.34.0 was successfully deployed yesterday and I can confirm that it does fix the issue! 🙂 Thanks @cicoub13 for the fix! ---
**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\ **Post date:** [January 9, 2024, 9:55am UTC](https://community.gladysassistant.com/t/dysfontionnement-decouverte-zigbee-gladys-nest-pas-accessible-lie-au-changement-de-service-node-red/8673/9 "2024-01-09T09:55:19Z")
It’s not useful, but I confirm too 😉. Thanks!