@ortin said in New plugin pimatic-sounds:
One thing I forgot this pops up after announcement:
I also notice sometimes these error. Works the system despite that error?
New plugin pimatic-sounds
@ortin said in New plugin pimatic-sounds:
One thing I forgot this pops up after announcement:
I also notice sometimes these error. Works the system despite that error?
Yepp, like a charm!
Therefore take your time…
I have configured the plugin for a set of Sonos Play 1 speakers. I have placed them in a Group Device. When I trigger a rule to play a text the file is being generated, but the file is not played. The log shows:
[pimatic] info: rule speech: Rule not executed device offline
@bertreb Thanks for the quick reply.
I have installed 0.0.32. The initsound.mp3 works on restart. After that the rule still returns the offline error.
The log shows the following, every 15 seconds:
18:35:59.870 [pimatic-sounds] debug: Device ‘sonos_192168178153’ is online
18:35:59.896 [pimatic-sounds] debug: Set attribute ‘status’ to 'idle’
18:36:00.103 [pimatic-sounds] debug: The PlayState changed to playing
18:36:00.117 [pimatic-sounds] debug: Set attribute ‘status’ to 'announcement’
18:36:00.122 [pimatic-sounds] debug: Set attribute ‘info’ to ‘init sounds’
18:36:00.274 [pimatic-sounds] debug: New mainvolume ‘11’’ in device 'sonos_192168178153’
18:36:00.375 [pimatic-sounds] debug: Set attribute ‘status’ to 'offline’
18:36:00.392 [pimatic-sounds] debug: Set attribute ‘info’ to ''
18:36:00.396 [pimatic-sounds] debug: Check online status device 'sonos_192168178153
Unhandled rejection Error: Request failed with status code 500
at createError (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/sonos/node_modules/axios/lib/core/createError.js:16:15)
at settle (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/sonos/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/sonos/node_modules/axios/lib/adapters/http.js:236:11)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
@bertreb When I do a discovery I see 2 devices:
20:41:24.018 [pimatic] info: Device discovered: pimatic-sounds: sonos_192168178185
20:41:24.032 [pimatic] info: Device discovered: pimatic-sounds: sonos_192168178153
The devices form a speaker pair.
Now one device stays online.
The other one is online for a moment and then goes offline. This repeats after 15 seconds.
When I configure a group device then I can use a rule that sends a file or a tts text to the group, so the good news is that is works. A minor issue are the changing state of one speaker and the log info every 15 seconds.
I released version 0.0.34 with the error messaging reduced.
Is the grouping something you do in the Sonos app? I assume that only 1 of the 2 devices is becoming the master.
What happens if you only add the master speaker?
It works!
I have deleted all the devices and rediscovered them.
Now the devices stay online. Only one is only a short while offline after playing a file. Shortly after that the idle state is restored.
The grouping is done in the Sonos controller app.
It seems the problem has been solved.
Thanks.
Hi bertreb,
I like to ask for play vol [0-100]
. Could you be so kind to reimplement it?
Thx, it works!
My test was only for the possibility to set the volume. As written, this works fine. But play text...
does not work for me anymore.