Hue Essentials Error when connecting

Hello Everyone,

When I try to connect the diyHue Bridge to Hue Essentials i get an Error :


Error

Unexpected response from the bridge. Please try again later.

Expected a(mystic symbol), but had a(mystic symbol) as the serialized body of com.superthomaslab.hueessentials.common.core.bridge.hue.json.v1.HueV1Root at element: $.primitive JSON input: <!DOCTYPE


The bridges seems to connects with Hue Essentials for 5 seconds then disconnects and is never able to connect again

Do you have any idea on how to fix it ?

Here is a screen of the Error :

Hi what is the log in diyhue?

Here are the logs i hope they are the right ones :

For details, my phone is 192.168.0.68(Hue Essentials) / My Pc is 192.168.0.36(DiyHue App)

2025-12-22 20:32:30,216 - services.deconz - 91 - INFO - {“attr”:{“lastseen”:“2025-12-22T19:32Z”},“e”:“changed”,“id”:“11”,“r”:“lights”,“t”:“event”,“uniqueid”:“c4:98:86:00:00:0e:f6:c6-01”}
2025-12-22 20:32:30,216 - services.deconz - 23 - DEBUG - Cache Hit for lights 11
2025-12-22 20:32:30,628 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:30] “GET /api/9dc6cf22b38b11f0ab1f005056835314/config/swupdate2 HTTP/1.1” 200 -
2025-12-22 20:32:31,675 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:31] “GET /api/9dc6cf22b38b11f0ab1f005056835314/groups/0 HTTP/1.1” 200 -
2025-12-22 20:32:32,010 - services.ssdp - 44 - DEBUG - Sending M-Search response to 192.168.0.68
2025-12-22 20:32:35,686 - services.remoteApi - 37 - DEBUG - remote sever is down
2025-12-22 20:32:35,691 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:35] “GET /api/9dc6cf22b38b11f0ab1f005056835314/config/swupdate2 HTTP/1.1” 200 -
2025-12-22 20:32:35,798 - services.deconz - 91 - INFO - {“attr”:{“lastseen”:“2025-12-22T19:32Z”},“e”:“changed”,“id”:“17”,“r”:“lights”,“t”:“event”,“uniqueid”:“00:15:8d:00:06:f0:28:fd-01”}
2025-12-22 20:32:35,799 - services.deconz - 23 - DEBUG - Cache Hit for lights 17
2025-12-22 20:32:36,246 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET / HTTP/1.1” 200 -
2025-12-22 20:32:36,380 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /assets/index-CyzsjfeZ.css HTTP/1.1” 200 -
2025-12-22 20:32:36,384 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/index-BGcdHbbG.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,429 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/background-BA295pIK.webp HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,515 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/Bridge-DG8HH0h2.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,518 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/react-confirm-alert-CT3xFzne.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,523 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/react-confirm-alert-B7EkYfmo.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,524 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/GenericText-CykSJak5.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,527 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/GenericText-Cxe-pwOc.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,530 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/SelectMenu-CMQ-rAZe.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,535 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/SelectMenu-CNylQg5x.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,537 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/GlassContainer-274NnONw.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,541 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/PageContent-BidV3keP.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,544 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/CardGrid-CNfFK47B.js HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,551 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/GlassContainer-DZ37rgdA.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,553 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/PageContent-DB_YHES7.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,555 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “e[36mGET /assets/CardGrid-BOWJJjh7.css HTTP/1.1e[0m” 304 -
2025-12-22 20:32:36,554 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /get-key HTTP/1.1” 200 -
2025-12-22 20:32:36,649 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /api/9dc6cf22b38b11f0ab1f005056835314/config/swupdate2 HTTP/1.1” 200 -
2025-12-22 20:32:36,652 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /api/9dc6cf22b38b11f0ab1f005056835314/groups/0 HTTP/1.1” 200 -
2025-12-22 20:32:36,655 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /api/9dc6cf22b38b11f0ab1f005056835314/info/timezones HTTP/1.1” 200 -
2025-12-22 20:32:36,658 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /api/9dc6cf22b38b11f0ab1f005056835314/config HTTP/1.1” 200 -
2025-12-22 20:32:36,670 - werkzeug - 97 - INFO - 192.168.0.36 - - [22/Dec/2025 20:32:36] “GET /info HTTP/1.1” 200 -
2025-12-22 20:32:36,690 - services.deconz - 91 - INFO - {“attr”:{“lastseen”:“2025-12-22T19:32Z”},“e”:“changed”,“id”:“16”,“r”:“lights”,“t”:“event”,“uniqueid”:“00:15:8d:00:06:f0:32:68-01”}
2025-12-22 20:32:36,691 - services.deconz - 23 - DEBUG - Cache Hit for lights 16
2025-12-22 20:32:37,240 - services.ssdp - 44 - DEBUG - Sending M-Search response to 192.168.0.36
2025-12-22 20:32:37,541 - services.ssdp - 44 - DEBUG - Sending M-Search response to 192.168.0.90

I tried it my self and get the same error, will check later.

It have nothing to do with diyhue but with the remote server.

Diyhue.org is down so hue essentials cannot check if your bridge have remote service and there is the error coming from.

I will contact the maintainer of the site.

I have contact with the maintainer he is looking into it

Thank you for taking the time to look into my issues.

I don’t know if it’s related or not, but I tried to connect the DiyHue Bridge to the official Hue app (on Android). When it said that it detected a bridge and asked me to press the link button, I did, but nothing happened. Also, nothing appears in the logs.

I also tried to connect the Bridge to Hue Sync, but it’s not detecting any bridge. When I enter the IP address of the Bridge, nothing happens and it goes back to searching. Just like with the official app, there is nothing in the logs.

With the hue app did you login to your philips account? If so this will not work, you have to remove the app and reinstall and continue without an account

I’ve tried that as well. I reinstalled the app and tried to set it up without an account, but it still gets stuck at the ‘Link Button’ step. This happens whether I let the app search for the Bridge automatically or if I provide the IP address manually.

We will look at this later, enjoy your Christmas