That is an idea. It would still add up to my total energy usage though. Too bad it seems there is no alternative power node that has power metering per outlet!
What happens if I remove the app entirely? Will then the driver that installed yesterday be removed as well? To me it seems that I installed “something”, but I cannot see it anywhere
No, that’s not correct, you maybe have forgotten to disable AutoUpdate?
You have to do that in the 3.1.0 version, in the 1.1.1 version, this option does not exist.
You should see this:
Yes, this works better! In an attempt to not add the overall power consumption to the separate power consumption I changed the “Status indicator” from “Watt” to “None”. After doing that, I noticed I cannot update any settings of the overall power node anymore.
The app gives me:
Tried that, but it didn’t work. What DID work was removing the power node and adding it again. Quite a lot of work for something that used to work
This is the only thing still open now. I’ve sent an E-mail to Athom requesting this feature (I think it is useful in other places than just this use case) and got the reply that they take it in consideration but cannot guarantee it will be done.
Then I noticed there is at least one topic on this: [Feature request] Excluding zones and devices from Homey Energy - Ideas & Suggestions - Homey Community Forum
And people are getting the same response on this for months/years.
By the way: I think it was stated that individual power monitoring isn’t supported anymore and instead we would get only the overall power metering, right?
I would be ok with that, but I don’t think this is implemented as such. With the most recent version of the app upon adding it it is displaying some data and then the data from PN1 is updated and duplicated as overall. Or am I doing something wrong there as well?
Anyway, it’s working smooth right now. And I have added a virtual sensor to compensate for the double metering.
Dear all. It’s been quiet for a while vv the power monitoring. I am hoping there are still some people here using greenwave equipment with homey and may have some wise words.
I am currently a heavy user of Homeseer but have been testing a Homey Pro (2023) recently for someone else and want to gradually move to Homey myself.
For me there are two issues with Greenwave (both the single and the 6 socket).
they don’t show power usage (why this is in Homey with the current greenway app version has become clear in this post)
but also, and I haven’t seen any comment on this (I may have missed): it’s not reporting the status of the switch (single unit) back to homey.
I am the lucky owner of some extra Powernodes 1 and 6… so I’ve been testing with each one of those in Homeseer to see how it works there. Important context: I’ve been using a 6 for many many years in Homeseer with no problems with regard to quick power reporting to Homeseer.
So today I included a new 6 and a 1 in Homeseer and discovered neither report back power AND switch status.. unless I define a polling interval.
BUT: the Powernode 6 I’ve been using for ages has no polling active. How curious.
Another thing worth mentioning is that I do not understand why
polling should be necessary for switch status at all
polling should be necessary for power usage when I have a parameter available to SEND changes from the unit to Homeseer/Homey when a difference of 10% is measured. This should be a proper SEND from the node, no? And Homeseer/Homey should pick this up on the zwave network. (AND: my current Powernode 6 is doing exactly that.)
The fact that Athom decided that it didn’t want to support polling anymore should not have altered the actual Powernode and its workings.
But as I wrote above: I can not explain why both power nodes also play schtumm in Homeseer when the very same Powernode 6 has been doing what you expected for years and the parameters are set the same way.
I wanted to get this off my chest and hope there is someone out there who can add some insights to this issue.
When I do get my own Homey Pro, I will try to install the older Greenwave app (I hope that still works) as I get the impression that works for people out here.
Anyway: thanks a lot for some extra info and thoughts on this. Thank you!
Thanks JPe4619… I had read this entire post but thanks for pointing it out again. The questions remain… I remain completely puzzled by the need of polling (which, as you may have read, is not necessary for a Powernode 6 I have had for many years). As soon as I have my Homey I will install that version anyhow! Thanks!
And I think that is exactly the issue that Athom had with these devices: they are built based on the assumption the effort lies on the side of the controller. That should do the polling every now and then. And a lot of people set the polling interval to poll very often.
Whereas other devices push information as soon as they have it.
param 0: Power change required to send a notification, in % from 1 to 100, default 10
if they assumed that… is that parameter a bogus/dummy?
I think you are right, it makes sense… in those days we were (I was) polling like there was no tomorrow… but still: can you make sense of that parameter? And is it in fact not sending anything? (Or is homey not picking it up for some reason.) I know Homeseer is picking it up from the Powernode 6 I had for years… and ISN’T from the one I included yesterday.
I have 3 of those Powernode 6 devices and they work okay’ish.
If something similar comes along (I am not looking very hard though), I will sell the Powernode 6 devices and switch. (Most likely I will however think of some reason to keep them and just add even more stuff )
As a ‘by the way’, since we are on topic: has anyone ever seen a list of parameters from parameter 5 and up? I have 0-4… and have never seen others… even though homey shows there are many more.
Thanks JP! That could have been what I was looking for… but I can not even see parameters 0-4 in that document. Or am I missing something. (Apparently I am/was, see below!)
The 5 parameters that I know are:
- param 0: Power change required to send a notification, in % from 1 to 100, default 10
- param 1: Keep alive time, in minutes from 1 to 255, default 2
- param 2: Color wheel selection, read only
- param 3: State after power loss, 0 = all off, 1 = remember last state, 2 = all on, default 2
- param 4: Led for network error, 0 = disable, 1 = enable, default 0
Power on relay state:
XX = 0x03
YY = 0x01
AA=0x02 (All ON, this is the 1st boot up default)
AA=0x00 (All OFF)
AA=0x01(Remember last state)
LED for network error:
XX = 0x04
YY = 0x01
AA=0x00 or 0x01
0x00 Disable the LED for network error
0x01 Enable the LED for network error
Therefor I don’t find the erge to look for more, good luck.