Very much appreciated
1 Like
v3.6.42 runs fine now, Jeroen!
1 Like
Hi Jeroen, everything is working fine here all the readings from the 3 phases is fine, see attached screenshot
Thanks for all your effort and best regards Peter.
1 Like
@Jeroen_Tebbens Hi,
The app keeps crashing, I have restarted the app a few times and also reinstalled the app.
Also reconnected the P1 dongle again to wifi.
A few seconds after this message, it only says “device unavailable.” A few seconds later, I see that the P1 meter is back online. But a few seconds later, the same thing I described above starts all over again.
Diagnostic report code:
9775b6ed-ec68-47be-a35d-66f8c5ae5bbb
Your polling is set to 0…..why?
Settings for P1 apiv1: 0
2025-07-09T22:23:31.055Z [log] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] URL: http://192.168.2.3:80/api/v1
stderr:
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.221Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.223Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.224Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.225Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.227Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-09T22:23:41.233Z [err] [ManagerDrivers] [Driver:energy] [Device:809f06b3-1291-4d7f-aaa2-6e420ae9f999] FetchError: request to http://192.168.2.3/api/v1/data failed, reason: socket hang up
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketOnEnd (node:_http_client:525:9)
at Socket.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
<--- last few gcs --->
i[63656:0x43d498a0] 16307 ms: Mark-sweep (reduce) 62.7 (65.8) -> 62.5 (66.0) MB, 11.2 / 0.0 ms (+ 8.1 ms in 25 steps since start of marking, biggest step 0.4 ms, walltime since start of marking 154 ms) (average mu = 0.829, current mu = 0.879) finalize [63656:0x43d498a0] 16487 ms: Mark-sweep (reduce) 63.4 (66.0) -> 62.9 (66.3) MB, 48.7 / 0.1 ms (+ 13.9 ms in 38 steps since start of marking, biggest step 0.6 ms, walltime since start of marking 158 ms) (average mu = 0.733, current mu = 0.653) finalize
<--- js stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xb826e4 node::Abort() [com.homewizard@3.6.37]
2: 0xa9bf08 [com.homewizard@3.6.37]
3: 0xd43e90 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [com.homewizard@3.6.37]
4: 0xd44060 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [com.homewizard@3.6.37]
5: 0xf22814 [com.homewizard@3.6.37]
6: 0xf347ac v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [com.homewizard@3.6.37]
7: 0xf35754 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [com.homewizard@3.6.37]
8: 0xf38d2c v8::internal::IncrementalMarkingJob::Task::RunInternal() [com.homewizard@3.6.37]
9: 0xe1d968 non-virtual thunk to v8::internal::CancelableTask::Run() [com.homewizard@3.6.37]
10: 0xbe4ac4 [com.homewizard@3.6.37]
11: 0xbe7ef8 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [com.homewizard@3.6.37]
12: 0x15e8e64 [com.homewizard@3.6.37]
13: 0x15fafc8 [com.homewizard@3.6.37]
14: 0x15e98cc uv_run [com.homewizard@3.6.37]
15: 0xacf478 node::SpinEventLoop(node::Environment*) [com.homewizard@3.6.37]
16: 0xbc1560 node::NodeMainInstance::Run() [com.homewizard@3.6.37]
17: 0xb4036c node::LoadSnapshotDataAndRun(node::SnapshotData const**, node::InitializationResult const*) [com.homewizard@3.6.37]
18: 0xb43c2c node::Start(int, char**) [com.homewizard@3.6.37]
19: 0x7f91ad9dd8 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xacd9a8 [com.homewizard@3.6.37]
⚠ The app has crashed.
Exit Code: null, Exit Signal: SIGABRT
I wasn’t aware of that. I changed the polling to 1. Is that what caused the crashes?
I wasn’t aware of that. I changed the polling to 1. Is that what caused the crashes?
I will add extra check to avoid value 0.
Strange nothing in log.
Do you have a 1 or 3 phase grid? I think it is about the sliders I added.
---- stdout ----
HomeWizard app ready!
HomeWizard Heatlink has been inited
HomeWizard has been inited
HomeWizard EnergyLink has been inited
HomeWizard Rainmeter has been inited
HomeWizard Kakusensors has been inited
HomeWizard Thermometer has been inited
HomeWizard Wattcher has been inited
HomeWizard Windmeter has been inited
Settings for P1 apiv1: 10
Offset polling for Watermeter: 2
2025-07-09T15:55:00.526Z [log] [ManagerDrivers] [Driver:energy] [Device:6bf624ae-c1f9-4c07-87d3-afcbd6551fe7] URL: http://192.168.1.254:80/api/v1
2025-07-09T15:55:03.705Z [log] [ManagerDrivers] [Driver:watermeter] [Device:4fd25f27-9665-47de-89e1-3b9254c7fecc] URL: http://192.168.1.154:80/api/v1
---- stderr ----
Thanks!
Since I changed it to 1, I haven’t had a crash.
I actually want a real-time display of the current wattage in my home. That’s why I set the polling rate to 0, thinking it would change immediately if the wattage changed.
Yeah 0 will break the polling as there is no way to 0s fetch.
3 phases
Ok I’ve prepped v3.6.43 now for test. Please try that one. Problem is my energy grid is a 1 phased link not 3 so some of the code doesnt kick in when I test it locally (sadly).
I added/moved some checks and code and hope this improves/fixes the crash for you.
1 Like
No more crashes, thanks.
1 Like
Okay than i leave it on 1!
1 Like
Since a week (or two maybe) I have an issue regarding my P1. It stops showing actual energy usage in Homey so my energy tab is not accurate from that time. Plugging the P1 out and in again it starts working again for a couple of days. What is strange to me is that the P1 is still connected to the internet and my HW Energy display keeps showing actual energy consumption. The mDNS looks like is not visible any more when this happens but what I cannot explain then is why my water meter has no issues. The P1, water meter and energy display are all connected to the same wifi network, no client isolation is active. My Homey is connected by Ethernet adapter and also connected to the same network. I now installed the test version of the HW app, hopefully this changes the behavior but I’m curious if more people have same kind of issues. Running on HP23 by the way
Thoughts on this is that the mDNS problem you face is limited to one AP where you P1 connects to. Another issue might be you have changed the polling interval to 1s?
First post in this topic suggest to reboot/restart the AP concerned as that seems to fix identical issues raised by other users. It all comes down to wifi problems which I cant see or control from my app point if view.
I already added timeouts and retry attempts (3x retry when timeout happens).
I test every release in publish in my own wifi (unifi/ubiquiti) network and that works fine (even with my P1, watermeter,kwh, sockets in an IoT vlan).
You can drop me a duag report but am 95% sure it supports my thoughts above.
1 Like
That’s a great tip Jeroen, I will check which AP which HW device has connected. At this moment all on the same AP. I will send a report if same error shows up again
Just a reminder to not restart the app or homey before you sent such a report. Log is lost after a restart.
1 Like
