[pimatic-echo] Control your pimatic devices using Amazon's echo

---

@christoph.ch Do have any switches in your list? These devices don’t sound like switches.

@michbeck100 yes, i have several switches:

{
“xOnLabel”: “Ein”,
“id”: “ds-heizung”,
“name”: “Heizung”,
“class”: “DummySwitch”
},

or

{
“xOnLabel”: “Ein”,
“id”: “ad-ds-simulation-abwesenheit”,
“name”: “Simulation Abwesenheit”,
“class”: “DummySwitch”
},

@christoph.ch Please try to enable the debug output as described in https://github.com/michbeck100/pimatic-echo/issues/7#issuecomment-269228509

@michbeck100 said in [pimatic-echo] Control your pimatic devices using Amazon's echo:

Please try to enable the debug output as described in

here the debug output:

pi@raspberrypi3:~/pimatic-app/node_modules/pimatic $ sudo DEBUG=ssdp-server node pimatic.js
20:18:58.682 2016-12-27 Tuesday
20:19:07.496 [pimatic] Starting pimatic version 0.9.37
20:19:12.906 [pimatic, ppm] 2.15.11
20:19:12.985 [pimatic] Loading plugin: “pimatic-cron” (0.8.8)
20:19:13.787 [pimatic] Loading plugin: “pimatic-mobile-frontend” (0.9.11)
20:19:14.990 [pimatic] Loading plugin: “pimatic-edimax” (0.3.14)
20:19:15.519 [pimatic] Loading plugin: “pimatic-homeduino” (0.9.11)
20:19:16.658 [pimatic] Loading plugin: “pimatic-iframe” (0.2.0)
20:19:16.712 [pimatic] Loading plugin: “pimatic-max” (0.8.19)
20:19:16.825 [pimatic] Loading plugin: “pimatic-openweather” (0.9.3)
20:19:16.936 [pimatic] Loading plugin: “pimatic-ping” (0.9.5)
20:19:17.019 [pimatic] Loading plugin: “pimatic-pushover” (0.9.2)
20:19:17.080 [pimatic] Loading plugin: “pimatic-shell-execute” (0.9.8)
20:19:17.141 [pimatic] Loading plugin: “pimatic-sonos” (0.1.1)
20:19:17.988 [pimatic] Loading plugin: “pimatic-sunrise” (0.8.7)
20:19:18.048 [pimatic] Loading plugin: “pimatic-filebrowser” (0.9.0)
20:19:18.256 [pimatic] Loading plugin: “pimatic-links” (0.8.6)
20:19:18.304 [pimatic] Loading plugin: “pimatic-hap” (0.9.2)
*** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libd ns_sd&e=node>
*** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not su pported (or only supported partially) in the Apple Bonjour compatibility layer o f Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libd ns_sd&e=node&f=DNSServiceRegister>
20:19:19.241 [pimatic] Loading plugin: “pimatic-sysinfo” (0.9.4)
20:19:19.602 [pimatic] Loading plugin: “pimatic-echo” (0.0.3)
20:19:22.443 [pimatic-cron] the time is: Tue Dec 27 2016 20:19:22 GMT+0100 (CET)
20:19:23.679 [pimatic-hap] Starting homekit bridge
20:19:23.790 [pimatic-echo] Starting pimatic-echo…
20:19:24.283 [pimatic] New device “Heizung”…
20:19:24.494 [pimatic] New device “Wetter morgen”…
20:19:24.643 [pimatic] New device “Wetter heute”…
20:19:24.707 [pimatic] New device “Simulation Abwesenheit”…
20:19:24.756 [pimatic] New device “Kamerabewegung”…
20:19:24.809 [pimatic] New device “Wohnzimmer Heizung Küche”…
20:19:24.817 [pimatic] The device type MaxHeatingThermostat does not implement a destroy function
20:19:24.910 [pimatic] New device “Urlaubsmodus”…
20:19:24.959 [pimatic] New device “Testschalter”…
20:19:25.003 [pimatic] New device “raspberry pi herunterfahren”…
20:19:25.057 [pimatic] New device “Küchenfenster”…
20:19:25.061 [pimatic] The device type MaxContactSensor does not implement a des troy function
20:19:25.113 [pimatic] New device “Balkontüre”…
20:19:25.163 [pimatic] New device “raspberry pi neustarten”…
20:19:25.268 [pimatic] New device “SmartHome neustarten”…
20:19:25.339 [pimatic] New device “Wohnzimmer Temperatur”…
20:19:25.343 [pimatic] The device type MaxWallThermostat does not implement a de stroy function
20:19:25.404 [pimatic] New device “Wandthermostat Batteriestatus”…
20:19:25.481 [pimatic] New device “Balkontüre Batteriestatus”…
20:19:25.544 [pimatic] New device “Küchenfenster Batteriestatus”…
20:19:25.710 [pimatic] New device “Büro Heizung”…
20:19:25.781 [pimatic] New device “Router”…
20:19:25.827 [pimatic] New device “Bürofenster”…
20:19:25.875 [pimatic] New device “Waschmaschine”…
20:19:25.924 [pimatic] New device “Bürofenster Batteriestatus”…
20:19:25.979 [pimatic] New device “Kamera”…
20:19:26.021 [pimatic] New device “Drucker”…
20:20:42.581 [pimatic-homeduino] data: "ready"
20:20:42.722 [pimatic-homeduino] Connected to homeduino device.
20:20:42.834 [pimatic-homeduino] data: "ACK"
20:20:43.740 [pimatic-homeduino] Receiving on pin 2
20:20:44.027 [pimatic-mobile-frontend] packing static assets
20:20:45.521 [pimatic-mobile-frontend] packing static assets finished
20:20:45.532 [pimatic-mobile-frontend] rendering html
20:20:58.167 [pimatic-mobile-frontend] rendering html finished
20:20:58.427 [pimatic] Listening for HTTPS-request on port
20:20:58.431 [pimatic] Listening for HTTP-request on port

