In Zabbix a host should always belong to a group. If you set "Group for discovered hosts" to "none", which group would it belong to?

Maybe I described it a little bit unclear...

If some host is discovered it is always added to Discovered Hosts group. Even if it is added to different group in actions. If it is already added to some group during discovery there should be possibility to avoid adding it to discovered hosts.

try adding action (in 2.2) to remove host from that group. does that help ?

In Discovery I can set "remove from group". Yet Auto registration does not have option to remove from group...

Some more information:

In auto registration actions, one can add a host, add the host to the group you want, but not remove it from a group.
So when one manually sets up an agents config, and starts it the first time, the host will automatically be added to zabbix and to the group you want. But you can not remove it from the "discovered hosts" group.

The "solution" i'm currently using is scheduling a script that lists all hosts inside the "discovered hosts" group, and then host.massremove them using the API.
Perhaps a better way would be running a command on the zabbix server through the auto registration action.

The "pretty/easy" way would be that "auto registration" rules support the "remove from group" action just like the "discovery" rules do.

EDIT: or that the "add host" action allows you to set a group. That way the system wouldn't need to add the host to the "discovered groups" action. Although that would change the current behaviour (and that might be bad)

I also would like to see a fix for this. I use auto registration and when we go live with Zabbix I would get way to much (unnecessary) hosts in the Discovered hosts group.