"ADD NODE" produces "too much" config

snmp-config.xml:
----------------
<snmp-config xmlns="http://xmlns.opennms.org/xsd/config/snmp" retry="1"
timeout="1800" read-community="myCommunity" version="v2c">
</snmp-config>
----------------

• so the snmp-community is system-wide configured, right?

When i click "ADD NODE", i can fill the form.
Prov. Group: i only have one
IP Address: 10.1.10.1
N. Label: NET_SWCORE01
Category: Switches + HQ
Community String: LEFT BLANK (i want my default to be used)
Version: LEFT v2c

now the "Provision" Button produces this xml entry:
---------------------------------------------------
<node node-label="NET_SWCORE01" foreign-id="1258381425210">
<interface status="1" snmp-primary="P" managed="true" ip-addr="10.1.10.1">
<monitored-service service-name="ICMP"/>
<monitored-service service-name="SNMP"/>
</interface>
<category name="Switches"/>
<category name="HQ"/>
<asset value="" name="username"/>
<asset value="" name="password"/>
<asset value="" name="enable"/>
<asset value="telnet" name="connection"/>
<asset value="" name="autoenable"/>
</node>
---------------------------------------------------
and this snmp-conf entry:
-------------------------
<definition read-community="" version="v2c">
<specific xmlns="">10.1.10.1</specific>
</definition>
-------------------------

so there are 2 problems:
1. <monitored-service service-name="SNMP"/>
— this is a problem on devices without snmp service -> it displays ugly outage messages on new nodes until i manually set SNMP to "unmanaged" on this node

2. <definition read-community="" version="v2c"><specific xmlns="">10.1.10.1</specific></definition>
— it uses "" as community -> it does not use my default snmp settings