HomeWizard

Monitors and controls HomeWizard Energy's local-network devices - Energy Socket, P1 Meter, kWh Meter (1- and 3-phase), and Watermeter - flat, no gateway layer, closest in shape to the Shelly integration's own local-HTTP approach.

Two API versions, side by side

Choose per device when adding it:

• v1 - plain, unauthenticated HTTP, no pairing step. Reaches every device type above. The default choice.
• v2 - bearer-token authenticated HTTPS, needed for the Plug-In Battery and optional on everything else. Pairing is a one-time step: press the physical button on the device, and Athena retries automatically for up to a minute while showing a "press the button now" prompt.

Entities stay addressable the same way regardless of which version a device is connected over - a Dashboard card or Automation reference keeps working unchanged even if you switch a device's own connection between v1 and v2 later.

What's exposed

Every measurement field a device actually reports becomes its own read-only sensor entity - power, energy totals, voltage, current, and so on, whichever fields that specific device type sends. An Energy Socket also gets a controllable on/off switch; a v2-connected Plug-In Battery (managed through the P1/kWh Meter it's attached to, not addressed directly) gets a mode selector plus read-only power/target-power/count sensors.

Adding a device

Auto-discovered via mDNS on your local network, connecting straight from a Discovered row - or use "+ Add device" in the Configured tab's own header menu to type a device's name, address, and port in by hand instead (see Devices & Services). Works with Dashboard cards, History, and Automations exactly like every other integration.