# Sonos Error: nrcsp: device not reachable/rejected \>\>192.168.10.10

**URL:** <https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572>\
**Category:** General\
**Created:** [13 January 2025 10:51 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572 "2025-01-13T10:51:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)\
**Post date:** [13 January 2025 10:51 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/1 "2025-01-13T10:51:12Z")

</div>

My Sonos controls stopped working, and all the Sonos nodes have the above error under them. I updated to the newest pallette version node-red-contrib-sonos-plus 6.9.2 but that did not clear the error. Any idea please ?

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [13 January 2025 11:01 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/2 "2025-01-13T11:01:30Z")

</div>

> <https://github.com/hklages/node-red-contrib-sonos-plus/issues/292>
>
> \### Description
> I am suddenly having this error with basically all node types:
> …
> \<img width="361" alt="image" src="https://github.com/hklages/node-red-contrib-sonos-plus/assets/73143201/311f53d6-a331-4b1d-95f0-ea14b032b358"\>
> 
> At first I thought one of my speakers had gone bad, so I tried removing it from the configuration but the issue persists. It seems to be a new issue between the module and the speakers.
> 
> I've tried:
> \- Installing Sonos speaker updates
> \- Reverting to 6.7 of this module
> \- Factory resetting speakers
> 
> I don't really know that the problem originates in a code change here given reversion doesn't fix it. Perhaps what I'm doing is unique and others aren't seeing this.
> 
> \### What node/command (topic)/state (payload)
> 
> node: 
> command: 
> state: 
> 
> \### In case of a bug: Are you able to reproduce the error
> 
> 
> 
> \### Versions and Infrastructure
> 
> \*\*what system:\*\* podman on Fedora box, Home Assistant
> \*\*node-red-contrib-sonos-plus version:\*\* 6.7.3, 6.7.8, 6.8.0
> \*\*Node-RED version:\*\* 3.1.3 and 3.1.9
> \*\*NodeJS version:\*\* using Docker container for node-red
> 
> \`\`\`
> "dependencies": {
> "node-red-contrib-home-assistant-websocket": "~0.63.1",
> "node-red-contrib-homekit-bridged": "~1.6.0",
> "node-red-contrib-log-elk": "~1.2.8",
> "node-red-contrib-pythonshell": "~1.5.4",
> "node-red-contrib-sonos-plus": "^6.7.3",
> "node-red-contrib-state": "~1.6.1",
> "node-red-contrib-sunevents": "~3.1.1",
> "node-red-contrib-tts-ultimate": "~2.0.5"
> }
> \`\`\`
> 
> see: \[https://flows.nodered.org/flow/a5c42641bf33dd0da9bfd4426a06950a\]

---

<div class="post-metadata">

**Author:** ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)\
**Post date:** [13 January 2025 11:03 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/3 "2025-01-13T11:03:34Z")

</div>

I just found the issue (sort of). I had to change the config speaker to another one, and it works now. Not sure why it worked with the speaker I had for ages, now it stopped, but changing it to anotehr and it starts working again...

---

<div class="post-metadata">

**Author:** ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)\
**Post date:** [13 January 2025 11:08 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/4 "2025-01-13T11:08:05Z")

</div>

Just read this, I did have some network issues, but I resolved them. So still not sure why it doesnt like that speaker any more, but others used as config and its working again.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 January 2025 09:10 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/5 "2025-01-14T09:10:10Z")

</div>

> [@Mikee1234K](#):
>
> still not sure why it doesnt like that speaker any more

Have you tried going back to that one again to confirm it still does not work?

---

<div class="post-metadata">

**Author:** ![Mikee1234K](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mikee1234k/32/70283_2.png) [@Mikee1234K](https://discourse.nodered.org/u/Mikee1234K)\
**Post date:** [14 January 2025 15:25 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/6 "2025-01-14T15:25:14Z")

</div>

I have just tried going back to that speaker, still the same error. I have 5 speakers, only one of them will produce this error, all the others work. But the speaker in question functions normally, but in NR is gives this error

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [14 April 2025 15:26 UTC](https://discourse.nodered.org/t/sonos-error-nrcsp-device-not-reachable-rejected-192-168-10-10/94572/7 "2025-04-14T15:26:10Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.