I believe my assumption in the last paragraph of my post above is turns out to be true and I know why my original way of teaching in results in always both dimmers reacting: When teaching in the USB300 with the dimmer, the dimmer learns to listen to specific sender. And without further configuration during the teach in process, that sender (i.e. sender ID) is always the base ID of the USB300. Therefore, we need to choose a different sender ID when teaching in. Apparently, this sender ID has to be in a certain range of the USB300 base ID.
I found a post on a symcon forum in German. The platform is different, but I believe the process is the same. I was not able to test yet, but it sounds promising.
Here’s the link to the original post:
And here’s an English translation by deepl.com
if you were able to teach a button into IPS, then the USB300 will work But from now on it gets a bit more complicated. First you have to check if your 14 components FUD14, FSR14, FSB14 etc. have got a bus-ID, you can do this with the Eltako software PCT14, when you see your actuators then everything is OK. Next you have to create a corresponding instance (Eltako Dimmer) in IPS and assign a device ID to the instance.
The device ID can be freely assigned between 1 and 128 or 256, making the instance unique. I have thought of a small scheme and built an Excel sheet (see attachment) to keep the overview.
The Device ID is an extension for the Base ID of your USB300, because you want to be able to switch every single lamp separately and not all at once.
Next you have to teach the actuator accordingly, the ID to teach is now composed of the Base ID of the USB300 plus the Device ID of the instance. You have to add the values, e.g. Base ID is FFAB1080 and Device ID is 15 (corresponds to 0x0F) = FFAB108F, or Device ID 55 (0x37) -> 0x80+0x37 = 0xB7 -->> FFAB10B7.
Teaching-in is either cumbersome using the rotary switches on the actuator or much easier with the PCT14:
- start PCT14 and connect it to FAM14
- in PCT14 “Recognize ID - switch on”
- click on Teach in at the IPS instance, the ID then appears in PCT14 in the right block
- simply drag the ID with the mouse to the corresponding position (ID assignment area) in an actuator
- adapt the data (function, channel, etc.)
- take over data and transfer them to the device
- in PCT14 disconnect the connection to FAM14!!
- test if the actuator can be controlled via IPS
Then there is the message ID, this is used to receive status telegrams from the actuators to keep the status of the instance up to date. e.g. you switch on your light with the wall switch, without message ID IPS would not notice this and in the visual display the light would still be off. With the message ID, IPS receives the status telegram from the actuator stating that the light is on and IPS can update the display.
The message ID in turn is composed of the base ID of the FAM14 and the bus address (see PCT14) of the actuator/channel.
Alternatively you can also try to search for the message ID, but I prefer to do this manually.
So, this sounds very complicated, but it is not. Once you understand this and have set up two instances, everything goes easy. And with the Excel table you can enter your complete actuator/sensor system and then simply copy/paste the IDs into IPS.
Translated with www.DeepL.com/Translator (free version)
I post an update as soon as I can test.