Philips Hue integration issue

Herve · February 1, 2021, 2:20am

Good evening,
I installed gladys from the image on a raspberry 3, no problem. I configured the weather, a raspicam camera, mqtt and Telegram.
However, when I try to integrate a Philips Hue bridge, no luck…
The bridge and connected bulbs work well with the android app and with Google Home, but Gladys does not detect the bridge during the search. Whereas when I type the IP of the bridge in a browser, I can access the bridge’s home page.
I don’t know where to look to solve the problem, thank you for your help.

Hervé

Tlse-vins · February 1, 2021, 6:07am

Have you put the bridge in search mode by clicking the button?

VonOx · February 1, 2021, 7:11am

The bridge is supposed to appear whether you press the button or not.

@Herve Is the integration service started?

Terdious · February 1, 2021, 7:41am

For information, it often happens to me that the bridges (I have 2) only appear after a few minutes … and several refreshes … (I still don’t know how to determine if it’s one - time, the other - multiple refreshes, or both that solve the problem)

Tlse-vins · February 1, 2021, 8:56am

I thought it was still seen by Gladys.

Herve · February 2, 2021, 2:00am

Good evening,
And thank you for your feedback.
I have made X attempts… button pressed or not, refresh, reboot, etc… nothing to do…
The Philips hue service seems to be started. I tested by connecting to « Gladys.local » or @IP and nothing to do.
The software version of Gladys is ok v4.0.4 and the bridge as well.

Terdious · February 2, 2021, 6:10am

Hello @Herve, we can try to « debug » first.

First question, is there any subtlety in your installation? For example, multiple distinct networks? Is your Philips Hue bridge recent (1st or 2nd generation)?

Second question, do you know how to connect via SSH to your Raspberry Pi and would you like to test 2-3 verification commands?

Herve · February 2, 2021, 10:24am

Hello!

Single network, no sub-network. Bridge and Raspberry connected via cable to SFR 4G box.
I will check the bridge version tonight, but purchased in December here in Martinique at Fnac.
No issues for SSH.

Sorry for the « delayed » responses, but 5 hours time difference…
Hervé

Terdious · February 2, 2021, 10:34am

Héhé no problem ^^ We are not in a hurry … ^^ Even though I suppose you would like it to be functional as soon as possible ^^

So maybe the first thing would be to check the docker logs when starting the service!! I’m setting up a 2nd gladys to reproduce with you.

Terdious · February 2, 2021, 10:43am

Ok, for now I’m in the same situation as you on a fresh installation from the gladys-4.0.4-rev4.img.zip image:

And via the command sudo docker logs gladys --since 2020-01-02T10:00:00 -f --details over ssh on the pi:

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

 Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
 2021-02-02T11:31:16+0100 <info> index.js:19 (Object.start) Starting telegram service
 2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
 2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
 2021-02-02T11:31:16+0100 <info> index.js:20 (Object.start) Starting Open Weather service
 2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
 2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
 2021-02-02T11:31:16+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
 2021-02-02T11:31:16+0100 <info> index.js:16 (Object.start) Starting zwave service
 2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
 2021-02-02T11:31:16+0100 <info> index.js:13 (Object.start) Starting usb service
 2021-02-02T11:31:17+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 80
 2021-02-02T11:39:36+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:39:40+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:39:44+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:39:55+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:40:00+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:40:02+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:40:03+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T11:40:04+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges

And no errors on the front end:

@VonOx and @Tlse-vins, could you test on a fresh install as well… just to see if an update hasn’t messed things up?

Tlse-vins · February 2, 2021, 10:50am

Is it better to test on an SD card in the Pi or locally?

Terdious · February 2, 2021, 10:54am

The best I think is to do a new install on a new SD card if you have an extra one, to be in the same conditions.

Edit: If you reproduce, we can push it further. And @VonOx might have an idea … ^^

Terdious · February 2, 2021, 10:56am

For information, I tried to cut and restart the service in the settings, but it’s the same.

Terdious:

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2021-02-02T11:31:16+0100 <info> index.js:19 (Object.start) Starting telegram service
2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
2021-02-02T11:31:16+0100 <info> index.js:20 (Object.start) Starting Open Weather service
2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2021-02-02T11:31:16+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
2021-02-02T11:31:16+0100 <info> index.js:16 (Object.start) Starting zwave service
2021-02-02T11:31:16+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2021-02-02T11:31:16+0100 <info> index.js:13 (Object.start) Starting usb service
2021-02-02T11:31:17+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 80

