Its multicast on the new network you created for your shs homey. Guess you block broadcast somehow.
If I do an mdns-scan on my linux host running docker, and within the homey self hosted container, I both discover the HW-P1;
- p1meter-134368._hwenergy._tcp.local
- p1meter-134368._homewizard._tcp.local
Is the docker natted? Extra subnet in between? Port forwarding?
I got shs here too but running as lxc on proxmox which is fine.
I’ll try that, thanks a lot!
I will let you know tomorrow
Have a nice evening.
I cant do much more. This is Athom playground. Launching something new and hope community will support / troubleshoot it.
Good luck with finding the mDNS problem with shs docker flavor.
2 Likes
I have recently moved to Homey and added HomeWizard. I am running into 2 issues which I cannot figure out.
- Devices from HomeWizard can only be connected to Homey after I cut them from power and turn them on. Only shortly after turning on, they become visible in the Homey app to be added. Eventually it worked to get them all added but I had to power cycle them all (p1, batteries, energy sockets) before I could add them.
- KWH meter gives the error “Invalid Flow Card ID: measure_power” - Seems to work fine, power usage is visible in the graphs but on the dashboard I see the exclamation icon and this error.
Hi, english section here so please translate your message or drop/move it to the dutch topic here.
Please drop me a diagnostic report from my app so I can look but I think I know the problem already.
Done - 1e16ab0e-da55-455b-b932-f44c0c810cb8
test/beta
v3.9.10
- Bugfix: energy_socket connection_error capability fix
- Bugfix: energy_v2 (handleBatteries) - device_not_found crash
- Bugfix: trigger cards for SDM230_v2
- APIv2 change pairing: Modified the username that is used during pair made it unique per homey
1 Like
The fix for the single-phase kWh meter has helped; it is now providing data again on API v2. Could it be that the three-phase kWh meter needs the same fix, since it has the same problem on v2 as well?
What also stands out to me is that when I try to add a single-phase or three-phase kWh meter, I get the message below.
Yes I am aware. Due to the lovely SHS launch everyone wants to add their Homewizard devices to SHS as well but that gives issues as the app uses the same username which makes your old token void/revoked. So adding something to make it unique last night (2hours) but came across an issue now that I didnt link the Homey SDK properly. But hey, that is with test/beta…
1 Like
Ok I hope it is resolved in the latest test v3.9.13.
Username token wasnt having the mandatory local/ in its request, now it does.
Adding the single-phase and three-phase kWh meter is now working correctly on API v2 
Good work 
Only the three-phase meter still shows the message “device unavailable: measure_power”.
But that issue was already present before the previous two fixes.
Ok drop me a diagnostic again. Good to hear pairing is working now. Also a screenshot of the error and which 3 phase driver you use as there 3 at this moment.
2813ff9e-4bd7-4d75-84e2-6751fca77761
Software kwh 3 fase 5.0103 ( Problem also in the official release version)
Ok think I found the problem. Trigger cards are obsolete as these are default in Homey.
I’ve never been able to test this code as I dont have a SDM630 and not even APIv2 based as there are only a handful of users at this moment. So consider yourself special.
I pushed test version v3.9.14 now. Try that.
For those that want to play with Self Hosted Server (SHS) please make sure you use the test version v3.9.14 else your existing APIV2 devices in your Homey Pro will break (stored token will expire)
Thank you, Jeroen. Everything works now as it should be good work😁. Please send me your donation link for iDEAL.
I shared one earlier:
Received your donation, thank you kindly 
