I get no answer from the Echo
-
[pimatic-echo] Release 0.5.0
-
@michbeck100 the trick with switching a device while in discovery doesn’t work for me.
I get the following in the log when I try to switch:
18:12:17.420 [pimatic-echo] warn: device with id 01 not found
doesn’t matter which device I try to switch. -
@thex has you researched the Devices after the update to 0.5.2? This Warn mines that alexa dont know this device… or has a old device thats not in the pimatic
-
No I understood that this is not necessary with the fix @michbeck100 implemented.
@michbeck100 said in [pimatic-echo] Release 0.5.0:
@thex Waiting is over, just released version 0.5.1. If you start the discovery mode in pimatic and ask alexa to switch a device, the the user should be added automatically and a new file in echo-database should be created.
-
@thex 0.5.1 wars bugi and with 0.5.2 is needed to rescan
-
Get
npm WARN engine pimatic-echo@0.5.2: wanted: {“node”:">4.4",“npm”:">2.15"} (current: {“node”:“4.8.3”,“npm”:“2.15.12”})
pimatic-echo@0.5.2during update process.
Whats the problem?
Thanks -
@dk00000 Nope this should be no Problem!
-
Is anyone here using just the new echoes with pimatic-echo? It seems that discovery doesn’t work (anymore). I was quite sure that it did work when i tested the last time, but it seems that something changed since then.
See https://github.com/openhab/openhab2-addons/issues/2881 and https://github.com/bwssytems/ha-bridge/issues/810
I can confirm that it doesn’t work for me either.So if you have a working setup don’t remove the devices. I will do my very best to not break this with an pimatic-echo update. The echo dot and echo 1st gen work without problems.
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 -
@michbeck100 said in [pimatic-echo] Release 0.5.0:
o if you have a working setup don’t remove the devices. I will do my very best to not break this with an pimatic-echo
I do, I had the same problem with the new Echo. Yesterday I also received a dot witch could discover devices.
-
I now removed all devices and did a fresh pair… It found all devices but I can’t switch them via the Echo.
The respones is “Gerät XXXX unterstützt das nicht” however I can switch via the Alexa app.Maybe it is a Problem with the dimming as all devices are found as dimmable lights and saying “alexa dim device to x%” turns on a device which was off before…
-
@thex Please open an issue on github.
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 -
@michbeck100 said in [pimatic-echo] Release 0.5.0:
@thex Please open an issue on github.
FYI not necessary any more. It suddenly works. I did trigger the scan via the webinterface of Alexa, maybe it took some time to sync it correctly to the echos.
-
After updating the echo plugin, it doesnt work anymore. There is a directory echo-databse but without a echo-users file in it. Its also not in root. I tried to rescan devices in pimatic with switching a device with alexa without any sucess. All devices I used before are offline in alexa. I use the latest version 0.5.2 - any idea what i did wrong?
-
@michbeck100 - could you help me with my issue?
-
@vivathan use the „discover devices“ button in pimatic when scanning for devices with Alexa. This adds a file called echoUsers to the echo-database folder.
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 did this, but no file was generated - and alexa didn‘t find new devices - existing devices are still offline. Maybe I have port 80 in use. I did netstat where port 80 is listening - but without a PID/program name used. Pimatic runs with port 85. If start the browser with port 80 I got the result „Cannot Get /„ - any idea?
-
@vivathan you must use an echo dot. The new echo isn’t supported anymore.
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 -
@michbeck100 I‘m using ech dot 2. generation
-
@vivathan ok then please completely start from scratch.
- delete echo-database folder and node-modules/pimatic-echo from pimatic and restart pimatic
- remove devices from alexa.amazon.com
- start „discover devices“ in pimatic
- let Alexa search for new devices.
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 -
@michbeck100 I did all steps you described. I also uninstalled echo plugin with restarts after uninstalling and reinstalling. Folder echo-database was created again. If I start “discover devices” in pimatic and let Alexa search for new devices (1 sec after starting discover devices) no devices were found and there is no file in folder echo-database (also not in root).