[APP][Pro] Homewizard 🧙‍♂️

Apps
, ,
2609

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

2610

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

2611

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
1 Like
2612

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

2613

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

2614

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.

2615

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
IMG_37091290×2589 234 KB

2616

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

2617

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

2618

Please focus on your wifi:

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'
}
2619

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

2620

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

2621

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.

2622

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

1 Like
2623

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?

2624

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.

2625

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.

2626

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

2627

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.

2628

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.