# Mender 2.5.0 Problems with Filters, Hostnames and More

**URL:** <https://hub.mender.io/t/mender-2-5-0-problems-with-filters-hostnames-and-more/2683>\
**Category:** General Discussions\
**Created:** [October 16, 2020, 8:33pm UTC](https://hub.mender.io/t/mender-2-5-0-problems-with-filters-hostnames-and-more/2683 "2020-10-16T20:33:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mzedel](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mzedel/32/261_2.png) [@mzedel](https://hub.mender.io/u/mzedel)\
**Post date:** [October 17, 2020, 9:34am UTC](https://hub.mender.io/t/mender-2-5-0-problems-with-filters-hostnames-and-more/2683/2 "2020-10-17T09:34:17Z")

</div>

Hi @ckelloug2,

thanks for using Mender and I’m sorry to hear 2.5.0 is causing issues for you.

Can you please try entering the deviceauth container, e.g. running:

`$ docker exec -it <name of your deviceauth container> sh`

Then, from the container, you can run:

```
$ deviceauth propagate-inventory
$ deviceauth propagate-inventory-statuses
$ deviceauth propagate-inventory-id-data

```

This will sync all inventory, statuses and identity\_data attributes from deviceauth to inventory.

Please let us know if it solves your issue.

Regarding the unassigned group, it is only relevant for statically grouped devices, since a device might join a dynamic group any moment. So a list of unassigned devices that takes all groups (static and dynamic) into account might be outdated the second it is sent from the backend. Does this clarify the location a bit? With that in mind, would you consider a different location to be more intuitive?

---

_[View the full topic](https://hub.mender.io/t/mender-2-5-0-problems-with-filters-hostnames-and-more/2683)._