after Upgrade to Node 10, led-light plugin can't be re-installed

---

I tried to update pimatic to new version 0.9.54 with a new Node.js = 10.16.3 and did nearly all without bigger probs.
But there is still one issue I can’t fix however.
plugin led-light (i only need one dummy-led-light from this) is not installing.
First I tried with plugin section inside running pimatic and also now with stopped server and manual install like from this topic.

Anyone an idea how to figure out the problem?

Log from manual install:

pi@FHEM-PI ~/pimatic-app $ sudo rm -rf ls /home/pi/pimatic-app/node_modules/pimatic-led-light
pi@FHEM-PI ~/pimatic-app $ cd /home/pi/pimatic-app; npm install pimatic-led-light
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN checkPermissions Missing write access to /home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors
npm WARN checkPermissions Missing write access to /home/pi/pimatic-app/node_modules/pimatic/node_modules/ansistyles
npm WARN checkPermissions Missing write access to /home/pi/pimatic-app/node_modules/pimatic/node_modules/builtins
npm WARN checkPermissions Missing write access to /home/pi/pimatic-app/node_modules/pimatic/node_modules/path-is-inside
npm WARN usb@1.1.1 had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/pimatic-app/package.json'
npm WARN pimatic-app No description
npm WARN pimatic-app No repository field.
npm WARN pimatic-app No README data
npm WARN pimatic-app No license field.

