Homey Energy Dongle stopped detecting Wasion meter after re-pairing

Hello everyone,

I’m looking for other users who have experience with the Homey Energy Dongle and Wasion smart meters.

My setup:

  • Homey Pro (Early 2023)
  • Homey OS 13.4
  • Homey Energy Dongle (Firmware Build 12)
  • Country: Hungary
  • Energy provider: E.ON Hungary
  • Smart meter: Wasion aMeter300 (3-phase)

During the very first installation, the dongle did not receive any data immediately.

After approximately 2–3 hours, it suddenly started working.

At that point the Advanced Settings showed:

  • Meter Model: WSE5Wasion–Meter
  • Data Parser Type: DSMR 1/2/3

The dongle started reporting:

  • Total imported energy
  • Live power
  • Voltage on all three phases
  • Current on all three phases

Unfortunately, the readings were unstable. The reported power fluctuated heavily and updates were intermittent.

Because of these unstable readings, I removed the device and paired it again.

Since re-pairing, the dongle has never detected the smart meter again.

Now the Advanced Settings show:

  • Meter Model: empty
  • Data Parser Type: empty
  • Equipment ID: empty

No live energy values are available anymore.

The LED pulses white approximately every 10 seconds, so the dongle appears to receive telegrams from the P1 port.

I have already tried:

  • Factory reset
  • Pairing again multiple times
  • Reinstalling Firmware Build 12 via the official USB updater
  • External USB-C power
  • Different Wi-Fi networks
  • Rebooting Homey
  • Removing and adding the device several times

I have also opened an official Homey support ticket (#153497) and submitted Diagnostics Report ID: 044B4CE9.

Has anyone experienced this with a Wasion smart meter?

Has anyone seen the Homey Energy Dongle detect the meter once, then completely lose the Meter Model and Data Parser Type after re-pairing?

Any ideas or similar experiences would be greatly appreciated.

Thank you!

Some energy providers encrypt the P1 data, but since it worked before I don’t think that’s the issue. I think it’s just a hardware issue with the dongle in that case.