# Roon-core node usage (Roon audio server API), any experience?
**URL:** https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512
**Category:** General
**Created:** [27 October 2025 07:28 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512 "2025-10-27T07:28:52Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Herold](https://discourse.nodered.org/u/Herold)
#### Post date: [27 October 2025 07:28 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512/1 "2025-10-27T07:28:52Z")
Hi, i've installed roon-core node via NR palette. This node is supposed to deal with Roon (audio library system) API but no docs about configuration and usage. According to [https://www.npmjs.com/package/roon-core](https://www.npmjs.com/package/roon-core) this node is a wrapper for the roon node.js API.
Any information ? Regards.
---
### Author:  [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)
#### Post date: [27 October 2025 09:33 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512/2 "2025-10-27T09:33:08Z")
Hi @Herold
I have no experience, but I wouldn't pursue it IMO.
No updates in 4 years, and the author hasn't responded to a 3 year old issue - where there Node was crashing a users Node RED instance
>
>
> I have set up the Roon Core node as per instructions and added the sample flow. …I saw an extension appear in Roon, which I enabled.
>
> Adding Debug nodes to the sample flow, I see data flowing, and I can see MQTT topics populating as well. So everything seems to be working.
>
> However, after initial Node-Red startup, if I click 'Deploy', Node-Red will crash. My Node-Red (v2.1.4) runs in a docker, and if I inspect the log, I see that Roon Core is causing an error that seems to be the cause of the crash. If I restart Node-Red docker, all is well, until the next deploy.
>
> Here's the relevant portion of the log file that shows the roon-core node crashing after the deploy command stops and restarts node and flows;
>
> \`\`\`
> 8 Dec 21:21:01 - \[info\] Stopping flows
> 8 Dec 21:21:01 - \[info\] \[udp out:64342634.2e1408\] udp output stopped
> 8 Dec 21:21:01 - \[info\] \[udp out:230fb82.e504748\] udp output stopped
> 8 Dec 21:21:01 - \[info\] \[udp in:770903fa.bb1aec\] udp listener stopped
> 8 Dec 21:21:01 - \[info\] \[denon-in:Marantz\] Closed
> 8 Dec 21:21:01 - \[info\] \[denon-connection:AV8805\] Closed
> 8 Dec 21:21:01 - \[info\] \[denon-connection:AV8805\] Disconnected
> 8 Dec 21:21:01 - \[info\] Stopped flows
> 8 Dec 21:21:01 - \[info\] Starting flows
> 8 Dec 21:21:01 - \[info\] Started flows
> 8 Dec 21:21:01 - \[info\] \[udp in:770903fa.bb1aec\] udp listener at 0.0.0.0:10000
> 8 Dec 21:21:01 - \[info\] \[mqtt-broker:mqtt local broker\] Connected to broker: presencedetector@mqtt://192.168.1.199:1883
> 8 Dec 21:21:01 - \[info\] \[mqtt-broker:c9cd3208.c4535\] Connected to broker: mqtt://192.168.1.199:1883
> 8 Dec 21:21:01 - \[info\] \[mqtt-broker:8d10f29d.66b98\] Connected to broker: mqtt://localhost:1883
> \-\> REQUEST 0 com.roonlabs.registry:1/info
> \<- COMPLETE 0 Success {"core\_id":"e2634122-d408-4430-9584-59ca7937fd8e","display\_name":"UNRAID","display\_version":"1.8 (build 850) stable"}
> \-\> REQUEST 1 com.roonlabs.registry:1/register {"extension\_id":"com.jac459.nodeRedRoon","display\_name":"Roon Core","display\_version":"0.9.9","publisher":"jac459","email":"jeanarnaudcourcier@gmail.com","required\_services":\["com.roonlabs.transport:2","com.roonlabs.image:1","com.roonlabs.browse:1"\],"optional\_services":\[\],"provided\_services":\["com.roonlabs.status:1","com.roonlabs.pairing:1","com.roonlabs.ping:1"\],"website":"https://github.com/jac459/roon-node-red","token":"c034a86f-7d99-439a-8c85-32bd438e3a7d"}
> MOO: empty message received
> \-\> REQUEST 22 com.roonlabs.transport:2/get\_zones
> 8 Dec 21:21:01 - \[red\] Uncaught Exception:
> 8 Dec 21:21:01 - \[error\] TypeError: Cannot read property 'send' of undefined
>
> at Transport.send (/data/node\_modules/node-roon-api/transport-websocket.js:32:13)
> at Moo.send\_request (/data/node\_modules/node-roon-api/moo.js:75:24)
> at RoonApiTransport.get\_zones (/data/node\_modules/node-roon-api-transport/lib.js:339:19)
> at /data/node\_modules/roon-core/roon.js:33:31
> at /data/node\_modules/node-roon-api-transport/lib.js:375:41
> at /data/node\_modules/node-roon-api/moo.js:27:37
> at /data/node\_modules/node-roon-api/moo.js:204:10
> at Array.forEach (\)
> at Moo.clean\_up (/data/node\_modules/node-roon-api/moo.js:202:32)
> at Transport.moo.transport.onclose (/data/node\_modules/node-roon-api/lib.js:384:13)
> at Transport.close (/data/node\_modules/node-roon-api/transport-websocket.js:43:14)
> at WebSocket.Transport.ws.onmessage (/data/node\_modules/node-roon-api/transport-websocket.js:24:18)
> at WebSocket.onMessage (/data/node\_modules/ws/lib/event-target.js:120:16)
> at WebSocket.emit (events.js:400:28)
> at Receiver.receiverOnMessage (/data/node\_modules/ws/lib/websocket.js:800:20)
> at Receiver.emit (events.js:400:28)
> at Receiver.dataMessage (/data/node\_modules/ws/lib/receiver.js:413:14)
> at Receiver.getData (/data/node\_modules/ws/lib/receiver.js:352:17)
> at Receiver.startLoop (/data/node\_modules/ws/lib/receiver.js:138:22)
> at Receiver.\_write (/data/node\_modules/ws/lib/receiver.js:74:10)
> at writeOrBuffer (internal/streams/writable.js:358:12)
> at Receiver.Writable.write (internal/streams/writable.js:303:10)
> at Socket.socketOnData (/data/node\_modules/ws/lib/websocket.js:875:35)
> at Socket.emit (events.js:400:28)
> at addChunk (internal/streams/readable.js:293:12)
> at readableAddChunk (internal/streams/readable.js:267:9)
> at Socket.Readable.push (internal/streams/readable.js:206:10)
> at TCP.onStreamRead (internal/stream\_base\_commons.js:188:23)
> npm ERR! code ELIFECYCLE
> npm ERR! errno 1
> npm ERR! node-red-docker@2.1.4 start: \`node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data"\`
> npm ERR! Exit status 1
> \`\`\`
All I can tell you, is that there is an example flow
>
---
### Author:  [@Herold](https://discourse.nodered.org/u/Herold)
#### Post date: [28 October 2025 09:51 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512/3 "2025-10-28T09:51:20Z")
Hi @marcus-j-davies , thank you for the insight. Any other solution to deal with Roon API ?
Regards
---
### Author:  [@jac459](https://discourse.nodered.org/u/jac459)
#### Post date: [13 November 2025 04:27 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512/4 "2025-11-13T04:27:55Z")
hi, I am the creator of this node. it was indeed built for a specific username involving NEEO remotes. it works perfectly so I didn't change it
You can check in GitHub to fork it if you have any further need.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [11 February 2026 04:28 UTC](https://discourse.nodered.org/t/roon-core-node-usage-roon-audio-server-api-any-experience/99512/5 "2026-02-11T04:28:14Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.