@christoph.ch There should be at least something like this in the logs:

  ssdp-server using ip address: 192.168.178.4 +0ms
  ssdp-server binding to port 1900 for ssdp discovery +13ms
  ssdp-server Setup Server running. +180ms

Currently I have no idea whats wrong

@christoph.ch

please run the following command if pimatic is running and if not:

netstat -tulpn | egrep -i 1900

@n3ro the result:

pi@raspberrypi3:~ $ sudo netstat -tulpn | egrep -i 1900
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1083/kodi.bin
pi@raspberrypi3:~ $ sudo service pimatic stop
pi@raspberrypi3:~ $ sudo netstat -tulpn | egrep -i 1900
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1083/kodi.bin
pi@raspberrypi3:~ $

@christoph.ch stop kodi on you raspberry ant its working well

@christoph.ch There you have it, the port 1900 is blocked by kodi.bin. Please stop Kodi and try again. If it works then, you know why. I’m not sure if I can change the port for pimatic-echo

@michbeck100 or maybe you could include a internal test in the plugin with a error message in pimatic if port is locked

@n3ro Just put it on the list

@michbeck100 : I have added this option to the socket creation

dgram.createSocket({type:"udp4", reuseAddr:true})

Now it is possible to have minidlna, ha-bridge and the echo-plugin running on the same port.
For multicast listener it is not unusual to have more processes on same socket.

I have not yet tested it.

udp        0      0 0.0.0.0:1900            0.0.0.0:*                           21776/minidlnad  aus (0.00/0/0)
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           21582/node       aus (0.00/0/0)
udp6       0      0 :::1900                 :::*                                21685/java       aus (0.00/0/0)

@kosta Thats great, thanks for the info. This will be part of the next release which should be available later today

Later today is now . I’ve just released version 0.0.4, which should have no problems with existing UPNP listeners anymore. Also you can rename your devices now, if you like to have a more catchy name

@n3ro / @michbeck100 : Thx you very much, it work’s and its very nice THX!

@michbeck100

Whats to do no rename the device?

@n3ro RTFM: https://github.com/michbeck100/pimatic-echo/blob/master/README.md#configuration

@michbeck100

;P

THX just found :D
Next step. Multiple trigger words

@n3ro Why would you need multiple words for the same device?

@michbeck100

someone says “TV” another one “fernseher” and so on.
i have the same with lamps “deckenleuchten” or “deckenlampen”

or just multiple writing for a better match.

multimedia center, multimediacenter, multi media center