# \[APP\]\[Pro\] Homewizard 🧙‍♂️

**URL:** <https://community.homey.app/t/app-pro-homewizard/19267>\
**Category:** Apps\
**Tags:** app, official, homey-pro\
**Created:** [October 14, 2019, 2:25pm UTC](https://community.homey.app/t/app-pro-homewizard/19267 "2019-10-14T14:25:58Z")\
**Posts on this page:** 20\
**Page:** 197

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 3, 2026, 10:47am UTC](https://community.homey.app/t/app-pro-homewizard/19267/3956 "2026-08-03T10:47:55Z")

</div>

If nothing changed and stopped working since 2 day using an older app version, how can it be this app then? Is your Homey overloaded? Does it have enough resources free? Did you try a reboot of your Homey 2019?

You can try latest test version but that mainly focuses on the battery policy device feature which is something you dont have as per your commited log.

---

<div class="post-metadata">

**Author:** ![Arjank95](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjank95/32/17429_2.png) [@Arjank95](https://community.homey.app/u/Arjank95)\
**Post date:** [August 3, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-homewizard/19267/3957 "2026-08-03T10:54:57Z")

</div>

Because HW app is the only one giving trouble with unreachable devices since the last days (having 103 devices with multiple apps) and memory usage increase (after the update), so that’s why I ended up here

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 3, 2026, 11:10am UTC](https://community.homey.app/t/app-pro-homewizard/19267/3958 "2026-08-03T11:10:53Z")

</div>

I got nothing to work with based on your log, there is no crash info or memory/cpu warning listed. Homey purely complains about unable to reach your wifi devices. Interval / polling is fine with 10s as per log you shared so that is not the case either.

I really feel you are now hitting your max of your Homey 2019 where this app seems the first signal showing this.

I suggest a reboot of your Homey. Further check other apps on your Homey that may have increased memory size as well making it hard to work properly.

I will release 3.18.0 soon as impoved cpu and memory but that is battery policy focused but perhaps it does something for you.

---

<div class="post-metadata">

**Author:** ![Arjank95](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arjank95/32/17429_2.png) [@Arjank95](https://community.homey.app/u/Arjank95)\
**Post date:** [August 3, 2026, 12:30pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3959 "2026-08-03T12:30:10Z")

</div>

Hmm, thanks for the effort and quick replies,.. I’m aware of the limits of the HP19. A reboot seems like to have calmed down the HW app. Hopefully everything will go back to normal.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 3, 2026, 12:38pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3960 "2026-08-03T12:38:03Z")

</div>

Good to hear, no problem. But I cant support this any longer. I would have a full mailbox if it was the app with crashes and (unasked) diagnostics.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 6, 2026, 3:09pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3961 "2026-08-06T15:09:16Z")

</div>

Beta/test v3.19.0

- simplified PV forecast setting (solcast / meteosat)
- Meteosat available as replacement for Solcast (ratelimit issues and lack of 0-2h vision).
- Fixed peak shaving
- Corrected battery discharge floor calculation
- Corrected battery wear cost calculation
- Fixed underestimated learning standby consumption
- Correct timezone bug (lower memory and cpu utilization)
- Reduced background memory usage

Settings:

 ![IMG_4990](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/9/394e216ddd4a4ebb1c385671932f11337ea97bdd.jpeg)

Selection for meteosat or solcast. Will drop solcast if meteosat proofed itself. The free key with 10-12 updates is a problem (ratelimit / other sources use same key).

 ![IMG_4989](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/5/d5fe1223881083ac7bfad2eb07b8644fb3da5d41.png)

---

<div class="post-metadata">

**Author:** ![LonHom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lonhom/32/128516_2.png) [@LonHom](https://community.homey.app/u/LonHom)\
**Post date:** [August 9, 2026, 4:09pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3962 "2026-08-09T16:09:38Z")

</div>

The total current is not shown. The P1 meter API V1 Json contains active\_current\_a but the shown Current is same as Current Amp phase 1.

```auto

{
  "wifi_ssid": "SSDINAME",
  "wifi_strength": 100,
  "meter_model": "ADN9 7534",
  "unique_id": "GID_3",
  "total_power_import_kwh": 180.281,
  "total_power_import_t1_kwh": 180.281,
  "total_power_export_kwh": 0,
  "total_power_export_t1_kwh": 0,
  "active_power_w": 325,
  "active_power_l1_w": 130,
  "active_power_l2_w": 152,
  "active_power_l3_w": 45,
  "active_voltage_l1_v": 237.5,
  "active_voltage_l2_v": 238,
  "active_voltage_l3_v": 237.4,
  "active_current_a": 1.6,
  "active_current_l1_a": 0.7,
  "active_current_l2_a": 0.8,
  "active_current_l3_a": 0.1,
  "external": []
}

```

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/0/90843d3837638de689b79d874b614ad64c62ef03.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/3/d3e5512859edb73ffd94eba926faeb4889a0356f.png)

Edit: The firmware version is 6.0305.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 9, 2026, 4:42pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3963 "2026-08-09T16:42:32Z")

