Hi everyone,
I’ve been working on a Homey integration for Hitachi air conditioners using the AirCloud Go API.
The goal was to bring more reliable and unified control of multiple units directly into Homey, without relying on fragmented manufacturer apps.
The app currently provides:
- Connection to Hitachi AirCloud Go API
- Retrieval of all air conditioning units
- Real-time device state monitoring
- WebSocket-based live updates
- Automatic reconnection when connection drops
- HTTP fallback system for reliability
This ensures the system keeps working even when the real-time channel becomes unstable.
The integration is built around a dual-layer communication system:
- WebSocket for real-time updates
- HTTP fallback for state recovery
- Session/token lifecycle handling
- State synchronization between both layers
The main challenge was ensuring consistency between real-time updates and fallback polling without duplicating or desynchronizing device states.
I’ve documented the project, architecture, and real-world use case here:
Feedback, ideas or improvements are very welcome, especially from people working on Homey integrations or cloud-based devices.
