I am hoping for some useful advice from people with at working Alexa / HC2 system. After endless hours of Fibaro Support emails, testing, deleting and restoring my LAN, HC2 and Alexa, my problem still remains the same:
Alexa picks up my command (e.g. "Alexa, Turn off Kitchen Table") and one out of three things happen: (1) Light is turned off, Alexa responds "OK" (2) Light is turned off, Alexa responds "Sorry, Kitchen Table is not responding" (3) Light is NOT turned off, Alexa responds ""Sorry, Kitchen Table is not responding". Totally erratic, no pattern. Failure statistics: 1 out of every 4 (25%, N=40). Enough to reduce the WAF to Zero.
Fibaro Support finally made me aware that the problem is response time: If the time from command is given to remote Alexa/Fibaro server response is received, exceeds 7 seconds, Alexa times out. Fibaro Support keeps on insisting that the problem is my LAN/Internet connection. I have however gone so far as to disconnect all other devices on my net but for the HC2 and Echo Dot and confirmed my Internet speed is 92 Mbps Up/Down. Even followed the rather extreme Fibaro Support advice of reducing the physical distance between HC2 and the Fibaro Dimmer2 to less than 300 cm (!). I am now starting to suspect that the problem is the Alexa/Fibaro API server integration.
And I have of course upgraded firmware, reconfigured z-wave net, dis/enabled Fibaro skills, deleted and restored my HC2 from Fibaro ID, confirmed Alexa has selected my HC2, reset the Echo Dot, reset the HC2 and restored the system from backup and so on and so forth. Friendly guys at the Fibaro Support desk, but so far advice has not brought me any visible result, except for loosing all my custom Scene/VD icons, which apparent are not part of the HC2 back up file
Question
jodohl 8
I am hoping for some useful advice from people with at working Alexa / HC2 system. After endless hours of Fibaro Support emails, testing, deleting and restoring my LAN, HC2 and Alexa, my problem still remains the same:
Alexa picks up my command (e.g. "Alexa, Turn off Kitchen Table") and one out of three things happen: (1) Light is turned off, Alexa responds "OK" (2) Light is turned off, Alexa responds "Sorry, Kitchen Table is not responding" (3) Light is NOT turned off, Alexa responds ""Sorry, Kitchen Table is not responding". Totally erratic, no pattern. Failure statistics: 1 out of every 4 (25%, N=40). Enough to reduce the WAF to Zero.
Fibaro Support finally made me aware that the problem is response time: If the time from command is given to remote Alexa/Fibaro server response is received, exceeds 7 seconds, Alexa times out. Fibaro Support keeps on insisting that the problem is my LAN/Internet connection. I have however gone so far as to disconnect all other devices on my net but for the HC2 and Echo Dot and confirmed my Internet speed is 92 Mbps Up/Down. Even followed the rather extreme Fibaro Support advice of reducing the physical distance between HC2 and the Fibaro Dimmer2 to less than 300 cm (!). I am now starting to suspect that the problem is the Alexa/Fibaro API server integration.
And I have of course upgraded firmware, reconfigured z-wave net, dis/enabled Fibaro skills, deleted and restored my HC2 from Fibaro ID, confirmed Alexa has selected my HC2, reset the Echo Dot, reset the HC2 and restored the system from backup and so on and so forth. Friendly guys at the Fibaro Support desk, but so far advice has not brought me any visible result, except for loosing all my custom Scene/VD icons, which apparent are not part of the HC2 back up file
Any wisdom out there?
Link to post
Share on other sites
33 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.