core: Temperature entity of motion and contact sensors unavailable once value is lower than 1
The problem
Motion sensors (lumi.sensor_motion.aq2 / RTCGQ11LM) are of state unavailable once the temperature of the sensor is reported below 1 degrees. It comes back once the temperature rises.
While the temperature itself is available and shown e. g. in Phoscon, it is not in deCONZ. This is why I assume this is a deCONZ integration error. (otherwise I would have reported this at https://github.com/dresden-elektronik/deconz-rest-plugin/issues)



What version of Home Assistant Core has the issue?
core-2022.9.7
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
deCONZ
Link to integration documentation on our website
https://www.home-assistant.io/integrations/deconz
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Two things happened during the last days:
- Temperatures went down (assumption: error has always been there)
- deCONZ has been updated to v2.19.3 (from v2.19.1) (assumption: error has been introduced with v2.19.3)
- Probably related to https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6203 (don’t think so, just wanted to name one of the last changes affecting specifically those devices)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 24 (8 by maintainers)
https://www.home-assistant.io/integrations/logger/
There is a service to set debug logging I think, haven’t used it myself
I wrote up a test to validate it working with negative temperatures, which it does. Without logs I can’t proceed here.