Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

Fibaro - Alexa/Google Home integration


Question

Posted (edited)

While Fibaro devices seen in Alexa, but no sensor is included. In addition, Fibaro devices cannot trigger any Alexa's routine. By the way same issue with Google home.

Here is the answer and current status with Fibaro skill.

 

Short answer: Fibaro HC3 sensors don’t appear in Alexa because the official Fibaro Alexa skill only exposes basic device types (like switches, dimmers, and scenes), while sensors (motion, contact, temperature, etc.) are not implemented in the Alexa Smart Home API for Fibaro HC3. This is a limitation of the integration, not of Alexa itself.

 

🔎 Why HC3 sensors don’t show up in Alexa

  1. Skill limitations
    • The Fibaro Smart Home skill for Alexa was designed mainly for lights, plugs, and scenes.
    • It does not publish sensor capabilities (motion, door/window, temperature) to Alexa’s cloud.
    • As a result, Alexa cannot “see” those devices, even though they exist in HC3.
  2. Alexa Smart Home API requirements
    • For a sensor to appear in Alexa, the manufacturer must implement Amazon’s Sensor APIs (e.g., Alexa.MotionSensor, Alexa.ContactSensor, Alexa.TemperatureSensor).
    • Fibaro has not added these interfaces to their HC3 Alexa skill, so Alexa ignores those endpoints.
  3. Z‑Wave vs. Alexa compatibility
    • HC3 is a powerful Z‑Wave hub, but Alexa doesn’t natively understand Z‑Wave.
    • Alexa only knows about devices that the Fibaro skill explicitly exposes.
    • Even if HC3 recognizes a Z‑Wave sensor, Alexa won’t unless Fibaro’s cloud integration passes it through.
  4. Community reports
  • Users on Fibaro’s own forums confirm that Alexa discovers no HC3 sensors, only switches and scenes.
  • This has been a long‑standing request, but Fibaro has not expanded the skill to cover sensors.

 

Workarounds

  • Use Fibaro → Home Center → Alexa scenes
    • You can create a scene in HC3 that reacts to a sensor (e.g., motion detected → turn on light).
    • Then expose that scene to Alexa and trigger it by voice.
    • Downside: Alexa still doesn’t “see” the sensor itself, only the scene.
  • Bridge through another hub
    • If you connect your Fibaro sensors to SmartThings, Hubitat, or Home Assistant, those platforms can expose sensors to Alexa (because they implement the Sensor APIs).
    • This adds complexity but gives you full Alexa automation.
  • Wait for Fibaro skill updates
  • Fibaro would need to update their Alexa skill to support sensor APIs. Until then, sensors won’t appear natively.

 

 

The question if Fibaro team is working to provide a solution for this well-known limitation?

 

It’s not just about technical capability — it’s about market positioning.

 

I think by exposing sensors through Alexa’s Smart Home APIs (or Google Home), they’d suddenly become far more attractive to mainstream smart home buyers who want plug‑and‑play convenience.

Edited by cag014
  • Like 3

7 answers to this question

Recommended Posts

  • 0
Posted

@cag014 Thank You for feedback

 

Sensors and Alexa

Yes you got right, we don't support all sensors in Alexa. Today we only get temperature sensor and contact sensor for gate (category other)

 

We got 2 reasons for it

 

1) there is a limitation device how much you can link in alexa, and you have limited time to send list of device

2) there is a limitation respons - when we trying to give all events from device like energy, all temperature etc we are over the limit, that way we focused on actors over sensors (shutter, light swith, light dimmers, plug, blinds, gates, RGBW,)

 

Please login or register to see this image.

/monthly_2025_10/image.png.10262eff0aa330fdc9b03c91aae1786c.png">image.png

 

Based on changed i see more development and new features related to Google, like plan to introduce new speaker with Gemini new type devices and new Home Api, on Amazon side is more quiet 

 

