Yeah I wonder why, already had a slap in my face with community awards.
2 Likes
“Thanks for your help. It hasn’t helped so far, and I have created a ticket with HW.
To be continued.
Hi Jeroen,
Just purchased an 3 phase kwh meter from Homewizzard expecting it to connect to homey easily. However I seem to not be able to get the device in Homey. I installed the app - > add new device → select Homewizzard → kWh Meter (3 phase) → press connect → accept local API warning → press continue → it starts searching → then i get the message: “no new devices found in your network”
What I did to resolve this:
- Doublechecked that I have the local API enabled
- Installed test version of app
- Found out the IP address of the device and called the API: http:///api/v1/data which returns JSON data.
- Did a mDNS discovery on _hwenergy._tcp which returns the IP, port (80) and path (/api/v1) which seem good to me too.
- Restarted Homey
- checked mDNS settings in Unifi, All enabled and IGMP snooping is disabled.
- Read the support page if I missed something
Can you help me fix this?
Why are you pressing the kWh button?
I can’t recall the pairing steps require this for apiv1.
Hi Jeroen,
I do not understand what you mean. I just follow the steps of the add device wizzard for the KWh meter 3 phase. I do not press any button on the device.
Ok drop me a diagnostic
6b72888c-e269-4f4f-8e08-605f9b4b68cc
Thanks for your support
So yeah your Homey has no clue about mDNS at all and can’t find your devices as per log. Check settings as AP client isolation. Guest wifi network? Maybe restart the accesspoint that Homey connects to.
Stack Trace
Note: this log has been manually submitted by a user.
Log ID: 6b72888c-e269-4f4f-8e08-605f9b4b68cc
User Message:
Issue met connecten van 3phase kwh meter
stdout:
2025-12-14T13:33:58.266Z [log] [HomeWizardApp] HomeWizard app ready!
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Discovered devices: {}
Hmm, How can the mDNS app on my phone then find the service?
I did onother check. the KWH meter and the homey are on the same network. All mDNS settings are enabled. Any optimization (to minimise broadcasting) have been disabled.
Good question. Why can your phone find them and your Homey can’t. IOT network? Any pihole or adguard dns used internally? I have no understanding of your WiFi used and its configuration.
Questions like is it mesh network? What brand?
See if you can find related problems with your setup in relation to bonjour protocol and chromecast as it is the same technology used here.
Thanks, Did some more investigation and it now works. Do not understand why, but thank you for your help. Have a nice evening!
Ok good to hear. Perhaps share the problem so other users that might face challenge can learn from it.
I am not sure which setting made it work but I think it has to do with disabling: “Multicast Enhancement” in the unifi settings of a wifi network. This was enabled and is now disabled.
1 Like
test/beta
v3.9.8
- New Plugin Battery mode support (zero_charge_only & zero_discharge_only)
- Optional gas checkbox (default enabled) for P1 (apiv1 and apiv2). (User request)
- Added 15min power datapoint for Belgium (average_power_15m_w) P1(apiv2) (user request)
- Plugin Battery - Bugfix setMode for to_full (PUT)
- Updated SDM230_v2 and SDM630_v2 drivers
- Bugfix - Updated P1apiv2 check-battery-mode condition card
- Backward compatibilty fix for the new battery mode applied to older P1 firmware.
- Bugfix - Websocket payload battery mode adjustment
- Fixed: rare crash when _handleBatteries() ran after a device was deleted, causing Not Found: Device with ID … errors during setStoreValue.
- Phase overload notification setting added and a limiter to avoid notification flooding
- New Feature: Baseload (sluipverbruik) detection (experimental)
1 Like
@Jeroen_Tebbens, maybe this is a silly question, but is a notification sent automatically upon registering a new ‘Phase overload notification setting added and a limiter to avoid notification flooding,’ or does a flow still need to be created? I ask because I think it’s automatic with the Homey P1 meter. 
"
Hi, english here.
I do have a Homewizard P1 phase overload warning for all 3 phase. I also know a Homey P1 has these but that is out of my scope/control you have to check that with Athom.
There wasn’t anything to warn users about phase overload at all so I added it as a feature. I do understand that some users dont link it so it has a setting added now (test version) to disable the warning but also a rate limited warning in the future.
But somehow I never can do it right. One new feature for the one user is a pain/problem for the another user. I also added base load detection, gosh I might be wrong again.
Its a touch a go last 6 years and its getting less and less fun this way.
Woah, I definitely appreciate your effort, and what’s more, I had been looking for this feature for a while! But I was just wondering if your implementation for the phase detection happens automatically or if you need to set it up via a flow?
I added it as a feature is enabled by default (until you switch the notification off in the P1 settings in this app). No flows needed. In the same settings area you can adjust the Amps that reflects your grid.
1 Like
Sorry to say but pretty sure your wifi is the cause of that.