npm ERR! path /home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors'
npm ERR!  { [Error: EACCES: permission denied, access '/home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors']
npm ERR!   stack:
npm ERR!    'Error: EACCES: permission denied, access \'/home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path:
npm ERR!    '/home/pi/pimatic-app/node_modules/pimatic/node_modules/ansicolors' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-04-03T16_23_49_359Z-debug.log

Thanks a lot for any help!

Hi, this plugin is not maintained. The last commit is 4 years ago and in the package.json you the that the pimatic version is 0.8 and some of the depencies won’t work with node 8 or 10. So this plugin need a refurbish.
Why aren’t you using milight-reloaded or the dummydimmer?

@bertreb
"Not maintained" yes, thought so … that means plugin is dead and should be deleted from the list.

Why aren’t you using milight-reloaded or the dummydimmer?"

Sorry, but didn’t check to use other plugins. I need only GUI elements of a RGBW dimmer and connect to a selfmade mysensors rgbw led controller with some rules. I run additional iobroker and have already transfered more and more devices to this, maybe I will do also for this led dimmer now.

Anyway, it’s a pity when devices simply don’t work anymore after an update and you have to search for several hours again.

Hi, yes the plugin should not be visible anymore, but it’s automatically added when its on npm. You could still use the gui elements when you already have a dedicated mysensors solution.

@bertreb said in after Upgrade to Node 10, led-light plugin can't be re-installed:

You could still use the gui elements when you already have a dedicated mysensors solution.

I Don’t know, could you please explain? I need to chose colorcode, dimlevel and switch on/off

I need to know what your solution is, to explain if parts of led-light still can be used.
Is your ‘selfmade mysensors rgbw led controller’, a plugin or some javascript?
Are you using shell commands in rules to interface with your controller or something else?
And any other info to understand your solution will help.

@bertreb
Ah, Okay thanks for that in advance!
I used the led-light plugin with its class “DummyLedLight”. In that case it has only GUI elements with switch, color picker and dimlevel in one row!
From this device I used some rules on variable changement and from the 3 values I send custom commands to the mysensors device like this rule:

when $myledlight1.power changes then send custom "V_STATUS" nodeid: "13" sensorid: "1" cmdcode: "$myledlight1.power"

for the brightness:

when $myledlight1.brightness changes then send custom "V_PERCENTAGE" nodeid: "13" sensorid: "0" cmdcode: "$myledlight1.brightness"  

or for the color like this:

when $myledlight1.color changes then send custom "V_VAR1" nodeid: "13" sensorid: "2" cmdcode: "$myledlight1.color"

First I need a dummy control to interact on my GUI what gives me values in variables to use.
I remeber it has also problems with finding the right variable types to send as value/string via mysnsors gateway.

If you reduce the led-light plugin to only the dummyLedLight, you can use it with node 10.
The way to do that is editing 2 files. The following steps in commandline mode

0. stop pimatic (sudo service pimatic stop)
1. goto node_modules dir in your pimatic directory (mostly /home/pi/pimatic-app/node_modules)
2. remove the current pimatic-led-light dir in your node_modules dir
3. git clone https://github.com/philip1986/pimatic-led-light.git
4. cd pimatic-led-light
5. edit pimatic-led-light.coffee, replace the whole content with this

module.exports = (env) ->

  DummyLedLight = require('./devices/dummy')(env)

  class LedLightPlugin extends env.plugins.Plugin

    init: (app, @framework, @config) =>
      deviceConfigDef = require('./device-config-schema.coffee')
      @framework.deviceManager.registerDeviceClass 'DummyLedLight',
        configDef: deviceConfigDef.DummyLedLight
        createCallback: (config) -> return new DummyLedLight(config)

      @framework.on "after init", =>
        # Check if the mobile-frontend was loaded and get a instance
        mobileFrontend = @framework.pluginManager.getPlugin 'mobile-frontend'
        if mobileFrontend?
          mobileFrontend.registerAssetFile 'js', 'pimatic-led-light/ui/led-light.coffee'
          mobileFrontend.registerAssetFile 'css', 'pimatic-led-light/ui/led-light.css'
          mobileFrontend.registerAssetFile 'html', 'pimatic-led-light/ui/led-light.html'
          mobileFrontend.registerAssetFile 'js', 'pimatic-led-light/ui/vendor/spectrum.js'
          mobileFrontend.registerAssetFile 'css', 'pimatic-led-light/ui/vendor/spectrum.css'
          mobileFrontend.registerAssetFile 'js', 'pimatic-led-light/ui/vendor/async.js'
        else
          env.logger.warn 'your plugin could not find the mobile-frontend. No gui will be available'

  return new LedLightPlugin()

Save the file. Now you the only device thats left is the DummyLedLight

6. Edit the file package.json
   Change the following lines (remove dependencies and change pimatic version)

  "dependencies": {
    "bluebird": "^3.1.1",
    "cassert": "^0.1.2",
    "color": "^0.8.0",
    "lodash": "^3.10.1",
    "event-to-promise": "0.6.0"
  },
  "peerDependencies": {
    "pimatic": "0.9.*"
  },

Save the file. The references to unused (causing errors) dependencies are removed.

7. run command npm install
8. start pimatic again (sudo service pimatic start)
9. activate the led-light plugin in pimatic

whoaa, amazing! thank you so much!
Unfortunately I’m runing out of time for today, but will test it hopefully tomorrow. You’ll get info about it.

ok, good luck!

I’m still in trouble with this, do you know what is my mistake?
Did I use wrong folders or something similar?

Nevertheless Pimatic ist starting and also Led-Light dummy device has show up but the controls for colorpicker, dimmlevel and switch itself are missing. It shows only text like on/off , colorname and dimlevel as number.

Usually it should look similar to this picture from another thread

pi@FHEM-PI ~/pimatic-app/node_modules/pimatic-led-light $ npm install
npm WARN pimatic-led-light@0.3.5 requires a peer of pimatic@0.9.* but none is installed. You must install peer dependencies yourself.

audited 49 packages in 4.439s
found 7 vulnerabilities (3 low, 3 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

Did you refresh the browser (cache)?

@bertreb
Yes, but still not working.
Now after some playing and a few reboots, don’t know what it did in the background, the GUI elements are displayed and give some values. Tried everything with config as before, but still not working 100%.

Still get some strange errors, on/off is working but Dimlevel is a problem in rules:

error [pimatic]: rule ledlight-on-white error executing an action: this.device.getDimlevel is not a function

and also with color changes in rules.

error [pimatic]: Could not find an provider that provides the next action of “set myledlight1 to #FFBF10 after 2 seconds”.

Both errors effect only rules which are no more running now, but have done before with same code.
With GUI elements I can use the Slider for Dimlevel and also with color choose of color picker. That means new level and color is forwarded to the mysensors device while using GUI-elements but not if using same in rules which are triggered by a rf-button event.

I think i will give up for now and use rgbw only in switch on/off mode until i have another idea or swap to a new device in the kitchen …

Rules for sending command to the device

   {
      "id": "setdimmer",
      "name": "setRGBdimmer_Dimlevel",
      "rule": "when $myledlight1.brightness changes then send custom \"V_PERCENTAGE\" nodeid: \"13\" sensorid: \"0\" cmdcode: \"$myledlight1.brightness\"",
      "active": true,
      "logging": true
    },
   {
      "id": "setdimmer-2",
      "name": "setRGBdimmer_Color",
      "rule": "when $myledlight1.color changes then send custom \"V_VAR1\" nodeid: \"13\" sensorid: \"2\" cmdcode: \"$myledlight1.color\"",
      "active": true,
      "logging": true
    },

Rule from the RF-Button as a trigger

    {
      "id": "ledlight-on-white",
      "name": "LEDLight_onWhite",
      "rule": "when HomeEasy_FB_ch4 receives on or when Schalter_Kueche_links receives on then switch myledlight1 on and dim myledlight1 to 100% and set myledlight1 to #FFBF10 after 2 seconds",
      "active": true,
      "logging": true
    },

Hi, yes that could be a problem. I stripped the plugin probably to much. I will check whats needed to support what you are asking and how this can be implemented

@bertreb said in after Upgrade to Node 10, led-light plugin can't be re-installed:

Hi, yes that could be a problem. I stripped the plugin probably to much. I will check whats needed to support what you are asking and how this can be implemented

It’s very kind of you to help me like this, but please don’t put too much work into it! I know that this mysensor is a very special thing and I am sure I can come up with another solution.

I would have removed this RGB controller a long time ago, if it wasn’t also needed as a mysensors-repeater for a couple of other devices. I would have to switch others to ESP-Wlan first, but I just don’t have that much time to play on it all the time. Biggest problem is always when my wife can’t use something

Hi, the solution would be a separate plugin with a dummy led-rgb device. Like the dummy dimmer, extended with rgb functions. It’s not a big development, but if you don’t need it, i will stop the investigations.

@bertreb said in after Upgrade to Node 10, led-light plugin can't be re-installed:

Hi, the solution would be a separate plugin with a dummy led-rgb device. Like the dummy dimmer, extended with rgb functions. It’s not a big development, but if you don’t need it, i will stop the investigations.

It’s your decision to do this or not but I would be happy if there was a plugin that would allow me to control the mysensor RGB(W) boards. Whether then with rules as before or without it does not matter. I gave still two others with same function but not so important like kitchen light because its only ambient light.

Ok, i will make a plugin called pimatic-dummies with the led-light-rgb as a first device.
That device is available in the gui, variables and the rules part, but it doesn’t do anything further.

Hi, i made the plugin pimatic-dummies. You can install via the plugins page. Or if its not visible there you can add it in config.json in the plugins section, like this:

{
  "plugin": "dummies"
}

Pimatic needs to be stopped when you edit config.json. After restart you need to activate the plugin.
There’s 1 device DummyLedLight and is should behave like you are used to.
Let me know the results.