-
Notifications
You must be signed in to change notification settings - Fork 0
Understanding Risk and Advisory Confidence
The Risk and Advisory section explains how Asset Intelligence interprets the current environment around an asset.
It answers three important questions:
- What is happening in the room?
- Does that matter for this specific asset?
- What should the user understand or consider doing?
Asset Intelligence does not evaluate risk from a single sensor value.
Risk is determined by combining:
- The current room environment
- The asset’s environmental limits
- The asset’s placement and exposure
- Room sensor confidence
- Spatial context such as windows, facing direction, sun position, lux, and UV
- Debounce rules that prevent rapid state changes
- Advisory logic that explains what matters and why
This means that two assets in the same room may have different risk results.
For example:
- A receiver may tolerate normal household temperature and humidity.
- A painting near an east-facing window may be more sensitive to light, UV, and sun exposure.
- A wine collection may be most sensitive to temperature and humidity.
- A document archive may be sensitive to humidity, mold risk, and water leaks.
The room provides the conditions.
The asset determines whether those conditions matter.
Risk is calculated through several layers.
Asset Intelligence first builds a current snapshot of the room environment.
This may include:
- Temperature
- Humidity
- Dew point
- Lux
- UV
- VOC
- Formaldehyde
- Ozone
- NO₂
- PM2.5
- PM10
- Mold index
- Leak status
- Pressure
- Vibration
- Noise
- CO₂
- Sun position
- Window direction
- Sensor availability
- Confidence
This room snapshot comes from the sensors mapped in Room Configuration.
If a sensor is missing or unavailable, the system does not guess.
Missing data is recorded and may reduce confidence.
Each asset can have environment limits that define what is acceptable for that asset.
Examples:
- Minimum and maximum temperature
- Minimum and maximum humidity
- Maximum CO₂
- Maximum lux
- Maximum UV
- Maximum VOC
- Maximum PM2.5
- Maximum mold index
- Leak sensitivity
- Vibration sensitivity
These limits describe what the asset can safely tolerate.
The system compares the current room environment to the asset’s configured limits.
Examples:
- Current room CO₂ is above the asset’s maximum CO₂ limit
- Current humidity is above the asset’s maximum humidity limit
- Current temperature is below the asset’s minimum temperature limit
- Lux or UV data is missing for an asset that depends on light exposure analysis
- Leak is detected in the room
- Mold index exceeds the configured maximum
The result of this comparison produces risk reasons.
Risk reasons explain why the system reached its current conclusion.
Asset Intelligence also considers where the asset is located inside the room.
This includes:
- Whether the asset is near a window
- Which direction the asset faces
- Which windows exist in the room
- The direction of those windows
- Current sun azimuth
- Current sun elevation
- Whether the asset’s facing direction aligns with likely exposure
- Whether light or UV readings are available
This allows the system to reason beyond simple room averages.
For example:
An asset marked as near a window may be treated differently than an asset in the same room but away from direct exposure.
The system first produces a candidate state.
The candidate state is the system’s immediate interpretation of current conditions before transition timing is applied.
Typical states include:
- Green
- Amber
- Red
A simple way to understand the candidate state:
- Green means current conditions are within configured limits.
- Amber means warnings, missing data, reduced confidence, or cautionary conditions exist.
- Red means one or more configured limits are currently violated.
Asset Intelligence avoids rapidly switching risk states because of brief sensor spikes.
Debounce settings control how long a condition must persist before certain transitions occur.
Common debounce settings include:
- Red transition seconds
- Recovery seconds
For example:
If CO₂ briefly rises above the limit for a few seconds, the system may show a candidate Red condition but avoid immediately committing the asset to Red.
This prevents noisy data from creating unnecessary alarm.
After debounce rules are applied, the system determines the effective risk state.
This is the state that appears as the current risk state for the asset.
The effective state may be different from the candidate state while the system is waiting to confirm that a condition is persistent.
Example:
- Candidate state: Red
- Effective state: Amber
- Reason: Red transition debounce is still pending
This helps distinguish between immediate signal detection and confirmed risk state.
The coordinator is the runtime manager for Asset Intelligence.
It is responsible for:
- Running evaluation cycles
- Applying debounce timing
- Detecting state changes
- Recording environment events
- Recording advisory events
- Updating the projection used by Home Assistant entities
- Keeping the UI aligned with the current runtime state
The coordinator does not directly read sensors and does not define the risk rules.
Instead, it coordinates the flow:
Room environment snapshot
→ Asset requirements
→ Risk evaluation
→ State transition
→ Events
→ UI projection
This keeps risk behavior deterministic and consistent.
Risk tells you what state the asset is in.
Advisory explains what the state means.
The advisory layer uses the broader context of the asset and the room to generate explanations or recommendations.
Advisory context may include:
- Which condition is outside the preferred range
- Which sensor data is missing
- Whether a room needs better sensing
- Whether the asset is exposed to light or sun
- Whether placement contributes to risk
- Whether the asset type is sensitive to the current condition
- Whether the room appears unsuitable for the asset
- Whether environmental controls may need attention
Examples:
- No advisory message
- CO₂ is above the preferred maximum
- No room light data is available
- No room UV data is available
- Asset is near a window with potential exposure
- Add a UV sensor for better exposure evaluation
- Move the asset away from direct sunlight
- Review room environment limits
Advisory is informational.
It does not directly perform automation by itself.
Risk and advisory are related, but they are not the same thing.
| Concept | Purpose |
|---|---|
| Risk state | Current evaluated condition of the asset |
| Candidate state | Immediate proposed state from current signals |
| Effective state | Confirmed state after debounce rules |
| Risk reasons | Evidence used to explain the state |
| Advisory | Human-readable guidance or recommendation |
| Confidence | Completeness and reliability of available room data |
A Red risk state means a configured condition is outside acceptable limits.
An advisory explains what the user should understand about that condition.
The Risk and Advisory panel shows the current interpretation for an asset.
The time when the current effective state began.
This helps answer:
- Is this a new issue?
- Has this been stable for a while?
- Did the issue begin after a room condition changed?
The candidate state is what the current sensor readings suggest right now.
It may differ from the effective risk state if debounce rules are active.
The primary advisory is the most important message currently available.
If there is no advisory, the panel may show:
- None
- No advisory message
The primary message provides a user-readable explanation of the current advisory.
This may be empty when no advisory is required.
Risk reasons explain what contributed to the current result.
Examples:
- No room light data available
- No room UV data available
- CO₂ 1221.2 above preferred maximum 1201.0
- exposure_sensitivity: moderate
Risk reasons are important because they make the system explainable.
Instead of only showing “Amber” or “Red,” Asset Intelligence tells you why.
Exposure risk focuses on light, UV, sun position, windows, and asset placement.
It may include:
- Exposure level
- Exposure reasons
- Sun azimuth
- Sun elevation
This is especially important for:
- Artwork
- Photographs
- Documents
- Fabrics
- Wood
- Sensitive collectibles
Exposure risk may be limited if Lux or UV sensors are not configured.
Spatial context describes the relationship between the asset and the room.
It may include:
- Facing direction
- Directional match
- Lux
- UV
This helps determine whether the asset’s placement matters.
For example:
An asset facing east near an east-facing window may be more relevant during morning sun exposure than an asset facing away from the window.
Event count shows how many related environment or risk events have been recorded.
This helps indicate whether the asset has a history of risk changes.
Confidence describes how complete or reliable the room environment snapshot is.
Missing sensors may reduce confidence.
Examples:
- Missing Lux sensor
- Missing UV sensor
- Missing air quality data
- Sensor unavailable
- Stale value
Important:
Low confidence does not stop evaluation.
The system still evaluates using available data.
However, missing data may create warnings because the system cannot fully understand the environment.
If the panel shows:
- Candidate state: Green
- Primary advisory: None
- Risk reasons:
- No room light data available
- No room UV data available
- CO₂ 1221.2 above preferred maximum 1201.0
- exposure_sensitivity: moderate
This means:
- The current confirmed state may not be severe.
- The system detected at least one environmental concern.
- Light and UV analysis is incomplete.
- Exposure sensitivity is part of the asset context.
- The user may need better sensor coverage or adjusted limits.
Missing data is not treated as safe.
If a sensor is needed to evaluate an important risk domain, missing data may appear as a warning.
For example:
If an asset is sensitive to light exposure but the room has no Lux or UV sensor configured, the system cannot fully evaluate light risk.
That does not mean the asset is safe from light exposure.
It means the system does not have enough data to fully assess that risk.
The room environment describes what is happening.
The asset profile describes what matters.
The coordinator brings those together.
Example:
Room data:
- Temperature: 69.4 °F
- Humidity: 46.5%
- CO₂: 1241 ppm
- Lux: missing
- UV: missing
Asset context:
- Asset type: Electronics
- Near window: Yes
- Facing direction: East
- Exposure sensitivity: Moderate
- Environment limits configured
Result:
- CO₂ may raise a risk reason.
- Missing Lux and UV may reduce confidence or create warnings.
- Near-window placement may matter for exposure analysis.
- Advisory may recommend improving sensor coverage or reviewing placement.
Risk state may change when:
- Room sensor readings change
- Environment limits are updated
- Asset placement is updated
- Asset type or sensitivity changes
- Sensor mappings are added or removed
- Debounce timing completes
- Missing sensors become available
- A room condition recovers
An advisory may be created when:
- A risk state changes
- A monitored condition exceeds a preferred range
- A required signal is missing
- The room has incomplete sensing
- The asset’s placement increases exposure relevance
- The room may not be suitable for the asset
- A practical recommendation can be made
Advisory messages are meant to be understandable by a user.
They should help answer:
- What happened?
- Why does it matter?
- What should I consider doing?
Asset Intelligence does not:
- Assume missing sensor values
- Fabricate safe conditions
- Automatically move assets
- Automatically change Home Assistant automations
- Treat advisory messages as direct automation commands
- Rely on the UI to calculate risk
The UI displays the result.
The coordinator owns the runtime interpretation.
For better risk and advisory quality:
- Map all available room sensors
- Add Lux and UV sensors where exposure matters
- Configure realistic environment limits
- Use accurate asset placement details
- Mark whether assets are near windows
- Set facing direction when relevant
- Review advisory messages before changing thresholds
- Use debounce settings to avoid noisy state changes
Configure Lux and UV sensors in Room Configuration.
Check Risk Reasons.
Amber may indicate missing data, reduced confidence, or a warning that has not become a Red condition.
Debounce rules may be active.
The system may be waiting before confirming a transition.
No advisory was generated for the current state.
This can be normal when the asset is within limits and no meaningful recommendation is available.
Check:
- Room sensor mapping
- Asset environment limits
- Asset placement
- Facing direction
- Window configuration
- Debounce settings
- Sensor availability in Home Assistant
Risk and Advisory is the intelligence layer of Asset Intelligence.
It combines:
- Room sensing
- Asset requirements
- Placement context
- Sensor confidence
- State transitions
- Advisory reasoning
The goal is not just to say whether something is wrong.
The goal is to explain what matters, why it matters, and what the user may want to do next.