[APP][Pro] Homewizard 🧙‍♂️

Apps
, ,
2044

Jeroen, is it possible to also show the daily consumption with the P1 meter?

Scherm­afbeelding 2025-05-15 om 09.43.50
Scherm­afbeelding 2025-05-15 om 09.43.50466×1294 75.8 KB

Something like this

Scherm­afbeelding 2025-05-15 om 09.46.31
Scherm­afbeelding 2025-05-15 om 09.46.31632×356 29.9 KB

2045

Use Power by the Hour app for that. Pointless for me to add such code while there is a great app that does that.

2046

I use “Power by the Hour” but I get such extreme deviation values ​​that it cannot be used.
I removed the “Power by the Hour” meter and added it again. Let’s wait and see what the result is

Scherm­afbeelding 2025-05-15 om 10.09.12
Scherm­afbeelding 2025-05-15 om 10.09.12464×869 54.4 KB

2047

Somehow the link between P1 and the “Power by the Hour” doesn’t work. After adding it the _power stable remains

2048

Why? Sorry but I cant really help or fix if I have no clue what “doesnt work”

2049

I understand! After two reinstalls it seems to work. Let’s wait and see!

2050

beta/test
v3.6.19

  • Attempt to register the condition and action flow cards (error)
2051

Back to why I would like to see the daily consumption in the P1 meter.
You referred me to “Power by the Hour” However, that only updates the data once per hour plus it subtracts the generated power from the consumed power.
I have been logging to Pvoutput via Domoticz since 2013. I now want to do this with Homey. That is why it would be nice if you could see the total daily consumption in the P1 meter so that it can be exported.

2052

Happy?

image
image119×148 4.01 KB

1 Like
2053

Happy!

2054

@Jeroen_Tebbens Since yesterday evening I have problems reading the 3f meter. I do this with a plc and now also with the Homey every second.

Can requesting every second also cause a problem in the Home Wizard meter (app)?
It seems that the Home Wizard cannot process the data request fast enough, which is why there is a delay in their app.

When I stop polling Home wizard works normal.

Error from Raspberry Pi:
HTTPConnectionPool(host=‘192.168.178.24’, port=2020): Read timed out. (read timeout=5)

(Not Homey related)

Could you explain this?

2055

It’s not my app it’s your Homey probably not able to handle the every 1s
poll. Drop me a diagnostic report. It might hold an answer to my thought. Perhaps change polling from every 1s to 2 or 3s?

2056

I’m at a polling time of 6 seconds now. Then I have 10 data points in a minute. That’s fine for my EPM flow. And seems to work well on a pro 2023 with Ethernet connection and P1v2.

2057

Strange, after 14 hours no more errors and the Pi and Homey are working again with 1 sec. polling. I don’t understand anything. :person_shrugging:

The problem seems to be in the Home Wizard 3 phase meter because the 1 sec. display also stutters here.

Rapport
c91e21ae-f627-40ba-8dd8-e7be5d5e2952

2058

No errors in report.

2059

Thanks, I didn’t expect that either. Problem is in the Home Wizard or the connection I think.

2060

I don’t get your set up with pi and port 2020

2061

Created a flow to set the Battery in Standby Modus but execution of the card failed.
Setting the Battery in Standby mode via advanced settings didn’t work either.
c3e60cf7-dcff-4512-9899-64cba1263764

2062

Still register error? But also see your P1 has trouble communicating (timeouts and json errors).


2025-05-17T04:06:23.319Z [err] [ManagerDrivers] [Driver:energy] [Device:7bca3a46-5feb-423e-bae5-ebeb939eb1cf] Error: Invalid capability (meter_power.consumed) value type. Expected: number. Got: undefined
    at Remote Process
    at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
    at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
    at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
    at /node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:568:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at HomeWizardEnergyDevice.setCapabilityValue (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:560:23)
    at /app/drivers/energy/device.js:167:28
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  statusCode: 400
}
2025-05-17T04:06:24.978Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:57fd2f9b-1301-4f89-91ad-87c3ff4f73dd] Error: Network error: request to https://192.168.x.x/api failed, reason: read ECONNRESET
    at /app/includes/v2/Api.js:103:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async module.exports.api.getInfo (/app/includes/v2/Api.js:97:17)
    at async /app/drivers/energy_v2/device.js:372:20
unhandledRejection:
Error: Not Found
    at module.exports.api.setMode (/app/includes/v2/Api.js:149:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2063

Do I understand correctly that (if you use the beta for the P1 meter) you need to use the P1 (apiv2) to read the battery mode?

This is not (yet) possible with the old P1 meter?