# Rollershutters no longer operational in google assistant

**URL:** https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544
**Category:** Questions & Help
**Tags:** homey-pro-2023
**Created:** [June 25, 2026, 12:56pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544 "2026-06-25T12:56:58Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Priknr1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/priknr1/32/558_2.png) [@Priknr1](https://community.homey.app/u/Priknr1)
#### Post date: [June 25, 2026, 12:56pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/1 "2026-06-25T12:56:58Z")

</div>

Since recently, some of my roller shutters are no longer operated from within Google home .

Upto 2 weeks ago: Hey google, put all shutters to 50% → 5 shutters start moving  
Now: Hey google, put all shutters to 50% → 1 moves (FGR-222), 4 do not (FGR\_223)

**Bug Report – Fibaro Roller Shutter 3 devices are no longer controllable in Google H ome**

**Environment**

- Homey Pro (Early 2023)
- Homey firmware: **13.3.0**
- Fibaro app: **3.8.7**
- Google Home
- Google Nest Mini
- Google Nest Audio
- Google Gemini enabled on Android p hone

**Devices**

**Working**

- 1 × Fibaro Roller Shutter 2 (FGR-222)

**Not working**

- 4 × Fibaro Roller Shutter 3 (FGR-223)

All devices are configured as **Sunshade** in Homey and have been successfully calibr ated.

**Descr iption**

All Roller Shutters work perfectly in Homey.

After synchronizing with Goog le Home:

- All devices are imported.
- In Google Home All devices; have device typ e **Blinds**.
- In Google Home All devices; Manufacturer is shown as **Homey**.
- In Google Home All devices; Connected via **Homey**.

However:

- The **FGR-222** opens a control screen in Google Home with **Up** and **Down** buttons and is fully c ontrollable.
- The **FGR-223** devices open only the information page. There are **no Up/Down buttons and no pos**** ition slider**.
- Voice control no longer works for the FGR-223 devices from:
  - Google Home app
  - Google Nest Mini
  - Google Nest Audio

**Expected behaviour**

All Roller Shutter devices should expose the same controls in Google Home and should be control lable by voice.

**Actual behaviour**

Only the FGR-222 is treated as a co ntrollable blind.

The FGR-223 devices are recognised as blinds but Google Home does not ex pose any controls.

**Troubleshooting already performed**

- Updated Homey to firmware 13.3.0.
- Updated Fibaro app to 3.8.7.
- Removed Homey integratio n from Google Home.
- Linked Homey again.
- Executed “Sync my devices”.
- Enabled Google synch ronization in Homey.
- Waited for synchro nization to complete.
- Verified all Roller Shutter 3 d evices are calibrated.
- Verified all Roller Shutter 2 and Roller Shutter 3 devices are configured as **Sunshade**.
- Verified all devices work correctly inside Homey.
- Verified Google Home identifi es all devices as **Blinds**.

None of these st eps changed the behaviour.

**D ev eloper T o ols obser vations**

**FGR-222**

Driver:

- com.fibaro:FGR-222

Capabilities include:

- dim
- windowcoverings\_state

**FGR-223**

Driver:

- com.fibaro:FGR-223

Capabilities include:

- dim
- measure\_power
- meter\_power

The FGR-223 does not expose windowcoveri ngs\_state, unlike the FGR-222.

I do not know whether this difference is intentional, but it appears to correlate with Google Home exposing controls for the FGR-222 while not exp os in g controls for the FGR-223 .

**Additional observations**

This exact setup worked correctly in Google Home in the past. (Hey google, put all blinds to 50% worked for all, now only for my 1 FGR-222 device)

The problem appeared after the r ecent Google Home / Gemini changes.

The FGR-223 devices are still fully controllable from Homey itself, so the issue only af fe c ts the Goo gle Home integration.

**Question**

Could you verify whether the Google Home integration is exporting the FGR-223 with the correct Google device traits and capabilities?

Since the FGR-222 and FGR-223 behave differently in Google Home despite both being configured as window coverings in Homey, this may indicate a regression in the Google Home export or a compatibility issu e wi th the current Google Home platform.

---

<div class="post-metadata">

### Author: ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [June 25, 2026, 1:04pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/2 "2026-06-25T13:04:02Z")

</div>

I think you should report that to Athom, since they are the developer of the Fibaro app

> **[Support | Homey](https://homey.app/en-us/support/)**

---

<div class="post-metadata">

### Author: ![Priknr1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/priknr1/32/558_2.png) [@Priknr1](https://community.homey.app/u/Priknr1)
#### Post date: [June 25, 2026, 1:21pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/3 "2026-06-25T13:21:47Z")

</div>

Have you tried it yourself. I have been there. I keep getting forwarded to this forum.

They start looking like KPN and Microsoft

I have no idea where to actually contact them.

Even an email to supprort@… Gave me a reply. This is not the correct way to start a topic. Your issue is not being handled this way.

---

<div class="post-metadata">

### Author: ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [June 25, 2026, 1:23pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/4 "2026-06-25T13:23:06Z")

</div>

If you can’t create a support ticket, you just need to select “My Homey isn’t listed” at their support page and then you can create a ticket

---

<div class="post-metadata">

### Author: ![Priknr1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/priknr1/32/558_2.png) [@Priknr1](https://community.homey.app/u/Priknr1)
#### Post date: [June 25, 2026, 1:29pm UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/5 "2026-06-25T13:29:04Z")

</div>

That was a great tip! Thanks

---

<div class="post-metadata">

### Author: ![Priknr1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/priknr1/32/558_2.png) [@Priknr1](https://community.homey.app/u/Priknr1)
#### Post date: [June 26, 2026, 7:52am UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/6 "2026-06-26T07:52:58Z")

</div>

As expected Athom just says. Not our problem, go fetch with Google.  
I even pointed them to a possible solution, but hey, why make an effort to fix it from your side if your could also lay it with someone else.

---

<div class="post-metadata">

### Author: ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)
#### Post date: [June 26, 2026, 8:22am UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/7 "2026-06-26T08:22:22Z")

</div>

Well, it’s an issue in **their** Fibaro app. The `dim` capability shouldn’t be used for this, they should use `windowcoverings_set`. Dim is only for lights.

So you should just create another ticket​😉

---

<div class="post-metadata">

### Author: ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)
#### Post date: [June 27, 2026, 9:46am UTC](https://community.homey.app/t/rollershutters-no-longer-operational-in-google-assistant/156544/8 "2026-06-27T09:46:31Z")

</div>

> [@Priknr1](#):
>
> FGR-223

Something is probably different at you end, as I have only FGR-223 and all are shown like this in a Google Home :

 ![Screenshot_2026-06-27-11-46-11-66_2d2bd67b5e15ae98c151ac739cd6881e](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/b/ab626ffeb8fe495f904f2b61f87ce9249cbc4ac0.jpeg)

Naturally don’t forget to set this property as well

 ![Screenshot_2026-06-27-11-47-19-25_4bbfc4a7dd885a2bb189f300112a7ed4](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/1/e1ba100ae0768bc2185d6b31f6e6f4e039c1cbe6.jpeg)
