Should be working now in v3.9.20 (test)
Thanks for the quick reply!
It no longer displays the error, but it seems it can’t find my 3 Phase meters, using v1 or v2. This is a diagnostics report: fe8f1875-e256-4ecb-9d67-5b261e823203
I restarted my access points as you mentioned above as well. Local API is enabled.
Multicast / mDNS problem for sure. Empty result discovery:
Note: this log has been manually submitted by a user.
Log ID: fe8f1875-e256-4ecb-9d67-5b261e823203
User Message:
Cant find devices
stdout:
2025-12-25T11:33:39.726Z [log] [HomeWizardApp] HomeWizard app ready!
2025-12-25T11:33:39.916Z [log] [ManagerDrivers] [Driver:energy] [Device:95c38434-1450-4a51-a6dc-4cb79e0d6153] Discovered device URL: http://10.210.5.6:80/api/v1
2025-12-25T11:33:39.951Z [log] [ManagerDrivers] [Driver:watermeter] [Device:93a7a703-0352-4557-acf6-e31c394d54e4] URL: http://10.210.5.7:80/api/v1
2025-12-25T11:34:01.241Z [log] [ManagerDrivers] [Driver:SDM630_v2] Discovered devices: {}
2025-12-25T11:34:17.156Z [log] [ManagerDrivers] [Driver:SDM630] Discovered devices: {}
2025-12-25T11:37:01.833Z [log] [ManagerDrivers] [Driver:SDM630-p1mode] Discovered devices: {}
2025-12-25T11:37:56.208Z [log] [ManagerDrivers] [Driver:SDM630_v2] Discovered devices: {}
2025-12-25T11:39:04.660Z [log] [ManagerDrivers] [Driver:SDM630] Discovered devices: {}
2025-12-25T11:40:49.969Z [fetchQueue] error on http://10.210.5.6:80/api/v1/data: request to http://10.210.5.6/api/v1/data failed, reason: read ECONNRESET
2025-12-25T11:40:49.969Z [fetchQueue] retrying once: http://10.210.5.6:80/api/v1/data
2025-12-25T11:42:36.271Z [log] [ManagerDrivers] [Driver:SDM630_v2] Discovered devices: {}
2025-12-25T11:42:50.629Z [log] [ManagerDrivers] [Driver:SDM630] Discovered devices: {}
2025-12-25T11:43:18.148Z [log] [HomeWizardApp] HomeWizard app ready!
2025-12-25T11:43:18.320Z [log] [ManagerDrivers] [Driver:energy] [Device:95c38434-1450-4a51-a6dc-4cb79e0d6153] Discovered device URL: http://10.210.5.6:80/api/v1
2025-12-25T11:43:18.340Z [log] [ManagerDrivers] [Driver:watermeter] [Device:93a7a703-0352-4557-acf6-e31c394d54e4] URL: http://10.210.5.7:80/api/v1
2025-12-25T11:43:48.007Z [log] [ManagerDrivers] [Driver:SDM630] Discovered devices: {}
stderr:
n/a
Thanks for looking into this. The weird thing is, the P1 and watermeter were found fine.
Also, other apps using mDNS don’t have any problems, for example the Chromecast and Sonos apps resolve devices without any issue.
I am running on Unraid, where I have avahi-browse available. Running that gives me a list of devices, including the kWh meters I have in my utility closet.
I build a quick debugging app and when discovering HomeWizard devices, I actually see the following appear in my logs:
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Strategy hwenergy_tcp found 4 devices`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“hwenergy_tcp”,“resultId”:“10.210.5.15:80”,“address”:“10.210.5.15”,“port”:80,“host”:“kwhmeter-0E2AD2.local”,“name”:“kwhmeter-0E2AD2”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“Barebone”,“serial”:“5c2faf0e2ad2”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.15:80”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.15”,“host”:“kwhmeter-0E2AD2.local”,“port”:80,“name”:“kwhmeter-0E2AD2”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“Barebone”,“serial”:“5c2faf0e2ad2”}}}`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“hwenergy_tcp”,“resultId”:“10.210.5.18:80”,“address”:“10.210.5.18”,“port”:80,“host”:“kwhmeter-174752.local”,“name”:“kwhmeter-174752”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“Barebone”,“serial”:“5c2faf174752”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.18:80”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.18”,“host”:“kwhmeter-174752.local”,“port”:80,“name”:“kwhmeter-174752”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“Barebone”,“serial”:“5c2faf174752”}}}`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“hwenergy_tcp”,“resultId”:“10.210.5.6:80”,“address”:“10.210.5.6”,“port”:80,“host”:“p1meter-11E336.local”,“name”:“p1meter-11E336”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“P1 Meter”,“product_type”:“HWE-P1”,“serial”:“5c2faf11e336”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.6:80”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.6”,“host”:“p1meter-11E336.local”,“port”:80,“name”:“p1meter-11E336”,“fullname”:“”,“txt”:{“api_enabled”:“1”,“path”:“/api/v1”,“product_name”:“P1 Meter”,“product_type”:“HWE-P1”,“serial”:“5c2faf11e336”}}}`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“hwenergy_tcp”,“resultId”:“10.210.5.7:80”,“address”:“10.210.5.7”,“port”:80,“host”:“watermeter-1549D4.local”,“name”:“watermeter-1549D4”,“fullname”:“”,“txt”:{“product_name”:“Watermeter”,“product_type”:“HWE-WTR”,“serial”:“5c2faf1549d4”,“path”:“/api/v1”,“api_enabled”:“1”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.7:80”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.7”,“host”:“watermeter-1549D4.local”,“port”:80,“name”:“watermeter-1549D4”,“fullname”:“”,“txt”:{“product_name”:“Watermeter”,“product_type”:“HWE-WTR”,“serial”:“5c2faf1549d4”,“path”:“/api/v1”,“api_enabled”:“1”}}}`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Strategy homewizard_tcp found 2 devices`
`2025-12-26T08:21:49.949Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“homewizard_tcp”,“resultId”:“10.210.5.15:443”,“address”:“10.210.5.15”,“port”:443,“host”:“kwhmeter-0E2AD2.local”,“name”:“kwhmeter-0E2AD2”,“fullname”:“”,“txt”:{“api_version”:“2.1.0”,“id”:“appliance/energymeter/5c2faf0e2ad2”,“product_name”:“Barebone”,“serial”:“5c2faf0e2ad2”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.15:443”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.15”,“host”:“kwhmeter-0E2AD2.local”,“port”:443,“name”:“kwhmeter-0E2AD2”,“fullname”:“”,“txt”:{“api_version”:“2.1.0”,“id”:“appliance/energymeter/5c2faf0e2ad2”,“product_name”:“Barebone”,“serial”:“5c2faf0e2ad2”}}}`
`2025-12-26T08:21:49.950Z [log] [ManagerDrivers] [Driver:mdns_device] Discovery result {“strategyId”:“homewizard_tcp”,“resultId”:“10.210.5.18:443”,“address”:“10.210.5.18”,“port”:443,“host”:“kwhmeter-174752.local”,“name”:“kwhmeter-174752”,“fullname”:“”,“txt”:{“api_version”:“2.1.0”,“id”:“appliance/energymeter/5c2faf174752”,“product_name”:“Barebone”,“serial”:“5c2faf174752”},“raw”:{“_events”:{},“_eventsCount”:0,“id”:“10.210.5.18:443”,“lastSeen”:“2025-12-26T08:21:49.313Z”,“address”:“10.210.5.18”,“host”:“kwhmeter-174752.local”,“port”:443,“name”:“kwhmeter-174752”,“fullname”:“”,“txt”:{“api_version”:“2.1.0”,“id”:“appliance/energymeter/5c2faf174752”,“product_name”:“Barebone”,“serial”:“5c2faf174752”}}}`
These are my defined strategies:
"hwenergy_tcp": {
"type": "mdns-sd",
"mdns-sd": {
"name": "hwenergy",
"protocol": "tcp"
},
"id": "{{address}}:{{port}}"
},
"homewizard_tcp": {
"type": "mdns-sd",
"mdns-sd": {
"name": "homewizard",
"protocol": "tcp"
},
"id": "{{address}}:{{port}}"
}
Thanks this helps a lot. Seems the strategyId homewizard_tcp is missing a product_type in the payload which I need to filter for the APIv2 flavored firmware. You can see product type is there in the hwenergy_tcp so those are fine.
Which firmware are your kwh’s now? Seems mDNS got changed and reports differently based on your findings shared.
It seems they are running on 5.0011, at least, that’s the only version I can find in the app.
Running same version so that is ok. But why are your kwh’s called Barebone and lacking a product type like I get from my kWh meter (
SDM230) apiv2 mdns which does hold a product type see screenshot.
Is there something in between?
Let me check my contact on this with Homewizard.
At least we found the cause of your problem.
The problem seems to get weirder and weirder. They also now appear offline in my HomeWizard app, while when I turn on the HomeWizard integration in Home Assistant, they appear there and fully working.
Could there be anything at HW side that is borked at the moment?
Tried removing them and re-adding them to my HW app, but that fails as well. It seems there is a communication issue somewhere.
To be clear I do see the kWh meters connected to my Wifi network by the way.
Good question, I cant voice for Homewizard as am just a hobbyist supporting an integration for their products into Homey.
Your kwh’s do act weird, maybe they were fine in the beginning and you were able to add them to Homeassistant. Hence they keep working after as the the serial is the unique identifier so not pending on product type etc.
What I can do in the latest is add some Barebone filter to to the SDM630 (3 phase right?) to help you adding them and see if that helps.
Yes, they are 3 phase versions, but it is weird behavior.
Thanks, but I wonder if anything else is up with the platform at the moment.
Platform looks ok for me. I think its more the weird behavior of your SDM630’s in relation to local and cloud updates (push datapoints to their cloud platform).
Let me prep the filter here and see when I get some feedback on my query for you to my contact.
Sounds good, but it is also my watermeter. Online in both Home Assistant (when I enable that integration) and on my WiFi, but in the HW app this is offline.
what I would love, but that is just for this use case, is a manual setup mode. I got the IPs, I could enter them myself, but again, this is such an advanced setup thingy, that I am not sure it is worth the time.
Your water meter should work that is APIv1. If it still shows as “down” that would hint me on connectivity issues “Connection resets” or Unreachables.
Manual set up is a pain and a lot of work as I need to align the whole process where code currently rely on mDNS discovery and updates. I do get these questions more and more but not looking forward to get all those support questions. But I have some time off this and next week so maybe I should give it a shot.
Lets just say, that they could connect now. More and more stuff was going down in my local network, except phones / laptops..
My DNS was down…
Wut?! Right…that makes sense. The means the .local through DNS got lost.
FYI: my Homey Pro kept crashing for days after the update to 12.10.0. Or at least the day after the update. After. Lot of troubleshooting I removed some apps yesterday and after disabling the HomeWizard app in homey it was stable aging? Is it a known issue? And can I remove and install the app again or do you advise otherwise?
No this is new, drop me a diagnostic report if you can before it crashes.
I run SHS 12.10.0 and the app is ok there no issues but its pure basic testing.
There is no load there at all.
So yes please share a diagnostic report before it crashes if you can, perhaps the log shed some light on the reason for the crash.
b48dcf69-1a39-49f5-9789-4505e1987f7d
No smoking gun yet
Log ID: b48dcf69-1a39-49f5-9789-4505e1987f7d
User Message:
Homey crasht
stdout:
2025-12-26T12:52:47.013Z [log] [HomeWizardApp] HomeWizard app ready!
2025-12-26T12:52:47.719Z [log] [ManagerDrivers] [Driver:energy] [Device:481fa568-5aa6-48d2-b053-21cf66bb4211] Polling settings for P1 apiv1: 10
2025-12-26T12:52:47.735Z [log] [ManagerDrivers] [Driver:energy] [Device:481fa568-5aa6-48d2-b053-21cf66bb4211] Discovered device URL: http://10.0.10.49:80/api/v1
stderr:
n/a
Oké, not sure what to do in this case. As soon as I enable the app and I.e. click on the energy tab is crashes immediately. But also when just doing anything homey crashes within a few minutes