</div>

Looks like you are on an old firmware of your P1 as active\_current\_a is not w valid datasource anymore so removed it. But let me make it somehow backwards compatible again.

> **[Recent Measurement | HomeWizard API Documentation](https://api-documentation.homewizard.com/docs/v1/measurement/)**
>
> Get the most recent measurement from the device.

---

<div class="post-metadata">

**Author:** ![LonHom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lonhom/32/128516_2.png) [@LonHom](https://community.homey.app/u/LonHom)\
**Post date:** [August 9, 2026, 5:00pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3964 "2026-08-09T17:00:25Z")

</div>

I updated my P1. The version is now 6.0503. active\_current\_a is still there.

```auto
{
  "wifi_ssid": "SSDINAME",
  "wifi_strength": 100,
  "meter_model": "ADN9 7534",
  "unique_id": "GID_4",
  "total_power_import_kwh": 180.558,
  "total_power_import_t1_kwh": 180.558,
  "total_power_export_kwh": 0,
  "total_power_export_t1_kwh": 0,
  "active_power_w": 415,
  "active_power_l1_w": 130,
  "active_power_l2_w": 240,
  "active_power_l3_w": 45,
  "active_voltage_l1_v": 237.8,
  "active_voltage_l2_v": 237.5,
  "active_voltage_l3_v": 237.5,
  "active_current_a": 2.1,
  "active_current_l1_a": 0.7,
  "active_current_l2_a": 1.3,
  "active_current_l3_a": 0.1,
  "external": []
}

```

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 9, 2026, 5:03pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3965 "2026-08-09T17:03:57Z")

</div>

Strange as api documentation stripped or will soon.  
Anyway I added the backward compatible replacement. Will come with next release v3.19.1 so it will either pull that datapoint (if it exists) else it will add up all 3 currents and populate the main one.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 10, 2026, 4:17pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3966 "2026-08-10T16:17:55Z")

</div>

Test version (v3.19.1)

- Fixed watermeter day usage reset at 2:00 CEST
- Fixed a backwards compatibility P1 active current A for 3 phase
- (New) API method with Power by the Hour to pull dap prices. Make sure you update then policy tab setting to your preferred source (or fallback to entsoe method I already had in place. This makes the xadi and kwhprice sources obsolete and has been removed.

 ![IMG_0191](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/d/9d2fb85b4f347163583d9da1b50d900f9217d695.jpeg)

---

<div class="post-metadata">

**Author:** ![Flodur](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/flodur/32/113601_2.png) [@Flodur](https://community.homey.app/u/Flodur)\
**Post date:** [August 23, 2026, 12:11pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3967 "2026-08-23T12:11:38Z")

</div>

@Jeroen_Tebbens, I have a question; I am using the not-connected trigger card for the P1 meter (APIv1). I didn’t see this trigger in the API v2 version, is that correct?

I use the P1 meter for charging station load balancing, and for that, it is important to know that the P1 meter has a continuous connection. Wi-Fi is never perfect, so I have built in rules that reduce the charging speed after a certain amount of time offline, just to be safe. The not-connected trigger worked perfectly for this. But I want to switch to the API v2 to reduce load on Homey.

Otherwise, I will look into Smart Presence/ Net Scan like solutions, no problem.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 23, 2026, 1:34pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3968 "2026-08-23T13:34:03Z")

</div>

Good catch, Will be fixed in next release. Working on the post 2027 salderen code at this moment but your request is included.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 27, 2026, 3:52pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3969 "2026-08-27T15:52:58Z")

