If nothing changed and stopped working since 2 day using an older app version, how can it be this app then? Is your Homey overloaded? Does it have enough resources free? Did you try a reboot of your Homey 2019?
You can try latest test version but that mainly focuses on the battery policy device feature which is something you dont have as per your commited log.
Because HW app is the only one giving trouble with unreachable devices since the last days (having 103 devices with multiple apps) and memory usage increase (after the update), so that’s why I ended up here
I got nothing to work with based on your log, there is no crash info or memory/cpu warning listed. Homey purely complains about unable to reach your wifi devices. Interval / polling is fine with 10s as per log you shared so that is not the case either.
I really feel you are now hitting your max of your Homey 2019 where this app seems the first signal showing this.
I suggest a reboot of your Homey. Further check other apps on your Homey that may have increased memory size as well making it hard to work properly.
I will release 3.18.0 soon as impoved cpu and memory but that is battery policy focused but perhaps it does something for you.
Hmm, thanks for the effort and quick replies,.. I’m aware of the limits of the HP19. A reboot seems like to have calmed down the HW app. Hopefully everything will go back to normal.
Good to hear, no problem. But I cant support this any longer. I would have a full mailbox if it was the app with crashes and (unasked) diagnostics.
Beta/test v3.19.0
Settings:
Selection for meteosat or solcast. Will drop solcast if meteosat proofed itself. The free key with 10-12 updates is a problem (ratelimit / other sources use same key).
The total current is not shown. The P1 meter API V1 Json contains active_current_a but the shown Current is same as Current Amp phase 1.
{
"wifi_ssid": "SSDINAME",
"wifi_strength": 100,
"meter_model": "ADN9 7534",
"unique_id": "GID_3",
"total_power_import_kwh": 180.281,
"total_power_import_t1_kwh": 180.281,
"total_power_export_kwh": 0,
"total_power_export_t1_kwh": 0,
"active_power_w": 325,
"active_power_l1_w": 130,
"active_power_l2_w": 152,
"active_power_l3_w": 45,
"active_voltage_l1_v": 237.5,
"active_voltage_l2_v": 238,
"active_voltage_l3_v": 237.4,
"active_current_a": 1.6,
"active_current_l1_a": 0.7,
"active_current_l2_a": 0.8,
"active_current_l3_a": 0.1,
"external": []
}
Edit: The firmware version is 6.0305.
Looks like you are on an old firmware of your P1 as active_current_a is not w valid datasource anymore so removed it. But let me make it somehow backwards compatible again.
I updated my P1. The version is now 6.0503. active_current_a is still there.
{
"wifi_ssid": "SSDINAME",
"wifi_strength": 100,
"meter_model": "ADN9 7534",
"unique_id": "GID_4",
"total_power_import_kwh": 180.558,
"total_power_import_t1_kwh": 180.558,
"total_power_export_kwh": 0,
"total_power_export_t1_kwh": 0,
"active_power_w": 415,
"active_power_l1_w": 130,
"active_power_l2_w": 240,
"active_power_l3_w": 45,
"active_voltage_l1_v": 237.8,
"active_voltage_l2_v": 237.5,
"active_voltage_l3_v": 237.5,
"active_current_a": 2.1,
"active_current_l1_a": 0.7,
"active_current_l2_a": 1.3,
"active_current_l3_a": 0.1,
"external": []
}
Strange as api documentation stripped or will soon.
Anyway I added the backward compatible replacement. Will come with next release v3.19.1 so it will either pull that datapoint (if it exists) else it will add up all 3 currents and populate the main one.
Test version (v3.19.1)
@Jeroen_Tebbens, I have a question; I am using the not-connected trigger card for the P1 meter (APIv1). I didn’t see this trigger in the API v2 version, is that correct?
I use the P1 meter for charging station load balancing, and for that, it is important to know that the P1 meter has a continuous connection. Wi-Fi is never perfect, so I have built in rules that reduce the charging speed after a certain amount of time offline, just to be safe. The not-connected trigger worked perfectly for this. But I want to switch to the API v2 to reduce load on Homey.
Otherwise, I will look into Smart Presence/ Net Scan like solutions, no problem.
Good catch, Will be fixed in next release. Working on the post 2027 salderen code at this moment but your request is included.
