ValueID list / Configuration Optimizer for DeltaSol Fresh (OEM: Cosmo CFWME)

[Carsten Krumm]

Hi Daniel,

first of all: thanks a lot for the resol-vbus library and the great documentation — it's been incredibly helpful.

I'm working on integrating a Cosmo CFWME fresh water station into my Home Assistant setup. As you probably know, the Cosmo CFWME appears to be an OEM rebrand of the DeltaSol Fresh (2018) — it has the same hardware layout, same Huba 235 flow sensor, same Wilo PARA pump, and the K-Bus / VBus terminal layout matches.

What works already (or what I'm planning):

Reading data via Protocol v1.0 from device address 0x1510 looks straightforward — the VSF specification covers all 18 fields (S1-S7, flow rate S9, setpoint temperature, pump speed, disinfection state, etc.). That alone already covers my primary use case (logging hot water draws / Warmwasserzapfungen).

Where I'm stuck:

I'd also like to do some basic parameterization via Protocol v2.0 — specifically:

Set the hot water setpoint temperature
Enable/disable the circulation pump (or switch its operating mode)
Possibly trigger thermal disinfection on demand
I've read your vbus-parameterization.md doc and understand the mechanism (master role offer, getValueIdByIdHash, setValueById, etc.). However:

There doesn't seem to be a ConfigurationOptimizer for the DeltaSol Fresh in the library
The RESOL RPT tool doesn't list the DeltaSol Fresh as a supported device, so I can't extract ValueIDs from an XML
I can't find a published list of ValueID hashes for this controller anywhere
My questions:

Is there an (unpublished) list of ValueID hashes for the DeltaSol Fresh 2018 that you could share? Even just for the parameters mentioned above would be a huge help.
If not — would a brute-force scan of value indices getValueById(0x1510, 1..N) be safe to run against the controller, or could that cause issues (EEPROM wear, lockups, etc.)?
Do you know if Cosmo-branded units use the same device address 0x1510 and the same ValueID hashes as the original DeltaSol Fresh, or are OEM units expected to differ?
Any other advice for tackling this controller would be very welcome.
Happy to share my findings (and any scan results) back with the community if useful.

Thanks a lot in advance,

Carsten