HC3 and Alexa skill

[squirblej 2]

Hi folks - am I right in thinking that the Fibaro Alexa Skill doesn't work with the HC3?

[Guest Gaff]

On 3/13/2020 at 8:51 PM, squirblej said:

Hi folks - am I right in thinking that the Fibaro Alexa Skill doesn't work with the HC3?

I can confirm it's not working with my HC3. Although the skill ist shown "active" and all the devices are listed in the Alexa app, she says "this skill isn't active" (something like that) on every command. 

[Macschimmi 35]

You have to activate the device used for Alexa in the Fibaro Cloud.
Integration - active

Google and Alexa work for me

[squirblej 2]

On 3/16/2020 at 8:27 PM, Macschimmi said:

You have to activate the device used for Alexa in the Fibaro Cloud.
Integration - active

 

This fixed it.  Thanks so much!  Hidden setting...

[DICI 0]

Where do I find this ?

[interested 10]

go to id.cloud.fibaro.com & under MENU > Remote Access > more  .... you can see a similar window

 

 

 

 

Please login or register to see this attachment.

[Kaffeeloeffel666 0]

I have the same issue and can't find a resolution...
1. I have only one HC3 as I sold my HC2 already. I moved all 129 actors and sensors to the new HC3 already. The 'Integrations' = Active flag in the Fibaro Cloud setup is set.

2. I use a Fibaro ID 'Admin', which has the HC3 owner rights.

3. There is a user account 'Alexa', which has separate credentials but full access to all relevant devices. All users are synced with the HC3.

4. I activated the Fibaro skill for Alexa and used the Fibaro ID 'Admin' when I tried the first time. --> No success. No devices found.

5. I deactivated the skill again and used the Fibaro ID 'Alexa' when I reactivated the skill. --> same result. No devices found, but also no error message.

 

As there is no log file I am a lost where to start working on a resolution. All try & error activities failed so far.

It worked well on my old HC2 for months. Obviously the new HC3 makes additional trouble.

 

All recommendations are welcome. 

 

Cheers

  

[Guest mol7os]

Anyone got this fixed?

 

I have the same issue and getting crazy on it.
Bad enough that the bug seems to be quite old and there is no official guide to a solution.

 

Thanks for any hint.

[Kaffeeloeffel666 0]

2 months ago the Fibaro team reset my "Integration = Active" setting in my Fibaro ID account. I did not request that and I had no direct contact to Fibaro. I just received an email telling me that the Integration = Active was reset.

Since that day it's working well again.

Based on my experience I guess the issue happens, when a second HC was set up in the Fibaro ID some time before. When the second HC got removed, it screwed up the Integration = Active setting. Even if it shows up correctly, it doesn't work.

Maybe a complete new Fibaro ID and HC setup helps!?

[moltos 4]

A creation of a new Fibaro ID did not changed my situation.

It feels more like an HC3 issue than a real Fibaro ID one.

 

After checking this i have switched back to my old account and still waiting to get my issue fixed.

[CharlyBlack 0]

Any news?

 

I am new to all of this Fibaro & Zwave thing. I have a HC3 and I managed to make a shutter roller work, but before add all the other devices I tried to make it work with Alexa but I dont have no clue on how to make it properly.

 

Some info:

- Alexa doesn't discover fibaro hc3 nor the shutter roller

- I have "Integration: Active" in the cloud

- I installed the Alexa skill

- The shutter roller works from the Fibaro app

 

Should Alexa discover a HC3 or only the devices like Shutter Roller, Switches, etc.?

 

Any clue about what I can try now?

 

Thanks

[AU. 0]

I have experienced a similar issue migrating from HCL to HC3 - lost functionality via Alexa App whereas it was previously was quite good. 

 

I have changed Integrations = Active to the HC3 in id.cloud.fibaro.com.

Any devices which were already identified in Alexa from the HCL are now unresponsive and cannot be re-discovered.

Any new devices added via the HC3 can be discovered in Alexa, but they are unresponsive. 

I have removed Fibaro skills from Alexa and then re-added...  No change

I have deleted unresponsive devices from Alexa added via the HCL, but they are not re-discovered.

 

If anyone has experienced same as above and has an answer, I'd love to hear your solution.

... and I will sing a song about the Fibaro Ninja who saved the day. 

 

[aleilia 0]

I have the same problem after migrate to hc3.is there a solution?

 

[ABDULLAH258 4]

Hello 

I want to play skill called (Alarm sound) which is enabled in Alexa by scene.

Is there is any way to do that?

How can I found the API of this skill or any skill to play it by scene.

[ppeterr 205]

Please login or register to see this link.

 

With this you can do a lot with Alexa, for instance let her talk anything.

 

But also, you can "send" through the amazon servers things like "alexa say: start the alarm scene" 

 

Its pretty complex, and you need a device running linux. From there you can use the HC3 to trigger url's to execute from that script.

 

I use it for my doorbell, when someone presses the doorbell, the script sends "there is someone at the door" to alexa. And it starts a scene, that shows the video feed from the doorbell on the echo show.

 

 

Edited November 15, 2022 by ppeterr