pimatic-echo@0.5.9

---

Bugfix release:

• #77 add compatibility with node 4 again
• add peerDependencies on package.josn again. this fixes the problem that pimatic does’t find the update

From now on the updates of pimatic-echo will be available in pimatic again.

Hi!
Thanks for your work and commitment to the project, even though it is getting pretty quiet around here…

I am using pimatic for 5 years and just recently upgraded the echo-plugin to 5.9 and my configuration broke…I came from an older version before the id change (5.6?). At first all existing Alexa devices were not responding. After a complete cleanup including the echo-database I tried to rediscover my devices, but that was not successful.

I also tried to install “fauxmo” as a workaround to switch the devices using the URL-interface, but fauxmo also fails, altough I can see a lot of communication going on in the debug logs.

Today I found: https://github.com/vintlabs/fauxmoESP/issues/166
They state that the uniquieid requires this format: “uniqueid”:“F0:08:D1:D8:3B:00:00:11-01” (9 Bytes)
In the source code of pimatic-echo (hue.coffee) I saw that pimatic-echo is using “00:17:88:5E:D3:” + uniqueId + “-” + uniqueId. This is only 7 Bytes, so missing 2…

Have you tried the fix? Unfortunately I could not try it myself. I am not able to work with coffeescript, I have to setup some kind of development environment first .
<Edit>
Today I tried the fix and voilá!!! Everything is up and running. So just add another “00:01:” behind the “D3:” in the above line and you’re good to go and everything is discovered again.
</Edit>
Cheers,
Stefan

@stefanthepi I’ve published 0.6.0. https://forum.pimatic.org/topic/4982/pimatic-echo-0-6-0
This release contains the changes from fauxmoESP project.