Tested with version 3.6.32. It works via flows!
I get the idea switching from full to zero I had to do the flow twice. I will retest but get the message the P1 meter is over connected.
I have HA and now also Homey connected to the P1 with 2 batteries.
1 Like
Yeah might be a little to much of your polling is very often (every 1s etc).
But happy to hear the cards work! 
Now the real fun starts.
1 Like
Goto https://my.homey.app/insights, and lookup your P1;
When it appears:
Power usage (“huidig vermogen”) or similar descriptions can be present multiple times.
You can delete the one entry which doesn’t seem active and has no recorded data:
If it has recorded data, you can save it by downloading it.
This cannot be reverted, the only way to revert is to restore a cloud- or offline backup.
1 Like
Okay. I have signed up for it. Thanks.
Hi Peter
Thank you for the response.
I have two items that have the same values from the past. “Huidig vermogen” and “Stroomverbruik”.
“Huidig vermogen” stopped since the upgrade to the new Homey 2023, and “Stroomverbruik” is still active.
Tried to delete the date from “Huidig vermogen” and get this error:
No problem, Arnold.
Oh, bummer.
Because I noticed the word “cache”:
Try to force reload the web page, or open it in a private tab, and then delete the entry. Maybe that works.
If not:
You’d contact Support about why deleting an Insights entry results in that error after migrating.
P1 meter requires at least firmware 6.0201 (still beta)
Install test version v3.6.32 of my app.
Add P1 Meter (apiv2)
Then in the flow section you find the action cards with the new added P1:
C O N G R A T U L A T I O N S v3.6.32 is working with the Flow Cards for changing the PiB mode!
Really a great job done!
3 Likes
Hi Jeroen,
Thanks for adding the Daily usage capability! Only it appears to use UTC time instead of local time.
Is it possible to have it follow local time so it resets at local midnight time?
This is from my EU/Amsterdam +2 GMT based Homey:
No hurries of course.
Ah of course, Homey uses internal UTC as timezone.
Was afraid of that.
This should be fixed in version v3.6.33.
1 Like
Thanks Jeroen!
Hoi Jeroen. Just now started the flow for Full Charge mode. No effect. Also second time. Via geavanceerde setting it works directly.
I thought so yesterday but I was not sure.
No messages were shown.
English please here.
Please drop me a diagnostic report.
181ebccb-e30f-4eaf-a0ce-23ace7a38d2d
Thanks!
Your P1 is having connectivity problems. I see a lot of connection resets and timeouts.
2025-05-26T12:37:36.967Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:34830d3d-749c-412d-ab7e-bd0c4102f537] ActionCard: Set Battery to Full Charge Mode
api.setMode: This mode will be sent to P1apiv2: to_full
Error set mode to full charge: Error: Network error: request to https://192.168.1.22/api/batteries failed, reason: read ECONNRESET
at /app/includes/v2/Api.js:145:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.setMode (/app/includes/v2/Api.js:137:17)
at async /app/drivers/energy_v2/device.js:82:28
Thank you for the quick response. I was affraid for that.
2 batteries, Homewizard and 1 Homey connection is perhaps too much. I allready disconnected the HA connection before changing the mode.
I think no problem on your “side”. When I think about it, changing it via the advanced settings is different than via a flow? Because it then always works?
No it literally is using the same setMode function. So you were lucky it worked via settings.
I am looking at adding a retry code section to this setMode with a retry attempt of 3 with 2 seconds delay. This isn’t perfect but hopefully a workaround to unstable P1 connections. You already adjusted your polling interval from 6s to 10s today at 13:28. Not sure when you disabled (?) HA polling.
1 Like
Tested here with 1 PiB. Both in a flow and with a virtual button. Works perfectly. Jeroen thanks!
1 Like
Thx for the confirmation 
