# \[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:** 95

<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:** [April 12, 2025, 11:04pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1903 "2025-04-12T23:04:13Z")

</div>

Not yet, it requires coding time to customize interval where it is now a static number per model.

---

<div class="post-metadata">

**Author:** ![Robin\_De\_Lange](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_de_lange/32/25173_2.png) [@Robin\_De\_Lange](https://community.homey.app/u/Robin_De_Lange)\
**Post date:** [April 12, 2025, 11:07pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1904 "2025-04-12T23:07:32Z")

</div>

aah, okay. thanks for the answer!

---

<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:** [April 12, 2025, 11:29pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1905 "2025-04-12T23:29:32Z")

</div>

But a note of warning, even a HomeyPro23 doesnt like 20 sockets pulling every second.

Here a crash report yesterday:

```auto

errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-04-11T10:30:01.952Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:8b03b314-ff8c-4e96-ba52-dce577ce535f] TypeError: Cannot read properties of undefined (reading 'statusText')
    at /app/drivers/energy_socket/device.js:205:29
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

⚠ The app has crashed.
CPU Warning Limit Reached

⚠ The app has crashed.
CPU Warning Limit Reached

⚠ The app has crashed.
CPU Warning Limit Reached

```

---

<div class="post-metadata">

**Author:** ![Tom\_ten\_Den](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tom_ten_den/32/120986_2.png) [@Tom\_ten\_Den](https://community.homey.app/u/Tom_ten_Den)\
**Post date:** [April 13, 2025, 12:57pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1906 "2025-04-13T12:57:35Z")

</div>

I also don’t think there is a need for every socket, Usually it concerns the return of the solar panels that you want to control. So per socket setting would be a nice future. 🤞

---

<div class="post-metadata">

**Author:** ![Johan\_Bruyn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_bruyn/32/132683_2.png) [@Johan\_Bruyn](https://community.homey.app/u/Johan_Bruyn)\
**Post date:** [April 13, 2025, 1:48pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1907 "2025-04-13T13:48:34Z")

</div>

To be clear, it was a question why polling was every 10 seconds. As it turns out, the Homey doesn’t handle 1 second very well. It’s fine that the update has been rolled back. But my Homey still gets an update every second. Not bad, but it still gives a problem sometimes.

In the energy graph I sometimes get crossing lines. Probably because Homey is being overloaded. So I think we can conclude that polling every 10 seconds is the best. (it remains a consumer system) That leaves one question open. How do I get my early 2019 Homey (12.4. 0) back to 10 second polling?

 ![IMG_0006](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/ed36044cf46b3628e9c7022a7f8bca90a5c29d6e.jpeg)

---

<div class="post-metadata">

**Author:** ![Mike1233](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mike1233/32/20991_2.png) [@Mike1233](https://community.homey.app/u/Mike1233)\
**Post date:** [April 13, 2025, 1:56pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1908 "2025-04-13T13:56:35Z")

</div>

> [@Johan\_Bruyn](#):
>
> How do I get my early 2019 Homey (12.4. 0) back to 10 second polling?

@Johan_Bruyn Install the latest version, 3.6.4.  
Polling is reverted to 10 seconds.

---

<div class="post-metadata">

**Author:** ![Johan\_Bruyn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_bruyn/32/132683_2.png) [@Johan\_Bruyn](https://community.homey.app/u/Johan_Bruyn)\
**Post date:** [April 13, 2025, 3:05pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1909 "2025-04-13T15:05:47Z")

</div>

That’s the funny thing, that’s the version that’s running.

---

<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:** [April 13, 2025, 3:14pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1910 "2025-04-13T15:14:35Z")

</div>

Ok ok I will fix it. Hard to keep 16000+ users happy.

---

<div class="post-metadata">

**Author:** ![Tom\_ten\_Den](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tom_ten_den/32/120986_2.png) [@Tom\_ten\_Den](https://community.homey.app/u/Tom_ten_Den)\
**Post date:** [April 13, 2025, 4:52pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1911 "2025-04-13T16:52:52Z")

</div>

I think we are all happy with your will.  
There is nothing you can do if the hardware is not compatible. Keep on the good work. 👏

---

<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:** [April 13, 2025, 4:55pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1912 "2025-04-13T16:55:07Z")

</div>

Thx but you don’t see the crash / debug reports.

---

<div class="post-metadata">

**Author:** ![Theo\_de\_Koning](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theo_de_koning/32/136062_2.png) [@Theo\_de\_Koning](https://community.homey.app/u/Theo_de_Koning)\
**Post date:** [April 13, 2025, 6:01pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1913 "2025-04-13T18:01:46Z")

</div>

For me I can’t find something that’s needed that 1 s polling and how to do that.  
Therefore no idea to make and gives a crash / debug reports. 😉

---

<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:** [April 13, 2025, 7:25pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1914 "2025-04-13T19:25:19Z")

</div>

Try version v3.6.5 in test please

> **[HomeWizard](https://homey.app/en-us/app/com.homewizard/HomeWizard/test/)**
>
> Helps you understand and save

- Adjusted P1 polling for Homey Early 2019 older/slower models (10s), HomeyPro2023 will stay 1s

---

<div class="post-metadata">

**Author:** ![Johan\_Bruyn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_bruyn/32/132683_2.png) [@Johan\_Bruyn](https://community.homey.app/u/Johan_Bruyn)\
**Post date:** [April 13, 2025, 8:44pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1915 "2025-04-13T20:44:13Z")

</div>

At an early 2019, 10 seconds polling now works well again. Thank you!

And idea, make a “tikie” QR for donations. I don’t have PayPal. (ever had, but don’t take it again)

---

<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:** [April 13, 2025, 9:11pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/1916 "2025-04-13T21:11:36Z")

</div>

Never looked at “tikkie” problem is those are timebombed and need to be refreshed every few weeks. It’s ok @Johan_Bruyn.

---

<div class="post-metadata">

**Author:** ![Peter\_N](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_n/32/79361_2.png) [@Peter\_N](https://community.homey.app/u/Peter_N)\
**Post date:** [April 14, 2025, 8:36am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1917 "2025-04-14T08:36:49Z")

</div>

Good day,

Is it possible to read the error codes from a plug-in battery and process them in flows? Unfortunately, I’ve encountered error codes several times that cause the battery to go inactive, and I would like to receive a notification for this (which currently doesn’t happen in the Homewizard app)

---

<div class="post-metadata">

**Author:** ![Johan\_Bruyn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_bruyn/32/132683_2.png) [@Johan\_Bruyn](https://community.homey.app/u/Johan_Bruyn)\
**Post date:** [April 14, 2025, 9:21am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1918 "2025-04-14T09:21:09Z")

</div>

For your information. On an early 2019 a kilowatt hour meter gives an update every second. Plug I don’t know, because I don’t have 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:** [April 14, 2025, 9:28am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1919 "2025-04-14T09:28:11Z")

</div>

I only changed the P1, that was asked…

---

<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:** [April 14, 2025, 9:29am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1920 "2025-04-14T09:29:29Z")

</div>

Sadly no, the PIB API doesnt cater any error messages so this is something that needs to be added in the PIB firmware to support.

---

<div class="post-metadata">

**Author:** ![Johan\_Bruyn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johan_bruyn/32/132683_2.png) [@Johan\_Bruyn](https://community.homey.app/u/Johan_Bruyn)\
**Post date:** [April 14, 2025, 9:43am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1921 "2025-04-14T09:43:07Z")

</div>

So far I don’t see any problem with the kWh meter.

Could the “problems” with the p1 meter come because a lot of things are triggered on it? And therefore a lot of calculations are done. (at 1 sec. polling on an early 2019)

---

<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:** [April 14, 2025, 9:43am UTC](https://community.homey.app/t/app-pro-homewizard/19267/1922 "2025-04-14T09:43:18Z")

</div>

test/beta → now live.  
v3.6.6

- Reverted interval back 10s as this has an increased load on some wifi networks and (older) homeys (Early2019). So only the HomeyPro2023 have P1 and kwh meters with a 1s interval.

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

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