dalicontrol-e64 0.2.0__tar.gz → 0.2.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (17) hide show
  1. {dalicontrol_e64-0.2.0/src/dalicontrol_e64.egg-info → dalicontrol_e64-0.2.2}/PKG-INFO +54 -24
  2. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/README.md +53 -23
  3. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/pyproject.toml +1 -1
  4. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/__init__.py +1 -1
  5. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2/src/dalicontrol_e64.egg-info}/PKG-INFO +54 -24
  6. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/LICENSE +0 -0
  7. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/setup.cfg +0 -0
  8. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/commands.py +0 -0
  9. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/http.py +0 -0
  10. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/knx.py +0 -0
  11. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/writer.py +0 -0
  12. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64.egg-info/SOURCES.txt +0 -0
  13. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64.egg-info/dependency_links.txt +0 -0
  14. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64.egg-info/requires.txt +0 -0
  15. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64.egg-info/top_level.txt +0 -0
  16. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/tests/test_commands.py +0 -0
  17. {dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/tests/test_writer.py +0 -0
{dalicontrol_e64-0.2.0/src/dalicontrol_e64.egg-info → dalicontrol_e64-0.2.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: dalicontrol-e64
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Unofficial protocol notes and Python tools for the IPAS DaliControl e64 KNX/DALI gateway
5
5
  Author: NashEQify
6
6
  License-Expression: MIT
@@ -21,32 +21,54 @@ Dynamic: license-file
21
21
 
22
22
  # dalicontrol-e64
23
23
 
24
- Unofficial protocol notes, field experience and a small Python library for the
25
- **IPAS DaliControl e64** KNX/DALI gateway.
24
+ Use and program the DALI lights behind an **IPAS DaliControl e64** KNX/DALI
25
+ gateway from any home automation system or script, without ETS and without
26
+ the DCA (IPAS' Device Configuration App plug-in for ETS). Unofficial protocol
27
+ notes, field experience, a Python library and a Home Assistant integration.
28
+
29
+ ## Why
30
+
31
+ - **No ETS, no DCA, no licence.** Switching, dimming, group assignment,
32
+ storing and recalling scenes, even a DALI new installation: all of it works
33
+ over plain HTTP (a browser, curl, Python) or over KNX with a free library
34
+ such as [xknx](https://github.com/XKNX/xknx).
35
+ - **Any home automation system.** Home Assistant (integration in this repo,
36
+ or a few lines of YAML), Node-RED, openHAB, ioBroker, a shell script. The
37
+ request is one HTTP GET.
38
+ - **Colour wheels for RGBW LED strips.** A strip is four DALI channels; the
39
+ Home Assistant integration turns each into one colour light with the normal
40
+ colour wheel, white slider and brightness. Pick a colour on a wall tablet
41
+ and the strip follows.
42
+ - **Fast and stable on old hardware.** The approach here drives a flat with
43
+ 38 DALI ballasts every day and has for months: scene changes and dimming
44
+ react immediately, nothing needs restarting. That was not expected from a
45
+ gateway of this age on its original firmware; it took a lot of testing to
46
+ find what makes it quick (scenes instead of many single writes, one queue,
47
+ no blind retries; see [lessons-learned.md](docs/lessons-learned.md)).
48
+ - **No firmware update needed.** Everything here runs on firmware 1.3_06. An
49
+ update to 3.x destroyed the KNX side of a second gateway in the same
50
+ installation; manufacturer support could neither update the other one nor
51
+ downgrade the broken one in a remote session. Staying on 1.x is a choice,
52
+ and this repository is what makes it workable.
26
53
 
27
54
  The gateway is usually commissioned once with ETS and then only reached
28
- through KNX group addresses. It can do more: its built-in web page uses a plain
29
- HTTP interface, and the same commands can be sent over KNX without any ETS
30
- change. Neither is documented by the manufacturer. This repository writes down
31
- what was found while building a lighting control for a flat with 38 DALI
32
- ballasts, including the parts that went wrong.
33
-
34
- Use it with or without a home automation system.
35
-
36
- ## No ETS, no DCA, no KNX software
37
-
38
- For working with the DALI side you do not need ETS, the DCA plug-in, an ETS
39
- licence or any other KNX vendor software. Switching and dimming channels,
40
- assigning groups, storing and recalling scenes and starting a DALI new
41
- installation all work with this repository alone: over HTTP with a browser,
42
- curl or Python, or over KNX with a free KNXnet/IP library such as
43
- [xknx](https://github.com/XKNX/xknx).
55
+ through KNX group addresses. Its built-in web page, however, uses a plain HTTP
56
+ interface, and the same commands can be sent over KNX as device management
57
+ telegrams, without any ETS change. Neither is documented by the manufacturer.
58
+ This repository writes both down, including the parts that went wrong.
44
59
 
45
60
  ETS is only needed for the KNX side of the gateway: its individual address,
46
61
  group objects and KNX application parameters. If the gateway was commissioned
47
62
  once, you can leave that untouched. If you only use the HTTP interface, the
48
63
  KNX side does not matter at all.
49
64
 
65
+ For that KNX side there is an open-source alternative to ETS as well:
66
+ [bussard](https://github.com/tmbo/bussard), a command-line tool that keeps the
67
+ KNX configuration in text files and writes it to the devices. Check its device
68
+ list for your gateway's application version before relying on it.
69
+
70
+ Reading this with an LLM or coding agent: start with [llms.txt](llms.txt).
71
+
50
72
  > **Tested on one device type and firmware only:** DaliControl e64, firmware
51
73
  > 1.3_06, ETS application e64-01-0110. Not affiliated with or endorsed by
52
74
  > IPAS. Several commands re-address or reconfigure your installation and have
@@ -63,7 +85,7 @@ KNX side does not matter at all.
63
85
  | [docs/lessons-learned.md](docs/lessons-learned.md) | What failed and what replaced it |
64
86
  | [docs/home-automation.md](docs/home-automation.md) | Home Assistant, Node-RED, openHAB, ioBroker: from one HTTP request to a full integration |
65
87
  | `src/dalicontrol_e64/` | Python library on PyPI: command encoding with an allowlist, HTTP client, KNX transport, request queue |
66
- | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, scene recall, all on/off, HTTP or KNX |
88
+ | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, RGBW strips with colour wheel, scene recall, all on/off, HTTP or KNX |
67
89
 
68
90
  ## Five things to know first
69
91
 
@@ -153,11 +175,19 @@ python3 -m pytest # Home Assistan
153
175
  The tests run against a simulated device. They prove the encoding, the
154
176
  allowlist and the queue logic, not the behaviour of your hardware.
155
177
 
156
- ## Contributing
178
+ ## Status and contributing
179
+
180
+ Finished for the installation it was written for: it has run stable and fast
181
+ there for months, so it will not be developed further from that side. Pull
182
+ requests are welcome, for example:
183
+
184
+ - other firmware versions (3.x) or the e64 Pro: which commands still work
185
+ - other gateways of the IPAS DaliControl family
186
+ - integrations or examples for further systems (openHAB, ioBroker, Node-RED, Loxone …)
187
+ - decoded error flags and properties
188
+ - tunable-white channels as one light in Home Assistant
157
189
 
158
- Reports from other firmware versions, the e64 Pro, or decoded error flags and
159
- properties are welcome. Please say what you observed on the lamps, not only
160
- what the gateway answered.
190
+ Please say what you observed on the lamps, not only what the gateway answered.
161
191
 
162
192
  ## License
163
193
 
{dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/README.md RENAMED
@@ -1,31 +1,53 @@
1
1
  # dalicontrol-e64
2
2
 
3
- Unofficial protocol notes, field experience and a small Python library for the
4
- **IPAS DaliControl e64** KNX/DALI gateway.
3
+ Use and program the DALI lights behind an **IPAS DaliControl e64** KNX/DALI
4
+ gateway from any home automation system or script, without ETS and without
5
+ the DCA (IPAS' Device Configuration App plug-in for ETS). Unofficial protocol
6
+ notes, field experience, a Python library and a Home Assistant integration.
7
+
8
+ ## Why
9
+
10
+ - **No ETS, no DCA, no licence.** Switching, dimming, group assignment,
11
+ storing and recalling scenes, even a DALI new installation: all of it works
12
+ over plain HTTP (a browser, curl, Python) or over KNX with a free library
13
+ such as [xknx](https://github.com/XKNX/xknx).
14
+ - **Any home automation system.** Home Assistant (integration in this repo,
15
+ or a few lines of YAML), Node-RED, openHAB, ioBroker, a shell script. The
16
+ request is one HTTP GET.
17
+ - **Colour wheels for RGBW LED strips.** A strip is four DALI channels; the
18
+ Home Assistant integration turns each into one colour light with the normal
19
+ colour wheel, white slider and brightness. Pick a colour on a wall tablet
20
+ and the strip follows.
21
+ - **Fast and stable on old hardware.** The approach here drives a flat with
22
+ 38 DALI ballasts every day and has for months: scene changes and dimming
23
+ react immediately, nothing needs restarting. That was not expected from a
24
+ gateway of this age on its original firmware; it took a lot of testing to
25
+ find what makes it quick (scenes instead of many single writes, one queue,
26
+ no blind retries; see [lessons-learned.md](docs/lessons-learned.md)).
27
+ - **No firmware update needed.** Everything here runs on firmware 1.3_06. An
28
+ update to 3.x destroyed the KNX side of a second gateway in the same
29
+ installation; manufacturer support could neither update the other one nor
30
+ downgrade the broken one in a remote session. Staying on 1.x is a choice,
31
+ and this repository is what makes it workable.
5
32
 
6
33
  The gateway is usually commissioned once with ETS and then only reached
7
- through KNX group addresses. It can do more: its built-in web page uses a plain
8
- HTTP interface, and the same commands can be sent over KNX without any ETS
9
- change. Neither is documented by the manufacturer. This repository writes down
10
- what was found while building a lighting control for a flat with 38 DALI
11
- ballasts, including the parts that went wrong.
12
-
13
- Use it with or without a home automation system.
14
-
15
- ## No ETS, no DCA, no KNX software
16
-
17
- For working with the DALI side you do not need ETS, the DCA plug-in, an ETS
18
- licence or any other KNX vendor software. Switching and dimming channels,
19
- assigning groups, storing and recalling scenes and starting a DALI new
20
- installation all work with this repository alone: over HTTP with a browser,
21
- curl or Python, or over KNX with a free KNXnet/IP library such as
22
- [xknx](https://github.com/XKNX/xknx).
34
+ through KNX group addresses. Its built-in web page, however, uses a plain HTTP
35
+ interface, and the same commands can be sent over KNX as device management
36
+ telegrams, without any ETS change. Neither is documented by the manufacturer.
37
+ This repository writes both down, including the parts that went wrong.
23
38
 
24
39
  ETS is only needed for the KNX side of the gateway: its individual address,
25
40
  group objects and KNX application parameters. If the gateway was commissioned
26
41
  once, you can leave that untouched. If you only use the HTTP interface, the
27
42
  KNX side does not matter at all.
28
43
 
44
+ For that KNX side there is an open-source alternative to ETS as well:
45
+ [bussard](https://github.com/tmbo/bussard), a command-line tool that keeps the
46
+ KNX configuration in text files and writes it to the devices. Check its device
47
+ list for your gateway's application version before relying on it.
48
+
49
+ Reading this with an LLM or coding agent: start with [llms.txt](llms.txt).
50
+
29
51
  > **Tested on one device type and firmware only:** DaliControl e64, firmware
30
52
  > 1.3_06, ETS application e64-01-0110. Not affiliated with or endorsed by
31
53
  > IPAS. Several commands re-address or reconfigure your installation and have
@@ -42,7 +64,7 @@ KNX side does not matter at all.
42
64
  | [docs/lessons-learned.md](docs/lessons-learned.md) | What failed and what replaced it |
43
65
  | [docs/home-automation.md](docs/home-automation.md) | Home Assistant, Node-RED, openHAB, ioBroker: from one HTTP request to a full integration |
44
66
  | `src/dalicontrol_e64/` | Python library on PyPI: command encoding with an allowlist, HTTP client, KNX transport, request queue |
45
- | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, scene recall, all on/off, HTTP or KNX |
67
+ | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, RGBW strips with colour wheel, scene recall, all on/off, HTTP or KNX |
46
68
 
47
69
  ## Five things to know first
48
70
 
@@ -132,11 +154,19 @@ python3 -m pytest # Home Assistan
132
154
  The tests run against a simulated device. They prove the encoding, the
133
155
  allowlist and the queue logic, not the behaviour of your hardware.
134
156
 
135
- ## Contributing
157
+ ## Status and contributing
158
+
159
+ Finished for the installation it was written for: it has run stable and fast
160
+ there for months, so it will not be developed further from that side. Pull
161
+ requests are welcome, for example:
162
+
163
+ - other firmware versions (3.x) or the e64 Pro: which commands still work
164
+ - other gateways of the IPAS DaliControl family
165
+ - integrations or examples for further systems (openHAB, ioBroker, Node-RED, Loxone …)
166
+ - decoded error flags and properties
167
+ - tunable-white channels as one light in Home Assistant
136
168
 
137
- Reports from other firmware versions, the e64 Pro, or decoded error flags and
138
- properties are welcome. Please say what you observed on the lamps, not only
139
- what the gateway answered.
169
+ Please say what you observed on the lamps, not only what the gateway answered.
140
170
 
141
171
  ## License
142
172
 
{dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "dalicontrol-e64"
7
- version = "0.2.0"
7
+ version = "0.2.2"
8
8
  description = "Unofficial protocol notes and Python tools for the IPAS DaliControl e64 KNX/DALI gateway"
9
9
  readme = "README.md"
10
10
  license = "MIT"
{dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/src/dalicontrol_e64/__init__.py RENAMED
@@ -4,4 +4,4 @@ from .http import CommandRejected, HttpClient
4
4
  from .writer import Macro, Writer
5
5
 
6
6
  __all__ = ["commands", "CommandRejected", "HttpClient", "Macro", "Writer"]
7
- __version__ = "0.2.0"
7
+ __version__ = "0.2.2"
{dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2/src/dalicontrol_e64.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: dalicontrol-e64
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Unofficial protocol notes and Python tools for the IPAS DaliControl e64 KNX/DALI gateway
5
5
  Author: NashEQify
6
6
  License-Expression: MIT
@@ -21,32 +21,54 @@ Dynamic: license-file
21
21
 
22
22
  # dalicontrol-e64
23
23
 
24
- Unofficial protocol notes, field experience and a small Python library for the
25
- **IPAS DaliControl e64** KNX/DALI gateway.
24
+ Use and program the DALI lights behind an **IPAS DaliControl e64** KNX/DALI
25
+ gateway from any home automation system or script, without ETS and without
26
+ the DCA (IPAS' Device Configuration App plug-in for ETS). Unofficial protocol
27
+ notes, field experience, a Python library and a Home Assistant integration.
28
+
29
+ ## Why
30
+
31
+ - **No ETS, no DCA, no licence.** Switching, dimming, group assignment,
32
+ storing and recalling scenes, even a DALI new installation: all of it works
33
+ over plain HTTP (a browser, curl, Python) or over KNX with a free library
34
+ such as [xknx](https://github.com/XKNX/xknx).
35
+ - **Any home automation system.** Home Assistant (integration in this repo,
36
+ or a few lines of YAML), Node-RED, openHAB, ioBroker, a shell script. The
37
+ request is one HTTP GET.
38
+ - **Colour wheels for RGBW LED strips.** A strip is four DALI channels; the
39
+ Home Assistant integration turns each into one colour light with the normal
40
+ colour wheel, white slider and brightness. Pick a colour on a wall tablet
41
+ and the strip follows.
42
+ - **Fast and stable on old hardware.** The approach here drives a flat with
43
+ 38 DALI ballasts every day and has for months: scene changes and dimming
44
+ react immediately, nothing needs restarting. That was not expected from a
45
+ gateway of this age on its original firmware; it took a lot of testing to
46
+ find what makes it quick (scenes instead of many single writes, one queue,
47
+ no blind retries; see [lessons-learned.md](docs/lessons-learned.md)).
48
+ - **No firmware update needed.** Everything here runs on firmware 1.3_06. An
49
+ update to 3.x destroyed the KNX side of a second gateway in the same
50
+ installation; manufacturer support could neither update the other one nor
51
+ downgrade the broken one in a remote session. Staying on 1.x is a choice,
52
+ and this repository is what makes it workable.
26
53
 
27
54
  The gateway is usually commissioned once with ETS and then only reached
28
- through KNX group addresses. It can do more: its built-in web page uses a plain
29
- HTTP interface, and the same commands can be sent over KNX without any ETS
30
- change. Neither is documented by the manufacturer. This repository writes down
31
- what was found while building a lighting control for a flat with 38 DALI
32
- ballasts, including the parts that went wrong.
33
-
34
- Use it with or without a home automation system.
35
-
36
- ## No ETS, no DCA, no KNX software
37
-
38
- For working with the DALI side you do not need ETS, the DCA plug-in, an ETS
39
- licence or any other KNX vendor software. Switching and dimming channels,
40
- assigning groups, storing and recalling scenes and starting a DALI new
41
- installation all work with this repository alone: over HTTP with a browser,
42
- curl or Python, or over KNX with a free KNXnet/IP library such as
43
- [xknx](https://github.com/XKNX/xknx).
55
+ through KNX group addresses. Its built-in web page, however, uses a plain HTTP
56
+ interface, and the same commands can be sent over KNX as device management
57
+ telegrams, without any ETS change. Neither is documented by the manufacturer.
58
+ This repository writes both down, including the parts that went wrong.
44
59
 
45
60
  ETS is only needed for the KNX side of the gateway: its individual address,
46
61
  group objects and KNX application parameters. If the gateway was commissioned
47
62
  once, you can leave that untouched. If you only use the HTTP interface, the
48
63
  KNX side does not matter at all.
49
64
 
65
+ For that KNX side there is an open-source alternative to ETS as well:
66
+ [bussard](https://github.com/tmbo/bussard), a command-line tool that keeps the
67
+ KNX configuration in text files and writes it to the devices. Check its device
68
+ list for your gateway's application version before relying on it.
69
+
70
+ Reading this with an LLM or coding agent: start with [llms.txt](llms.txt).
71
+
50
72
  > **Tested on one device type and firmware only:** DaliControl e64, firmware
51
73
  > 1.3_06, ETS application e64-01-0110. Not affiliated with or endorsed by
52
74
  > IPAS. Several commands re-address or reconfigure your installation and have
@@ -63,7 +85,7 @@ KNX side does not matter at all.
63
85
  | [docs/lessons-learned.md](docs/lessons-learned.md) | What failed and what replaced it |
64
86
  | [docs/home-automation.md](docs/home-automation.md) | Home Assistant, Node-RED, openHAB, ioBroker: from one HTTP request to a full integration |
65
87
  | `src/dalicontrol_e64/` | Python library on PyPI: command encoding with an allowlist, HTTP client, KNX transport, request queue |
66
- | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, scene recall, all on/off, HTTP or KNX |
88
+ | `custom_components/dalicontrol_e64/` | Home Assistant integration (HACS): one light per channel, RGBW strips with colour wheel, scene recall, all on/off, HTTP or KNX |
67
89
 
68
90
  ## Five things to know first
69
91
 
@@ -153,11 +175,19 @@ python3 -m pytest # Home Assistan
153
175
  The tests run against a simulated device. They prove the encoding, the
154
176
  allowlist and the queue logic, not the behaviour of your hardware.
155
177
 
156
- ## Contributing
178
+ ## Status and contributing
179
+
180
+ Finished for the installation it was written for: it has run stable and fast
181
+ there for months, so it will not be developed further from that side. Pull
182
+ requests are welcome, for example:
183
+
184
+ - other firmware versions (3.x) or the e64 Pro: which commands still work
185
+ - other gateways of the IPAS DaliControl family
186
+ - integrations or examples for further systems (openHAB, ioBroker, Node-RED, Loxone …)
187
+ - decoded error flags and properties
188
+ - tunable-white channels as one light in Home Assistant
157
189
 
158
- Reports from other firmware versions, the e64 Pro, or decoded error flags and
159
- properties are welcome. Please say what you observed on the lamps, not only
160
- what the gateway answered.
190
+ Please say what you observed on the lamps, not only what the gateway answered.
161
191
 
162
192
  ## License
163
193
 
{dalicontrol_e64-0.2.0 → dalicontrol_e64-0.2.2}/LICENSE RENAMED
File without changes