Ok then something in the poll mode isnt working correctly.
I tested websocket (which is default here) and had no issues so I was sure it should work.
Need to dig for the problem now.
v3.11.9 (test)
- Bugfix: P1 (apiv2) polling mode - Charge mode fixes
- Extra log info on Group Battery State of Charge
- Bugfix: Group Battery State of Charge (increased timestamp check)
- Realtime pull from all batteries as fallback Battery Group State
Jeroen,
I ask if there was an option to dim or turn off the LED on the PIB?
HW replied that the option was already included with the following link:
1 Like
Aah missed that, sorry. Ok then I can implement it.
Hi @Jeroen_Tebbens ,
Regarding base load / sluipverbruik.
I have a smart battery and this means large spread of loads throughout the night. This delivers a ‘reset baseload’ every day and it also shows in my configuration screen:
This is a rough summary of my usage:
My baseload is around 750W. The peaks are 10kW.
Occasionally during the night, my battery supplies back to the grid -10kW. I have no example graph for that behaviour.
Perhaps this helps with your baseload algorithm “resetting to default/fallback’.
If it cannot be solved on your end that is fine, but then perhaps a setting is welcome to not have this measured, or not have this mentioned on the timeline.
Thanks for considering.
1 Like
Hi, good question. I haven’t made up this scenario as it’s a bit of the chart baseload “sluipverbruik” is actively loading or returning energy. Not sure what to do with it at this moment or how to track or measure it properly as this can vary per user. But good point raising it. Thank you.
There is a setting to turn it off in advanced settings of your P1, this was already created.
But what do you expect from me here?
I am running .311.9 test
Since this update, my Plug-in Battery lost connection within the app.
The battery is within the HW app on Android or online, connected and working
Could this be related to latest update?
Restarting your app, or the Homey will not solve the problem for me right now
Not sure, most of the functionality got added to the P1.
Drop me a diagnostics.
5d57c912-3d4f-4a34-8ade-3524762c2558
Homey doesn’t get a respond from your battery at least that is what the log tell me.
Your P1 is websocket mode, you can try websocket mode for the Plugin Battery as well vs polling setting now. Maybe that improves the connection handling.
Stack trace
Note: this log has been manually submitted by a user.
Log ID: 5d57c912-3d4f-4a34-8ade-3524762c2558
User Message:
HW Plug-in Battery offline
stdout:
2026-01-17T16:31:01.876Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-17T16:31:02.346Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c57c89f5-f48d-4fdc-826d-77180135af2e] Settings for P1 apiv2: 10
2026-01-17T16:31:02.451Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] Plugin Battery settings: {
use_polling: true,
polling_interval: 10,
url: 'https://192.168.78.228'
}
2026-01-17T16:31:02.454Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] Restored URL from settings: https://192.168.78.228
2026-01-17T16:31:02.454Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] ⏱️ Polling enabled at init, interval 10s
2026-01-17T16:31:03.272Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c57c89f5-f48d-4fdc-826d-77180135af2e] 🔐 Sending WebSocket authorization
2026-01-17T19:58:04.763Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-17T19:58:05.154Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c57c89f5-f48d-4fdc-826d-77180135af2e] Settings for P1 apiv2: 10
2026-01-17T19:58:05.226Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] Plugin Battery settings: {
use_polling: true,
polling_interval: 10,
url: 'https://192.168.78.228'
}
2026-01-17T19:58:05.228Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] Restored URL from settings: https://192.168.78.228
2026-01-17T19:58:05.228Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] ⏱️ Polling enabled at init, interval 10s
2026-01-17T19:58:06.032Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c57c89f5-f48d-4fdc-826d-77180135af2e] 🔐 Sending WebSocket authorization
stderr:
2026-01-17T18:41:43.881Z [err] [ManagerDrivers] [Driver:plugin_battery] [Device:43b6a88b-710a-4b41-b492-ff86e3343fb2] Polling error: request to https://192.168.78.228/api/measurement failed, reason: connect ETIMEDOUT 192.168.78.228:443
1 Like
Testing locally but already working for plugin battery now:
2026-01-17T22:33:13.706Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:e500830d-845f-46a6-9618-29413fd91f2c] LED brightness set to 2%
2026-01-17T22:33:17.903Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:e500830d-845f-46a6-9618-29413fd91f2c] LED brightness set to 100%
2026-01-17T22:33:23.581Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:e500830d-845f-46a6-9618-29413fd91f2c] LED brightness set to 10%
1 Like
Changed and immidiate online
1 Like
Ah great, not sure if the tcp connection got full or response is delayed somehow. I can try to increase the timeout detection for the PIB. Websocket should be better as it is nearly realtime data (every second).
EDIT:
Other reason might be more connections are hammered to the plugin battery. Log does not say connection reset or refused only timeout but perhaps if there are multiple sessions or polling interval of 1s it will hurt and show unreachable behavior.
So hopefully the websocket method (different from polling) is more stable for you.
Polling method is fetch from Homey to your PIB. Websocket is the other way round.
The plugin battery pushing its data to Homey instead.
1 Like
At this point in time, nothing. If you ever consider smart homes with batteries to be supported, you now have an idea of what to expect measurement-wise.
Thanks for an amazing App!
I added some adjustment last night to ignore power return (ie batteries).
Current test version is still pending certification so cant release my local alpha till then.
1 Like
@Ad_van_Liempt thank you for your donation 
test / beta
v3.12.4
- Baseload ignore return power (compensate battery return to grid datapoints) @RogerSt
- Plugin Battery LED brightness adjustment (user request) - @Ad_van_Liempt
- Bug fix: Battery Group (SoC missed when there are fetch errors)
- Bug fix: Polling deadlock fix for (energy, energy_socket, SDM230, SDM630, watermeter)
- Energy socket setAvailable fix
- Bugfix: _cacheSet undefined
(Websocket & caching)
- Optimized external meters hash calculation (eliminates array.map() garbage collection pressure)
- Battery group settings now cached with 60-second refresh
Baseload / sluipverbruik
- Detection algorithms now run every 30 seconds instead of on every power sample
- Eliminates expensive array scans during night hours
1 Like
I’ve noticed a discrepancy between the total power consumption measured in the Homewizard app for Homey and the Homewizard app itself.
This is what’s measured in Homey;
And this is what’s measured in the Homewizard app itself;
As I type this, I see on the developer page that the value is from 2 hours ago. Isn’t it possible to retrieve this in real time?
meter_kwh_this_day is not a capability from my app. That one is from Power by the Hour app.
1 Like
Hi @Jeroen_Tebbens,
The P1 (HomeWizard) is crashing again. It is multiple times a day. After a restart everything is working again, until it crashes again. The difference now is, that this is on the new Homey Pro 2026 (the Homey Pro 2023 is working fine).
The Report code is: e220fde4-e75a-4307-8613-04b2886cbe6c
