Checked Discover Devices still worked with other skill - (Logitech Harmony had no issues) Full reset (deregister AND reset button) of Echo Fresh install of Alexa app (have to use device with US iTunes account) Reduce Fibaro ID remote access to a single HC2 (rather than multiples) as the "Alexa tell/ask Fibaro to list Home Center Devices" appeared to not function
Remove multiple layer network structure (disconnect access points and only use router) reconnect everything from scratch including forgetting known networks Reboot everything in various order (Network, HC2, Echo ) The following is a list of steps i have taken to try and remedy the issue. With the above in mind, there are no setup configurations that are outside of what would be considered "correct" in terms of system design. I use the remote access via Fibaro ID as designed - No Port forwarding or alternative setup Echo devices (both "Echo" model - Not Dot) Software version 5264 I am in New Zealand and also have a setup on a bench in Australia Therefore, I list the following steps I have undertaken to date without success in the hope that we can identify a fix/workaround, or simply discover that we should stop trying as it is possible that certain unsupported (officially) use cases won't allow (in the hope that this is the reasoning behind the "Custom Skill" However a number of UK forum users have also experienced the same. I wanted to open a thread to specifically debug this issue, as I accept that Amazon currently only supports (officially) US, UK and EU, and I was expecting that some restriction of cloud to cloud service maybe implemented from the multiple data extraction points involved in the layers of this integration. After the release of the official Alexa skill for Amazon Echo, a number of us are unable to "Discover Devices" after successfully setting up the skill and connecting the Amazon account to Fibaro ID
0 kommentar(er)
