Ok, good to hear. Cleaning up debug info as this might mask the cause of these spike.
New test version v3.15.112
Ok, new version (again) more tweaks.
There will always be peaks but should not crash. Great news.
Hi Jeroen, to come back on the isssue it looks that there will only a crash at 07:00 in de morging. today and yesterday. (version 3.16.0)
“Hi Jeroen, I’ve been experiencing an issue for a while where the gas consumption isn’t being displayed correctly in Homey. The strange thing is that the gas consumption is shown correctly in the native HomeWizard app. Could you take a look at the diagnostic log and see if you can find anything?”
22a223eb-09e0-4135-973c-b80b7fcd2f44
Sorry confused, you show me Homey Energy graph rather than the P1 daily gas usage of what is measured by the device itself. And dont spam me with diagnostics if I dont ask for it.
Assuming here you got 2x P1’s adding up gas together so Homey Energy gas shows combined.
@Jeroen_Tebbens , I have a question
I use the P1 meter to calculate the running average of the load per phase (average of 5 measurements). I need this for load balancing of a charging station. For this, I need the current per phase every 4/5 seconds.
Initially, I used APIv1; that worked well, but I found the CPU load a bit on the high side (CPU 0.9%, Homey 2023).
Then I saw that APIv2 was recommended for frequent updates, so I switched to that(WebSocket every 4 sec and polling off). CPU load dropped to 0.7%, so that is good.
(For the complete picture: I have a second P1 meter, a water meter, and 2 sockets. All set to polling 10 sec)
However, I now noticed that current amps per phase-capabilities (“Huidig Amp fase 1/2/3”) are only updated every 32 sec (and some more capabilities like voltage). With APIv1, that was equal to the polling freq (every 5 sec).
Is this intentional?
Using current (amps) is the purest option in my case, because that is what the fuses react to. Wattage is slightly less reliable, because of heavy equipment and slightly fluctuating voltage.
What is the best course of action?
I did notice that the phase load capability (“fase 1/2/3 belasting %”) is updated every 4 seconds; how exactly is this determined? Maybe I could use this, but only if this uses the real current of the phases every 4 sec.
The energy_v2 websocket mode has the Amp’s and Volts updated every 10s not 30s.
Which makes me wonder your wifi has troubles. Check the websocket tab in Homewizard app settings for issues.
EDIT: You are right, eventhough code updates every 10s I see the 30s in my P1 as well.
Let me investigate (assuming the websocket update has some different message update interval)
Wifi is not flawless here (long mesh-network), but good enough. But the updating of the values is quite consistent: 4 sec for wattages, around 30 sec for amps.
But also 10sec updates is a bit too long for me, because I need to detect the use of heavy equipment within 30 sec or so. For this I need at least 5 samples from the P1-meter.
But maybe I could use “fase 1/2/3 belasting %”? Do you know how this value is calculated?
Yeah I’ve found the problem here, it was indeed 30s and not 10s.
I changed it to 5s now, but we need to monitor the CPU increase.
I went through a lot of pain and time to get it where it is now.
Test version v3.16.1 has this change.
Thanks for the super fast adjustment, and I can understand that this app is tricky to fine-tune.
I installed the test version; what I see now is the following:
| WebSocket Update | Amps Update |
|---|---|
| 4 sec | 8 sec |
| 2 sec | 6 sec |
| 5 sec | 5 sec |
So it seems that a new Current Amps is internally available every 5 sec, but it only becomes usable in the ‘heartbeat’ of the main update frequency.
But this is totally fine by me, 5 sec is perfect.
I will monitor the CPU load for a while.
Yes correct, to be exact, the update is upon change every 5s.
So if values are the same it wont update so that might be the Amps going 8s sometimes.
