Greenwave Systems v.2.0 removed power capabilities

Hmm, never thought of that being a power user feature :thinking:, thought it was always available.

1 Like

Jan,

You’re a hero, the power user setting gave me the option to send a zwave command.

Thanx, Patrick.

1 Like


Via Advanced parameters of the greenwave device, the Raw parameters also can be send. (Ruwe Configuratie Parameters), No node-ID needed.

i have set off the LED with this:

any news here?

I also sent that to athom as a supplement. unfortunately that was many months ago. :frowning:

No news, I don’t expect news anyway anymore. But, unexpectected things can happen.

Does your LED stay OFF, with only this setting?

yes stays out. But I would like to finally have the entire current measurement :frowning:

Athom won’t fix this, it was there in previous versions, but it was removed to reduce communication traffic.
Maybe there is some one who has the source of this old app and want to share it, then you can install that by CLI.

1 Like

Can anyone give me any pointers please?

Ok trying Homey again after a few years.

The unsupported critical devices are not longer critical.

I have about 35 Greenwave plugs all singles.

Would really like to use them.

The Current v3.0.0 Greenwave App has removed a lot of the functionality, ie the Power Meter function that I use to track how much power a device has used over a 24 hr period. Don’t really need polling but need to capture daily usage at midnight then reset usage. That will give me an indication to health of device.

ie the fridge uses 200W per day, the freezer 800W per day, the Dishwasher 1.5KWh etc etc

If I see any deviation in this I can trigger and alert.

So have been trying to install a previous version of the Greenwave App.

I have Node.js installed
npm ver 8.16.0
I have Homey CLI installed
Struggling to find versions of the Greewave code, multiple version on Git Hub and a lot of the links to the right version in this thread result in a 404 error.

I have tried installing v1.1.0 at v1.1.0 but ran in to a lot of issues during install.

homey app install

✓ Pre-processing app...

Command failed: npm ls --parseable --all --only=prod

npm WARN config only Use `--omit=dev` to omit dev dependencies from the install.

npm ERR! code ELSPROBLEMS

npm ERR! invalid: homey-zwavedriver@1.1.8 /Users/xxxxxxxxxxxxxxx/Desktop/Greenwave/node_modules/homey-zwavedriver

npm ERR! A complete log of this run can be found in:

npm ERR! /Users/xxxxxxxxx/.npm/_logs/2022-08-09T11_16_48_140Z-debug-0.log

This error may be fixed by running `npm install` in your app

Running npm install resulted in

 npm install
