USER-level string system-variable methods (SysVar.setString / createString)

[claymore666]

I'd like to understand whether a design decision is being observed or an oversight.

The HomeMatic JSON-RPC API (/api/homematic.cgi) exposes typed create* and set* methods for bool, float, and enum system variables, all at privilege LEVEL=USER. There is no equivalent for the string type — no SysVar.setString and no SysVar.createString exist.

As a result, the only way a JSON-RPC client can create or write a string system variable is via ReGa.runScript (dom.GetObject(...).State(...) / dom.CreateObject(OT_VARDP)), which is LEVEL=ADMIN. So string system variables are effectively admin-only, while every other type can be managed by a normal USER-level account.

Is that intentional?

[claymore666]

Opened a PR implementing the oversight branch of this question: #130 adds SysVar.createString and SysVar.setString at LEVEL=USER, mirroring the existing enum/float methods (createString sets ValueType(ivtString) + ValueSubType(istChar8859) so the variable reports as STRING). Happy to adjust if the asymmetry turns out to be intentional.