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

<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, 2025, 10:16am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2609 "2025-10-03T10:16:22Z")

</div>

Does it show up in mDNS Browser as per first post suggested?

---

<div class="post-metadata">

**Author:** ![Yankee\_Delta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/yankee_delta/32/83449_2.png) [@Yankee\_Delta](https://community.homey.app/u/Yankee_Delta)\
**Post date:** [October 3, 2025, 11:01am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2610 "2025-10-03T11:01:55Z")

</div>

That is the only thing i cant see from here, im @ remote for now 😕

---

<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, 2025, 11:10am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2611 "2025-10-03T11:10:03Z")

</div>

test/beta

v3.6.73

- More try/catch code to avoid any crashes on Homewizard Legacy main unit getStatus fail (Device not found)
- Fine tune “estimated kwh” plugin battery calculation based on user feedback
- Code fixes: unhandledRejections CloudOn/Off for sockets and P1

---

<div class="post-metadata">

**Author:** ![\_Bredero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/_bredero/32/30978_2.png) [@\_Bredero](https://community.homey.app/u/_Bredero)\
**Post date:** [October 5, 2025, 10:28am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2612 "2025-10-05T10:28:14Z")

</div>

Hi,

Is it possible that Homey can also give a message when a Plugin Battery has an error or fault status? Now i open sometimes the Energy App to see of there is a failure or everything is stable/works fine.

Regards,

Adriaan

---

<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 5, 2025, 10:41am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2613 "2025-10-05T10:41:11Z")

</div>

No, Plugin Battery API has no datapoints exposed that show errors.

---

<div class="post-metadata">

**Author:** ![\_Bredero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/_bredero/32/30978_2.png) [@\_Bredero](https://community.homey.app/u/_Bredero)\
**Post date:** [October 5, 2025, 11:01am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2614 "2025-10-05T11:01:28Z")

</div>

Hi, thanks for the fast reply. Okay, i hope HW will change the API soon, so errors are also show in the future so Homey can send a message when something is broken.

---

<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 5, 2025, 11:59am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2615 "2025-10-05T11:59:41Z")

</div>

Not sure if they will, they want the Plugin Battery to be a careless unit. So exposing errors via API is not high on their to do list.

But you got a Homey, you got all the information you need to create a flow check. It is just as easy as checking if energy is getting back to your energy grid while it should go in your PIB. Some of extra checks to avoid false alerts like state of charge and mode isn’t standby etc. You can improve it to your liking.

Example:

 ![IMG_3709](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/6/06ba1bdde6fad78d3a08b421c3797f4b7b59e000.jpeg)

---

<div class="post-metadata">

