pimatic-echo@0.5.6

---

Just released a minor update to pimatic-echo.

Changes:

Move from int for index to string using device id, seems to work, too. This fixes the issue, that alexa mixes up devices if a device is deleted or moved in pimatic

Background: the devices that were published for alexa were indexed using an integer index, which was just the position in the device list. When deleting one of these devices the index was broken, because after restart the list was created again, but with different indexes for the devices. This lead to either Alexa
not finding devices anymore or even switching the wrong device.
No I’m using the unique id of the device, as it seems that Alexa also works with strings.

Please report if you have any issues with this change. I did test this on my setup, but it turns out that the Echos are sometimes behaving pretty strange.

IMPORTANT: You will have to delete your devices from Alexa and start over again. Sorry for that!

Really nice update. I was fighting the last days with exactly this problem. I did test different setups and sometimes it ends in the szenario, that the found devices was named by number (first device, second device… twentyth device). Only a reset of the relevant echo fixed the problem. I will update and can report then, because I really have to delete a device.

Unfortunately my test on my production system weren’t really successful, hope it’s better on your side. But chances are good that I have to revert that change.

Hello! How do I update? The pimatic update page does not show me that the echo plugin has a new update.

@andi-tudor It was shown almost immediately on my system. Maybe restart pimatic?

@andi-tudor said in pimatic-echo@0.5.6:

Hello! How do I update? The pimatic update page does not show me that the echo plugin has a new update.

Same for me. Even after restart.
I am still on version 0.5.4. I have never seen 0.5.5 in the update list. Other plugins as the gBridge, charts or stats where shown in the last days. Seems something went wrong in this regard.

I’m not using echo, under the ‘browse pluging’ tab in pimatic node 4.x and node 10.x,
I see the following to install

Oh yes, I’ve made a change to the pimatic core to make the updates work. Usually the update server url is http://api.pimatic.org/plugins?version=0.9.54. As you can see this url shows just the old version of the plugin. When pointing to http://api.pimatic.org/plugins it shows the correct version. I don’t know what the problem is, as I don’t host the plugins page. @mwittig maybe you can lighten us up?

Hello! …any progress in solving eco update?

I noticed today that I could see a new update to the gbridge plugin. The eco plugin still does not appear wet.

@andi-tudor Never mind, I had to unpublish the release because I had problems with the changes. So in the end it wasn’t too bad that the update server didn’t work. I have to come up with a different solution. Sorry for that.