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

<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 16, 2025, 3:46pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2428 "2025-08-16T15:46:00Z")

</div>

Yes wifi trouble (Homey cant reach your SDM630 3 fase kwh and P1).

```auto
2025-08-16T10:05:22.556Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.101:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-16T10:05:22.557Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.101:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-16T10:05:25.376Z [err] [ManagerDrivers] [Driver:energy] [Device:7724cf9c-3acd-4372-b2cf-28c002ce4d36] FetchError: request to http://192.168.68.65/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-08-16T10:05:25.447Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-08-16T10:05:25.449Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-08-16T10:05:25.451Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-08-16T10:05:25.454Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-08-16T10:05:25.455Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

```

---

<div class="post-metadata">

**Author:** ![Melvin\_Weerwag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melvin_weerwag/32/81907_2.png) [@Melvin\_Weerwag](https://community.homey.app/u/Melvin_Weerwag)\
**Post date:** [August 16, 2025, 3:59pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2429 "2025-08-16T15:59:57Z")

</div>

Thats strange because the kWh meter isnt giving any problem and giving thru all data. Have no missing data on the kWh meter side.

Will check my network log on the connection between the homey and my network. Will update you after i checked.

---

<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 16, 2025, 4:00pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2430 "2025-08-16T16:00:52Z")

</div>

Sorry can’t help it, this is what your log tells me.

This log clears every time my app is restarted.

---

<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 16, 2025, 7:21pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2431 "2025-08-16T19:21:12Z")

</div>

Found your issues, polling is 1s for both and probably with all other tasks you do with Homey and bit to much. Lower down the polling from 1 to perhaps 3s and see if it improves:

```auto
Settings for SDM630: 1
Polling settings for P1 apiv1: 1

```

---

<div class="post-metadata">

**Author:** ![Melvin\_Weerwag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melvin_weerwag/32/81907_2.png) [@Melvin\_Weerwag](https://community.homey.app/u/Melvin_Weerwag)\
**Post date:** [August 16, 2025, 7:35pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2432 "2025-08-16T19:35:06Z")

</div>

Thanks Jeroen!

I indeed changed this to 1 second a few days ago. I’m going to rase it step by step to see what holds it.

After your previous message I trouble shoot everything in my network and I couldnt find anything. I even ordered the homey pro ethernet adapter to make a more stable connection and check if that will solve it.

Really didnt understand how it could be a network problem, have a really strong and stable home network 😅

---

<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 16, 2025, 7:39pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2433 "2025-08-16T19:39:24Z")

</div>

I understand, I think the 1s is just to much for your current Homey set up.

---

<div class="post-metadata">

