Homematic Integration with Node Red and MQTT: A Winter Project Update

As the winter sets in, I find myself diving deeper into my smart home setup. I’ve been experimenting with Homematic for a while now, primarily using CCU2 to manage my switches, motion detectors, and actuators. The addition of Wemos 8266 devices has been a game-changer, especially for my garden automation. With MQTT and ioBroker running on a Raspberry Pi, I’ve managed to create a simple yet functional system that integrates sensors like temperature and humidity, along with some basic actuator controls. The ioBroker VIS interface has been a great way to visualize everything on my smartphone, though I know there’s so much more I can do.

Recently, I stumbled upon Node Red and have been blown away by its potential. Integrating it with ioBroker has opened up a whole new world of possibilities. My goal this winter is to expand my setup significantly. I want to implement routines like “All Lights Off” and simulate presence to make the house feel lived-in even when we’re away. To achieve this, I plan to replace my current Raspberry Pi with a more powerful Intel NUC, which will serve as the backbone of my smart home ecosystem.

I’ve been considering two main approaches:

  1. Option 1: Keep the CCU2 solely for learning and managing Homematic devices, while moving all logic and automation to Node Red on the NUC. This setup would leverage ioBroker VIS for the interface.
  2. Option 2: Upgrade to CCU3 with RedMatic and MQTT, using it exclusively for device learning and management, while handling all automation through Node Red. This would utilize Node Red’s built-in dashboard for visualization.

Both options seem viable, but I’m leaning towards Option 2 for its streamlined approach and the flexibility of Node Red. I’d love to hear others’ experiences with similar setups and any tips they might have for a smooth transition. The idea of consolidating everything into a single, robust environment is incredibly appealing, and I’m excited to see how this evolves over the next few months.

If anyone has advice on avoiding multiple learning curves or has tried a similar integration, I’d be grateful for your insights! Happy tinkering everyone! :rocket: