v3.0.4 - Beta/Test
Fix is live in v3.0.4
Super! Thankyou.
It works now fine
So if I understand correctly water can not be used with Homey when battery powered? No way to get the watermeter readings in Homey?
Correct, when the watermeter is battery powered it disables its API hence you cant pull local information from it to save its battery. If it would you might end up replacing that battery every month or so?
But you have to aim your issue at Homewizard yourself as this is beyond me.
All of a sudden Homey had no connection with my energy meter. Strange, always functioned correctly. Homewizard Energy app still has connection. It is a connected device in my router.
I removed the device in my Homey. Adding a device in Homey, using the Homewizard app of course, doesn’t show the energy meter to connect with. No new device found.
Wow, that’s weird. I saw that Homewizard is upgraded to version 3.0.7 yesterday, 11:03. Can that have something to do with it?
Do you know a way to get the energy meter back in my Homey???
Your internet router lost mdns functionality so that would my best guess for you. Further your are running my experimental/beta version 3.0.7 so there can always be problems. I did test this version myself and there are about 50 other users running it.
My Homey/Homewizard app uses mDNS to find/search your devices. If that protocol got stopped or blocked locally it will fail and wont find your device(s). Restart your internet router and perhaps your homey when the first restart doesnt help. It should start the mdns process again locally. Further I hope you didnt turn off Local API on your device else that would be the cause.
The watermeter is still up and running, visible in Homey. That uses mDNS as well? If so, than that isn’t the cause.
mDNS isn’t mentioned in my router. Do you know what name is used in different routers for it?
Local API isn’t turned off.
Tried to restart Homey? I am on 3.0.7 and no issues with p1, watermeter and 2 sockets. Does that make it a app problem or a local wifi/network problwm?
Went back from 3.0.7 to 3.0.4
Restarted Homey
Restarted router
Local API is switched on
Still problem to find a new device.
Now the watermeter has an exclamation mark. Before any of the restarts, the watermeter was still available and reachable. After the restarts (I don’t know which of them), it has a problem. It’s IP address is updated after the last reset of the router.
Ticking on the watermeter shows the errormessage:
request to http://192.1681.134/api/v1/data failed
reason: connect EHOSTUNREACH 192.1681.134:80
Does this point in the direction of mdns? According to the info of the TP-LINK Deco M9Plus, mdns is available.
Edit:
Solved.
The only setting I changed recently was when I was building a VPN for incoming connections. I switched on IPv6, besides IPv4, an advice during installation of the VPN software.
After switching that setting of everything was back to normal. So I van reach the watermeter agin. And I can install the energymeter.
But why does this setting influence those 2 devices???
Ask Homewizard? Maybe they stopped using ipv4 and only accepted a ipv6 address? Hence no ipv4 address means no connection possible from Homeyvas its ipv4 only?
Seriously no clue as this is a first having this kind of a problem. But you see messing around with network settings can also have unwanted side affects and a new version of an app like my Homewizard Homey should not always be the source of the problem.
It’s the other way around. I switched of IPv6 and then it worked again. So, just the good old IPv4 works.
Maybe it’s not your app that’s the primary cause, it’s something to investigate and keep account with for the (near) future.
Thanks for your support!
Verzonden vanuit Outlook voor iOS
Since this morning my P1 won’t connect to Homey anymore; the HW app works without problems, also no Wifi probs (reset all APs because I needed to update them anyway).
Also did the following:
I can’t find a P1 when I try to add a new device (the current P1 is still a homey device, don’t want to remove it yet because of flows…)
Any tips what I can do?
Which version of the app?
Sorry, forgot to mention: 3.0.4
I read other people having problems seemingly after updating, but I did not get an update this week.
My P1 stopped working (in Homey) this morning at 8:35-ish (dutch time)
Alright so I read you restarted your Homey/Homewizard app. When did you restart Homey?
If that doesnt help, you may need to restart your internet router. P1 and all the other devices locally are discovered by mDNS which is a multicast broadcast protocol which is a process supported also by your internet router and/or your accesspoint. So my best guess is to look at that.
I’ve updated a new test version this morning so hence asking which version you are using. 3.0.4 is a stable version for a few weeks so that cant be the issue and there are over 4500 people using it.
I restarted homey first, no result, then the app, then the P1 (the p1 can’t be the problem since it still reports in the HW-app)
My network is the only thing I did not restart (Ubiquity USG3p + USW-Lite-16-PoE). I’ll try that
P1 can still quit its mdns so worth the attempt
restarted my Ubiquty network, Homey, then Homey app and un-/replugged in the P1. Still nothing.
P1 went powerless as in no usb adapter connected?
