🎛️ iBlinds Device Detection & Management - Full v2 Control + Smart v3 Guidance

Blueprints Exchange
, , , ,
1

:control_knobs: iBlinds Device Detection & Management

Full v2 Control + Smart v3 Guidance

:clipboard: Overview

I’m excited to share a blueprint I’ve developed for managing iBlinds Z-Wave devices in Home Assistant. This blueprint provides intelligent version detection and handles both v2 and v3 devices optimally, and filled a gap when I came over from SmartThings.

:link: GitHub Repository:

:sparkles: Key Features

:dart: Smart Device Detection

  • Automatic Version Recognition: Distinguishes between v2, v3, and other devices using multiple detection methods
  • Multi-Device Support: Manage all your iBlinds devices in a single automation
  • Robust Fallback Logic: Uses model names, manufacturer info, and device capabilities for accurate detection

:gear: iBlinds v2 - Full Automation Control

  • Complete Position Management: Open, close, and set custom positions
  • Direction Reversal: Perfect for different mounting orientations
  • Smart Position Logic: Handles stop-before-position for reliable operation
  • Event-Driven Control: Responds to all cover service calls automatically

:wrench: iBlinds v3 - Intelligent Guidance System

  • Detection Only Approach: Identifies v3 devices but doesn’t interfere with their operation
  • Native Z-Wave Parameter Guidance: Direct links to Z-Wave JS configuration interface
  • Best Practice Recommendations: Guides users to optimal v3 setup via native parameters
  • Configuration Documentation: Built-in explanations of all 10 v3 parameters

:bar_chart: Advanced Reporting & Notifications

  • Flexible Notification System: Persistent notifications, logbook, custom services
  • Comprehensive Device Reports: Detailed analysis of all detected devices
  • v3 Detection Alerts: Automatic reminders about optimal v3 configuration
  • Action Confirmations: Optional notifications for completed operations

:thinking: Why This Approach?

After extensive testing and community feedback, I’ve learned that:

iBlinds v2 devices work best with Home Assistant automation control - they respond well to position commands and integrate seamlessly.

iBlinds v3 devices are optimally configured using their 10 native Z-Wave configuration parameters rather than Home Assistant automations. These parameters provide:

  • More precise control
  • Manufacturer-intended operation
  • Better reliability and performance
  • No conflicts with automation systems

:rocket: Quick Start

Installation

Option 1: Import Directly from the Blueprints Exchange
Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Option 2: GitHub Install

https://github.com/jshessen/home-assistant/blob/main/home-assistant/config/blueprints/automation/jshessen/iblinds_device_handler.yaml

Basic Setup

  1. Go to Settings → Automations & Scenes → Blueprints
  2. Click “Import Blueprint”
  3. Paste the GitHub URL or raw YAML
  4. Create Automation from the blueprint
  5. Select your iBlinds devices (cover entities)
  6. Configure settings as needed
  7. Save & Test

:gear: Configuration Options

Device Selection

  • iBlinds Devices: Multi-select your cover entities (both v2 and v3 supported)

v2 Operation Settings

  • Default Open Position: 0-100% (where devices open to by default)
  • Reverse Direction: Flip direction for different mounting orientations

v3 Configuration Guidance

  • Automatic Detection: Identifies v3 devices automatically
  • Configuration Links: Direct access to Z-Wave JS parameter interface
  • Parameter Documentation: Built-in guide to all 10 v3 parameters

Notification Settings

  • v3 Detection Alerts: Get notified when v3 devices are found
  • Device Reports: Comprehensive analysis of all devices
  • Multiple Methods: Persistent notifications, logbook, custom services

:mag: Device Detection Logic

The blueprint uses sophisticated detection:

  1. Primary: Model name matching (v2, v3, 2.0, 3.0, gen2, gen3)
  2. Manufacturer: HAB/iBlinds/MyiBlinds identification
  3. Capability Fallback: Uses tilt capability to identify v3
  4. Position Fallback: Uses position capability to identify v2

:iphone: Example Configurations

Basic Mixed Environment

# Handles both v2 and v3 devices automatically
iblinds_entities:
  - cover.bedroom_blinds_v2
  - cover.office_blinds_v3
  - cover.living_room_blinds_v2
default_on_value: 75
reverse_direction: false
notify_v3_detection: true

Advanced Setup with Full Reporting

# Comprehensive setup with detailed notifications
iblinds_entities:
  - cover.master_bedroom_blinds
  - cover.guest_room_blinds  
  - cover.kitchen_blinds
default_on_value: 50
reverse_direction: true
notify_v3_detection: true
device_detection_report: true
notification_service_predefined: "persistent_notification.create"

:hammer_and_wrench: Supported Actions

For v2 Devices (Fully Automated)

  • cover.open_cover → Opens to configured default position
  • cover.close_cover → Closes completely (respects direction reversal)
  • cover.set_cover_position → Sets specific position with direction logic

For v3 Devices (Detection + Guidance)

  • Smart Detection → Automatic identification
  • Configuration Guidance → Direct Z-Wave JS links
  • Parameter Documentation → Built-in help for all 10 parameters

:wrench: v3 Configuration Parameters (via Z-Wave JS)

When v3 devices are detected, you’ll get guidance for these parameters:

  1. Close Interval (1-32): Auto calibration tightness
  2. Reverse Direction (0/1): Reverse open/close direction
  3. Default ON Position (1-99): Default open position
  4. Device Reset Disable (0/1): Disable/enable reset button
  5. Speed (0-100): Closing speed in seconds
  6. Remote Calibration (0/1): Trigger recalibration
  7. Min Tilt (0-25): Minimum tilt level limit
  8. Max Tilt (75-99): Maximum tilt level limit
  9. Remap 99 (0/1): Remap ON command behavior
  10. Override Response to ON Command (0/1): Use default instead of 99

:bug: Troubleshooting

Common Issues & Solutions

Q: My v2 blinds move in the wrong direction
A: Enable “Reverse Direction” in the v2 settings section

Q: v3 devices aren’t being controlled
A: This is expected! Configure v3 devices via Z-Wave JS native parameters for optimal performance

Q: Device not detected as iBlinds
A: Check if manufacturer contains “HAB” or model contains version numbers. Enable “Device Detection Report” for detailed analysis.

Q: Getting too many notifications
A: Disable “Device Detection Report” and keep only “v3 Detection Notifications” enabled

Q: Blueprint not triggering
A: Ensure your devices are cover entities with device_class: blind

:handshake: Community Feedback Welcome!

This blueprint has been tested with various iBlinds configurations, but I’d love to hear about your experiences:

  • Different device models/versions
  • Unique mounting configurations
  • Integration challenges
  • Feature requests

Please share your device_detection_report output if you encounter issues - it helps with troubleshooting!

:books: Additional Resources

:tada: Success Stories

Share your experiences with this blueprint below!

Tags: #blueprints #iblinds #zwave #cover #automation #blinds #window-coverings

Hope this helps the community! Let me know if you have any questions or suggestions for improvements. :house::sparkles: