@crumpy10 Well, that may seem confusing, but this is how the binding does work.
You may create as much things as you like and it doesn't matter if you create those things via PaperUi or the text files. If node id and child Id do match on an incoming messages the thing gets updated.
Discovery by Openhab is only possible if and when the node presents itself. In most MySensors sketches this is done on initialization of the code. This is why a reboot of the node is needed for discovery. There is no list of known nodes (in the gateway) that the binding may read out.
There is some code in the binding that should prevent the discovery (inbox) of already known things but that doesn't work in some cases. I've the same problem with my sonos things which get discovered all the time although I've already configured them via text files.
The discovered things in inbox will disappear after a timeout.

@crumpy10

1. There is no need to. You may configure your devices in PaperUi or in the files (or use both types)

2. No. The ID is assigned automatically by the binding. But you are free to define one in the sketch.

The screenshot from PaperUi with the things looks good. What is the problem? Are there any updates in the control view from Openhab? What does the log say?

@nizoo91 Stick to addons.cfg in /etc/openhab2/conf/services and don't fiddle with the file you mentioned above.
With package=standard (look for the examples in the comments) the UIs should reappear.

@waspie I'm testing the binding against a mosquitto in my development environment (eclipse IDE) and it is working fine there. That makes it so hard for me to debug the issue.

@waspie Well, it's working for @Guillermo-Schimmel and it's working in my development environment. This bugs the hell out of me. But maybe that's a problem that will be fixed with a update to OH2.

@waspie Well, I do use an MySensors ethernet gateway with the MySensors binding which works fine.
In addition to that I have MQTT devices, for example may heating unit (ebusd) which I connect via Mosquitto and the generic MQTT binding to OpenHAB. MySensors is not involved here.
My advice: use the ethernet gateway with the MySensors binding and keep Mosquitto for the rest. There were some changes in the MQTT implementation of Openhab in 2.4 which lead to some problems, like the one in this thread and I've found some more, while trying to adapt the new configuration and I'm sure there will be some changes to that in the next release. I'm currently using two Openhab instances (2.3 and 2.4) in parallel till all problems are solved.

@waspie you're able to use more than one controller with the MQTT gateway. So while using Openhab for automation you may use My Controller for wireless node updates / firmware uploads. That is not yet possible with the binding.

@jimmy-loyens Could you please check if the embedded-mqtt-broker thing is online? I suppose not. If the embedded broker addon (misc) is installed OpenHAB automatically discovers this embedded broker, just add that thing from inbox.
Now connect your MySensors MQTT gateway (hardware) to the IP and Port of the embedded-broker. After that your MySensors-bridge configuration should work. The port configuration at this point is not needed, but should do no harm, it'll be ignored.

Documentation for the binding: https://github.com/tobof/openhab2-addons/wiki

I've still found no solution but if I use the new embedded broker in OpenHAB2 and connect the the MySensors MQTT gateway to that broker everything works fine.
But I'd no success in connecting the MySensors MQTT gateway to a working MQTT-broker (MQTT2) or in creating a SystemBroker (MQTT2).

So for those of you that are willing to use the embeeded broker, this works fine with the MySensors MQTT gateway.
Just use embedded-mqtt-broker as broker name in the MQTT gateway configuration.

@guillermo-schimmel OK, next question: how did you define the system broker named mosquitto? Because that's the one the MySensors binding seems to use. In a service (cfg) file? I've had no success defining one and maybe that's the key.