Hue Motion Sensor problem

CHTHSCH · February 7, 2022, 6:42pm

Since update from openHAB 3.2 to openHAB 3.3-M1 I have a error message for my hue Motion Sensors. These sensors also include a light sensor, that stopped working. See screen shot.

Any idea how this can be fixed again?
Is there a bug in the binding?

jwiseman · February 7, 2022, 9:11pm

I’ve been watching the new development with the HUE binding here. LOTS of changes, not sure if they are part of 3.3m1 yet?

[hue] Changed discovery to mDNS; added HTTPS handling; refactor HTTPClient to use jetty shared client by cweitkamp · Pull Request #11842 · openhab/openhab-addons (github.com)

Best, Jay

Rolli · February 7, 2022, 9:25pm

I use the same sensors on 3.3-M1 and they are working.

Have a look here

cweitkamp · February 7, 2022, 9:39pm

The lightsensor included in a Hue motion sensor suffers from a bug in that latest milestone. A fix already has been merged. I posted a workaround in the related issue on GitHub.

github.com/openhab/openhab-addons

[hue] Missing or invalid configuration / Hue ambient light sensor / openHAB 3.3M1

opened 08:17PM - 01 Feb 22 UTC

closed 07:01AM - 02 Feb 22 UTC

michaeljoos72

bug

## Expected Behavior Thing should stay online without error. Never had an issue… with this in openHAB 3.2 ## Current Behavior **1. openHAB auto discover does work for light sensor (motion sensor) but shows error in log:** ![image](https://user-images.githubusercontent.com/20517474/152042594-301dec80-bfa6-47ed-9f09-039d4d806518.png) Debug-Log: 2022-02-01 21:13:44.341 [DEBUG] [.discovery.HueDeviceDiscoveryService] - discovered unsupported sensor of type 'Daylight' and model 'PHDL00' with id 1 2022-02-01 21:13:44.896 [DEBUG] [.discovery.HueDeviceDiscoveryService] - discovered unsupported sensor of type 'Daylight' and model 'PHDL00' with id 1 **2. Add thing(s) does show status ONLINE:** ![image](https://user-images.githubusercontent.com/20517474/152042772-6e0bb824-27e5-4f01-822c-0b2f1d9f4052.png) **3. After change/save/reboot Thing(s) are in status UNINITIALIZED / HANDLER_CONFIGURATION_PENDING** ![image](https://user-images.githubusercontent.com/20517474/152043176-934765cf-a567-4463-8858-77bbcd3d6fed.png) ![image](https://user-images.githubusercontent.com/20517474/152043251-d9a5481a-a63b-4d53-a908-3269f6d67a51.png) Debug-Log after reboot: [openhab.log](https://github.com/openhab/openhab-addons/files/7981684/openhab.log) ## Your Environment openHABian v1.7.1 / Raspberry Pi OS Bullseye openHAB 3.3.0.M1 - Milestone Build java -version openjdk version "11.0.14" 2022-01-18 OpenJDK Runtime Environment (build 11.0.14+9-post-Raspbian-1deb11u1) OpenJDK Server VM (build 11.0.14+9-post-Raspbian-1deb11u1, mixed mode)

No, unfortunately not. They are still in review. I hope they will be merged soon.

CHTHSCH · February 8, 2022, 4:35pm

So I will wait for the next milestone release to get this fixed.

Thanks

OMR · April 8, 2022, 11:15pm

Still a problem om M3.
Fix is to just delet the item an re-include.
Must be done after each OH restart.

CHTHSCH · April 9, 2022, 5:41am

This problem had already been fixed in M2.

Removing the sensor and adding it again should work and cure the problem. At least in my setup it is ok again. There is NO necessity to delete and re-include after every OH restart.

OMR · April 9, 2022, 12:18pm

Just tested a restart on M3.
You are right, It’s OK now.
Reason I thought it was still a problem was that the Ambient Light Sensor was Online on M1 and went Offline with the Config error when I upgraded to M3. Had to removed and re-included and now it survives reboots.
Thanks!

Marisa_Heard · April 29, 2022, 5:26am

I screen shot an image of my phone and did a Google lens search on my phone to figure out what this code thing that just appeared in my drop down menu one day and since then my phone has been behaving very oddly. I Google lens searched the image and it brought me here. Can anyone tell me what this means or what it is. This is how it appears on my phone:
11(RP1A. 200720.011)