npm WARN deprecated mumath@3.3.4: Redundant dependency in your project.
npm ERR! code 128
npm ERR! git dep preparation failed
npm ERR! command /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/Users/michaelhorton/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN old lockfile 
npm ERR! npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm ERR! npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm ERR! npm WARN old lockfile 
npm ERR! npm WARN old lockfile This is a one-time fix-up, please be patient...
npm ERR! npm WARN old lockfile 
npm ERR! npm WARN old lockfile Error: An unknown git error occurred
npm ERR! npm WARN old lockfile     at makeError (/usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
npm ERR! npm WARN old lockfile     at /usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
npm ERR! npm WARN old lockfile     at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! npm WARN old lockfile  Could not fetch metadata for homey-jsdoc-template@git+ssh://git@github.com/athombv/homey-jsdoc-template.git#72a1f42f74a5795970f631852bf56eeee3200b69 GitUnknownError: An unknown git error occurred
npm ERR! npm WARN old lockfile     at makeError (/usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/make-error.js:28:13)
npm ERR! npm WARN old lockfile     at /usr/local/lib/node_modules/npm/node_modules/@npmcli/git/lib/spawn.js:37:26
npm ERR! npm WARN old lockfile     at runMicrotasks (<anonymous>)
npm ERR! npm WARN old lockfile     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
npm ERR! npm WARN old lockfile   cmd: 'git',
npm ERR! npm WARN old lockfile   args: [
npm ERR! npm WARN old lockfile     '--no-replace-objects',
npm ERR! npm WARN old lockfile     'ls-remote',
npm ERR! npm WARN old lockfile     'ssh://git@github.com/athombv/homey-jsdoc-template.git'
npm ERR! npm WARN old lockfile   ],
npm ERR! npm WARN old lockfile   code: 128,
npm ERR! npm WARN old lockfile   signal: null,
npm ERR! npm WARN old lockfile   stdout: '',
npm ERR! npm WARN old lockfile   stderr: "Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.\r\n" +
npm ERR! npm WARN old lockfile     'git@github.com: Permission denied (publickey).\r\n' +
npm ERR! npm WARN old lockfile     'fatal: Could not read from remote repository.\n' +
npm ERR! npm WARN old lockfile     '\n' +
npm ERR! npm WARN old lockfile     'Please make sure you have the correct access rights\n' +
npm ERR! npm WARN old lockfile     'and the repository exists.\n'
npm ERR! npm WARN old lockfile }
npm ERR! npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm ERR! npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm ERR! npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm ERR! npm WARN deprecated fsevents@2.1.3: "Please update to latest v2.3 or v2.2"
npm ERR! npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm ERR! npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm ERR! npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! npm WARN deprecated flat@4.1.0: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm ERR! npm WARN deprecated monitorctrlc@2.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm ERR! npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm ERR! npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm ERR! npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm ERR! npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm ERR! npm WARN deprecated mumath@3.3.4: Redundant dependency in your project.
npm ERR! npm ERR! code 128
npm ERR! npm ERR! An unknown git error occurred
npm ERR! npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/athombv/homey-jsdoc-template.git
npm ERR! npm ERR! git@github.com: Permission denied (publickey).
npm ERR! npm ERR! fatal: Could not read from remote repository.
npm ERR! npm ERR! 
npm ERR! npm ERR! Please make sure you have the correct access rights
npm ERR! npm ERR! and the repository exists.

Use the Power by the Hour app and be amazed

I have been - but have been getting some weird readings using it - early days yet but still not go my head around PBTH

It even works with water meters now :upside_down_face:

Just add a “power summarizer” device, select the power measure source (like, a socket) and enter the start values you want.

2 Likes

That version is probably a SDK-1 version, that don’t work anymore
On an old drive, I found a SDK-2 version 1.2.0. SDK-2 Apps are still usable on Homey-pro.
I have not tried this to install, but if you P.M. your email address, I’ll be glad, sending it to you.
Did try it to P.M. it to you, but Zip files are rejected.

{
	"id": "com.greenwavesystems",
	"name": {
		"en": "Greenwave Systems",
		"nl": "Greenwave Systems"
  },
  "sdk": 2,
	"version": "1.2.0",
	"compatibility": ">=1.5.0",
	"author": {
		"name": "Athom B.V.",
		"email": "info@athom.com"
	},
1 Like

Thanks I have IM d you

sorry, I think something went wrong, or did you receive the link?

Thanks received your email, many many thanks.

Will get to a computer today and download.

Much appreciated!

1 Like

Hello everyone, after discovering my old unused Zipato is discontinued and owning a considerable number of Greenwave sockets (which were never properly supported by Zipato), I’m very interested in this topic and am considering purchasing a Homey.

The standard Athom Greenwave App works fine for basic on/off functions.

It does not fix the issue of the Greenwave flashing, but you can work around that by sending a zwave ‘ping’ every 2 hours and when adding a new Greenwave you will need to send a zwave command to set time out to 255 minutes, I can help with all this having just gone through it :slight_smile:

If you need the full Greenwave energy tracking then it gets more complicated, doable, but complicated.

I use the Powerby the. Hour App for tracking energy tracking, it works but for better mananagement you will need to install an older pre Athom app, which I can help with too.

1 Like

This setting turns off the green Led :slight_smile:

1 Like

I wish it did , it would really useful.

Doesn’t on mine :frowning: