Greenwave powernode 6 kWh counters not working over z wave

I bought a greenwave powernode 6,
Everything works fine except the kWh counter/values do not increase.
I can see the load (in watt) perfectly fine. The relays work fine.

Does anybody know to get the kWh couters to works.
I also see no error related to z wave.

Other option could is us to convert the Watt value to a kWh value.

Hi,
The only way I could get mine to do it was to poll it.
I put instructions here

https://community.home-assistant.io/t/20-6-port-individually-controllable-powerstrip-found/160379/61?u=ezekiel

A few updates though. I stopped polling for W data as it comes in by itself like you say.
I made the time for my kWh 1800 seconds so every 30 minutes it updates the data.

I didn’t want to flood my zwave network so I offset each port by a second. So port 1 is polled ever 1801 seconds port 2 is polled every 1802 seconds, etc

I’ve only just done that (this week) but I want to start looking at an automation to poll it every 30 minutes so that it’s on the hour and half hour. Where at the moment it’s 1801 second but the service might have started at say 15 minutes past the hour so the poll triggers at 45 minutes past the hour. My plan is to get it to trigger at :00 and :30

Hope that helps and makes sense.

Another location that might help

https://zwave-js.github.io/zwavejs2mqtt/#/device-support/polling

Hi ezekiel,

Thanks for your reply,
So for what i understand is that i basicly have to switch for zwave-js to zwave-js-to-mqtt.
So i can add the polling for those values.

In the zwave js log i see the following:

2022-01-24T20:43:46.735Z CNTRLR « [Node 003] received wakeup notification
2022-01-24T20:43:46.769Z CNTRLR   [Node 003] The node is now awake.
2022-01-24T20:43:47.777Z CNTRLR » [Node 003] Sending node back to sleep...
2022-01-24T20:43:47.880Z CNTRLR   [Node 003] The node is now asleep.
2022-01-24T21:23:49.885Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-24T21:24:52.888Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-24T21:27:52.949Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-24T21:30:53.004Z DRIVER   Dropping message with invalid payload
2022-01-24T22:09:51.389Z DRIVER   Dropping message with invalid payload
2022-01-24T22:38:51.463Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T00:57:53.214Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:00:53.200Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:03:53.213Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:09:53.299Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:12:53.279Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:15:53.283Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:21:53.294Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:24:53.304Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:27:53.397Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:27:53.405Z DRIVER   Dropping message with invalid payload
2022-01-25T01:33:53.336Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2022-01-25T01:57:53.371Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

Could this have to do something with this, that the values are not transported correctly,

Other question is:
How can i see the registers from which address/data positition where the data is located in the database . Zwave devices
It shows the configuration options. But not the actual data that the device publises.

Hi,

Yes from all my research when I jumped from the old zwave to zwave js. I knew I would need some sort of polling.

As for the logs I’ve not seen those in the logs I have.
I have seen similar logs around failing to get data in attempt 1/3 and I found it was because I had doubled my zwave network and all the polling from the post I sent you was flooding the network. Through trial and error I realised that the power watts was sending find so my polling for it was a waste of time and bandwidth.

The other question I’ll need to look into.
I’m not 100% sure I understand what you’re asking but if screen shots of what I do to get the polling working will help I am happy to do that in the morning.

I suspect the info your after is probably the same thing I need to get values refreshed as part of the automation I spoke of earlier.

At this point if you want to read up on converting to zwave.js mqtt and have a play around we may be able to help each other.

Good luck

I had a look at the web site in the link you posted and yes its more for the configuration of the board.
but the zwave (whatever version you use) populates the device’s functions to HA.

In ZwaveJS-MQTT, you go to settings, and click new value, then you can setup your polling.
But it also looks like you can use the zwave_js.refresh_value service call as an automation.

here is a picture of a default newly included 6 port power board in HA.

not sure if that answered your question

Ezekiel,
Thanks for you briljant insight, :grinning: (calling the service to update the value) (why didn;t i think of that) :thinking:
Many thanks.

Hi @frank8the9tank,
I was playing around with this and was able to create a dynamic group that meant i could parse the one group entity to the zwave.js refresh service rather than every one of the 6 ports energy consumption entities.

here is the link if your interested
https://community.home-assistant.io/t/switching-from-zwave-1-4-deprecated-to-zwavejs2mqtt/276721/184?u=ezekiel

its early minutes of testing so I’ll see how it goes over night.

I wil take a look at it.
I created a automation that runs ervery 5 minuts.
It just calls the zwave_js.refresh_value for the entities.
So for the greenwave node 6 the above call just 6 times in a row.
With a 1 second deley in between calls.