New plugin pimatic-sounds

---

I know we wrote already about the friendName stuff, but I still fighting with it. My problem was just the time the function get_chromecast took. At the end it needs to be done just once during startup, from then it should be available and can be used immediately. It would be a benefit if groups created in the assistent app could be addressed in pimatic to send sounds ton it. What you mean?

Got a few errors in the log this morning. At the time they registered I was asleep, looks like the Google devices got a software update or something so they went offline, the plugin generates an error when that happens:

Log messages

Showing 8 of 16 Messages
2020-02-14 02:41:09error [pimatic]: An uncaught exception occurred: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:56:29)
at Object.connect (_tls_wrap.js:1154:12)
at Client.connect (/home/pi/pimatic-app/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:221:17)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:1:1)
at Timeout.startupTime [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:166:16)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
02:40:58error [pimatic-sounds]: Device ‘google-hub-keuken-’ offline
02:24:24error [pimatic]: An uncaught exception occurred: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:56:29)
at Object.connect (_tls_wrap.js:1154:12)
at Client.connect (/home/pi/pimatic-app/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:221:17)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:1:1)
at Timeout.startupTime [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:166:16)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
02:24:24error [pimatic]: An uncaught exception occurred: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:56:29)
at Object.connect (_tls_wrap.js:1154:12)
at Client.connect (/home/pi/pimatic-app/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:221:17)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:1:1)
at Timeout.startupTime [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:166:16)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
02:24:20error [pimatic]: An uncaught exception occurred: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:56:29)
at Object.connect (_tls_wrap.js:1154:12)
at Client.connect (/home/pi/pimatic-app/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:221:17)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:1:1)
at Timeout.startupTime [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:166:16)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
02:24:09error [pimatic-sounds]: Device ‘google-mini-slaapkamer’ offline
02:20:32error [pimatic]: An uncaught exception occurred: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
From connect
at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:56:29)
at Object.connect (_tls_wrap.js:1154:12)
at Client.connect (/home/pi/pimatic-app/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:221:17)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:1:1)
at Timeout.startupTime [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:166:16)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
02:20:21error [pimatic-sounds]: Device ‘google-mini-badkamer’ offline

Hi, i checked/improved the error handling when devices go offline.
There will be still a small error message when a device goes offline, but thats because ‘it’s like an error’

I published version 0.0.17 and need your help to test it also.

@bertreb installed 0.0.17 without issues. Casting not stopping after initialisation sound (as with previous version).
When scanning for devices (de ice Discovery) this message is visible now: “pimatic-sounds: Not yet implemented”.

Something specific you want me to test?

Thanks!

Hi,

I disabled the discovery (mdns installation error) and i did not found a solution yet to stop the casting info. Even when I stop pimatic/plugin the casting is staying on.

If you could test what the error are if you power down or disconnect a google device

This is the error that is registered when one device gets disconnected, absolutely fine!

“Showing 1 of 1 Messages
2020-02-14 13:34:23error [pimatic-sounds]: Device ‘google-mini-slaapkamer’ offline”

I’ve been playing with node-red before installing your plugin last week, with node-red-contrib-castv2 I can send “CLOSE” as a command to the ip address of a casting device, then the casting stops. Maybe you can see in the source on http://gitHub.com/i8beef/node-red-contrib-castv2 how this is implemented?

Hi thanks, it must be possible, but its hard to find with implicit or no documentation

Noticed a little layout issue

thats too much info

@bertreb haha yeah just a bit
tried to surpress it with extra attribute and option “hide in gui” but that doesn’t work.

Sending a text message to a google device is working but when trying to send a mp3 pimatic respond with “error [pimatic-sounds]: error: Error: Load failed”

Tried to send a text (wich generates the mp3 in the sounds folder" and made a new rule with the mp3 file in stead of the text also gave this error.

Also tiny translation error when filename isn’t found: “File /home/pi/pimatic-app/sounds/fantasia’ does not excist” (exist)

Thats a bug when I introduced using variable in text messages.
Its fixed in the already published version 0.0.18

@bertreb
tried 0.0.18 but still the same error when trying to play a file.

Hi, there was reason why files didn’t play. I solved that part.
The file you are playing must exist in the sounds directory.
When you save the rule the file existence is checked

@bertreb said in New plugin pimatic-sounds:

The file you are playing must exist in the sounds directory.
When you save the rule the file existence is checked

There’s no error when creating the rule, file just wont play. tried multiple files but none of them play for some reason. Will check later on if something is wrong on my end.

thanks!

@djmvt said in New plugin pimatic-sounds:

@bertreb said in New plugin pimatic-sounds:

The file you are playing must exist in the sounds directory.
When you save the rule the file existence is checked

There’s no error when creating the rule, file just wont play. tried multiple files but none of them play for some reason. Will check later on if something is wrong on my end.

thanks!

The filename must be without spaces!

@bertreb said in New plugin pimatic-sounds:

The filename must be without spaces!

I know, no spaces in the filenames, tried multiple files, even the files created with tts but error stays.

Can you run the url in a browser?
Its <your local ip>:8088/<filename>
If you didn’t change the port

@bertreb said in New plugin pimatic-sounds:

Can you run the url in a browser?
Its <your local ip>:8088/<filename>
If you didn’t change the port

Ah that’s the problem! Changed my port to 4321 because of some other stuff I’ve been testing. Will change it back to 8088 then.

The port number shouldn’t be the problem unless something else is already running on that port.
Your need to restart Pimatic when you change the port number.

Is the file playing in your current config <ip>:4321/<filename> ?
And what is the content type? (mp3, wav, …)