By the way, is it normal that it does not appear in the <info> service.start.js:40 (Service.start)?
Same when you stop/restart the service, no information.

Terdious · February 2, 2021, 11:07am

Well, it just appeared:

  2021-02-02T11:58:19+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
  2021-02-02T11:58:31+0100 <info> unsubscribe.js:10 (MqttHandler.unsubscribe) Unsubscribing to MQTT topic stat/+/+
  2021-02-02T11:58:31+0100 <info> unsubscribe.js:10 (MqttHandler.unsubscribe) Unsubscribing to MQTT topic tele/+/+
  2021-02-02T11:58:41+0100 <info> index.js:19 (Object.start) Starting telegram service
  2021-02-02T11:58:41+0100 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
  2021-02-02T11:58:56+0100 <info> index.js:13 (Object.start) Starting usb service
  2021-02-02T11:59:06+0100 <info> index.js:16 (Object.start) Starting zwave service
  2021-02-02T11:59:06+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
  2021-02-02T11:59:15+0100 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
  2021-02-02T11:59:25+0100 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
  2021-02-02T12:01:56+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 1 bridges

I stopped/started all services several times. Spamming the « Search on the network » button, going back and forth on the page. And waited about 30 minutes… I don’t know what triggered the discovery.

Tlse-vins · February 2, 2021, 11:19am

Ok, yes I still have an SD card.
Are the service info the same on a version where the bridge is seen immediately?

Terdious · February 2, 2021, 11:27am

No idea, but I guess!!^^

Terdious · February 2, 2021, 11:28am

For my part, I have 2 points, the second one was just seen, almost 1 hour later:

Tlse-vins · February 2, 2021, 8:59pm

Good, I just tested on a clean installation with V4.0.4 and the bridge was seen instantly.

As well as the devices.

No problem on my side.

VonOx · February 2, 2021, 9:00pm

Same thing, instant detection

Ps: @Terdious you have too many scenes

Herve · February 3, 2021, 12:58am

Good evening everyone,
Here is the log in question:

 > gladys-server@ start:prod /src/server
 > cross-env NODE_ENV=production node index.js

 Initialising OpenZWave 1.6.1051 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
 2021-02-02T23:49:15+0100 <info> connect.js:38 (MqttClient.<anonymous>) Connected to MQTT server mqtt://localhost
 2021-02-02T23:49:15+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/#
 2021-02-02T23:49:15+0100 <info> index.js:20 (Object.start) Starting Open Weather service
 2021-02-02T23:49:15+0100 <info> index.js:15 (Object.start) Starting Bluetooth service
 2021-02-02T23:49:16+0100 <error> index.js:19 (process.<anonymous>) uncaughtException catched: uncaughtException
 2021-02-02T23:49:16+0100 <error> index.js:20 (process.<anonymous>) Error: ENODEV, No such device
     at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
     at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
     at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
     at processTicksAndRejections (internal/process/task_queues.js:79:11) {
   errno: 19,
   code: 'ENODEV',
   syscall: 'bind'
 }
 2021-02-02T23:49:17+0100 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
 2021-02-02T23:490:17+0100 <info> index.js:16 (Object.start) Starting zwave service
 2021-02-02T23:49:17+0100 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
 2021-02-02T23:49:17+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic stat/+/+
 2021-02-02T23:49:17+0100 <info> subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic tele/+/+
 2021-02-02T23:49:17+0100 <info> index.js:13 (Object.start) Starting usb service
 2021-02-02T23:49:17+0100 <info> index.js:19 (Object.start) Starting telegram service
 2021-02-02T23:49:18+0100 <info> index.js:63 (Server.<anonymous>) Server listening on port 80
 2021-02-02T23:51:14+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T23:55:37+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T23:58:28+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges
 2021-02-02T23:58:33+0100 <info> light.getBridges.js:10 (PhilipsHueLightHandler.getBridges) PhilipsHueService: Found 0 bridges

What do you think? Is it serious doctor?

Topic		Replies	Views
Image Node 18 : Tests intégration Bluetooth Développement	41	1260	December 13, 2022
Z-Wave - Gladys v4 - Windows WSL Développement	118	4856	October 10, 2021
Intégration Ecowatt: Des scénarios intelligents dans Gladys en cas de tension sur le réseau électrique! Actualités	85	3172	January 16, 2023
Compatibilité ampoule yeelight Demande de fonctionnalités feature-integration , yeelight	150	5010	May 20, 2026
Découverte, questions basiques et remerciements Configuration	7	472	June 23, 2021

Philips Hue integration issue

Related topics