[APP][Pro] Homewizard 🧙‍♂️

Hi Jeroen,

Thanks for checking this so thoroughly.

This is very helpful and confirms what we were seeing on our side.

The fact that you see the same title: null behaviour on 60 cards across 17 different apps makes it clear that this is not specific to the HomeWizard app or the Plug-in Battery driver.

We will therefore leave the HomeWizard devices and driver unchanged and take the issue further upstream. We will also report that the client consuming the Homey Flow Card catalogue should tolerate null titles instead of rejecting the complete trigger catalogue.

Good to hear that our report also helped uncover the separate issue in the Battery state changed trigger. We will keep an eye out for the next release.

Thanks again for taking the time to investigate this and for the quick response.

Kind regards,
Johan

Good afternoon

I hope you can help me .

The following problem is new to me .

My homewizard p1 meter is giving me a warning in homey pro 2023 about the 50% wifi never had that before and there is no changes in setup in hardware.

Any suggestions?

Kind regards

Pascal

Hi Pascal, you should know how your own wifi is. :slight_smile:

So how you can improve your own wifi coverage in your house. Perhaps your P1 is without extra usb power? See if you can change wifi channel to one that has less noise due to neighbors changed their wifi. My app has nothing to do or able to change this. My only option is to make you aware your wifi is poor and needs urgent attention. I receive many complaints from users that there is no data in the app or devices are not found. Which all comes down to one core problem. Wifi connectivity issues.

Hi Jeroen

Thanks in advance.

Yes im aware of my own wifi settup and how it performs. Thats why I asked the question. There have been no changes in it at all. And the P1 shows 100% wifi in the homewizard app.

And never had a message from homewizard that connection is lost from my p1 meter.

As my homey pro does. The P1 has a fixed ip and it 1,5mtr from wifi. Again no changes made there. Was wondering if homey app had an issue.

Kind regards

Pascal

Before we start assuming or guess more, are you not mistaken dbm vs %?
Please share screen shot of your P1 where you see %.
Is this P1 APIv1 or the newer APIv2 method?

Hi Jeroen.

I’ve deleted the notifications for now and did a reset on my P1 meter just to be sure that isn’t the problem. I’ve even set the interval poll on 10 seconds for now.

If the notification shows up again in the next few days I’ll share it. Here.

Login in apiV1 that I use

Energy Sockets not found in Homey — ECONNRESET on firmware 4.08 (app v3.19.9 test)

Hi Jeroen,

I’m having an issue adding my HomeWizard Energy Sockets to Homey. They previously worked, but they are no longer discovered by the HomeWizard app.

I’m currently running HomeWizard for Homey v3.19.9 (test version). I installed this version because it restored the functionality of my 3-phase kWh meter.

My setup

  • Homey and all HomeWizard devices are on the same 10.16.30.x subnet.

  • Six Energy Sockets, all running firmware 4.08. No firmware updates are available.

  • Local API is enabled on all sockets.

  • UniFi UDM Pro, UniFi Network 10.6.106, access points on firmware 6.7.58.

  • mDNS discovery works: all six sockets are visible under _hwenergy._tcp.

What I’ve tested

Using HomeyScript directly from Homey:

  • GET http://10.16.30.43/api → ECONNRESET

  • GET http://10.16.30.43/api/v1/data → ECONNRESET

  • GET http://10.16.30.43/api/v1/state → ECONNRESET

I repeated the same tests against a second Energy Socket (10.16.30.177) with the same results.

For comparison, my 3-phase kWh meter (10.16.30.150) responds correctly to the same HomeyScript tests:

  • /api → HTTP 200 with valid JSON

  • /api/v1/data → HTTP 200 with valid JSON

I also toggled Local API off and back on for one socket, but this did not resolve the issue.

The sockets are online in the HomeWizard iOS app, and the API is enabled. Their Wi-Fi signal strengths differ, but both sockets fail identically.

Additional mDNS discovery details

For the affected socket:

  • Service: energysocket-071B92._hwenergy._tcp.local.

  • Host: energysocket-071B92.local:80

  • IP/port: 10.16.30.177:80

  • api_enabled = 1

  • path = /api/v1

  • product_name = Energy Socket

  • product_type = HWE-SKT

  • serial = 5c2faf071b92

The socket is correctly advertised via mDNS with its Local API enabled, but direct HTTP requests from HomeyScript to /api, /api/v1/data and /api/v1/state all fail with ECONNRESET. The 3-phase kWh meter responds normally to the same tests.

Could this be a regression or compatibility issue in v3.19.9, or is there another diagnostic step I should try?

I can provide additional details or run further tests if needed.

Thanks for your work on the app!

Hi Patrick, thanks for your diagnostic results sofar, this helps. Because yout HomeyScript test gets the same ECONNRESET, I don’t think it’s the app. The sockets seem to drop the connection themselves, while your 3-phase meter on the same network works fine.

Two things to try:

  1. Open http://10.16.30.177/api/v1/data in a browser on a laptop in the same subnet. If that works, something between Homey and the sockets blocks it (check client isolation on the sockets’ SSID). If it doesn’t, it’s the socket.

  2. Unplug one socket for 10 seconds and test again.

If neither helps, HomeWizard support is the next stop, since it could be a firmware 4.08 thing.

Hello,

My project is to install the watermater , but i have one question concerning the data, Is it possible to enter the total water volume already consumed and have Homey start tracking from that value? It seems that HomeWizard doesn’t allow you to set an initial reading.

Thank you

In the advanced setting in compensation watermeter?

Zeker!