@tees I would say yes, but as I don’t know which types you actually use, I’m not sure. From the sources of pimatic-shell-execute I would say that ShellSwitch should work OOB with pimatic-echo as it extends from env.devices.PowerSwitch. Just try it, and let us know.

@michbeck100 Hi, i am trying some hours, but i don´t understand the behavior.
I give a device a echo name and activate it for echo, after that i think i had to restart pimatic, then i can discover devices and search in alexa webfrontend for new devices.
After that, sometimes the device is showing up in alexa, but does not react. Sometimes it reactes after some minutes.
But the strangest thing is, that some devices did not show up in alexa and some device switch the wrong devices. When i say switch floorlight, it switches the kitchenlight for example. And i have to discover many times to get a device working at all.

Can someone give me a hint, with a best practice?
And should i only use echo dot gen 2 or gen 3 or does this play no role which version is on or both?
And a nother question, does alexa somewhere store the recent devices? I can delete all devices, but when i discover, alexa founds devices which no longer exist whith this name.

@tees If everything is messed up, I would suggest shutdown pimatic, then remove the devices from Alexa. It seems you must remove one by one. Removing all devices at once didn’t work for me. Then delete the echo-database folder from your pimatic root. Now restart pimatic and do the discovery again. So Devices -> Discover devices and then let Alexa search for new devices. you got 20 seconds for this!

@michbeck100 I tried nearly everything and all you mentioned. I stopped deconz service, pimatic service, disconneted my echo dot 2. gen and deleted every device in webbrowser alexa page and in the android app, multipletimes one by one. I disonnected the raspberry and the echo dot gen 3 and alexa still found devices. When i switched some devices, it switches a nother device with but never the correct one.

After i disconnected dot gen 3 and only activate dot gen 2 alexa found no devices. Then i started pimatic and the discovery found the correct devices and switches the correct ones. So maybe it does not work with dot gen 3 correctly.

@tees I’m starting to see these issues since yesterday, too. at least I can start to investigate now. I’m also having issues with german umlauts in my device names now. See https://github.com/bwssytems/ha-bridge/issues/1151. If anyone has hints how to solve this, please let me know.

The pimatic plugin pages are not updated since some time. It happened before and @mwittig restarted a deamon thats doing the update. That should be done again (and of course solve the problem).
When you go to the update pages an installed plugin will get notice that it can be updated. Because that update page is querying npm directly.

Ok, I’ve managed to install the current version and in the first place the umlauts were not gone. Then I’ve deleted echo-database from the pimatic root folder after stopping pimatic. Then deleted the device list from alexa.amazon.com and searched for devices again. But I unplugged my echo dot 2nd gen before. This time the umlauts were fixed. So it might be because of the new echo-database or because of the old echo dot.

Just in case you have an old echo dot and a newer version, make sure that just the newer versions search for devices.

@michbeck100 I always use the Website alexa.amazon.de to discover for new device and the results are depending on which echo device is activated.
Last it only works almost correct, when only my echo dot 2nd gen is active.

@michbeck100 Hi, i have one Echo dot 3rd gen and one Echo dot 2nd gen. I just had the 2nd gen active and the other deactive to discover initial my devices. The other way, only with 3rd gen or with both active, it does not work, as written before, the wrong devices where switched, i saif Küche and The TV was switched for example.

@tees Does your pimatic-echo run on port 80? I’ve seen elsewhere that the echo dot 2nd gen only works if the port is not 80.
I will try to check which combinations are working for me.
The problem with the wrong devices switched can actually only happen if you remove all devices and discover without resetting the echo-database. Every device has an id, which is just a number. The API is like api/lights/{id} and Alexa just remembers the name and the corresponding id. if this gets out of sync somehow I can imagine that you see such effects.