</div>

Work in progress for 2027 (end of “salderen”).

- import / export price differences

 ![IMG_0194](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/30738e5916de9fd6acb83725597636d898cc1ab7.jpeg)

- When export prices go negative (ie pv export will cost you money) there is now an trigger card curtailment to tune down your solar inverter. Mine is a homeyscript but anything that takes the max watts allowed (modbus or other inverter that you can control/tune down.

 ![IMG_0195](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3fbaeb8295a604c7fa4acf47b72784e0702a083f.jpeg)

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [August 29, 2026, 1:54pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3970 "2026-08-29T13:54:07Z")

</div>

Further tested export prices being negative. This is speculation based on dynamic prices today and deducted “energiebelasting”.

 ![IMG_0197](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/8/387c20d18c2a9e00e8033843ce845d60bab16bfb.jpeg)

The developed code and trigger card makes the solar inverter step down its power to minimize its production and match up household usage and battery needs.

Next step is to improve it to fully cut it off but that is not supported to every inverter.  
EDIT: fixed for both import and export negative. Real test would be in 2027. 😅

 ![IMG_0196](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/5/c51a0a7753c01dcae211bf9623c7a9815e21904e.jpeg)

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 7, 2026, 1:35pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3971 "2026-09-07T13:35:32Z")

</div>

- v3.17.4 — Performance improvements; solar ensemble accuracy improved
- v3.17.5 — Wear cost applied consistently across all charging paths; more reliable battery startup on multi-battery setups; satellite solar forecast improvements; camera chart & PV accuracy display fixes; cloud-cover  
forecast accuracy improved
- v3.17.6 — Cheap solar now stored at the best moment instead of exported
- v3.17.7 — Battery efficiency now broken down by charge/discharge workload
- v3.17.8 — More reliable device updates during app restarts
- v3.17.10 — Energy socket poll interval and thermometer offset now apply immediately
- v3.17.11 — Battery plan no longer collapses after a charge-rate calibration; corrected payback/profit figures on the expansion tab; no more tiny pointless charges around sunset
- v3.19.0 — Simplified PV forecast source setting; peak shaving no longer silently downgrades to standby; corrected discharge floor calculation; corrected battery wear cost in store-vs-export decisions; fixed  
underestimate in learned standby consumption; corrected timezone bug in a dynamic price window; CDP debug inspector off by default; reduced background memory usage
- v3.19.1 — Charging limit now uses the same maths as the planner; planning chart no longer shows the battery filling while idle; battery now charges ahead of a profitable peak on sunny days; PV curtailment trigger no  
longer fires with the setting off; new setting to weigh a weak solar surplus against exporting; battery no longer stops discharging while prices are still high; dynamic prices now come from Power by the Hour;  
elapsed/current hour now priced correctly; evening safety check no longer blocks waiting for cheaper solar; correct total current on three-phase P1 meters; water meter daily total now resets at local midnight;  
tomorrow’s plan no longer falls back to flat hourly prices
- v3.19.4— Internal cleanup: deduplicated repeated code blocks, removed dead functions and an unused setting; no functional change
- Settings reduction update
- P1 (energy) driver to warn user on the timeline to check their wifi has big problems 40x poll interval 50% fail → 1x warning per 24h
- v3.19.7 - Battery Policy DP cleanup, Price forecast added to fill gap until ENTSOE releases prices
- v3.19.9 - Various bugfixes on DP (delayed charging) profit on export solar

---

<div class="post-metadata">

