Any suggestions from you will be greatly appreciated. I have checked the date/time from my time server on the HC2 and this is within a minute of the time on Echo. I am in Australia, but this shouldn't be the problem. Previously, I had Echo working perfectly with two Homeseer controllers, but having moved to HC2, I can now view all my scenes in Echo, but notthe devices. Thanks everyone for your suggestions on getting devices on a HC2 being seen in Amazon Echo. Sent couple of emails to the support team yesterday but still no response.Īnyone from Australia have any luck finding the device? I am from Australia and currently using the HCL. I am having the same issue, tried numerous different ways, still couldn't find the device in the Alexa App. pages of "+1's" are annoying to work through and voicing general dissatisfaction or opinion, while valued, is not what this thread is for Keep the thread clean and relevant to the task. Let everyone know what you have experienced and add some value to see if we can debug effectively as a community. If the above is the case, can we expect a workaround in the "Custom Skill" ? Will send this detail to support to see if the developers can let us know if it is, in fact, due to restrictions driven from the Amazon build requirement Potentially there are some port (UDP/TCP) access issues as Alexa is largely driven through outside communication I read in another post that a user found "alexaProhibited:true" somewhere in the REST API - I couldn't find it in mine. Checked Discover Devices still worked with other skill - (Logitech Harmony had no issues)
#HOMESEER AMAZON ECHO FULL#
Full reset (deregister AND reset button) of Echo
#HOMESEER AMAZON ECHO INSTALL#
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
#HOMESEER AMAZON ECHO SOFTWARE#
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)
