[App][Pro] Power Guard — power management and EV charging

Apps
, ,
22

can you try DM on facebook, and we can talk about it.

23

I then try to read the current from the Easee charger and make it stop when it reaches 6 amps as the lowest phase.

25

Hi,

I am trying to set up Home/Away modes for my hot tub, but I have run into a hardcoded temperature limit.

Currently, the maximum limit in the configuration/app is set to 35°C, but I need to be able to set it to 38°C. Is it possible to adjust or override this limit in the configuration files, or could this be updated in a future release?

Thanks!

GREAT APP :+1:

26

Thx for for your message. I can fix that. What version of the app do you use?

27

v0.8.137

28

I can see there is a test version. i will try it out

29

Hi again,

I am now trying out the Test version, and my first impression is that it is much more functional, easier to understand, and much simpler to navigate. Great job on the improvements!

30

We’ve significantly expanded the functionality of Heat Plans and improved every part of the app. Direct Tesla charging support has now been added, making smart energy management even more powerful. Together with improved performance, a refreshed user experience, and numerous optimizations, this release delivers our most advanced and feature-rich version yet.

31

Power Guard v1.0.24 – Intermittent phase_data_unavailable with Tibber Pulse (230 V 3-phase IT)

Hi,

I’m experiencing an intermittent phase measurement warning in Power Guard v1.0.24 when enabling Use phase-based control and protection.

I’ve performed several tests and collected diagnostic data while the warning was active.

My setup

  • Homey: Homey Pro 2023

  • Power Guard: v1.0.24

  • HAN meter integration: Tibber Pulse

  • Electrical supply: 230 V, three-phase IT (Norway)

  • Main fuse: 3 × 50 A

  • Tibber Pulse update interval: 5 seconds

  • Confirmed Supply in Power Guard: 230 V / three phase

  • Confirmed Main Fuse: 50 A

  • HAN does not report L2: OFF

Tibber Pulse exposes the following capabilities:

  • measure_power

  • measure_current.L1

  • measure_current.L2

  • measure_current.L3

Problem

When I enable Use phase-based control and protection, Power Guard intermittently displays:

Missing or uncertain phase measurements. Power Guard lacks valid phase measurements (phase_data_unavailable).

The warning appears and disappears repeatedly, sometimes while I’m watching the dashboard.

At other times, the HAN Meter Summary displays Fresh even though the warning appears on the main Power Guard page.

When phase protection is disabled, normal total-power-based control continues.

Diagnostics captured while the warning was active

The diagnostic report showed:

Field Value
Phase protection Enabled
hanPhaseStatus.state stale
missingPhases []
measure_current.L1 1.36 A
measure_current.L2 2.61 A
measure_current.L3 2.58 A
measure_power 690 W
lastReadingAgeSeconds 5
readingSource event
controlFrozen false

All three phase-current capabilities were present, and the total power reading was recent, but the phase status was classified as stale.

Troubleshooting already performed

  1. Changed Tibber Pulse update interval from 30 seconds to 5 seconds.

  2. Restarted the Tibber Pulse app.

  3. Confirmed that all three phase-current values are available and vary in Homey Insights.

  4. Observed Power Guard switching between fresh and stale.

  5. Confirmed the installation settings as 230 V / three phase and 50 A.

  6. Saved the installation settings and restarted the Power Guard app.

  7. Confirmed that the UI retained the correct installation settings after restart.

The intermittent warning persisted with phase protection enabled.

Additional configuration discrepancy

The Power Guard UI shows:

  • Confirmed supply: 230 V / three phase

  • Confirmed main fuse: 50 A

  • Calculated maximum simultaneous power: 19,520 W

However, diagnostic output has also contained:

{
  "voltageSystem": "auto",
  "detectedVoltageSystem": "400v-3phase",
  "mainCircuitA": 25
}

I’m not sure whether these are legacy/internal fields or whether they affect the phase protection calculations.

Questions for the developer

  1. What causes hanPhaseStatus.state to become stale when total power readings are fresh and all three phase-current capabilities exist?

  2. Does Power Guard require each phase-current capability to receive a fresh update within a separate timeout?

  3. Could unchanged phase-current values cause the phase freshness check to fail, even when the electrical load is stable?

  4. Are the voltageSystem, detectedVoltageSystem, and mainCircuitA diagnostic fields separate from the confirmed installation settings?

  5. Is there a known issue with Tibber Pulse phase-current updates or 230 V three-phase IT installations in v1.0.24?

I can provide the full HAN Diagnostic JSON and additional screenshots if needed.

For now, I have disabled phase-based protection while keeping normal total-power control active.

Thanks for looking into this!

32

Hi,

Sorry for the late reply, and thank you for capturing the diagnostics while the warning was active. Your report helped pinpoint an issue we addressed after v1.0.24.

The five-second reading in your report was the age of the total power measurement. Power Guard checks the age of L1, L2 and L3 separately. So missingPhases: [] means it found all three readings, while state: stale means at least one was too old. That also explains how the HAN summary could show “Fresh” while the dashboard showed a phase warning. Your report doesn’t tell us which phase was late.

In v1.0.25, we increased the phase freshness window from 30 to 60 seconds and made the diagnostics show the age and source of each phase reading. A new phase event counts even if the current is unchanged. Simply reading the same cached value again does not reset its age. So a stable load is fine as long as Homey continues to receive phase updates.

We also corrected the diagnostic output for the installation settings. The confirmed 230 V three-phase IT / 50 A setup is the one Power Guard should use, and 19,520 W is consistent with that configuration. Older reports could show legacy or detected values such as 400 V / 25 A alongside the confirmed settings, which made it look as though a different installation was in use.

These changes are included in v1.0.52. I’d recommend updating and trying phase protection again. You can leave “HAN does not report L2” off, since your Pulse exposes L2. If the warning returns, the most useful thing to send is the HAN Diagnostic JSON captured while the warning is visible, particularly hanPhaseStatus.readings for L1, L2 and L3. That should let us identify exactly which reading aged out. There’s no need to repeat the restart and configuration checks you’ve already done.

Thanks again for the detailed report.