I am open to your suggestions and proposals. Let's figure out how to implement them without harming the actors, and the direction in which you want our integration to go

 

 

  • 0
  • Inquirer
  • Posted (edited)
    3 hours ago, A.Socha said:

    2) there is a limitation respons - when we trying to give all events from device like energy, all temperature etc we are over the limit, that way we focused on actors over sensors (shutter, light swith, light dimmers, plug, blinds, gates, RGBW,)

     

    Based on Alexa requirements there is no limit of how many devices could be integrated.

    Here a real-life example: I had HC2 integrated into Alexa and now have integrated HC3 and currently Alexa keeps HC2 and HC3 devices in the list and all 98 devices are working fine and could be controlled.

    In addition, I have about 60 devices from other application (Air conditioner, TV, dishwasher, washers and etc)

    You are saying that temperature sensors are included, but they are useful because they cannot trigger Alexa routines and I don't understand why you expose them to Alexa if the user has no option to use it.

    But maybe I'm wrong, could you please provide an example what can I do with temperature sensor in Alexa routine?

     

    My "request" is to be able to use devices as a trigger not only control.

    Regarding number of devices, you can give an option to user to select if the device should be exposed to Alexa (same assignment that we have for users). By the way have deleted devices that I don't use from Alexa list, but after while they have added again (probably Fibaro skill refreshes the list.

    Frankly speaking out of 98 integrated devices, I need just 13.

    By researching Fibaro skill and Alexa, looks like that some APIs have been not implemented. All third-party app (like Smart life, Smart things, Hubitat and others) can expose devices and could be used as triggers in Alexa.

     

    Same issues with Google home.

     

    Since I have third-party security system that cannot be integrated in HC3, it is very important (at least for me) to be able to trigger Alexa by motion sensors and to control security system which is integrated in Alexa.

    Also, I need temperature sensors to trigger climate control system. Right now, I am using workaround based on Voice Monkey skill (Smart Home + Routine Triggers) which triggers Alexa using HTTP commands sent from HC3.

    Edited by cag014
    • Like 1
    • 0
  • Inquirer
  • Posted

    May I ask if any user has been able to use temperature sensor in Alexa?

    • 0
  • Inquirer
  • Posted (edited)
    3 hours ago, A.Socha said:

    Based on changed i see more development and new features related to Google, like plan to introduce new speaker with Gemini new type devices and new Home Api, on Amazon side is more quiet 

     

    So, in the near future we will see sensors and devices could be used as triggers in Google?

    On Amazon side, I have raised a question to their support team, what we are missing in Fibaro Skill to use sensors and devices as a trigger. Will keep you updated.

    Edited by cag014
    • Like 1
    • 0
  • Inquirer
  • Posted
    3 hours ago, A.Socha said:

     

    I am open to your suggestions and proposals. Let's figure out how to implement them without harming the actors, and the direction in which you want our integration to go

     May be just implement as suggested?

    • For a sensor to appear in Alexa, the manufacturer must implement Amazon’s Sensor APIs (e.g., Alexa.MotionSensor, Alexa.ContactSensor, Alexa.TemperatureSensor).
    • Fibaro has not added these interfaces to their HC3 Alexa skill, so Alexa ignores those endpoints.
    • 0
    Posted

    @cag014

     

    I talked with developer

    • There is a limit of 300 devices (devices + scenes)
    • We need to send it during discovery so to improve our process of linking maybe option on hub with devices should be visible in Alexa/google, where user manually chose device and scenes and we prepare json witch we send during discovery  - to reduce time of generating it during process of discovery to made it in time limit
    • We need to change API to support Sensor API

    I will try to put it on our roadmap after discussion with board, however, I cannot promise how high a priority it will be given.

     

    For google we want to migrate to new Home API with will allow to control devices by Gemini

    • Like 1
    • Thanks 3
    • 0
  • Inquirer
  • Posted (edited)
    49 minutes ago, A.Socha said:

    There is a limit of 300 devices (devices + scenes)

    According to Amazon there is no limit on total number of connected devices.

    Device groups are limited to 10 devices, and you can only register up to 6 primary devices on an Amazon account for Prime Video and other services.  

    No other limitations.

    But I don't think anyone needs to expose 300 devices to Alexa.

    I am glad that you pointed a good solution for the future integration with Google and Alexa.

    Thank you

    Edited by cag014

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...