# Protection & Safety Properties

Properties for device protection, temperature monitoring, access control, and overheat safety features via Zigbee2MQTT.

## Temperature Monitoring (Read-Only)

### internalTemperature

- **Type**: Sensor (read-only)
- **Range**: 0-127°C
- **Unit**: Degrees Celsius (°C)
- **Description**: The temperature measured by the temperature sensor inside the chip, in degrees Celsius.
- **Home Assistant Entity**: `sensor.[device_name]_internal_temperature`
- **Read-only**: Cannot be changed by user, reports actual temperature
- **Use cases**:
  - Monitor switch health
  - Detect overheating conditions
  - Trigger cooling automations
  - Diagnostic information
- **Normal range**: Typically 30-50°C during operation
- **Warning signs**:
  - Above 60°C: High temperature, check ventilation
  - Above 70°C: Overheat protection may activate

### overheat

- **Type**: Sensor (read-only)
- **Values**: "No Alert", "Overheated"
- **Description**: Indicates if the internal chipset is currently in an overheated state.
- **Home Assistant Entity**: `sensor.[device_name]_overheat`
- **Read-only**: Cannot be changed by user, reports protection status
- **Use cases**:
  - Safety monitoring
  - Alert when switch is overheating
  - Diagnostic for load issues
  - Automation triggers for problems
- **Behavior when "Overheated"**:
  - Switch may reduce output or shut off load
  - LED may indicate error state
  - Switch protects itself from damage
- **Recovery**: Automatically resets when temperature drops to safe level
- **Causes**:
  - Excessive load (too many bulbs/watts)
  - Poor ventilation (box too small, insulation)
  - High ambient temperature
  - Short circuit or wiring issues

## Access Control

### localProtection

- **Type**: Select
- **Values**: "Disabled", "Enabled"
- **Default**: "Disabled"
- **Description**: Ability to control switch from the wall. When enabled, disables physical paddle control.
- **Home Assistant Entity**: `select.[device_name]_local_protection`
- **Use cases**:
  - Child safety locks
  - Prevent accidental changes
  - Commercial applications
  - Force automation-only control
- **Behavior when "Enabled"**:
  - Paddle presses do nothing
  - Zigbee commands still work
  - Switch can only be controlled via hub/automations
  - LED effects still respond to paddle (visual feedback)
- **Override**: Can be disabled via Zigbee command from hub
- **Note**: Does not affect config button or air-gap switch

### remoteProtection

- **Type**: Sensor (read-only via Zigbee2MQTT)
- **Values**: "Disabled", "Enabled"
- **Default**: "Disabled"
- **Description**: Ability to control switch from the hub.
- **Home Assistant Entity**: `sensor.[device_name]_remote_protection`
- **Read-only via Zigbee2MQTT**: Status can be read but not changed remotely
- **Use cases**:
  - Prevent automation interference
  - Local control only mode
  - Troubleshooting automation issues
- **Behavior when "Enabled"**:
  - Paddle works normally
  - Zigbee on/off/dim commands ignored
  - Configuration commands may still be accepted
  - Switch operates as manual-only dimmer

## Configuration Patterns

### Standard Operation (No Protection)

```yaml
service: select.select_option
target:
  entity_id: select.bedroom_switch_local_protection
data:
  option: "Disabled"
```

### Child Lock (Paddle Disabled)

```yaml
service: select.select_option
target:
  entity_id: select.bedroom_switch_local_protection
data:
  option: "Enabled"
```

### Temperature Monitoring Automation

```yaml
automation:
  - alias: "Inovelli Overheat Alert"
    trigger:
      - platform: numeric_state
        entity_id: sensor.bedroom_switch_internal_temperature
        above: 60
    action:
      - service: notify.mobile_app
        data:
          message: "Bedroom switch overheating: {{ states('sensor.bedroom_switch_internal_temperature') }}°C"

  - alias: "Inovelli Overheat Protection Triggered"
    trigger:
      - platform: state
        entity_id: sensor.bedroom_switch_overheat
        to: "Overheated"
    action:
      - service: notify.mobile_app
        data:
          message: "ALERT: Bedroom switch overheat protection activated!"
          title: "Switch Overheat"
      - service: light.turn_off
        entity_id: light.bedroom_switch
```

## Safety Considerations

### Overheat Protection
The switch has built-in thermal protection that cannot be disabled:
- Monitors internal temperature continuously
- Automatically reduces output if too hot
- Protects switch from permanent damage
- Resets automatically when cooled

### Common Causes of Overheating
1. **Overloaded circuit**: Too many bulbs/high wattage
2. **Poor ventilation**: Tight gang box, spray foam insulation
3. **Non-neutral wiring**: Generates more heat
4. **Ambient temperature**: Hot attic/outdoor locations
5. **Electrical issues**: Poor connections, high resistance

### Prevention
- Don't exceed rated wattage (typically 150W LED, 300W incandescent)
- Ensure adequate box size and ventilation
- Use fan/cooling for hot environments
- Regular temperature monitoring via automations
- Quality bulbs that don't overdraw current

### Emergency Procedures
If overheat protection triggers:
1. Check overheat sensor status
2. Read internalTemperature value
3. Turn off load via Zigbee if possible
4. Allow switch to cool (15-30 minutes)
5. Investigate cause before restoring power
6. Reduce load or improve ventilation

## Protection Use Cases

### Vacation Mode Child Lock
```yaml
# Before leaving, disable paddle
service: select.select_option
target:
  entity_id: select.bedroom_switch_local_protection
data:
  option: "Enabled"

# Configure automations for lighting schedule
```

### Critical Lighting Protection
```yaml
# For always-on circuits (security, safety)
service: select.select_option
target:
  entity_id: select.bedroom_switch_local_protection
data:
  option: "Enabled"
```

### Commercial Installation
```yaml
# Public spaces - prevent tampering
service: select.select_option
target:
  entity_id: select.bedroom_switch_local_protection
data:
  option: "Enabled"
```

## Important Notes

- localProtection can be changed remotely via Zigbee2MQTT
- remoteProtection is read-only via Zigbee2MQTT
- Physical config button can reset protections if needed
- Air-gap switch always works regardless of protection settings
- Overheat protection is hardware-based and cannot be disabled
- Temperature monitoring via internalTemperature sensor
- Local + Remote protection together creates fully locked state (not recommended)
- Temperature readings update based on reporting configuration