The point is mDNS discovery is only needed at start. So something connectivity wise is different from your old HomeyPro2019 compared to your newer Pro2023.
Are also having the LAN adapter? If yes disconnect and try again.
Ok share me the multicast setting on your Fritzbox for the SSID that your 3f kWh meter uses.
No LAN adapter
No additional settings on WIFI , most is standard or set to auto.
Tickbox with “Beveiligingsinstellingen voor de Wi-Fi-toegang optimaliseren voor een betere compatibiliteit met oudere Wi-Fi-apparaten“ is enabled
tickbox “Actieve Wi-Fi-apparaten mogen met elkaar communiceren” is enabled
I can’t find any Multicast settings
Strange behaouver , because all other HW stuff is connecting fine ( and connection very fast)
Okey shoot me 
Re-connect the 3f KWH device to the WIFI via HW app , same WIFi , same credentials.
And now its connected to Homey 
Created a new report ; 42edf0c2-9a6d-4d52-ac9f-9763293e9fdb
Appreciate you’re help !
Ah great 
Confirmed, your Homey says its ok:
Discovered devices: {
'removed': DiscoveryResultMDNSSD {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
id: 'removed',
lastSeen: 2025-10-08T09:57:46.459Z,
address: '192.168.xxx.xxx',
host: 'kwhmeter-XXXXX.local',
port: 80,
name: 'kwhmeter-XXXXX',
fullname: '',
txt: {
api_enabled: '1',
path: '/api/v1',
product_name: 'KWh Meter 3-phase',
product_type: 'SDM630-wifi',
serial: 'removed'
},
[Symbol(kCapture)]: false
}
}
Try test version I released. Start add/pair and share me diag report.
Version v3.6.75 now live
so had a power outage, after that it worked again xp. so reboot fixed it xp.
But is it posible that the option: ‘‘meet alle vermogen’’ is gone?
Cant seem to activate it anymore.
Sorry don’t know what you refer to.
Which device is this? P1, SDM230, SDM630?
HWE-KWH3 a kwh3 meter. it worked in youre test version v3.5.2 .
You added it as SDM630 (p1) mode?
Code for tracking total energy is enabled:
"energy": {
"cumulative": true,
"cumulativeImportedCapability": "meter_power.consumed.t1",
"cumulativeExportedCapability": "meter_power.produced.t1"
},
no, just as the normal.
I will delete it and try to reconnect it.
Or i have to wait for another power outage .
That is your choice.
I added that SDM630 p1mode a while back for a reason (for those that dont have a P1 dongle and use the kwh instead). Same as the 1F (SDM230) also p1mode.
Hi, Just made a report for you 965a09b6-090e-4aea-82e6-28b9480183fc,
Since yesterday I have no more data from my HomeWizzard 3P (setup as P1). The local API is on and works fine if I use the URL. HomeAssistant still works fine.
Also noticed the App was updated yesterday, and since then my data has stopped. Perhaps it is related? Restart of Homey and/or the App does not solve it.
Your mDNS is failing, Homey is unable to find your device.
Check first post in this topic for suggestions.
Discovered devices: {}
stderr:
n/a
Hi I’ve been using homewizard smartplugs for quite a while now through Homey, but since recently it keeps giving the error: “network error during onRequest”, resetting the homewizard app or the homey seems to fix this temporarily, but im in need of a more permanent solution
Ok,
So why does this suddenly happen? Has worked flawless for the last months with no change in my network setup?
Will have a look. Thanks
Sorry don’t understand, need more details.
Edit: searched that error in my code and it tells me that Homey was unable to connect to your socket. So there is an unstable wifi connection with your Homey and/or socket.
See if you can find that socket in your accesspoint log / connected state. Does it keep reconnecting all the time?
