WBE2-I-KNX KNX Extension Module/en: различия между версиями
(Новая страница: «== Working via MQTT ==») |
FuzzyBot (обсуждение | вклад) м (FuzzyBot переименовал страницу KNX Module for WB6 (WBE2-I-KNX)/en в WBE2-I-KNX KNX Extension Module/en без оставления перенаправления: Часть переводимой страницы KNX Module for WB6 (WBE2-I-KNX).) Метки: правка с мобильного устройства правка из мобильной версии |
||
(не показано 30 промежуточных версий 1 участника) | |||
Строка 55: | Строка 55: | ||
== Working via MQTT == | == Working via MQTT == | ||
Go to the console and install the packages [https://contactless.ru/wiki/index.php/MQTT_KNX_Bridge wb-mqtt-knx (MQTT KNX Bridge)], knxd, knxd-tools: | |||
'''apt-get update''' | '''apt-get update''' | ||
Строка 61: | Строка 61: | ||
'''apt-get install knxd knxd-tools wb-mqtt-knx''' | '''apt-get install knxd knxd-tools wb-mqtt-knx''' | ||
After installation, you must edit the file '''/etc/default/knxd''': | |||
Replace the line: | |||
DAEMON_ARGS="-u /tmp/eib -u /var/run/knx -i -b ip:" | DAEMON_ARGS="-u /tmp/eib -u /var/run/knx -i -b ip:" | ||
with: | |||
'''DAEMON_ARGS="-d /var/log/knxd.log -t 0xffe -f 9 -e 1.2.255 -E 1.1.10:30 -u /var/run/knx -i -b ncn5120:/dev/ttyMOD1 -D -T -R -S"''' | '''DAEMON_ARGS="-d /var/log/knxd.log -t 0xffe -f 9 -e 1.2.255 -E 1.1.10:30 -u /var/run/knx -i -b ncn5120:/dev/ttyMOD1 -D -T -R -S"''' | ||
Строка 72: | Строка 72: | ||
On WB6, with the new firmware version to run knxd correctly, you need to fix 2 files: | |||
/etc/knxd.conf - | /etc/knxd.conf - replace the second line with: | ||
KNXD_OPTS="-t 0xffe -f 9 -e 1.1.255 -E 1.1.10:30 -b ncn5120:/dev/ttyMOD1 -D -T -R -S" | KNXD_OPTS="-t 0xffe -f 9 -e 1.1.255 -E 1.1.10:30 -b ncn5120:/dev/ttyMOD1 -D -T -R -S" | ||
/lib/systemd/system/knxd.service - | /lib/systemd/system/knxd.service - comment User and Group (write # as shown below) or remove these lines: | ||
#User=knxd | #User=knxd | ||
#Group=knxd | #Group=knxd | ||
after that, you should reboot the controller and everything should work | |||
Decrypting keys: | |||
{| class="wikitable" | {| class="wikitable" | ||
! | !Key | ||
! | !Function | ||
|- | |- | ||
| -d /var/log/knxd.log | | -d /var/log/knxd.log | ||
| | | to go into the background mode and write to a log. | ||
|- | |- | ||
| -e 1.1.255 | | -e 1.1.255 | ||
| | |assigns KNX-address knxd equal 1.1.255 as the IP gateway. | ||
|- | |- | ||
| -E 1.1.10:30 | | -E 1.1.10:30 | ||
| | |specifies knxd to issue KNX addresses to nodes from an IP network in the range of 1.1.10..1.1.30 | ||
|- | |- | ||
| -u /var/run/knx | | -u /var/run/knx | ||
| | |opens local Unix-socket | ||
|- | |- | ||
| -t 0xffe | | -t 0xffe | ||
| | |set the output mask of debug messages. | ||
|- | |- | ||
| -f 9 | | -f 9 | ||
| | |set max verbosity level | ||
|- | |- | ||
| -i | | -i | ||
| | |specify listen to TCP-port (default 6720). It is possible to register -i 6721 or other port. Not exclusive alternative -u | ||
|- | |- | ||
| -b ncn5120:/dev/ttyMOD1 | | -b ncn5120:/dev/ttyMOD1 | ||
| | |activate ncn5120 driver for port MOD1 (when installing the module into the extension slot MOD 2 it should be noted ttyMOD2) | ||
|- | |- | ||
| -T -R | | -T -R | ||
| | |activate the gateway, tunnel mode (you need to work with ETS) | ||
|- | |- | ||
| -D | | -D | ||
| | |says knxd to announce themselves (Discovery) in the network | ||
|- | |- | ||
| -S | | -S | ||
| | |run the server (which responds to multicasts) | ||
|} | |} | ||
More detailed: | |||
knxd --help | knxd --help | ||
== | == Operation == | ||
To start KNX daemon, you need to write a line in the console: | |||
'''service knxd start''' | '''service knxd start''' | ||
Restart if necessary: | |||
'''service knxd restart''' | '''service knxd restart''' | ||
To check the status: | |||
'''service knxd status''' | '''service knxd status''' | ||
All logs are stored in the file '''/var/log/knxd.log''' | |||
When you receive a message from the KNX device, the data is published to the MQTT topic '''/devices/knx/controls/data''' in Wiren Board 6. | |||
To control KNX devices you need to send commands to MQTT topic '''/devices/knx/controls/data/on'''. | |||
An example of a command: | |||
mosquitto_pub -h 192.168.0.10 -p 1883 -t /devices/knx/controls/data/on -m "g:0/0/1 GroupValueWrite 0x01" | mosquitto_pub -h 192.168.0.10 -p 1883 -t /devices/knx/controls/data/on -m "g:0/0/1 GroupValueWrite 0x01" | ||
Where: | |||
-h 192.168.0.10 - IP- | -h 192.168.0.10 - IP-address of the controller with KNX | ||
-p 1883 - | -p 1883 - MQTT port | ||
-t /devices/knx/controls/data/on - MQTT | -t /devices/knx/controls/data/on - MQTT topic for uploading information | ||
-m "g:0/0/1 GroupValueWrite 0x01" - | -m "g:0/0/1 GroupValueWrite 0x01" - message for a KNX device | ||
Learn more about working with KNX data:[https://contactless.ru/wiki/index.php/MQTT_KNX_Bridge wb-mqtt-knx (MQTT KNX Bridge)] | |||
Script for [https://contactless.ru/wiki/index.php/%D0%94%D0%B2%D0%B8%D0%B6%D0%BE%D0%BA_%D0%BF%D1%80%D0%B0%D0%B2%D0%B8%D0%BB_wb-rules wb-rules] упрощающий обработку телеграмм: [https://gist.github.com/Yanni66/bc7604bb8646d52c9c864b4ca40c63b6 knx_group_addresses.js] | |||
When working with ETS, it's '''Important''': in “interfaces” ETS, it's necessary to choose the interface of the PC through which communication occurs. Requesting knxd b by unicast (host ip address with daemon) does not allow to program the devices. In the illustration, the arrow indicates which method of interaction with ETS works: | |||
[[Файл:EtsInterface.png|500px| | [[Файл:EtsInterface.png|500px|EST Interface]] | ||
Also, if you are a user of Windows 8, 10, we advise you to disable antivirus and firewall, as they can interfere with the work of ETS. |
Текущая версия на 15:25, 22 апреля 2021
Pinout
Terminal | Function |
---|---|
O1 (Red) | KNX (+) |
O2 (n/a) | n/a |
O3 (Gray) | KNX (-) |
Configuration
You need to set the module type in the web interface, sectionConfigs => Hardware Modules Configuration: for Internal slot 1 (MOD1) or for Internal slot 2 (MOD2) depending on the KNX module position.
Working via iRidium Server
Download the latest version of the installation of a deb package signed the iRidium server for Raspbian Jessie with the PIXEL 0 and WB (gen 6) here iRidium Pro downloads
copy the file to the controller (detailed description of how to copy files to the controller) and install it by running the command
dpkg -i iridiumserver_1.3.0-15590_RPI.deb
Go to the iRidium Server web interface via the link your_wirenboard_address:8888 and log in to the server.
Next, when you create the project, add the KNX Serial (UMC) driver and configure it as shown below
use /dev/ttyMOD2 if the module is installed in the second extension slot
Working via MQTT
Go to the console and install the packages wb-mqtt-knx (MQTT KNX Bridge), knxd, knxd-tools:
apt-get update
apt-get install knxd knxd-tools wb-mqtt-knx
After installation, you must edit the file /etc/default/knxd:
Replace the line:
DAEMON_ARGS="-u /tmp/eib -u /var/run/knx -i -b ip:" with:
DAEMON_ARGS="-d /var/log/knxd.log -t 0xffe -f 9 -e 1.2.255 -E 1.1.10:30 -u /var/run/knx -i -b ncn5120:/dev/ttyMOD1 -D -T -R -S"
On WB6, with the new firmware version to run knxd correctly, you need to fix 2 files:
/etc/knxd.conf - replace the second line with: KNXD_OPTS="-t 0xffe -f 9 -e 1.1.255 -E 1.1.10:30 -b ncn5120:/dev/ttyMOD1 -D -T -R -S"
/lib/systemd/system/knxd.service - comment User and Group (write # as shown below) or remove these lines:
- User=knxd
- Group=knxd
after that, you should reboot the controller and everything should work
Decrypting keys:
Key | Function |
---|---|
-d /var/log/knxd.log | to go into the background mode and write to a log. |
-e 1.1.255 | assigns KNX-address knxd equal 1.1.255 as the IP gateway. |
-E 1.1.10:30 | specifies knxd to issue KNX addresses to nodes from an IP network in the range of 1.1.10..1.1.30 |
-u /var/run/knx | opens local Unix-socket |
-t 0xffe | set the output mask of debug messages. |
-f 9 | set max verbosity level |
-i | specify listen to TCP-port (default 6720). It is possible to register -i 6721 or other port. Not exclusive alternative -u |
-b ncn5120:/dev/ttyMOD1 | activate ncn5120 driver for port MOD1 (when installing the module into the extension slot MOD 2 it should be noted ttyMOD2) |
-T -R | activate the gateway, tunnel mode (you need to work with ETS) |
-D | says knxd to announce themselves (Discovery) in the network |
-S | run the server (which responds to multicasts) |
More detailed:
knxd --help
Operation
To start KNX daemon, you need to write a line in the console: service knxd start
Restart if necessary: service knxd restart
To check the status: service knxd status
All logs are stored in the file /var/log/knxd.log
When you receive a message from the KNX device, the data is published to the MQTT topic /devices/knx/controls/data in Wiren Board 6.
To control KNX devices you need to send commands to MQTT topic /devices/knx/controls/data/on.
An example of a command:
mosquitto_pub -h 192.168.0.10 -p 1883 -t /devices/knx/controls/data/on -m "g:0/0/1 GroupValueWrite 0x01"
Where:
-h 192.168.0.10 - IP-address of the controller with KNX
-p 1883 - MQTT port
-t /devices/knx/controls/data/on - MQTT topic for uploading information
-m "g:0/0/1 GroupValueWrite 0x01" - message for a KNX device
Learn more about working with KNX data:wb-mqtt-knx (MQTT KNX Bridge)
Script for wb-rules упрощающий обработку телеграмм: knx_group_addresses.js
When working with ETS, it's Important: in “interfaces” ETS, it's necessary to choose the interface of the PC through which communication occurs. Requesting knxd b by unicast (host ip address with daemon) does not allow to program the devices. In the illustration, the arrow indicates which method of interaction with ETS works:
Also, if you are a user of Windows 8, 10, we advise you to disable antivirus and firewall, as they can interfere with the work of ETS.