Yes.
1 Like
v.3.3.21 is live as of now.
Great !!!
beta / tests v3.3.23
- Pairing prompt to enable LOCAL API in HomeWizard Energy app and warning for Watermeter that needs USB Power.
- Update images and manifest to match HomeWizard branding
1 Like
Hi @Jeroen_Tebbens ,
Great work! Using the app a lot for my flows.
Are there any plans making widgets for the new Homey Dashboards (beta)? Would love to see, a similar set of graphs to the HomeWizard app, in a widget on my dashboard.
Thanks in advance!
Hi Jim,
No plans yet. Don’t feel an urge to put effort in it.
I only get complaints via diagnostic reports so lost the joy to drive it for now.
1 Like
I have three locations where P1 and EnergySockets are installed.
In my app on the phone I can see and control all Sockets in every 3 locations.
Is there a way to connect all 3 locations in Homey ?
(In one location the WiFi sometimes fails. The enerySocket is disconnected and will not come back online. There for I want my homey to monitor all energySockets and create a flow to send me a message when one of the sockets goes offline)
If these locations are not connected to each other via VPN and allow mDNS traffic to be relayed the answer will be no. Currently I only support local wifi network related connections.
If you are able to interconnect all these “remote” locations via VPN, repeat/relay the mDNS traffic to your Homey it might be possible but that is really a big “IF”.
What you try to compare / replicate is Cloud based usage from your HomeWizard Energy app and the details you see there into your Homey. HomeWizard doesn’t allow Cloud connections from this app to their Cloud platform. Maybe in the future they allow such things but with the current technology and methods used I dont see this working.
Beta/Test:
v3.3.25
- BUG FIX SDM230 device (Solar panel class) negative values
It looks like 3.3.25 broke the connection to my HomeWizard products; both the P1 meter and Watermeter now have a red exclamation mark, even after resetting the app (Device Unavailable)… any idea how to fix this?
(Edit: yes, the devices went offline immediate after Homey pushed the update.)
Sorry to hear yet the last update did not touch anything on connections on that. All drivers have their own module. Please check first post in this topic for tips.
To me it sounds that mDNS stopped working for you in your WiFi network. Try a restart of your access point that connects your Homey and your Homewizard devices.
Hi @Jeroen_Tebbens , would it be possible to add a advanced setting to poll the P1 more frequently than per 10 seconds?
my new meter sends datagrams to the P1 every second.
this could help in keeping the main breakers alive when a load is added.
the 10 seconds may be too long for the logic to react to this to turn things off…
thanks for considering this!
Jeroen,
Can you elaborate on this installation instruction? " * Reboot your wifi accesspoints/routers (unifi / ubiquiti common issues)"
I have a P1 dongle and a 3-phase meter. Both are on the same (unifi) network. I’ve enabled mDNS and checked all the FW-rules. I’ve toggled the “enable local API” in the HW Energy app. But for some reason the mDNS discovery tool does not find the _hwenergy._tcp
I keep getting “no devices found”, either on the iOS app or on the web-app of Homey Pro (2023).
What am I missing?
Thanks!
Hi Reinout, I have received many questions on this where the access point where either Homey and or P1/sockets/kwh are connected with are somehow not processing multicast traffic (here mDNS). This is the same technique used for Chromecast so that probably doesn’t work either. In most of these cases a power cycle of that access point resolves it. But that is not a 100% fix for everyone but at least one option worth trying.
Not sure yet, as that would increase the load to the P1 by 10x. Even the internal flow checker that you might want to relate to will break as there is internal Homey protection that watches flows that are executed to often (every second) and will be turned of automatically. Moreover there is really extra coding work in my end to add these additional settings on the driver, add page to update the polling frequency value and the (re)start that polling interval with the updated value. Not to mention if there is a bit of latency on wifi I need to extra handle the timeout/retry properly as well.
So yeah, I am not taking this lightly as there is more around that change that has a bigger impact of the behavior.
Hi Jeroen, Thanks for considering though. I personally would not update with flows every second but would use the “Current Amp phase 1 (and 2 and 3) became greater than xxxxW” to not overwhelm the homey. I do get the other constraints on the wifi etc and those can cause issues if not properly working. if it is a configurable value some might even lower the frequency if they dont have the need tor frequent updates.
Thanks again for your efforts in making these apps.
Problem with Current Amp value is…it is a rounded value (2 A, 3A, not like 2,4A).
So what is the point having it polled every second? And you are right, if something like this is made available people can create a problem/situation and drop it my diagnostic bug report email bucket/bin and complain it doesn’t work (no joke, have a lot of reports about bad wifi/connection timeouts and say its my app problem).
Sorry to hear that… but i have seen this networking issue blaming to developers on the forum as well… the Watt value is the more accurate one that i actually use at the moment as well (as the Amp value was not there in the earlier versions / other version of the app). if there was a hidden feature that would be something but again that would need to be surrounded by a disclaimer that if it is not working as expected, revert it to the default 10 seconds interval…and don’t create a diagnostic report as it will be deleted if the polling value is less than 10 seconds… 
Sadly it doesn’t work like that.
Maybe next month when the plugin battery gets released (hopefully) I must do some coding to add support of some sort for it.
Currently my job doesnt allow me to.
Hi Jeroen, thanks for your response. I don’t have Chromecast so I cannot compare. When you mention a power cycle of AP’s, do you mean just the AP’s or also the unifi POE switch and Unifi router?
In Unifi you set the mDNS at network (VLAN) level and provision this over the whole infrastructure. I try to limit power cycles of my router, as there is a whole lot of infrastructure depending on it and it might cause disruptions (at least family members instantly yelling about the loss of internet).
