Andreas Gaus

Yes, the workaround presented by @rovercoder also worked for me: https://github.com/BlazorExtensions/Storage/issues/35#issuecomment-554121492 However, the blazor.extensions.storage.js file (see attachment below) must be always copied to the client's `\bin\Debug\netstandard2.1\dist\_content` folder which is not...

Any news on these topics?

Same issue here with HA-Bridge and > 10 Amazon Echo devices. A caching mechanism seems to store the devices e.g. on Echo with integrated Zigbee Hub or maybe on other...

> One workaround is to keep deleting "one-by-one" (remove-all doesn't seem to work) the devices. Then detect, clear again. > It will clear the detected devices in the other alexa...

Because the caching issue seems to be related to the duplicate names, please find here this related story in detail: https://github.com/bwssytems/ha-bridge/issues/1180#issuecomment-640122295

The workaround described by Superczar https://github.com/bwssytems/ha-bridge/issues/1180 worked fine for me. The details I checked so far: 1) Power off all physical Amazon devices (also software devices like Amazon App on...

Uff! @popy2k14 : good workaround, but too complicated to be really accepted by the folks that have the double name / umlaut issue. I really do not understand why Amazon's...

You are right. I am really frustrated, because of the "duplicated device" and "umlaut" issues arising again and again for years. A complex infrastructure with several companies involved needs a...