New plugin pimatic-sounds

---

Woke up and saw these messages in the pimatic log:

Log messages

Showing 7 of 10 Messages
2020-02-13 03:14:25warn [pimatic]: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!
03:14:25error [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/pimatic-sounds/node_modules/castv2-client/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:165: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:95: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!
03:14:12warn [pimatic]: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!
03:14:12error [pimatic]: An uncaught exception occurred: Error: Device timeout
at fn.ontimeout (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/lib/senders/platform.js:56:26)
at Object.onceWrapper (events.js:277:13)
at fn.emit (events.js:189:13)
at Timeout.ontimeout [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10)
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:31:31warn [pimatic]: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!
02:31:31error [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/pimatic-sounds/node_modules/castv2-client/node_modules/castv2/lib/client.js:35:21)
at PlatformSender.connect (/home/pi/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/lib/senders/platform.js:27:15)
at ChromecastDevice.initSounds (/home/pi/pimatic-app/node_modules/pimatic-sounds/pimatic-sounds.coffee:165: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:95: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:31:20error [pimatic-sounds]: Device ‘google-hub-keuken-’ offline

Hi, The error is coming from multiple webservers trying to start at the same port address. The webserver for serving the sounds was per device. I’m only having 1 GA so is didn’t test multiple devices. For the plugin i need only 1 webserver to serve devices so I moved the webserver to the plugin level and the server is now created once. That should solve this error in version 0.0.14.
Version 0.0.14 has has also support for Sonos (+SYMFONISK) devices and is published.

Thanks for testing and discovering.

installed and confirmed, multiple devices are accepted now. Thanks!

Also tested resume streaming: works, but only if the tune-in stream is started on the same device as to where I want to cast to. When I stream to a group of speakers and send a message with pimatic-sounds to 1 cast device it interrupts the stream on the group speakers, play a message on the cast device I selected and then the tune-in stream stops.

Group streams are sending on a different port, as far as I can see every group or pair gets is own port but I don’t know why it selects a certain IP (in my case, the IP from one of my google home speakers).
Strange thing is: when I try to cast to one speaker of a pair (wich is essentially also a group) that cast gets rejected. (got a json error from your plugin with the phrase “not allowed”)

Don’t know if you can do anything with that info though haha.

got a question:
Is it possible to reset the volume to the previous value when casting with a volume change in the rule?

The volume should go back to the value before the sound was played if you used the vol option after the text or file.
Example. When something is playing on vol 10 and the following action is executed "play text “vdvvdvddv” vol 40 on <hdhdhhd>"
After that the volume should go back to 10.

Or do you mean when nothing is playing after a Sound text/file the volume should go back to the old value?

@bertreb Ah didn’t noticed volume resume when something was playing but indeed I meant when nothing is playing.

@djmvt that is solved in next release, somewhere today

I released version 0.0.15 with

• fix of the volume
• device discover
• Usage of variables in text string

During installation I got this error:

Error installing plugin pimatic-sounds: Error running "./node_modules/pimatic/ppm.js install pimatic-sounds@0.0.15 --unsafe-perm"

> mdns@2.5.1 install /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns
> node-gyp rebuild
make: Entering directory '/home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from ../src/dns_sd.cpp:1:0:
../src/mdns.hpp:32:10: fatal error: dns_sd.h: No such file or directory
#include <dns_sd.h>
^~~~~~~~~~
compilation terminated.
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1
dns_sd_bindings.target.mk:156: recipe for target 'Release/obj.target/dns_sd_bindings/src/dns_sd.o' failed
make: Leaving directory '/home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/ortin/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.15.0-76-generic
gyp ERR! command "/usr/local/bin/node" "/home/ortin/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns
gyp ERR! node -v v10.16.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
> protobufjs@6.8.8 postinstall /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/node_modules/castv2/node_modules/protobufjs
> node scripts/postinstall
npm ERR! Linux 4.15.0-76-generic
npm ERR! argv "/usr/local/bin/node" "/home/ortin/pimatic-app/node_modules/pimatic/ppm.js" "install" "pimatic-sounds@0.0.15" "--unsafe-perm"
npm ERR! node v10.16.3
npm ERR! npm v2.15.12
npm ERR! code ELIFECYCLE
npm ERR! mdns@2.5.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mdns@2.5.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls mdns
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ortin/pimatic-app/npm-debug.log
> mdns@2.5.1 install /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns
> node-gyp rebuild
make: Entering directory '/home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns/build'
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from ../src/dns_sd.cpp:1:0:
../src/mdns.hpp:32:10: fatal error: dns_sd.h: No such file or directory
#include <dns_sd.h>
^~~~~~~~~~
compilation terminated.
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1
dns_sd_bindings.target.mk:156: recipe for target 'Release/obj.target/dns_sd_bindings/src/dns_sd.o' failed
make: Leaving directory '/home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/ortin/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.15.0-76-generic
gyp ERR! command "/usr/local/bin/node" "/home/ortin/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/mdns
gyp ERR! node -v v10.16.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
> protobufjs@6.8.8 postinstall /home/ortin/pimatic-app/node_modules/pimatic-sounds/node_modules/castv2-client/node_modules/castv2/node_modules/protobufjs
> node scripts/postinstall
npm ERR! Linux 4.15.0-76-generic
npm ERR! argv "/usr/local/bin/node" "/home/ortin/pimatic-app/node_modules/pimatic/ppm.js" "install" "pimatic-sounds@0.0.15" "--unsafe-perm"
npm ERR! node v10.16.3
npm ERR! npm v2.15.12
npm ERR! code ELIFECYCLE
npm ERR! mdns@2.5.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mdns@2.5.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs mdns
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls mdns
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ortin/pimatic-app/npm-debug.log

BTW: Did you see that it is really easy to send pictures and videos to a display based cast device (ATV, Hub, CC). Unfortunately you called it “just” sounds.

Nice name isnt it

How did you install 0.0.15 ?

@bertreb
tried updating to 0.0.15 but got the same problem as @OrTiN.
reverted back to 0.0.14

first tried to install with the pimatic gui, then with terminal.

I did a manual install of primatic-chromcast. This plugin uses the same mdns lib.

• git clone … pimatic-chromecast
• npm install in the pimatic-chromecast directory
  The log lstart at the same point but i can’t explain the difference after that.

> mdns@2.5.1 install /Users/Bert/pimatic-dev/node_modules/pimatic-chromecast/node_modules/mdns
> node-gyp rebuild

  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_browse.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_enumerate_domains.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_get_addr_info.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_process_result.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_deallocate.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_ref_sock_fd.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_register.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_resolve.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_service_update_record.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/mdns_utils.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/network_interface.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/socket_watcher.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_ref.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_create.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_deallocate.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_set_value.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_get_length.o
  CXX(target) Release/obj.target/dns_sd_bindings/src/txt_record_buffer_to_object.o
  SOLINK_MODULE(target) Release/dns_sd_bindings.node

> protobufjs@6.8.8 postinstall /Users/Bert/pimatic-dev/node_modules/pimatic-chromecast/node_modules/protobufjs
> node scripts/postinstall

@djmvt said in New plugin pimatic-sounds:

@bertreb
tried updating to 0.0.15 but got the same problem as @OrTiN.
reverted back to 0.0.14

first tried to install with the pimatic gui, then with terminal.

Ok i will skip the discovery for now
You can revert to 0.0.14 or upgrade to 0.0.16

@ortin said in New plugin pimatic-sounds:

…/src/mdns.hpp:32:10: fatal error: dns_sd.h

I forgot to put in the following requirement when using the mdns library

On Linux and other systems using the avahi daemon the avahi dns_sd compat library and its header files are required. On debianesque systems the package name is libavahi-compat-libdnssd-dev, on fedoraesque systems the package is avahi-compat-libdns_sd-devel. On other platforms Apple’s mDNSResponder is recommended. Care should be taken not to install more than one mDNS stack on a system.

This requirement is only for the Chromecast devices. Ik will look if there’s a solution without extra requirements

@bertreb said in New plugin pimatic-sounds:

Nice name isnt it

Sure, I love it

@bertreb

0.0.16 test: works, volume goes back to previous value, even when nothing is playing.
But casting doesnt stop. You cannot see this on speakers (except in the home app) but on the nest hub the cast icon keeps displaying in the screen, have to manually stop casting on the nest hub or in the home app.

What is being casted after the text of file from Sounds stops?

@bertreb

Nothing, it just waits but doesn’t revert back to the clock. Same with the google home speakers although that’s only visible in the google home app.

@djmvt I see it now on my own Home app.
I will do a next update for you to test

@bertreb

Don’t rush it
The plugin is getting better and better, only those damn groups haha…