# \[APP\]\[Pro\] \< group \> (3.2.4 - Stable)

**URL:** <https://community.homey.app/t/app-pro-group-3-2-4-stable/3168>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [October 23, 2018, 4:16pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168 "2018-10-23T16:16:01Z")\
**Posts on this page:** 11\
**Page:** 56

<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:** [April 15, 2026, 12:49pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1131 "2026-04-15T12:49:43Z")

</div>

> [@JoshR](#):
>
> Is 160 MB memory usage expected?

Where do you see it ? I’m not using Matter (un)fortunately (even I don’t think it’s relevant in this case frankly), but anyway, my mem util is max. 96MB.

> [@JoshR](#):
>
> And it just crashed again…

Because Homey “OS” restarts it, as it’s above mem limit.

---

<div class="post-metadata">

**Author:** ![Tiwas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tiwas/32/10066_2.png) [@Tiwas](https://community.homey.app/u/Tiwas)\
**Post date:** [April 28, 2026, 12:22pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1133 "2026-04-28T12:22:48Z")

</div>

I hope this hasn’t been answered too many times before - I couldn’t find the answer, though.

I have a group that consisted of two Ikea bulbs. One of them died, so I figured I’d change to Hue. I can add the new bulb, but when it’s added I get an error saying the app couldn’t communicate with the device while setting dim to 1 (or something). Just in case Ikea and Hue couldn’t co-exist, I removed the Ikea bulb from the group, but I’m still getting the same error and the Hue bulb isn’t controlled throught the app.

Am I doing something wrong here? If I create a new group, it works with the Hue bulb - but the whole idea here was to not have to change my flows.

Anyone have any ideas?

---

<div class="post-metadata">

**Author:** ![Hellisloose](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hellisloose/32/55908_2.png) [@Hellisloose](https://community.homey.app/u/Hellisloose)\
**Post date:** [July 14, 2026, 10:25am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1134 "2026-07-14T10:25:43Z")

</div>

Hi,  
Love the app  
Trying to Group Third Reality Smart Soil Moisture sensors (Battery,Temperature and Humidity %)  
I can group all of them, but only temperature and battery is available  
Does the group app support Humidity? Fukt is humidity in norwegian 🙂  
Would like to get the average humidity for 5 sensors

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/2/92fc9e87afdb42d37c87551a82d0dc7ee5be39bf.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/b/8bf66a5c5d58d19ce70802839e80b52236f951bd.png)  
If I create a “Fused Group” I see the sensor but not able to get average

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/6/b6b04cd7e2b0e04dad487b6f9e31b414689489e9.png)

---

<div class="post-metadata">

**Author:** ![Jocke\_Wallen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jocke_wallen/32/76525_2.png) [@Jocke\_Wallen](https://community.homey.app/u/Jocke_Wallen)\
**Post date:** [August 17, 2026, 10:27am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1135 "2026-08-17T10:27:18Z")

</div>

I have a couple of lamp groups all controlled via flows using \< group \> device.

I recently noticed that if/when a \< group \> device is turned on the status isn’t updated in web-app or mobile app (Android) even though everything works as supposed. I.e. I can’t trust the status neither on web-app or mobile app… But when managed “directly” the status is reflected properly.

Annoying as I have to turn the lamps on and off manually to ensure the status is correct.

All \< groups \> contains 3, 4 and 6 IKEA TRÅDFRI bulbs.  
I re-created two \< groups \> recently but the issue remains.

Any idea how/where to troubleshoot?

---

<div class="post-metadata">

**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\
**Post date:** [September 8, 2026, 10:05pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1136 "2026-09-08T22:05:29Z")

</div>

How do I add lights to a group. I no longer see a maintenance option

---

<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:** [September 9, 2026, 4:32am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1137 "2026-09-09T04:32:45Z")

</div>

The maintenance option is still there, unless you mean native Homey grouping option.

---

<div class="post-metadata">

**Author:** ![JMDPC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jmdpc/32/121098_2.png) [@JMDPC](https://community.homey.app/u/JMDPC)\
**Post date:** [September 9, 2026, 10:40am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1138 "2026-09-09T10:40:49Z")

</div>

Thank use, I had used the native group. Once I changed it worked

---

<div class="post-metadata">

**Author:** ![Julian\_Borghuis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julian_borghuis/32/113503_2.png) [@Julian\_Borghuis](https://community.homey.app/u/Julian_Borghuis)\
**Post date:** [September 17, 2026, 4:45am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1139 "2026-09-17T04:45:30Z")

</div>

For the past week, my groups have stopped updating. I’ve tried repairing them, but unfortunately that doesn’t seem to work.

Are there any troubleshooting steps I can try to resolve this issue?

Diagnostic ID: 57eeeecf-d244-4a59-befe-98503bd61a5b

---

<div class="post-metadata">

**Author:** ![hyeung](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hyeung/32/41223_2.png) [@hyeung](https://community.homey.app/u/hyeung)\
**Post date:** [September 25, 2026, 10:39am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1140 "2026-09-25T10:39:40Z")

</div>

> [@Michiel\_van\_Delft](#):
>
> @Jamie

Hi @Jamie,

I’m seeing two issues with the `< group >` app and wanted to check whether these are known problems or whether you’ve seen similar behaviour before.

For context, I’m currently running **`< group >` app v3.3.0**. However, I still have some older group devices that were originally created under **v2.4.304** , alongside newer groups created under **v3.3.0**.

### 1. Unable to add newer v3.3.0 groups into an older v2.4.304 group

I have an older group called **Downstairs Lights** , created under v2.4.304.

I’ve since created two newer groups under v3.3.0:

- **Dining Lights**
- **Kitchen Lights**

I want to include both of these newer groups inside the existing **Downstairs Lights** group.

If I run **Repair** on Downstairs Lights, both Dining Lights and Kitchen Lights appear in the device selection list and I can select them.

However, after completing the repair, they do not appear to have actually been added.

If I go to:

**Downstairs Lights → Advanced Settings → Devices**

the two newer groups are not listed, and they do not appear to participate when controlling the Downstairs Lights group.

So it looks as though the older group can see and select the newer v3.3.0 group devices during Repair, but the membership change is not being saved/applied.

I reproduced this again immediately before generating a diagnostic report.

**Diagnostic for Issue 1:** `3AF235CC`

I would normally consider simply recreating the older `< group >` devices under v3.3.0. However, I’m currently constrained by a separate issue with the **native Homey Alexa integration** , where newly created Homey devices/groups are not being discovered by Alexa.

My existing older `< group >` devices are already known to Alexa and continue to work correctly through the native integration, but any newly created groups cannot currently be discovered. Because of that, recreating my older groups would risk losing existing Alexa voice control with no way to discover the replacement groups.

So at the moment I’m effectively restricted from recreating all of the older groups, which is why being able to repair/update them successfully is quite important.

### 2. “Homey was unable to communicate…” warnings when opening groups

I’m also seeing intermittent warnings when opening some `< group >` light devices, across both older and newer groups.

For example:

> **Homey was unable to communicate with Family 3 while setting onoff to true**

I’ve also seen the same type of warning referring to other lights.

What is strange is that the groups themselves generally appear to work. I can turn the group ON/OFF and the individual lights also respond normally when controlled directly.

In one case, the device named in the warning has changed between different members of the same group.

Immediately before generating the second diagnostic, I opened both **Kitchen Lights** and **Family Lights** , and both displayed this type of warning.

Despite the warnings, the groups themselves still appeared to control the lights normally.

I also noticed an older report in this thread showing very similar behaviour, where Homey reported that it was unable to communicate with a group member while the individual lights themselves continued to respond normally.

**Diagnostic for Issue 2:** `4F101F87`

A few questions:

1. Is there a known compatibility or migration issue when repairing older group devices created under v2.4.304 and trying to add newer v3.3.0 `< group >` devices?
2. Should older groups ideally be recreated under v3.3.0 rather than repaired, and if so, is there any supported migration path that preserves the existing device identity/integrations?
3. Is the intermittent **“Homey was unable to communicate…”** warning a known issue in v3.3.0, particularly where the actual lights continue to respond normally?
4. Could the two issues be related to older group-device data/state being carried forward across app versions?

Many Thanks Jamie!

Kind Regards,

Hung

---

<div class="post-metadata">

**Author:** ![melectro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melectro/32/78999_2.png) [@melectro](https://community.homey.app/u/melectro)\
**Post date:** [October 2, 2026, 4:04am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1141 "2026-10-02T04:04:26Z")

</div>

Hello,

Thank you for this app. It is really useful for someone like me who has 12 RGB lights outdoors that all need to be switched on and off simultaneously.

Unfortunately, the app is missing an important function. If I set the lights to a specific colour, that works fine, but I cannot reset them to a specific colour temperature using either the group’s tile or a Flow card.

It would be highly desirable to have the ability to control and set the colour temperature as well.

---

<div class="post-metadata">

**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\
**Post date:** [October 19, 2026, 8:53am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/1142 "2026-10-19T08:53:14Z")

</div>

Hey @melectro - yep you can absolutely do that, just make sure you add the light mode capability which is used to switch between colour and temp.

[Previous page](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168.md?page=55)
