-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paired speakers doesn't work and crashes Node Red #7
Comments
And an export of the nodes used for testing:
|
I'm creating a "pair" for stereo output, not a speaker group. The process is described here: |
I'm having the same issue, only, node red no longer crashes, but when I send a simple timestamp to it, to trigger a "test" message, it's simply ignored. |
Update: seems to me that the port used by the google home speakers is hard coded and it is the 8009 port. |
Running latest Home Assistant 2021.12.10 on Home Assistant OS 7.1. Latest Node Red 10.3.4 installed as an Add-On.
Casting to one speaker works flawlessly, but today I added another speaker and paired them for stereo use through Google Home. I'm now unable to cast to the group or any of the speakers, as Node Red crashes when I try.
Overview of my two speakers and the group when searching for devices using the magnifying glass:
I noticed that when selecting the group-device ("Google Cast Group.Køkken - Nest Audio"), the name is set to "Nest Audio.Køkken - Nest Audio 1" and not the group name. It might be as designed, I just wanted to mention it in case it's part of the root cause of the issue.
Trying to cast something crashes Node Red as can be seen in the log below.
Let me know if I can provide any further useful information or help out with testing. Thank you :)
`20 Jan 23:04:21 - [info] Started flows
fileServer listening on ip 10.10.10.20 and port 8098
20 Jan 23:04:21 - [info] [mqtt-broker:Home Assistant] Connected to broker: mqtt://localhost:1883
20 Jan 23:04:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
20 Jan 23:04:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
20 Jan 23:04:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
20 Jan 23:04:26 - [info] [server:Home Assistant] Connected to http://supervisor/core
20 Jan 23:04:26 - [info] [server:Home Assistant] Connected to http://supervisor/core
20 Jan 23:04:26 - [info] [server:Home Assistant] Connected to http://supervisor/core
new message -----
Queued messages [
{
devicePlaySettings: {
msg: [Object],
sourceNode: [GoogleNotify],
ip: '10.10.10.80',
playVolumeLevel: 0.5,
playMessage: 'Testing paired speakers',
language: 'en',
speakSlow: false,
mediaServerUrl: 'http://10.10.10.20',
mediaServerPort: '8098',
cacheFolder: '/tmp'
},
callback: [Function (anonymous)]
}
]
Queued messages [
{
devicePlaySettings: {
msg: [Object],
sourceNode: [GoogleNotify],
ip: '10.10.10.80',
playVolumeLevel: 0.5,
playMessage: 'Testing paired speakers',
language: 'en',
speakSlow: false,
mediaServerUrl: 'http://10.10.10.20',
mediaServerPort: '8098',
cacheFolder: '/tmp'
},
callback: [Function (anonymous)]
}
]
setting up mediaPlayUrl
preparing socket for connection to device
connecting with device
preparing player on device
20 Jan 23:05:04 - [red] Uncaught Exception:
20 Jan 23:05:04 - [error] ReferenceError: error is not defined
at /opt/node_modules/google-notify/google-notify.js:373:18
at /opt/node_modules/castv2-client/lib/senders/platform.js:95:20
at /opt/node_modules/castv2-client/lib/controllers/receiver.js:51:14
at fn.onmessage (/opt/node_modules/castv2-client/lib/controllers/request-response.js:27:7)
at fn.emit (node:events:402:35)
at Channel.onmessage (/opt/node_modules/castv2-client/lib/controllers/controller.js:16:10)
at Channel.emit (node:events:390:28)
at Client.onmessage (/opt/node_modules/castv2/lib/channel.js:23:10)
at Client.emit (node:events:402:35)
at PacketStreamWrapper.onpacket (/opt/node_modules/castv2/lib/client.js:81:10)
[23:05:04] INFO: Starting Node-RED...
The text was updated successfully, but these errors were encountered: