Log flooded with "Unknown application group with ID"

Setup, Configuration and Use Migration
1

Hey guys, I just migrated from OH 2.5 to OH3.1.
While most bindings seem to work fine the logs are flooded with messages like this. I already searched for that message in the forum but I did not find anything.

2021-07-03 21:04:42.156 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:42.159 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:42.162 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:42.166 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:44.022 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:44.026 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:44.030 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:44.033 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:44.037 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:44.041 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:44.045 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:44.049 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:44.053 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:46.246 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:46.248 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:46.250 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:46.252 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:46.254 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:46.256 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:46.258 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:46.261 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:46.263 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:48.219 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:48.222 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:48.225 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:48.228 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:48.235 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:48.238 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:48.242 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:48.246 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:48.249 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:50.141 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:50.144 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:50.146 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:50.149 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:50.151 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:50.153 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:50.155 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:50.158 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:50.160 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:51.956 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:51.959 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:51.962 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:51.965 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:51.969 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:51.972 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '18' found! Ignoring group
2021-07-03 21:04:51.975 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '17' found! Ignoring group
2021-07-03 21:04:51.978 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:51.982 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:53.773 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group
2021-07-03 21:04:53.777 [WARN ] [ib.structure.devices.impl.DeviceImpl] - Unknown application group with ID '16' found! Ignoring group

Does anyone have an idea how this could be resolved?

2

Do you use the digitalstrom binding ? It looks like the warning message is raised by that binding.


    /**
     * Adds the ApplicationGroup of the given groupId to the internal list
     *
     * @param groupID
     * @return true if the groupId is a valid ApplicationGroup id, false otherwise
     */
    private boolean addGroupToList(Short groupID) {
        ApplicationGroup group = ApplicationGroup.getGroup(groupID);
        if (ApplicationGroup.UNDEFINED.equals(group)) {
            logger.warn("Unknown application group with ID '{}' found! Ignoring group", groupID);
        } else {
            if (!this.groupList.contains(group)) {
                this.groupList.add(group);
            }
        }

        return group != null;
    }
3

Yes indeed. And the digitalstrom Binding was also the main reason to upgrade to OH 3. Everything else is working fine with OH 2.5.

I will check the configuration of the binding. Although a quick look at it did not reveal any explanation for this error. I have defined a lot of scenes but all refer to group “2”. Thus I wonder why the error refers to groups 16,17 and 18.

4

I just created a clean setup with only one binding (digitalstrom) and only one thing, the (digitalstrom bridge). No other bindings, things or items. The log messages still appear as soon as the digitalstom bridge goes online.
I checked my digitalstrom server configuration. In fact I have 3 custom groups to group some roller shutters. Those groups have IDs 16,17,18.

So conclusion:

  1. Yes it is related to digitalstrom
  2. It is a bug.
1 Like
5

open/register an issue on github.

6

Already done: [digitalstrom] custom groups on digitalstrom server cause log flooding · Issue #10939 · openhab/openhab-addons · GitHub

7

No, you are violating th digitalstrom concept :

image
image696Ă—623 59.6 KB

I wonder why you can define custom groups, as they don’t exist in the concept.

8

I wonder why the concept does not reflect custom groups while this feature is implemented in the Digitalstrom UI. That would mean that the Digitalstrom violates their own concepts.

9

Indeed, but as the binding follows the concept, it is no bug in the binding.

10

I suppose we could ask for a binding enhancement, that continues to WARN about ignoring custom group, but only once per session, so as to avoid the word bug.

11

As I can’t even remember to have created any groups in the digitalstrom gui I do get exactly the same log entry with 16, 17 and 18. And the table doesn’t say anything about throwing a warning when the group ID is not in the list. In this list there are already three entries with a non related group ID. So why should the binding throw any messages when there are adittional group IDs which are not mentioned in the list. I don’t see any advantage as a user to get this warning information every second in the log file. As we all should agree, even if the user should get a warning, it is not the idea throwing warnings every second to the log file. Especially, when you use an raspberry PI with SD Card this can generate a quick death of the SD-Card.

12

Easy workaround, enter the following on the openHAB console:

log:set ERROR org.openhab.binding.digitalstrom

As written in many other posts/topics, warning log entries can simply be ignored, so this does not harm.

1 Like
13

The log flooding now affected me as well, I’d say these new IDs appeared with the latest dSS server versions, possibly indicating new features appearing which have not been documented in the concept.
As I’m guilty of having introduced the log-flooding, I’ve prepared a pull request which should remedy the problem.

14

Hi together,

maybe my little test can provide some helpful information. I run openHab with digitalStrom since openHAB 1.8 in several versions and I have created some zones, groups and custom scenes in the digitalStrom-GUI to control rollershutters (GR-KL200), awnings (GR-KL210) and lights (GE-TKM210).
Curretly the digitalStrom firmware is 1.16.6.1 (server) and 12.1.4.0 (meters).
openHAB is running in a virtual environment and is currently 3.0.2 in production and 3.1.0 in the test environment. The versions shown in the OH-UI and console for the DigitalSTROM Binding are the same as the OH-version.

These warnings only appear in oh 3.1, in 3.0 there are no warnings abt. unknown allpicaion groups.
The digitalstrom hardware and config should be the same as there is no digitalStrom test-equipment :slight_smile:
The OH test environment is made by cloning the prod system and updated to latest version via openhabian-config, branch “main”.

Frontnail shows the warnings every 2 seconds, always the same 32 warnings for 7 groups in always the same order.
Checking the digitalStrom UI (system properties tree: dSS/apartment/zones/zone0/groups/groupXYZ), the warnings do exactly match the groups, created in the digitalStrom-UI respectively the devices inside each group. Group16 e.g. has 4 devices, so I receive 4 warnings for group 16 etc for 32 devices / warnings in total.

It really looks like that the custom groups are causing the warnings in 3.1. But since there are no warnings in 3.0.2, the reason seems to be located somewhere in the update from 3.0.2 to 3.1.

Regarding the DS-concept. Groups are also created by the DS-software automatically when you set a property likje “windbreaker class” for awnings or rollershutters. This group is also mentioned in the warnings. So DS has invented a “home-made automated concept violation”? :slight_smile:

15

Log flooding has been fixed and is available with latest openHAB 3.2 SNAPSHOT.

1 Like