node-red-contrib-ccu - GitLite

KO | EN

gitlite — search

#hacktoberfest #go #android #rust #deep-learning #java #awesome #kubernetes #awesome-list #security #ios #mcp #openai #open-source

node-red-contrib-ccu

(★ 69)

Node-RED Nodes for the Homematic CCU

파일 탐색기

최종 버전 다운로드 (.zip)

- - nodejs.yml
- no-response.yml
- ccu-config-debmatic.png
- ccu-config-docker.png
- ccu-config-pivccu.png
- schema-debmatic.png
- schema-docker.png
- schema-multiCCU.drawio
- schema-multiCCU.png
- schema-pivccu.png
- - ccu.png
- - status.js
- ccu-alexa.html
- ccu-alexa.js
- ccu-connection.html
- ccu-connection.js
- ccu-display.html
- ccu-display.js
- ccu-get-value.html
- ccu-get-value.js
- ccu-mqtt.html
- ccu-mqtt.js
- ccu-poll.html
- ccu-poll.js
- ccu-program.html
- ccu-program.js
- ccu-rpc-event.html
- ccu-rpc-event.js
- ccu-rpc.html
- ccu-rpc.js
- ccu-script.html
- ccu-script.js
- ccu-set-value.html
- ccu-set-value.js
- ccu-signal.html
- ccu-signal.js
- ccu-switch.html
- ccu-switch.js
- ccu-sysvar.html
- ccu-sysvar.js
- ccu-value.html
- ccu-value.js
- - .gitignore
- - channels.json
  - devices.json
  - functions.json
  - programs.json
  - rooms.json
  - variables.json
- context_spec.js
- regahss_spec.js
- rpc_spec.js
- utils.js
- get-channels-working.js
- paramsets-join.js
.editorconfig
.gitignore
.npmignore
.travis.yml
AGENTS.md
LICENSE
package-lock.json
package.json
paramsets.json
README.md
TODO.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/rdmtc/node-red-contrib-ccu

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd node-red-contrib-ccu

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Node.js

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Node.js npm 명령어를 쓰려면 Node.js가 설치되어 있어야 합니다. LTS(장기지원) 버전을 추천합니다.

npm install

package.json에 명시된 라이브러리들을 내려받아 설치합니다.

npm start

개발/실행 서버를 켭니다.

✅ 명령어 실행 후 터미널에 나타나는 주소(보통 http://localhost:3000 형태)를 브라우저에서 열어보세요.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# node-red-contrib-ccu

[![NPM version](https://badge.fury.io/js/node-red-contrib-ccu.svg)](http://badge.fury.io/js/node-red-contrib-ccu)
[![Dependencies Status](https://david-dm.org/rdmtc/node-red-contrib-ccu/status.svg)](https://david-dm.org/rdmtc/node-red-contrib-ccu)
[![Build Status](https://travis-ci.org/rdmtc/node-red-contrib-ccu.svg?branch=master)](https://travis-ci.org/rdmtc/node-red-contrib-ccu)
[![Coverage Status](https://coveralls.io/repos/github/rdmtc/node-red-contrib-ccu/badge.svg?branch=master)](https://coveralls.io/github/rdmtc/node-red-contrib-ccu?branch=master)
[![XO code style](https://img.shields.io/badge/code_style-XO-5ed9c7.svg)](https://github.com/sindresorhus/xo)
[![License][mit-badge]][mit-url]

> Node-RED Nodes for the Homematic CCU

With these Nodes you can connect [Homematic](https://github.com/hobbyquaker/awesome-homematic) and 
[Node-RED](https://nodered.org/). Homematic is a series of smart home automation hardware from the manufacturer 
[eQ-3](http://www.eq-3.de/), popular especially in Germany.

**⚠️ node-red-contrib-ccu >= 3.0 needs Node-RED >= 1.0.** If you're still on Node-RED 0.20 or lower you should use the 
latest 2.x version of node-red-contrib-ccu.

For the communication with the CCU both RPC and ReGaHSS remote script are used. It's possible to connect to multiple 
CCUs from one Node-RED instance. RPC setValue calls can be comfortably complemented with ON_TIME and RAMP_TIME values
and special nodes ease the control of displays and mp3 actuators. RPC events can be filtered comprehensively (even 
through regular expressions and also by rooms and functions). It's possible to start rega-programs and set 
rega-variables and last but not least there are nodes to execute arbitrary rega-scripts and RPC calls.

These nodes are included in [RedMatic](https://github.com/rdmtc/RedMatic) which ships Node-RED as an addon package 
for installation on a Homematic CCU3 or RaspberryMatic.

Some example flows can be found in the [RedMatic Wiki](https://github.com/rdmtc/RedMatic/wiki) (German language).

__A modern Browser is required, Internet Explorer won't work.__

__Starting with Version 3.x these Nodes need Node-RED >= 1.0 to work correctly__

## Configuration Examples

The communication with the Homematic CCU needs independent connections in two directions. Node-red-contrib-ccu connects to the CCU's interface listeners (e.g. 2001/TCP for BidCos-RF) while the CCU connects to node-red-contrib-ccu's BINRPC/XMLRPC listeners (2048/tcp and 2049/tcp in examples below).

### NAT'd network

If Node-RED/node-red-contrib-ccu runs inside a Container or a VM with NAT'd network it's necessary to forward/expose the ports for connections _from_ the CCU _to_ node-red-contrib-ccu's callback listeners (example below for a Docker container: use options `-p 2048:2048 -p 2049:2049`in the docker run command).

![schema-docker](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/schema-docker.png)

![ccu-config-docker](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/ccu-config-docker.png)

The config option `Init address`will be used to tell the CCU on which Address node-red-contrib-ccu is reachable. As 172.17.0.20 is not reachable for the CCU the Hosts IP Address and port forwarding/exposal has to be used. As `Listen address` setting also `0.0.0.0` (which tells node-red-contrib-ccu to bind it's listeners to all available interfaces) would be possible.

### piVCCU

This example shows a configuration for piVCCU and Node-RED running in containers with bridged networking.

![schema-pivccu](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/schema-pivccu.png)

![ccu-config-pivccu](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/ccu-config-pivccu.png)

### debmatic

In this example both Node-RED and debmatic are installed on the same (possibly virtual) host.

![schema-debmatic](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/schema-debmatic.png)

![ccu-config-debmatic](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/ccu-config-debmatic.png)

### Multiple CCUs

With the same logic as shown above, multiple CCUs can be managed within one Node-RED instance.
This will require two individual configuration nodes, in which the respective connection setting are provided.

![schema-multiCCU](https://raw.githubusercontent.com/rdmtc/node-red-contrib-ccu/master/docs/schema-multiCCU.png)

- `Listen address` typically is the same for both Configurations as it is determined by the host that is running Node-RED
 - `BINRPC listening port` and `XMLRPC listening port` need to be different across the two configurations. One configuration can use the defaults (2048/tcp and 2049/tcp), the other needs to use two new ports. node-red-contrib-ccu will make a proposal, but this can be modified, e.g. if the proposed ports are already used.
 - The examples for [NAT'd network](#NAT'd-network), [piVCCU](#piVCCU) and [debmatic](#debmatic) will apply likewise for multiple CCUs. This means, for running Node-RED within a docker, all BINRPC and XMLRPC ports must be forwarded, e.g. `-p 2048:2048 -p 2049:2049 -p 2061:2061 -p 2062:2062`

## License

MIT (c) Sebastian Raff and node-red-contrib-ccu contributors

[mit-badge]: https://img.shields.io/badge/License-MIT-blue.svg?style=flat
[mit-url]: LICENSE