Hi Tino (@flynux),
great to hear, that it work now with the snapshot version.
Regarding the Ids. The ThingId does not matter any longer, you can define the ThingId like you want now. To link a Thing to the device messages, you have to use the enoceanId property now. Therefore it is possible to define more than one thing which listens to the messages of a device. Currently the only exception for this is the ClassicDevice. As this thing just combines an old virtualRockerSwitch and one or more rockerSwitches, it does not own an enoceanId. You have to use the listener channels now, to bind the classicDevice thing to a device.
Therefore your classicDevice has to look like this:
Thing classicDevice cd01 "FMS61NP " [
senderIdOffset=XXX, // set this to the right id
Type virtualSwitchA : virtualSwitchA [duration=300, switchMode="rockerSwitch"]
Type rockerswitchListenerSwitch : FMS61NPListener "FMS61NP" [enoceanId="05127F5B", channel="channelA", switchMode="rockerSwitch"]
As you can see, the listener gets the device Id now.
Can I do everything within PaperUI or do I need to define it in config files?
It is up to you. You can only use PaperUI or define everything in config files. However I would always recommend to use config files.