The current implementation pairs a new EB-Therm 500 based on "app wide" credentials (e.g this.homey.settings.get('email')). This way of handling settings is not supported on Homey Bridge.

https://apps.developer.homey.app/advanced/custom-views/app-settings

For Homey Bridge, we need to ask the user for Ebeco credentials every time the user pairs with a new device. The credentials will then be stored in the device settings - and not in app settings. This means that we need an additional pairing step for cloud devices - a step which prompts the user to enter Ebeco username and password.

How do we best implement pairing, taking into account the existing functionality as well as the limitations on Homey Bridge?

In order to change existing functionality, one way to do this would be to set up a parallel representation of EB-Therm 500 which would only apply to cloud. That way, the existing functionality would apply to local (Homey Pro), while the new functionality would apply to cloud (Homey Bridge).

What's your thoughs on this @christian-ek ?