I can remove and re-add the single-phase meter just fine, so I don’t think this is an mDNS issue.
I’ve restarted the 3-phase meter multiple times, but it still fails to connect.
Feels like there’s something else at play here.
Nope I wont, to much of a hazzle for these rare cases.
It means I have to modify all 11 pairing code.
I already have catered for a fallback solution for devices that fail mDNS (url setting).
But manually adding a device via an IP address is not an option for me.
@Jeroen_Tebbens Thanks for your help! I just found out that reconnecting it to my network through the app, by selecting “Change wifi” and connecting it to the same network, solved the issue. Really strange, since I had already disconnected and reconnected the meter to the power several times without any results.
Good to hear. See I don’t see the value in adding ip based pairing as there is clearly a malfunctioning device or misconfiguration playing.
@Jeroen_Tebbens I get your point, but I still think having an IP-based pairing option would be really useful as a fallback.
Even if the issue is caused by the device or network setup, mDNS can be unreliable in more complex or mesh networks. Being able to add a device directly by IP would make troubleshooting and recovery a lot easier.
Hello!
With the latest update the current usage is working, but current usages for phase 1, 2 and 3 are not working.
Drop me a diagnostics report please.
5ac306fc-5ac8-4fb9-8e26-27d5d57a4aca
Yes received, but no errors.
Tried to restart app or perhaps restart your Homey?
Currently I have no idea what the reason is.
HomeWizard app ready!
2025-11-07T19:00:42.223Z [log] [ManagerDrivers] [Driver:energy] [Device:c747c9cb-27df-4406-9fa5-e0cd21a32c17] Polling settings for P1 apiv1: 10
2025-11-07T19:00:42.288Z [log] [ManagerDrivers] [Driver:energy] [Device:c747c9cb-27df-4406-9fa5-e0cd21a32c17] Discovered device URL: http://192.168.0.87:80/api/v1
---- stderr ----
I have tried to restart my Homey but no changes. Many parameters haven’t received any updates within the latest 13 hours
Sent another report see if something changed.
New report 93dd7d47-51a9-444b-b28e-3f2b5fe4662e
That’s the same issue as I have. Hereby the diagnostics: 4adb301f-43fb-46db-942c-9b023d2be5ef
I’ve reinstalled the Homewizard P1 meter two hours ago on Homey, so there is no data from before that moment.
Same output, no clue. Try to pull the P1 so it reboots (remove it from your smartmeter and usb cord).
Yours is different. Seems no token is stored. What you can try is to enable polling mode in the P1 adavanced settings.
2025-11-07T17:19:13.992Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:b033c709-c863-4674-b09c-b78dfd4fb778] ❌ Missing token or URL — cannot start WebSocket
I have tried that as well, no changes
Thanks for your answer. I’ve no option to enable/disable polling mode:
The total power consumption is updated each polling cycle. Also the kWh counters and the current of phase 1. It seems to stop after receiving the current of phase 1 value and start a new cycle. Phase 2 and 3 current and power per phase don’t get values anymore.
These values per phase are updated every 10s in Homeassistant, so the P1 meter and the API appear to function correctly.
Am confused here as error is about your energy apiv2 and you show me your apiv1.
stderr:
2025-11-07T17:19:12.553Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:b033c709-c863-4674-b09c-b78dfd4fb778] ❌ Missing token or URL — cannot start WebSocket
2025-11-07T17:19:12.571Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:b033c709-c863-4674-b09c-b78dfd4fb778] Error: Invalid Value: mode
at Remote Process
at HomeyClient.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
at Object.emit (/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:126:50)
at HomeWizardEnergyDeviceV2.setSettings (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:427:41)
at HomeWizardEnergyDeviceV2.onDiscoveryAvailable (/app/drivers/energy_v2/device.js:693:14)
at HomeWizardEnergyDeviceV2._onDiscoveryStrategyResult (/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:215:20)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
statusCode: 400
}
Really clueless here, what was the last working version?
3.8.3.
It stopped working this morning with the update to version 3.8.4
