This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official
Comments
Man the interface of my Homey feels much more responsive and snappie again
A remark I have to make, I do observe several Greenwave devices flashing with their green leds... but this does NOT impact the responsiveness of this devices / Z-wave network (with these settings).. Will look into the issue though.
The second pull request (intended to add the parameter to the sub-nodes) still has an issue in it that first needs to be resolved by athom...
For the time being, I would recommend to simply use the App store version and remove Homey's ID manually out of Association group 3.
@posthok, default settings (poll interval = 300 and keep alive time = 255) combined above mentioned action resulted at my place in a stable operation; see below settings (in Dutch):
It is still the advise to differentiate the polling interval over the different nodes (e.g. 5 seconds difference combined with larger polling intervals that you hardly use).
@Eternity if this is not solving your issue, please let me know.
I left the polling interval at the default, if it fails I will try to differentiate the intervalls.
@posthok see DM on slack
Since I don't think it is a device specific issue, I created a new topic for it: [TROUBLESHOOT] Z-wave ProcesSendData lockup. Please contribute (also in case it solved your issue) to this topic to support the community.
On topic: I do notice that my Z-wave is stable and responsive again.
Yet my greenwave devices are still blinking their green leds from time to time... this does not influence their responsiveness. So please interpretate the led as an indication, but verify if the switch is responding.
I downloaded and installed the version from here
Also, I checked the association group 3 settings: all are empty:
I saw a few days ago on slack also a pre-announcement that NEO Coolcam is planning to release extention sockets and other device types. These will be Z-wave plus...
@Eternity did you install 1.0.4 already and did this solve your issue with non-responding powernodes?
I can't believe my eyes.... Greenwave has been running without any issues, since I updated to latest firmware!
Some additional functions have been implemented:
Ability to differentiate polling interval for all capabilities (onoff, power measure (W), power meter (kWh)
use case: Change the polling interval for the different capabilities to reduce Z-wave network load (previously, all capabilities were polled at the same time (1 polling interval).
how to implement:
- Open the settings of the Greenwave powernode devices
- Update the polling intervals based on own preferences (0 to disable).
- Save settings
Notes:- The Polling interval On/Off is disabled in this example. On/Off state will still be updated once the device has been switched On or Off
- Polling interval Measure (W) is complementary to the 'Power change for update' setting, providing an update if the power value has changed by more than 50% in this example. This capability is quite often used for device monitoring
- Polling interval Meter (kWh) is most commonly used only for data logging, hence the relatively high interval used in this example
- To be able to use these new polling intervals, you will need to re-pair your devices
'Reset meter values' action card for all supported devices:use case: reset the meter values (kWh) as recorded on the device (including all sockets in case of the Powernode-6) to 0 via a flow on the defined interval (January 1st, 1st of the month, etc)
What is the best way to re-pair the Greenwave powernodes?
- backup the flows that have PN's
- remove the current PN's (again; how?)
- re-add the PN's and give them the same name as before
- restore flows.
Or is there a better /easier way?
Containment for the time being: CLI install of the app and manually include the v1.1.8 Zwavedriver
and has even been auto updated 5 minutes ago on my Homey...
Should all be working now.
since device ID's will break, also the restored flow will be broken after restore.
My suggestion:
Thanks for the updated update and the instructions :-)