That’s a good hint. Will contact the support.
-
Somebody on the board with an Echo2?
-
On the German Amazon support side (https://www.amazon.de/gp/help/customer/display.html?nodeId=201749240) there are less devices with non skill support:
Its only
- Amazon Echo
- Echo Dot
Seems I need a Dot to make it running…
-
@ortin Which echo are you using?
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Echo 2 = new Echo (2nd gen.)
-
Please try to set the port to 80. This seems to be necessary (see https://www.alefo.de/ha-bridge-f59/alex-echo-plus-habridge-t3980.html)
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Okay, we have some proceed. With port 80 the activated devices gets discovered. But when I try to switch one of the devices on or off I get a negative response like “No response from Server” (Server reagiert nicht) or from Alexa “Device does not react” (Gerät reagiert nicht).
The Devices are shown as Royal Philips Eletronics intelligant Device. Don’t know if this is correct.BTW: I had the chance to test today with a Echo Dot. This work without any change in the config!
-
@ortin please check for any errors in the pimatic log.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Here the related part of the log when I try to switch on the a switch via Alexa App. The switch gets ever to the state on.
07:59:52.643 [pimatic-echo] debug: changing state for Saugron: {"on":true} SyntaxError: Unexpected token o at Object.parse (native) at Object.devices.(anonymous function).changeState (/home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:73:32) at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:291:27 at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5) at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:137:13) at Route.dispatch (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5) at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:281:22 at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:354:14) at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14) at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14) at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:410:3) at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10) at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:248:11 at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13) at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12) at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10) at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/lib/read.js:130:5 at invokeCallback (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:224:16) at done (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:213:7) at IncomingMessage.onEnd (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:273:7) at emitNone (events.js:67:13) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:923:12) at nextTickCallbackWith2Args (node.js:511:9) at process._tickCallback (node.js:425:17)
Is the switch type mentioned above the correct one?
-
@ortin I would need the complete payload that is send when changing the state. Please create an issue on github for this. Then set pimatic-echo to debug mode and post the log there. Most interesting part is the log output saying
Request to /api/[userid]/lights/[id]/state
Payload: [json]The json in the payload is what contains the info of the new state. This seems to have a different layout as with the echo dot.
If you have the chance, the same output coming from the echo dot would be interesting, too.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
I will try to make this evening a test with the Dot. But in general the log looks okay from you point of view, especially the discovered device type as asked before?
I created a new issue on git: https://github.com/michbeck100/pimatic-echo/issues/35