**Author:** ![\_Bredero](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/_bredero/32/30978_2.png) [@\_Bredero](https://community.homey.app/u/_Bredero)\
**Post date:** [October 5, 2025, 5:21pm UTC](https://community.homey.app/t/app-pro-homewizard/19267/2616 "2025-10-05T17:21:35Z")

</div>

Hi Jeroen,

Thanks, i have a Homey and thanks for the example and your advice, it’s easy to build a check by myself👍

Regards, Adriaan

---

<div class="post-metadata">

**Author:** ![Fusionyx](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fusionyx/32/56405_2.png) [@Fusionyx](https://community.homey.app/u/Fusionyx)\
**Post date:** [October 7, 2025, 9:50am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2617 "2025-10-07T09:50:24Z")

</div>

Hi since a few day my flow with Energy Socket Toggle On / Off don’t work anymore.  
Diag Report: dec02bb8-89db-490f-8cee-00cdc0d6c70e

I installed the test version that seemed to have a fix for something but this didnt resolve the problem.

Error: Network Error During onRequest

---

<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 7, 2025, 10:04am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2618 "2025-10-07T10:04:58Z")

</div>

Please focus on your wifi:

```auto
2025-10-07T09:35:22.215Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:36:26.204Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:37:31.087Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: socket hang up
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketOnEnd (node:_http_client:466:9)
    at Socket.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:38:34.348Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:39:38.327Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: socket hang up
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketOnEnd (node:_http_client:466:9)
    at Socket.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:40:42.339Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:41:46.305Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:42:50.306Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:43:54.288Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: socket hang up
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketOnEnd (node:_http_client:466:9)
    at Socket.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:44:43.436Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: read ECONNRESET
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:44:58.327Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: socket hang up
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketOnEnd (node:_http_client:466:9)
    at Socket.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
2025-10-07T09:46:02.291Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:f8fa5055-0272-4d97-8aba-c644b729ecd3] FetchError: request to http://172.31.252.137/api/v1/state failed, reason: socket hang up
    at ClientRequest. (/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketOnEnd (node:_http_client:466:9)
    at Socket.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}
    

```

---

<div class="post-metadata">

**Author:** ![Rene\_Veenendaal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rene_veenendaal/32/79245_2.png) [@Rene\_Veenendaal](https://community.homey.app/u/Rene_Veenendaal)\
**Post date:** [October 7, 2025, 10:13am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2619 "2025-10-07T10:13:26Z")

</div>

Good morning,

Why I cannot connect more than one HW plug-in battery to my Homey Pro 23? One works fine but after adding 2 and 3 the app stops. I have read that this problem is known from May 2025, but still no solution?  
Perfect Wifi and all Hw and Homey items have the latetst software.  
Like to hear from anyone if any progrees has been made.

René Veenendaal

---

<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 7, 2025, 10:16am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2620 "2025-10-07T10:16:05Z")

</div>

I am not aware of this? What error is there? I have users with 2 batteries.

---

<div class="post-metadata">

**Author:** ![Rene\_Veenendaal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rene_veenendaal/32/79245_2.png) [@Rene\_Veenendaal](https://community.homey.app/u/Rene_Veenendaal)\
**Post date:** [October 7, 2025, 10:35am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2621 "2025-10-07T10:35:15Z")

</div>

In the Homey community this problem has been mentioned in May and had been mentioned several times after that.  
After connecting battery 2 the apps works fine (very nice graphics) and the stops. After removing battery 2 everything works fine again. Restarting the Homey gives no result. I did not restart the app, because I am afraid to lose my settings/lamps/flows.

---

<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 7, 2025, 10:45am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2622 "2025-10-07T10:45:22Z")

</div>

Unrelated to my app. This is Athom’s challenge. I have no control over their Energy dashboard with my code. Sorry.

---

<div class="post-metadata">

**Author:** ![Fusionyx](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fusionyx/32/56405_2.png) [@Fusionyx](https://community.homey.app/u/Fusionyx)\
**Post date:** [October 7, 2025, 10:51am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2623 "2025-10-07T10:51:57Z")

</div>

Home Assistant is working fine with toggle the socket on of off. Also the homewizard app work fine aswell why would homey have a problem with this any idea?

---

<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 7, 2025, 10:54am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2624 "2025-10-07T10:54:39Z")

</div>

Then maybe your Homey has wifi issues? You say HA is ok but from Homey is not. Clearly log shows issues with that socket. And why is it that one socket and not the others?

This isnt an easy job on my end I cant keep track of all the different flavor wifi set ups.

---

<div class="post-metadata">

**Author:** ![Fusionyx](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fusionyx/32/56405_2.png) [@Fusionyx](https://community.homey.app/u/Fusionyx)\
**Post date:** [October 7, 2025, 11:06am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2625 "2025-10-07T11:06:02Z")

</div>

it seems if i disable the device in HASS then it works seems they are not working happy together. Thanks for pointing me in the right direction. I will look into this.

---

<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 7, 2025, 11:06am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2626 "2025-10-07T11:06:48Z")

</div>

Sounds if you are hammering your socket with multiple apps (HA, Homey, HW Cloud?)

---

<div class="post-metadata">

**Author:** ![Rene\_Veenendaal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rene_veenendaal/32/79245_2.png) [@Rene\_Veenendaal](https://community.homey.app/u/Rene_Veenendaal)\
**Post date:** [October 7, 2025, 11:23am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2627 "2025-10-07T11:23:45Z")

</div>

I you have users with 2 HW batteries, how did they manage to do so? There is just one official HW app for Homey and thats is your app. What did those users do that I cannot do?  
I also contacted HW support and they also refer to Athom/you.

---

<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 7, 2025, 11:27am UTC](https://community.homey.app/t/app-pro-homewizard/19267/2628 "2025-10-07T11:27:54Z")

</div>

Wait, confusion here. You can have multiple batteries via my app. That works.  
BUT…as like you they don’t have their 2nd battery in the Homey Energy Dashboard.  
Why? No clue, up to Athom to fix.

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

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