Issues

• circuit connection: add connection-point, so consumers can tell a hosted circuit from a monitored one

  electrification-bus/specification#37 · Filter by author dcj opened on Oct 14, 2026

• Device IDs: state only that they are opaque, and drop the prescribed ID forms

  electrification-bus/specification#36 · Filter by author dcj opened on Oct 14, 2026

• Registration: should a client be able to verify the broker host before it trusts any CA?

  electrification-bus/specification#35 · Filter by author dcj opened on Oct 9, 2026

• _ebus._tcp: the SRV port is unspecified, and the SDKs disagree

  electrification-bus/specification#34 · Filter by author dcj opened on Oct 9, 2026

• Conformance vectors: shared, machine-readable test cases every implementation runs

  electrification-bus/specification#33 · Filter by author dcj opened on Oct 8, 2026

• framework.md rule 5: a host with several interfaces on one link claims its hostname on only one of them

  electrification-bus/specification#32 · Filter by author dcj opened on Oct 8, 2026

• _ebus._tcp: one advertisement per host needs device_id to carry several devices

  electrification-bus/specification#31 · Filter by author dcj opened on Oct 8, 2026

• Broker advertisement TXT: cannot express multiple MQTT versions, and required keys are unspecified

  electrification-bus/specification#30 · Filter by author dcj opened on Oct 8, 2026

• framework.md rule 5: a unique .local hostname belongs to a host, not to each entity it publishes

  electrification-bus/specification#29 · Filter by author dcj opened on Oct 8, 2026

• framework.md rule 13: QoS 0 for every /set conflicts with Homie's split by the target property's retained flag

  electrification-bus/specification#28 · Filter by author dcj opened on Oct 8, 2026

• spec-provenance: field table says implements.data-models, schema and examples say implements.devices

  electrification-bus/specification#27 · Filter by author dcj opened on Oct 7, 2026

• _ebus._tcp: add homie_domain, homie_version and homie_roles TXT keys

  electrification-bus/specification#26 · Filter by author dcj opened on Oct 6, 2026

• mDNS: define an advertisement for a diagnostic log stream (_telnet._tcp)

  electrification-bus/specification#25 · Filter by author dcj opened on Oct 6, 2026

• No rule for device-id continuity when one device becomes several, so adopting the multi-load split orphans metering history

  electrification-bus/specification#23 · Filter by author cayossarian opened on Aug 29, 2026

• meter: bare current has no defined meaning on a two-pole circuit, which is neither a single-conductor meter nor a split-phase one

  electrification-bus/specification#22 · Filter by author cayossarian opened on Aug 29, 2026

• load-shed: priority settability is defined publisher-wide, but real panels vary it per circuit

  electrification-bus/specification#21 · Filter by author dcj opened on Aug 27, 2026

• Define CONFIGURATION in capabilities/switch.md, and settle how a commissioned circuit's shed is attributed

  electrification-bus/specification#20 · Filter by author dcj opened on Aug 27, 2026

• devices/circuit.md says switch is omitted on a non-controllable circuit, which capabilities/switch.md contradicts

  electrification-bus/specification#19 · Filter by author dcj opened on Aug 25, 2026
  1

• connection: no upstream analogue of feeds-role, so an enclosure fed by a non-eBus device reads as fed by the utility

  enhancement
  electrification-bus/specification#18 · Filter by author dcj opened on Aug 23, 2026

• meter: no property for enclosure busbar loading, which is a different conductor from the service entrance

  enhancement
  electrification-bus/specification#17 · Filter by author dcj opened on Aug 23, 2026

• info: no structured location for a circuit, and the free-text argument breaks when the name is composed

  enhancement
  electrification-bus/specification#16 · Filter by author dcj opened on Aug 23, 2026

• circuit-tags: no tag for network equipment, which is never curtailed for a reason the critical-load categories do not cover

  enhancement
  electrification-bus/specification#15 · Filter by author dcj opened on Aug 23, 2026

• Shared-hardware declaration and multi-load breakers give two models for the same hardware, with no cross-reference

  enhancement
  electrification-bus/specification#14 · Filter by author dcj opened on Aug 23, 2026
  1

• info: no property for a device's user-assigned name

  enhancement
  electrification-bus/specification#13 · Filter by author dcj opened on Aug 21, 2026
  1

• PV child publishes rated power as info/nameplate-capacity in W, but info.md defines that property as energy and routes power-rated devices to nominal-power

  electrification-bus/specification#12 · Filter by author dcj opened on Aug 20, 2026