**Author:** ![Melvin\_Weerwag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melvin_weerwag/32/81907_2.png) [@Melvin\_Weerwag](https://community.homey.app/u/Melvin_Weerwag)\
**Post date:** [August 16, 2025, 8:59pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2434 "2025-08-16T20:59:53Z")

</div>

Sadly even setting it to 10 seconds didnt solve it. But i’m seeing that the Homey Pro is going offline for a fraction of a second and after that it gives trouble with the P1 meter. So made a support ticket to Athom.

Thanks for you help so far Jeroen, i will give an update when Athom has more information and if it has something to do with the HW app.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [August 16, 2025, 9:50pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2435 "2025-08-16T21:50:07Z")

</div>

> [@Melvin\_Weerwag](#):
>
> and if it has something to do with the HW app.

Not to nag, but wouldn’t every HW app user report here if that was the case?

---

<div class="post-metadata">

**Author:** ![Melvin\_Weerwag](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/melvin_weerwag/32/81907_2.png) [@Melvin\_Weerwag](https://community.homey.app/u/Melvin_Weerwag)\
**Post date:** [August 16, 2025, 10:03pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2436 "2025-08-16T22:03:44Z")

</div>

It doesnt have to be a thing everybody is experiencing. Could be something that happens to some kind of combined hardware combination.

i didnt said it to be negative. Just to lett Jeroen know that I will follow up if Athom comes with new information regarding the problem. Jeroen helped pretty well, so he deserves some kind of follow up.

---

<div class="post-metadata">

**Author:** ![Kevin\_Vullings](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kevin_vullings/32/107360_2.png) [@Kevin\_Vullings](https://community.homey.app/u/Kevin_Vullings)\
**Post date:** [August 17, 2025, 11:09am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2437 "2025-08-17T11:09:54Z")

</div>

5845e750-7d2b-433c-ad3e-9cb2010b54d7

Problemen met de app, wie kan me helpen?

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [August 17, 2025, 11:18am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2438 "2025-08-17T11:18:51Z")

</div>

It helps if your first explain the problem you are running into and only send an error log at the request of / based on the guidance of the developer.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [August 17, 2025, 11:28am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2439 "2025-08-17T11:28:46Z")

</div>

> If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. Please translate your post into English, otherwise it will be deleted in three days to keep the thread in just one language as stated in the forum rules [Welcome to the forum!](https://community.homey.app/t/31)

Please do also check out the categories in other languages:

[Nederlands (Dutch)](https://community.homey.app/c/nederlands)

If you need help, because depending on the trust level of your account, you may have limited permissions, please PM me or another moderator or reply to this post.

Or

> [@Jeroen\_Tebbens](#):
>
> Nederlands forum topic hier, maar meeste info zal in dit engelse gedeelte te vinden zijn omdat dit al langer loopt.  
> → [[APP][Pro][NL] Homewizard 🧙‍♂️](https://community.homey.app/t/app-pro-nl-homewizard/71211)

---

<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 17, 2025, 2:39pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2440 "2025-08-17T14:39:50Z")

</div>

Check first post in this topic for tips:

Logs show wifi problems:

```auto
2025-08-17T11:07:05.480Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:07:15.496Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:07:25.512Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:07:35.529Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:07:45.546Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:07:55.592Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:08:05.576Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2025-08-17T11:08:15.624Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:517:28)
    at Socket.socketErrorListener (node:_http_client:501:9)
    at Socket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}

```

---

<div class="post-metadata">

**Author:** ![Roger\_Gorissen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roger_gorissen/32/9534_2.png) [@Roger\_Gorissen](https://community.homey.app/u/Roger_Gorissen)\
**Post date:** [August 17, 2025, 9:16pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2441 "2025-08-17T21:16:08Z")

</div>

I’m experiencing the same problem @Melvin_Weerwag describes. Every x minutes my HW P1 meter is having a red triangle, no connection possible. Restarting the HW app solves the problem for some time. The watermeter works fine, no problem.

Although this shouldn’t happen, I’m looking for a way to notice it by a flow to restart the app. Netscan doesn’t help me this far. I thought the P1 meter loses it’s connection to the router. Nope.

The problem arose when I changed from the white Homey Pro (2019) to the mew Homey Pro (2023). Before that everything worked just fine.

I’ll check the polling interval as Jeroen describes.

_ **Edit** _: I changed the polling interval from 2 to 5 seconds. The energy meter is still online, no red triangle so far (12 hours have passed since I made the change 🤫😱😓)

---

<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 18, 2025, 10:17pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2442 "2025-08-18T22:17:36Z")

</div>

beta/test:

v3.6.58

\* Bugfix that was caused by experimental firmware Homey 12.5.2RC3 and slider capability that could not be removed

\* Added energy flags for sockets so they can trace imported/exported energy in Homey Energy Dashboard (Home Batteries connected via sockets, eg Marstek, Zendure, Anker, eeeeh)

\* Code cleanup

\* Added some fine tuning to spread the API call’s to the P1

---

<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 18, 2025, 10:21pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2443 "2025-08-18T22:21:09Z")

</div>

version v3.6.57 should fix this.

---

<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:** [August 18, 2025, 10:34pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2444 "2025-08-18T22:34:36Z")

</div>

Unfortunately battery 2 lost in the beta.

b9349f21-8776-4a0b-892c-5ffde228f5e9

---

<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 18, 2025, 10:49pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2445 "2025-08-18T22:49:06Z")

</div>

Fixed in v3.6.58

---

<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:** [August 19, 2025, 7:01am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2446 "2025-08-19T07:01:22Z")

</div>

Thanks, battery 2 is now also reporting values. I’ve reset the P1 meter’s polling to 10 seconds. We’ll see what happens.

---

<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 19, 2025, 7:13am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2447 "2025-08-19T07:13:34Z")

</div>

@Gerard_L is also testing atm

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

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