[Config Support]: upgraded from 0.16 to 0.17; seemed "deaf"; used AI config assistance/got confused; downgraded to 0.16 #22447
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
I can review your 0.16 config and highlight areas that may cause issues or are potentially misconfigured based on the available documentation. Issues Identified in Your Config1. Zone name with spaces 2. Duplicate record:
enabled: true
retain:
days: 3
mode: motion
# ... other settings ...
enabled: true # <-- This appears again before cameras sectionThis duplicate key could cause unexpected behavior. 3. Motion mask placement 4. Object filter masks vs motion masks 5. Required zones configuration Recommendations
The blank timeline periods you're seeing in 0.17 when there's no activity is expected behavior - the timeline shows blank when no recordings are available. However, if you're seeing significantly fewer detections overall, the configuration issues above (especially the mask placement and zone restrictions) could be contributing factors. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Your config is slightly incorrect. should be: This would be one reason why 0.17 was "deaf" - detection is disabled by default, and nesting |
Beta Was this translation helpful? Give feedback.




The correct syntax would be:
However, this would apply a detect width and height of 640x360 to all of your cameras, as this is defining a
detectsection at the global level of your config. I'm not sure that's what you want.You can specify the detect width and height at the camera level, eg: