Using the built-in Philips HUE bridge integration.
In my C8 hub I always had one Philips hue motion sensor giving debug messages in the logging, even when the debugging option was disabled.
I have now moved to a new C8 Pro (re-bui;d my enviroment as migration was not an option) and now a diverent Hue motion sensor is doing the same.
Debug option is disabled, but debug messages are given. It's only one motion sensor, and not the same one as on my old hub.
Tried toggeling debug slider, removed the motion sensor and re-imported it, nothing seems to fix this issue.
How to fix this?
From the contents of the logs you shared, it appears that the Hue Motion Sensor in question is directly paired to the HE Hub via Zigbee, not using the built-in Hue Bridge integration…. Is that correct? If so, we can remove the Hue Bridge integration from the troubleshooting process.
Tagging @bertabcd1234
1 Like
As @ogiewon mentioned, if this is a directly paired Zigbee device (and your log entries indicate that it is), then the Hue Bridge Integration app/drivers don't come into play.
That being said, I can't see anything in the built-in "Hue Motion Sensor" driver that would be causing this, either. Make sure you hit "Save" on the "Preferences" tab. Otherwise, can you confirm what driver you're using? (See How to Change the Driver Used by a Device | Hubitat Documentation, but don't actually change the driver.)
The sensor is not paied directly. Non of my HUE devices is paired directly to Hubitat.
The log in your screenshot shows that at least this one is -- that log entry contains Zigbee or maybe Matter data but is not from the Hue Bridge Integration.
This question matters for either case:
2 Likes
When debug is turned on, it usually sets a scheduled job to turn back off. It sounds like it got turned on during a driver change or something, and you lost the job to turn it back to off. So the logDebug setting is still set to true, and it will stay that way.
Turn debug logging on, and then check scheduled jobs. There should be a job there now to turn it off, and when that timer expires, it should turn off by setting the logDebug setting back to false.
Edit: Actually, when the setting is false, the preference switch should also show off, so if it is still showing off while sending debugs, you may have a different issue.
We really need to know which Driver that Motion Sensor device (dev 38 in the logs) is using, as @bertabcd1234 has asked above a few times. If you're somehow using a community developed driver, that might explain why the debug logging isn't fully turned off. Even if using a built-in driver, the only way the Hubitat team can take a look at the issue is to know which driver's code to review.
1 Like
Sorry for my late reply, kind of swamped with work. I see i placed the wrong screenshots to my original message. It's from another device that is doing the same thing as the Hue device.
After removing the Hue device again and including it on the hub again, that one is not sending any debug messages anymore.
Still have one device, an Aqara Matter Motion and Light Sensor P2, doing the same:
It was included from my homekit using matter, and is using the default Aqara driver:
That makes more sense! 
There was a typo in this driver that would make the "descMap" debug logs appear even when disabled, which will be fixed in the next platform release, currently in beta.
In the meantime (or really forever), if you want to work around this, I'm pretty sure you could use the "Generic Matter Motion/Light Sensor" driver (be sure to run "Configure" after you switch). I never tested this exact device with the driver, but the Aqara driver pre-dates the "Generic..." one, and the generic should be generic enough to work with any device that matches these capabilities.
1 Like
