[APP][Pro] Homewizard πŸ§™β€β™‚οΈ

Thanks, much appreciated!

339b1a18-d776-4c37-acb9-9ed554cf07c0

Yeah your wifi connection is jumpy (check that too) and some recover code not working on my end.


2025-11-01T08:07:56.509Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "meter_power.consumed.t1" missing β€” skipping update
2025-11-01T08:07:56.510Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "meter_power.consumed" missing β€” skipping update
2025-11-01T08:07:56.510Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_current.l1" missing β€” skipping update
2025-11-01T08:07:56.540Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_voltage.l1" missing β€” skipping update
2025-11-01T08:07:56.540Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_current.l1" missing β€” skipping update
2025-11-01T08:07:56.540Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_power.l1" missing β€” skipping update
2025-11-01T08:07:56.540Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_voltage.l1" missing β€” skipping update
2025-11-01T08:07:56.540Z [log] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] ⚠️ Capability "measure_current.l1" missing β€” skipping update

    stderr:
      type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}
2025-11-01T02:31:45.397Z [err] [ManagerDrivers] [Driver:energy] [Device:70c56171-b446-449f-b918-0af29f93639a] FetchError: request to http://192.168.1.249/api/v1/data failed, reason: connect ECONNREFUSED 192.168.1.249:80
    at ClientRequest. (/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: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}

It worked without issues on the same setup on the fw version 5.x.x, not sure which exact was it before. Just the fw got updated recently, nothing else changed on my side.

Ok I think I found it please try this test version

Seems to be working now.

Do you know what was the issue?

Here DR if you want to check anything.

be28e598-6bb1-4f9f-8b94-9260fc127044

Yes for some strange reason the capabilities were removed probably due to the app receiving null data for those capabilities which I then remove (as if it is not there then there is no reason to show). I added some additional checking that if I receive a null value AND the capability on Homey is also having a value of null then I can remove it, else skip to avoid incorrectly removal.

Thanks for your donation :smiling_face_with_three_hearts:

1 Like

test/beta

v3.7.9

  • Extra check upon websocket creation to avoid crashes
  • Plugin battery catch all error (unhandled exception)
  • Additional checking and error handling on bad wifi connections (websocket based)
  • (fix) Error: WebSocket is not open: readyState 0 (CONNECTING)
  • Fetch was not defined for fetchWithTimeout function
  • Missed net_frequency update, also made it 3 decimals
  • Capability update fix (avoid removal check)

I started using my Homey Pro this weekend. With this app, I’ve already managed to add my P1 meter and two sockets. However, I can’t seem to add my 3-phase kWh meters (SD630). The Local API is enabled, and I’ve tried all the troubleshooting tips from the original post; everything is found just fine with the mDNS app. All components are on the same network as my Homey, except that the 3-phase meters are connected to a Wi-Fi point in the attic (the rest are downstairs). I’ve already checked my Unifi settings. No isolation or anything like that.

Is this related to the recent reports that something is wrong with 3.7.7 and should I be patient, or does anyone else have a golden tip?

(translated)

@Freezer You can try the latest version, 3.7.9. Maybe that will help.
And this is the english topic, can you translate your post?
Translate with deepl.com , works easy.

This is the Dutch topic. https://community.homey.app/t/app-pro-nl-homewizard/71211

2 Likes

@Freezer as @Mike1233 suggests try test version but honestly version v3.7.x is all about websocket method for P1 and Plugin Battery nothing else.

My guess is, your homey is unable to reach/connect to your top floor access point and it’s connected wifi clients.

Try to test this with app Net Scan

Then add the ip of your kWh (SDM630) like this and see if it is reachable.

3 Likes

Today my devices where unavailable. Homey said the app was not installed. It is not possible to install the app even after several restarts of my homey. The app was already updated to the latest version. What can I do to install the app?

Sorry can’t help. Raise a support ticket with Athom/Homey.
Must be a problem with your Homey.

Same here. Problem solved bij restarting Homey. Everything works fine now.

test/beta

Note: this version will only work on 12.9.x and up.

v3.8.3

  • Removed node-fetch for Homey 12.9.x (nodejs v22 - native fetch)
  • Moved Websocket functions to include to clean up P1 and plugin_battery code

Multicast was not switched on in the wifi network of my homewizard equipment. Now problem solved :slight_smile:

(Multicast requirement is not mentioned in the troubleshooting tips. Could this be added?)

1 Like

Sure will do

Live

v3.8.4

  • Conditional require (node-fetch) it will try to use native fetch with a fallback to take the node-fetch module instead
  • Moved Websocket functions to include to clean up P1 and plugin_battery code

The latest version does not work for me. Older Homey pro 2019 version.

It stopped working right after the update 1h ago

1 Like

Yes I am aware and working on a fix. Older versions run v12 nodejs.
I tried a conditional fetch that would work for both Homey 2016-2019 and Homey Pro 2023. But error seems to be that some keywords dont work.

Please try this one so I know if it works: