# \[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:** 20\
**Page:** 26

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 15, 2023, 9:20am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/524 "2023-01-15T09:20:16Z")

</div>

Thanks @Jamie, much appreciated! 👍🏻😃

---

<div class="post-metadata">

**Author:** ![Erik\_Batenburg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/erik_batenburg/32/12735_2.png) [@Erik\_Batenburg](https://community.homey.app/u/Erik_Batenburg)\
**Post date:** [January 16, 2023, 2:22pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/525 "2023-01-16T14:22:01Z")

</div>

Ha, good to hear . thats the news i was looking for

---

<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:** [January 22, 2023, 12:23pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/526 "2023-01-22T12:23:48Z")

</div>

Hi,  
Been using this app for quite some time now, love it.  
Recently i tried adding a group of alarm/contact sensors - when selecting the sensors under alarm-\>contact alarm, it returns the correct list of sensors. However, when i select the sensor to create the group i get the following error:

An unknown error has occurred [invalid\_class]

Using the v2.5.301 on the homey pro (early 2019).

Any ideas?  
Thx  
Hung

---

<div class="post-metadata">

**Author:** ![AxelS](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/axels/32/69263_2.png) [@AxelS](https://community.homey.app/u/AxelS)\
**Post date:** [January 30, 2023, 8:39am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/527 "2023-01-30T08:39:38Z")

</div>

Thanks for a great app @Jamie 😁

I have created some groups with the Power capability, which I use to see the current energy usage in the device list and to calculate electricity bill per group using the Norwegian Electricity Bill app for Homey (ie “all heating sources on 1st floor”, “floor and heating pump in living room”).

My problem is that these groups are included in the Energy reporting, which skews the statistics with redundant data, since the individual devices are already in the reporting.

Ideally these groups should be kept out of the energy reporting, or perhaps a per-group setting can be added? I don’t know if this is possible, or if Homey always include all power metering.

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [January 30, 2023, 9:08am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/528 "2023-01-30T09:08:15Z")

</div>

Made a [[Feature request] Excluding zones and devices from Homey Energy](https://community.homey.app/t/feature-request-excluding-zones-and-devices-from-homey-energy/74138) for users to be able to ignore some measurements from Homey energy, as they may indeed be irrelevant for various reasons.

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [February 8, 2023, 10:22am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/529 "2023-02-08T10:22:19Z")

</div>

Just to say thank you. I am really enjoying the \< group \> app. It replaces writing & maintaining many flows and allows for easy exclusion or inclusion of devices.

---

<div class="post-metadata">

**Author:** ![Henrik\_Johnsson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_johnsson/32/13707_2.png) [@Henrik\_Johnsson](https://community.homey.app/u/Henrik_Johnsson)\
**Post date:** [February 8, 2023, 1:01pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/530 "2023-02-08T13:01:33Z")

</div>

Exactly that, it becomes a kind of “abstraction layer” between flows and devices. If for some reason a device need replacing you don’t need to touch the flows, just update the group. This is why I have groups with just one device in them.  
And it has a toggle card for lights, something zones doesn’t.

---

<div class="post-metadata">

**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\
**Post date:** [February 11, 2023, 10:52am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/531 "2023-02-11T10:52:26Z")

</div>

Have you got you new Homey 2023 yet?  
Looking forward to \< group \> being updated as it’s the last app I use that’s not compatible yet 😀  
Happy to help / test it you need it.

---

<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:** [February 13, 2023, 3:28am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/532 "2023-02-13T03:28:19Z")

</div>

I have, and its been good, bnut my focus has been on the Alexa app first - as it is a much smaller (if not still complicated) upgrade.

The Group app relies very heavily upon the web-api which has had a new version created and is still a little buggy.

I still plan on updating the group and and ideally looking at increasing the stability even further.

I am excited to see what can be done around the group zigbee available on the new pro, as well as how it will react with really large groups and groups of groups now that the CPU has been upsized.

---

<div class="post-metadata">

**Author:** ![Rrrr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rrrr/32/629_2.png) [@Rrrr](https://community.homey.app/u/Rrrr)\
**Post date:** [February 16, 2023, 2:21pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/533 "2023-02-16T14:21:47Z")

</div>

I want to create a group for a Broadlink device with class other and capabilities as follows:  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/5/55c79b5bddbe62897ce8a60117464d7ff6e75d5a.png)

I do not manage to create the group. When I create a group with class “other” and capability “power”, I can select my device, but that gives me a group that cannot be turned on/off, just show the power measure. Would appreciate to know if it is possible / a tip.

---

<div class="post-metadata">

**Author:** ![Arie\_J\_Godschalk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arie_j_godschalk/32/63027_2.png) [@Arie\_J\_Godschalk](https://community.homey.app/u/Arie_J_Godschalk)\
**Post date:** [February 16, 2023, 4:29pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/534 "2023-02-16T16:29:41Z")

</div>

> [@Rrrr](#):
>
> Would appreciate to know if it is possible / a tip.

Hey Rrrr,

No, with Group, you cannot create a device other than “default” ones, based on class of capabilities.

If you want a device with multiple OnOff and Energie, you need to create an [AVD](https://community.homey.app/t/app-pro-advanced-virtual-device-device-capabilities-app-with-unique-text-status-indicator/68198) from the [Device Capabilities](https://homey.app/a/nl.qluster-it.DeviceCapabilities/) app.  
You can then create an AVD with multiple buttons and a numberfield=energie, and configure the status through flows.

This is how i am re-building my grouped devices: for instance, my lamp-group in the hal im gonna make a AVD which in the Device Tile will show the time left before the group is turned off by a [Chronograph timer](https://homey.app/a/nl.fellownet.chronograph/).

And it will still react to being pushed on the device tile: Having all lights in the hal and it’s time in one device!

---

<div class="post-metadata">

**Author:** ![Homey2](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homey2/32/37387_2.png) [@Homey2](https://community.homey.app/u/Homey2)\
**Post date:** [February 16, 2023, 4:51pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/535 "2023-02-16T16:51:46Z")

</div>

Nice! Will try.

---

<div class="post-metadata">

**Author:** ![Matthias76](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/matthias76/32/47946_2.png) [@Matthias76](https://community.homey.app/u/Matthias76)\
**Post date:** [February 22, 2023, 7:02am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/536 "2023-02-22T07:02:11Z")

</div>

Hi, I get an error when trying to edit a group. I tried to delete an entry:

 ![Screenshot_20230221-203511](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/2/72265e18ce923ca223cf8cac54972d2fb82dda4e.png)

---

<div class="post-metadata">

**Author:** ![akafester](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/akafester/32/298_2.png) [@akafester](https://community.homey.app/u/akafester)\
**Post date:** [February 23, 2023, 9:29am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/537 "2023-02-23T09:29:51Z")

</div>

I haven’t found an answer to this, but would it be possible to have a setting for a group motion that at least 2 should be on before the group goes active?

---

<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:** [February 23, 2023, 11:53am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/538 "2023-02-23T11:53:48Z")

</div>

That already exists, you can choose min/max/ave/all etc.

---

<div class="post-metadata">

**Author:** ![akafester](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/akafester/32/298_2.png) [@akafester](https://community.homey.app/u/akafester)\
**Post date:** [February 23, 2023, 12:17pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/539 "2023-02-23T12:17:56Z")

</div>

Then I must be doing it wrong.  
I have created a group with 3 motion sensors. The only setting i have in that group is:

- On if any devices are on
- On if all devices are on

I can’t set a min/max/ave?

---

<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:** [February 23, 2023, 3:35pm UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/540 "2023-02-23T15:35:49Z")

</div>

You look to be right,

When I get around to updating the app, ill look at adding this new feature.

---

<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:** [March 3, 2023, 5:02am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/541 "2023-03-03T05:02:25Z")

</div>

Currently I would say this app expects a medium level of understanding to use (it asks you to select device capabilities). But the more detailed features such as how it reacts when one light is on etc, are hidden away in the settings.

To me it feels like a compromised solution, not easy to use for first time users **and** features are hidden away, so I have been thinking about how I could improve the user experience. I think there are a couple of options but most come down to :

Remove the need to select capabilities have the app automagically determine and manage based on the device class (light/socket/speaker etc).

The the question becomes where how to allow the app to do everything we want it to do and this is where I was wondering if anyone has any opinions :

1. Separate the use cases of the app - and have two apps, ie. and create a ‘basic’ version.
2. Move more of the advance features into the application settings so that they can be managed from in there.
3. Remove advance features from the current drivers but add a new “advance” group driver which has these extra abilities.

Let me know if anyone has any thoughts on what the best approach for the new / pro users is.

---

<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:** [March 3, 2023, 5:54am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/542 "2023-03-03T05:54:40Z")

</div>

> [@Jamie](#):
>
> Remove the need to select capabilities

For me, I had to experiment with it in case of some “custom” devices, eg. created via MQTT Hub, not sure if same might happen in case of Device capabilities, possibly Virtual Devices etc.  
So loosing this option could be bummer for more advanced users. Would it be possible to keep it and during Group device creation phase to simply choose method?

> [@Jamie](#):
>
> Separate the use cases of the app

Would it be resulting in two apps required? I’m running out of memory already on my Homey…

If I understand the use cases, the most preferred would be probably Option 2 - but I’m little bit lost here because there are already advanced settings in the settings and with remark above l’m not sure how it correlates.  
_But let’s see if others understood this fully then feel free to ignore my thoughts 🙂_

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [March 3, 2023, 9:20am UTC](https://community.homey.app/t/app-pro-group-3-2-4-stable/3168/543 "2023-03-03T09:20:01Z")

</div>

I would go for option 2 as well.  
No need for an extra app or device choice then (that would be confusing for new users too imo).

Are these changes inevitable when updating the app to SDK 3 or do you plan to update this part first?  
I very much welcome the proposed changes and evt new features, but would welcome an update to SDK 3 most atm… If there is no further delay, my new HP23 is shipped next week and this app is one of the last on SDK 2 in my case…  
No offence of course, I do understand you are doing this voluntary. Which is very much appreciated! 👍

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

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