I just release version 0.3.0 of the pimatic-echo plugin which add two much requested features:

support for all buttons on a ButtonsDevice

whitelist instead of blacklist

For the whitelist there is a new config entry: active. This replaces the exclude flag. It will be migrated after the update. Basically this is the opposite of the exclude flag. But now a new device is not visible by Alexa in the first place. You have to activate it manually.

Please let me know if everything works as expected. If you like my work please consider a donation in the link below

Thanks. Unfortunately I have a problem after the update. The wrong devices are switched. So I deleted all devices in the Alexa app and had them searched again. Only the Philips Hue devices are found. Even searching multiple times didn’t work.

After uninstalling the plugin, restarting, reinstalling and restarting the plugin, I reactivated it and restarted it again. Then the echo settings for the devices were gone (also in the config).

So I restored a backup to the Raspberry Pi. But also with the old plugin (0.2.4) no devices could be found. Plugin removed again and the same procedure to version 0.3.0 again, again no success.

Then the whole network (Router, Switch, Raspi, Echoes,…) restarted - still no success!

No devices (Pimatic) are found even after some time.

I have connected the Raspi via LAN as well as via WLAN (vlan) at the same time.

having another issue!
even if i set devices active : false, there are devices that still show up. the devices are gone when i delete them completely from the config.json
it’s not only buttons devices. i had another common switch device that showed up for no reasons even after setting to false.

if i edit and save the buttons device, after editing active to no / false, it shows the state false but still the device is found in the alexa app. the state is changed ghostly from active false to true, so that the device is available for alexa again.

could it be that there is some kind of “device cache” that is not updated
here is an example of one of the devices (for me it looks ok so far). Maybe it’s the amount of buttons that the plugin cannot handle?

edit:
after editing my config.json and put my shutter devices on top of the config in front of the denon devices, i do not have any devices in the alexa app anymore - the 50 devices limit maybe again …

@leader21 looking at the sources i think i found a bug, but I won’t be able to fix it this weekend.
If a device gets disabled in pimatic it won’t get removed automagically in the Alexa app. You still have to remove it manually.

What should I say, as soon as I unplugged the LAN cable, the devices were found. I had tried everything unsuccessful for hours before.

I would also like to be able to do without the WLAN connection. But then I would have to forego the security I have if I run my IoT devices in my own vlan. Maybe there is a routing rule that allows the Raspi to be reachable from both networks under one IP, but I haven’t managed that yet.

sorry to say no … i installed your latest commit but the behaviour is becoming even more weird.
here’s a copy of the description.xml
strange thing is that the api/xxx/lights is empty and no devices are found.
The shutter / rolladen devices are set active = true but after pimatic has been started the active = true is overwritten with active = false!!

here’s a screen from the debug view (the shutters should be recognized but they aren’t)