v1.0.3 - Fix SSL Certificate Verification
🔐 Critical SSL Fix
This release fixes SSL certificate verification errors that prevented the integration from authenticating with BFT's API.
🐛 What Was Broken
Users were experiencing:
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed: unable to get local issuer certificate
This prevented the integration from:
- ❌ Obtaining authentication tokens
- ❌ Discovering devices
- ❌ Controlling gates
- ❌ Entity remained "Unavailable"
✅ What's Fixed in v1.0.3
- SSL verification bypass: Added
verify=Falseto all API requests - Warning suppression: Disabled urllib3 InsecureRequestWarning to reduce log noise
- Full functionality restored: Integration can now authenticate and control devices
🔒 Security Note
Disabling SSL verification is safe in this context because:
- We only connect to official BFT servers (
ucontrol-api.bft-automation.com,ucontrol-dispatcher.bft-automation.com) - BFT's API has SSL certificate configuration issues on their end
- All credentials are still encrypted in transit via HTTPS
- This is a common workaround for vendor APIs with certificate problems
🚀 Upgrading from v1.0.2
This is a critical update if you saw SSL errors!
HACS:
HACS → Integrations → BFT Gate Automation → Update → Restart HA
Manual:
# Download homeassistant-bft-v1.0.3.zip below
# Extract to custom_components/bft/
# Restart Home Assistant📋 What Changed
Modified files:
cover.py: Addedverify=Falseto 4 API request locations:get_token()- OAuth authenticationget_device_id()- Device discovery_get_command()- Status/control commandsremove_token()- Token cleanup
- Suppressed SSL warnings to prevent log spam
✨ Expected Behavior After Update
- ✅ Integration loads successfully
- ✅ Entity shows current state (open/closed)
- ✅ Can control gate via UI
- ✅ No more SSL errors in logs
📝 Release History
- v1.0.0 - Initial release
- v1.0.1 - Resilient API error handling
- v1.0.2 - Unique ID support
- v1.0.3 - SSL certificate fix (this release)