Hello everyone, I wanted to share my recent experience integrating a new Homematic IP motion detector with my existing CCU2 system. While I’ve been very satisfied with my CCU2 setup for years, adding Homematic IP devices has introduced some interesting challenges that I thought others might find helpful to discuss.
Current Setup:
- CCU2 as the central control unit
- Various actors for roller shutter control
- 2x Heating thermostats
- 1x Wall thermostat (mainly for humidity monitoring)
- 1x Motion detector for exterior lighting
New Addition:
- 1x Homematic IP motion detector (HmIP-SMO-A) for terrace security
Goal:
Have the new IP motion detector control the exterior lighting, similar to how my existing non-IP motion detector works. The challenge came when trying to link the new IP motion detector with the lighting actor. Despite several attempts to create programs, nothing seemed to work as expected.
What I Tried:
- Copied the existing program from the non-IP motion detector, replacing the device with the new IP one
- Experimented with different program configurations
Lessons Learned:
- Compatibility Considerations: While Homematic IP devices are designed to work with CCU2, there might be nuances in programing that aren’t immediately obvious
- Documentation Gap: I was surprised to find limited resources specifically addressing CCU2 + Homematic IP integrations
- Community Knowledge: This is where forums like this become invaluable! The collective experience here can often bridge gaps in official documentation
Questions for the Community:- Has anyone successfully integrated Homematic IP motion detectors with CCU2 lighting actors?- Are there specific programing techniques or settings that make this integration smoother?- Any recommendations for troubleshooting program connections between IP and non-IP devices?
I’d be happy to share more details or try out suggested solutions. Let’s keep the knowledge flowing! 