[APP][Pro] Homewizard 🧙‍♂️

Apps
, ,
2164

Four IF actions higher and lower power for one 3 phase meter.

I don’t know what’s the difference between power and current power.

1000014458
1000014458493×329 27.8 KB

1000014457
1000014457505×232 19.5 KB

2165

Check your device values it might be a duplicate with same value.

2166

Indeed, looks like a duplicate.
Slow polling = same value
1 sec. polling = not always the same.

Foto = fast polling

1000014459
10000144591440×3216 247 KB

2167

Hi Jeroen. I have a new HW P1 meter. Installed it, batteries are working well, added the new P1 to Homey and changed the flows. When I change the mode, the new mode is visible in the app (under advanced settings) but it isn’t changed in HW, batteries are charging despited of setting the mode to standby.
Do I have do something because of the new P1?
494e02ad-dd93-4b16-8a56-3aaea0bd9d54

edit: when I change the mode via a curl command (after getting a token) the return maessage is “Nothing matches the given URI”.

2168

You are facing connection issues (retry fails)


2025-06-05T10:01:55.181Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:30c57a7b-50e7-4e06-9260-1021ad05cedc] Mode for Plugin Battery via P1 advanced settings changed to: to_full
api.setMode: This mode will be sent to P1apiv2: to_full
2025-06-05T10:45:19.005Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:30c57a7b-50e7-4e06-9260-1021ad05cedc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Error set mode to standby: Error: Max retries reached, fetch failed
    at module.exports.api.setMode (/app/includes/v2/Api.js:161:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/drivers/energy_v2/device.js:107:28


Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
Attempt 1 failed: HTTP error! Status: 404
Attempt 2 failed: HTTP error! Status: 404
Attempt 3 failed: HTTP error! Status: 404
unhandledRejection:
Error: Max retries reached, fetch failed
    at module.exports.api.setMode (/app/includes/v2/Api.js:161:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2170

It’s ok Peter and you are right, it is very frustrating for me getting diag reports without asking for it.

These type of reports are common and I just ignore them:

image
image704×385 12.2 KB

1 Like
2171

Sorry Jeroen for the diag report, I thought I was being helpful (and because there were no messages in the Homey app).

2172

It’s ok, was having a short break from work as I am still twiddling with the battery code and P1 in the app. I just cant keep looking at every report as 95% are wifi connection issues and sadly so is yours. Your P1 deny/drops the request, getting timeouts/retry.

I will add more alarms and maybe a notification/timeline alert.

2173

Okido. Thanks.
Strangely enough, I can get info from the P1 with curl, for example
curl https://192.168.xxx.xxx/api …:
{“product_name”:“P1 Meter”,“product_type”:“HWE-P1”,“serial”:“5c2faf35c624”,“firmware_version”:“6.0112”,“api_version”:“2.0.0”}
But when I use curl https://192.168.xxx.xxx/api/batteries … for battery info I get:
Nothing matches the given URI
Looks like there is a wifi connection but something else is happening. I will try to investigate further…

2174

“6.0112" firmware doesnt have batteries support yet

image
image648×331 15.8 KB

2175

I’m very sorry, I have wasted your time :face_with_peeking_eye:, I didn’t look further, I requested to join the beta program and received message form HW that P1 was oké and also the history was added.

2176

Battery control is still beta, I understand everyone wants it.
Making it fool proof and keep checking firmware is a nightmare at this moment.

2177

Yes, I can imagine…My first P1 was in the beta program, I will have to wait somewhat

2178

My developer p1 died (was beta firmware, after reset cant get it back to my wifi) so rely on what others provide as feedback at this moment.

1 Like
2179

test/beta

v3.6.34

  • Plugin Battery: added time_to_empty and time_to_full (minutes)
2180

Hi All ,

sinds i have the homeward batterij my p1 is often offline in Homey it only will start connecting after a reboot op the p1 Disconnect /connect is there a way to solve this

The energy ap keeps connected so any one suggestions ?

2181

Drop a diag report but 95% of these issues are on wifi connection problems.

1 Like
2182

Thanks for the advice I made a Diag after the rebootI send the code .

Never had issues p1 is already in place for 9 years wifi 6 is in place 2022 butt I did now a reboot of the complete system will test if this did help .

2183

As expected unreachable errors:


2025-06-14T06:50:34.900Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:50:41.844Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:50:41.845Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:50:51.860Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:50:53.748Z [err] [ManagerDrivers] [Driver:plugin_battery] [Device:c701e06c-8b6e-470d-b6b5-1fe5f9a72dcf] Error: Network error: request to https://192.168.1.195/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.195:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/plugin_battery/device.js:138:20
2025-06-14T06:51:01.908Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:51:08.468Z [err] [ManagerDrivers] [Driver:plugin_battery] [Device:c701e06c-8b6e-470d-b6b5-1fe5f9a72dcf] Error: Network error: request to https://192.168.1.195/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.195:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/plugin_battery/device.js:138:20
2025-06-14T06:51:11.893Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/measurement failed, reason: connect EHOSTUNREACH 192.168.1.14:443
    at /app/includes/v2/Api.js:65:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
    at async /app/drivers/energy_v2/device.js:302:20
2025-06-14T06:54:17.595Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:be4168eb-e444-413a-8a76-9f47e996b269] Error: Network error: request to https://192.168.1.14/api/system failed, reason: Parse Error: Expected HTTP/
    at /app/includes/v2/Api.js:84:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
    at async /app/drivers/energy_v2/device.js:303:26

Homey has trouble reaching your P1 so perhaps its Homey with a bad wifi connection?

2184

Hi Jeroen,

thanks I will check the homey connection.