Hue items doesn't work after a time. No issue in the logs

Add-ons Bindings
1

Hi all,

I have an OpenHAB4.3.1 running with a huge setup running on a Pi4 in a docker environment. In general all is working fine and without issues.

Since a few weeks I have an issue with the hue binding, that the hue items don’t react after time. Actors don’t react, sensors don’t deliver updates. In this case I don’t see any issue in the logs. OpenHAB thinks that all works as expected, but it doesn’t.

Does anybody has an advice what to check in such a case? How to find this issue?

Thanks,
Denis

2

OpenHAB4.3.1 does not yet exist.

3

Yes sorry it’s the latest 4.1.3…

Btw. I already tried to restart the hue binding in such a case, but this didn’t help.

4

Nobody an idea how to find the issue here?

5

Do actors, sensors, lights react when you use the Philips Hue App? Just to make sure that it is really openHAB related?
For example I needed to change the Hue communication channel to a different one because some Hue Lights were not reachable due to frequency-overlap (with Wifi).

did you try to change logging level?
You can see the current logging level:

  log:get org.openhab.binding.hue.internal.connection.Clip2Bridge

Change logging to trace:

  log:set TRACE org.openhab.binding.hue.internal.connection.Clip2Bridge

you can revert to info-level:

  log:set INFO org.openhab.binding.hue.internal.connection.Clip2Bridge

I am currently running approx. 70 Hue-things without any problems.

Best, Kai

6

Hi Kai,

Thanks for your reply.

  1. Yes they are working using the app when openhab can not control them
  2. I tried to set a debug loglevel already but didn’t see anything. But to be honest there where a lot information with debug. Maybe I missed something…

Openhab lists the things as online when they do not work. There is no indicator, that it doesn’t work. Regarding to the log the actors take their commands and there are no signals from sensor like motion.

I will activate the trace log the next time when it happens. But I don’t think that I will see anything. Normally this happens each 3-4 days. So I should see it latest tomorrow or the day after…

Thanks,
Denis

7

Ok this night I had the issue again. Something changed in the behavior since I moved to hue api2:

  1. The actors seems to work, also when the issue exists. My lights and plugs can be controlled with OH
  2. Motion sensors and dimmer switches doesn’t work
  3. BUT I can see that the motion sensors and the dimmer switches send data to the hue binding after enabled the TRACE log of them
  4. BUT I have rules which should get triggered by them and they don’t do!
  5. The switches for the hue motion items in the UI also doesn’t trigger when I see the motion events in the logs
  6. After a restart of the hue bundle nothing of the hue binding works and I get messages like this in the logs (I replaced the IDs with xxx and yyy):
    2024-07-25 06:45:26.012 [WARN ] [e.internal.handler.Clip2ThingHandler] - Command 'ON' for channel 'hue:device:xxxx:yyyy:brightness' cannot be processed by thing 'hue:device:xxx:yyy'.

The only fix is to restart OH then.

So for me it currently looks as the connection between the hue binding and the ?eventing? system from OH is broken in this situation?

8

maybe this is something @AndrewFG can help with?
Best, Kai

9

You seem to be talking about too many things at the same time. Can we please focus on one at a time? Say the motion sensor. Can you please share the thing and item configuration for that device? Does it have an item connected to the motion detector enabled channel? And is that channel enabled?

Motion sensors are usually combined with light and temperature sensors, but they will have three channels associated with the motion functionality – namely motion, motion-enabled, and motion-last-updated – in particular the latter should help you in debugging…

10

Hi,

I’m talking about of many things, because they are those which are not working :yum:

Currently all is working since 25th. of July. I don’t know why, because I didn’t change anything. The only thing I did not do is to reconfigure stuff in openhab I think. Normally I do this with VS Code / Openhab extension / ssh. Do you think that the openhab vscode plugin can happen issues like that? Or is there a known issue that openhab needs to be restarted after editing the thing, item or rules files from hue related stuff?

I will not open vscode right now until I have the next issue, to see if the system stays stable without that. So I can send you my thing and item configuration example as soon as the issue occurs again. But I don’t think that there is an issue with them, because normally everything runs fine, except when this issue occurs after days. But normally I had this each few days. So 1,5 weeks till now is a really long timespan…

11

System is still stable until today. So I uninstalled the openhab extension in VS Code today to check if this changes something.

12

Hi all,

meanwhile the issue is back and seems to happen nearly once a day.

My things file and items file looks like:

...    
Thing device 4e7f6a9a-bb1b-4bd1-82df-3844eec59673 "Esstisch Sensor" [resourceId="4e7f6a9a-bb1b-4bd1-82df-3844eec59673"] // Hue motion sensor idV1:/sensors/22
...

...
Number:Illuminance LightLevelSensorIlluminanceEsszimmer "Esszimmer Helligkeit" <light> (gHueItems, gAlleLichtmengenmesser) { channel="hue:device:001788fffea4f27f:10303795-2e02-499a-9196-0d23cfcac247:light-level" }
Number:Temperature TemperatureSensorTemperatureEsszimmer "Esszimmer Temperatur" <temperature> (gHueItems, gAlleTemperatursensoren) { channel="hue:device:001788fffea4f27f:10303795-2e02-499a-9196-0d23cfcac247:temperature" }
Switch   MotionSensorPresenceEsszimmer    "Esszimmer Bewegung erkannt" <motion> (gHueItems, gBewegungsmelderWohnEsszimmer, gBewegungsmelderEsszimmer, gAlleBewegungsmelder) { channel="hue:device:001788fffea4f27f:10303795-2e02-499a-9196-0d23cfcac247:motion" }
Number   MotionSensorBatteryLevelEsszimmer "Esszimmer Batteriestand" <batterylevel> (gHueItems, gAlleBatterieLevel) { channel="hue:device:001788fffea4f27f:10303795-2e02-499a-9196-0d23cfcac247:battery-level" }
Switch   MotionSensorLowBatteryEsszimmer  "Esszimmer Batterie leer" <lowbattery>  (gHueItems, gAlleBatterieLeer) { channel="hue:device:001788fffea4f27f:10303795-2e02-499a-9196-0d23cfcac247:battery-low" }
...

As already set I have a lot of them and after restarting openhab they work fine, until they don’t work anymore. If the issue occurs, other hue based items like lamps and switches are working, but there is no event at all from the motion sensors. I also can’t find anything regarding motion in the logfiles then.

I just tried to get a devices from the bridge using the karaf command:

openhab> openhab:hue hue:bridge-api2:xxxxxxxxxx things

when I’m in the faulty state. I get the motion sensors in the list as well. I can see them in the HUE app, too, and there I can also see the motion event. Just openhab doesn’t get the motion events then.

13

Can you please say more precisely what you mean by ‘work’ resp. ‘don’t work’?

PS for the avoidance of doubt, I suppose you know that these things have motion-enabled resp. light-level-enabled channels?

14

Work=Change of item state when motion happens
Not Work=No change of item state. Item stays „OFF“

I’m aware of the enabled state but I didn’t check it yet because normally they are working so they have to be enabled. After a restart of openHAB they are working again without changing anything else

15

@HuberDe can you please log:set TRACE org.openhab.binding.hue and do the following;

  1. Disable/enable the bridge Thing
  2. Move in front of your motion sensor
  3. Send me the log
16

Hi all,

just wanna let you know that I have the same behavior at my system since a few weeks.
At the moment I try to catch the moment the sensors stoped working…
What I can say is that 1. disable/enable the bridge Thing doesn’t fix the error, as the bridge doesn’t come onlien then. I have to restart OH.

regards Thomas

17

Hi Thomas,

Thanks for that feedback. I’m not alone :vulcan_salute:

Are you using the OH plugin and VS Code? I feel like there is a dependency to the plugin. This installs a server component to be able to get the thing state etc. In the past I had the feeling that the issue occurs x hours after accessing OH with the VS Code plugin. It may be that my issue came back when I installed the plugin again.

I can confirm that disable/enable the thing doesn’t work as well restarting the hue bundle.

I will check for the requested logs when the issue occurs the next time.

Thanks,
Denis

18

Hi Denis,

yes I’m using VS Code too. And I’m also wondering if changing rules, items and things may have an impact. Sometimes rules stopped working or thinds doesn’t change.
I’m looking at the googletv binding atm. There are http connection errors too. And this devices are the last big changes at my system.

Thomas

19

@Thomas_Frank @HuberDe thanks for reporting. However I cannot replicate this issue. So I need trace logs in order to find a fix. Also what OH version are you on? If you think it is related to VS code, then it is probably NOT related directly to the binding. Can you both confirm that it is ONLY related to motion or light level sensors? In other words can you confirm that other devices (lights and switches) resp. rooms/zones do work as before?

20

For me only the motion signal seems not working. The temperature and I think also the light channels are sending their values.

Lights are working, but I have found this messages in the log:

image
image2842×273 27.4 KB

Then the lights doesn’t work too.
But this could be an ohter problem, as it heals after some minutes…