node-red-contrib-knx-ultimate: "KNXUltimate-KNXEngine: Multicast: cannot add membership" - can't tx or rx to/from KNX bus
Hi Massimo!
Sorry to trouble you. I’m new to node-red and knx-ultimate, and I can’t seem to get it working. I’m hoping I’ve missed something basic?
Describe the bug I can’t send to or receive from the KNX bus.
I’ve stripped back my initial attempt (to send a ‘response’ to a ‘read’) to simply injecting true/false to a light’s SW GA, but still no good.
To Reproduce Steps to reproduce the behavior:
- I can restart Node-Red and it restarts ok/cleanly.
- Create a basic flow:

(Is this flapping to be expected? The KNX objects cycle between “Connected. On duty” to “Next cycle will reconnect”).
- I’m clicking the Injects for
trueorfalsebut the light does not respond, and I don’t see it logged in ETS.
Expected behavior The light should light/extinguish and ETS should log it. (Yes, my Group address is otherwise working and KNX logs other interactions).
Screenshots
[error] 10/6/2022, 5:05:36 PM.643 knxUltimate-config: received KNXClientEvents.error: addMembership EINVAL
[error] 10/6/2022, 5:05:36 PM.646 knxUltimate-config: Disconnected by: addMembership EINVAL
[error] 10/6/2022, 5:05:56 PM.645 KNXUltimate-KNXEngine: Multicast: cannot add membership (Error: addMembership EINVAL
at Socket.addMembership (node:dgram:841:11)
at Socket.<anonymous> (/config/node-red/node_modules/node-red-contrib-knx-ultimate/KNXEngine/KNXClient.js:170:30)
at Socket.onListening (node:dgram:244:7)
at Socket.emit (node:events:539:35)
at startListening (node:dgram:173:10)
at node:dgram:358:7
at processTicksAndRejections (node:internal/process/task_queues:84:21) {
errno: -22,
code: 'EINVAL',
syscall: 'addMembership'
})
[error] 10/6/2022, 5:05:56 PM.648 knxUltimate-config: received KNXClientEvents.error: addMembership EINVAL
[error] 10/6/2022, 5:05:56 PM.650 knxUltimate-config: Disconnected by: addMembership EINVAL
Knx-Ultimate Version 1.4.3
Node-red version: 13.4.0 Home Assistant:
Home Assistant 2022.10.0
Supervisor 2022.09.1
Operating System 9.0
Frontend 20221005.0 - latest
Are you running node-red behind homematic, docker or anything similar? Node-Red running natively on a Raspberry Pi 4, co-residing with HA.
Additional context I found knx-easy before knx-ultimate, and it worked well for less than an hour (I told you I was new to this), up until it stopped responding, presumably this bug.
I uninstalled it, installed knx-ultimate, rebuilt my flow, but have not been able to get any response from the KNX bus. Changing the “bind to local gateway” from Auto to eth0 didn’t help.
I’ve power cycled the Pi running HA/Node-Red & my Weinzierl 752 IP Gateway in case ports were still locked up, all to no avail.
Existing (legacy) automations in HA that use KNX are still working fine. In case there was a clash/conflict I disabled that Integration and restarted HA but that wasn’t the fix.
I’ve seen you ask for debug text, so here’s that too:
-> id: 6e363d0f7e6698c5
-> type: knxUltimate-config
-> info: undefined
-> users: [object Object],[object Object],[object Object],[object Object],[object Object]
-> _config: [object Object]
-> host: 10.10.16.111
-> port: 3671
-> physAddr: 15.15.22
-> hostProtocol: Multicast
-> suppressACKRequest: false
-> csv:
-> KNXEthInterface: eth0
-> KNXEthInterfaceManuallyInput:
-> statusDisplayLastUpdate: true
-> statusDisplayDeviceNameWhenALL: true
-> statusDisplayDataPoint: false
-> stopETSImportIfNoDatapoint: stop
-> loglevel: error
-> name: KNX Gateway
-> localEchoInTunneling: true
-> delaybetweentelegrams: 50
-> delaybetweentelegramsfurtherdelayREAD: 1
-> ignoreTelegramsWithRepeatedFlag: false
-> keyringFileXML: undefined
-> knxSecureSelected: undefined
-> autoReconnect: yes
-> label: function () {
return typeof this.name === undefined ? (this.host + ":" + this.port) : this.name + " " + (this.host + ":" + this.port);
}
-> _def: [object Object]
-> _: function(){var e=Array.prototype.slice.call(arguments,0),t=e[0],o=(-1===e[0].indexOf(":")&&(e[0]=i+":"+e[0]),RED._.apply(null,e));return o=o===e[0]?t:o}
-> valid: true
-> validationErrors:
-> dirty: true
-> changed: false
-> credentials: [object Object]
-> infoEditor: [object Object]
Thanks,
- Greig.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (7 by maintainers)
Thanks Massimo, it looks to be working now. I’ll let it sit overnight (approaching 8pm here) then play some more tomorrow.
I had a look at the Wiki and that’s a hell of a lot of documentation. Huge kudos for putting all that effort into it!
Thanks for your help today too.