**Author:** ![Francois\_Pauwelsen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/francois_pauwelsen/32/57037_2.png) [@Francois\_Pauwelsen](https://community.homey.app/u/Francois_Pauwelsen)\
**Post date:** [September 23, 2026, 3:06pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3972 "2026-09-23T15:06:26Z")

</div>

Is het ook mogelijk van een Goodwe inverter die is toegevoegd in de Homewizard app te zien in Homey?

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [September 24, 2026, 8:12am UTC](https://community.homey.app/t/app-pro-homewizard/19267/3973 "2026-09-24T08:12:58Z")

</div>

Hi @Francois_Pauwelsen, this is the english section here so please translate your query to english or post it the dutch section. But…regarding your query, I doubt if this the right direction to ask me to add solar inverters that are managed via HW Cloud directly. There risk of delay and gaps is very high, a slight change in the cloud based integration from GoodWe makes this fail easily as you might have noticed with their latest changes. Check the other GoodWe apps here on the platform that are already aiming this issue and be a better fit to make it work for you then asking me to incorporate this cloud based “GoodWe” solar inverter via Homewizard online.

It is not about I can’t do, but the complexity and risk of problems are bigger rather having the other GoodWe apps here on the platform giving you a better result.

---

<div class="post-metadata">

**Author:** ![Johan\_Konijnenburg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_konijnenburg/32/120755_2.png) [@Johan\_Konijnenburg](https://community.homey.app/u/Johan_Konijnenburg)\
**Post date:** [October 3, 2026, 5:33pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3974 "2026-10-03T17:33:51Z")

</div>

**Possible issue with Plug-in Battery `measure_battery_threshold_below` Flow Card – v3.19.9**

Hi Jeroen,

I am using HomeWizard app v3.19.9 on a Homey Pro 2023 with two HomeWizard Plug-in Batteries.

During an API-based validation of the Homey Flow Card catalogue, I found a reproducible issue affecting both Plug-in Batteries.

For both devices Homey exposes the trigger:

`measure_battery_threshold_below`

The raw Homey Web API shows the trigger argument as:

`name: "threshold"`  
`type: "number"`  
`placeholder: "%"`  
`title: null`

Both batteries generate the same result independently.

The batteries themselves are working normally and their SoC is reported correctly. The Condition and Action Flow Card catalogues also validate correctly. Only the Trigger catalogue fails schema validation on the generated battery-threshold cards.

The Homey integration consuming the Web API expects the Flow Card metadata title to be a string and therefore rejects the Trigger catalogue when these `null` values are encountered.

I realise this might be generated automatically by Homey from the `measure_battery` capability rather than being an issue in your app itself.

Could you please advise whether the Plug-in Battery driver explicitly adds `measure_battery`, and whether this `null` metadata can be prevented at app/driver level? If this is entirely generated by Homey, I can report the issue further upstream instead.

I have deliberately not removed/re-paired the batteries or changed their capabilities, as everything else is functioning correctly.

If useful, I can provide the exact Flow Card IDs and additional API/diagnostic output.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Jeroen\_Tebbens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_tebbens/32/62246_2.png) [@Jeroen\_Tebbens](https://community.homey.app/u/Jeroen_Tebbens)\
**Post date:** [October 3, 2026, 10:07pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/3975 "2026-10-03T22:07:32Z")

</div>

Hi Johan, thanks for the report.

measure\_battery is a standard Homey capability that our driver adds, but the measure\_battery\_threshold\_below trigger isn’t defined in our app. Homey generates it, including the threshold argument with title: null. On my own Homey the same null title appears on 60 cards from 17 different apps, so we can’t change it at app level. Best to report it to Athom, and have the client tolerate a null title.

While checking I did find a real issue in our own “Battery state changed” trigger: its dropdown values also had a null title. That’s fixed and will be in the next release. I’m not sure it’s the card your validation hit, since you mentioned the threshold card

[Previous page](https://community.homey.app/t/app-pro-homewizard/19267.md?page=196)

[Next page](https://community.homey.app/t/app-pro-homewizard/19267.md?page=198)