Verbrauchersteuerung - #3808

data/config/mosquitto/public/default-dynamic-security.json:1791

• The three send ACLs omit the broker's openWB/set/... prefix, unlike the charge-point configuration ACLs above and the per-consumer role template. With user management enabled, writes to config, module, and usage are therefore denied. Add set to all three send topics; keep the receive topics unchanged.

					"topic": "openWB/consumer/+/config",

packages/modules/web_themes/koala/source/src/components/charts/dailyTotals/DailyTotalsRow.vue:138

• Only the aggregate consumer ID is handled. Expanded rows use IDs such as consumer-7, so their nonzero power is rendered with the no-current horizontal line. Resolve consumer-* IDs with consumerPower, as is already done for individual counters.
  packages/control/counter_all/loadmanagement_prio.py:24
• Vehicle IDs and consumer IDs use separate namespaces, but removal now matches only the numeric ID and removes the first vehicle or consumer entry encountered. Deleting consumer 2 can therefore remove vehicle 2's priority entry (or vice versa). Pass the component type through the removal API and require both type and ID to match.
  packages/control/counter_all/hierarchy.py:56
• Returning consumers here exposes a caller incompatibility: Counter._get_loadmanagement_state() iterates this result but always indexes data.data.cp_data[load_key]. If a counter enters fault state with a consumer below it, that raises KeyError and aborts counter setup, leaving its load-management limits stale. Update that caller to resolve both cp... and consumer... keys before including consumers here.

 elif child["type"] == ComponentType.CONSUMER.value:
 self.connected_loads.append(f"consumer{child['id']}")

packages/modules/devices/shelly/shelly/status_handler.py:119

• For em1:0 devices, total power and currents apply factor, but the per-phase powers value does not. With any factor other than 1, the emitted phase power no longer sums to total power. Apply the same factor here.
  packages/control/general.py:61
• The consumer surplus switch-on delay defaults to 30 seconds here, while datastore initialization adds the same topic with 60 seconds (helpermodules/update_config.py:666). This makes behavior depend on whether the value came from the dataclass or initialized broker data. Use one default consistently.
  data/config/mosquitto/public/default-dynamic-security.json:1776
• The consumer configuration role has no ACL for the addConsumer or removeConsumer command topics. Unlike the charge-point configuration role at lines 1674-1684, a user granted this role cannot actually create or delete consumers. Add both command ACLs to this role.

			"acls": [

data/config/mosquitto/public/default-dynamic-security.json:1815

• The configuration role never grants access to openWB/set/consumer/+/extra_meter or its corresponding receive topic, although consumer creation and configuration use that topic. Users relying on this role cannot configure an external meter. Add scoped send and receive ACLs for extra_meter.

					"topic": "openWB/system/configurable/consumers",