Node v8 plugin compatibility

---

While the plugin i2c-bme280 0.9.1 in node version 8.16 still works, it can no longer be installed in node version 10.16.
Radiohead 1.3.1 has been upgraded to version 2.0 and now also works under node version 10.16

Too bad the RF link plugin does not work. I ran into this when transitioning to a new install with a brand new RFlink to replace my homeduino setup. Seems I should have stayed with homeduino…

Any chance that someone might update the RFlink plugin? I am not a programmer myself.

Main problem is the dependency on serialport 2.0.6, which can not be compiled with node 10.x.x., or node v8 for that matter.

@woodhouse said in Node v8 plugin compatibility:

Main problem is the dependency on serialport 2.0.6, which can not be compiled with node 10.x.x., or node v8 for that matter.

You could try to set serialport to version 6.2.2 which is the latest du support node 4 but also has support for newer versions. This is what was done in homeduinojs: https://github.com/pimatic/homeduinojs/commit/4cb803fdf4c9fa5e2fb3b22782d5b4c34566291e

@michbeck100 Side note: Updating to serialport 6.2.2 (and newer version) also requires some code changes to adapt to the current API of serialport.

@mwittig

Would it be a lot of work to account for the api changes?

Where should one start?

@woodhouse

1. Create a fork of the plugin from Github and checkout into pimatic-app/node_modules.
2. set the version of serialport to 6.2.2 in the package.json of pimatic-rflink.
3. run npm install in the plugin directory
4. Run pimatic and try if the plugin works
5. I you have problems check the documentation of serialport@6.2.2 and restart at 4.
6. If everything is working push your changes and create a pull request so everyone can use your changes.

If you have no idea what these points mean, then you should ask someone with developer skill and the necessary hardware for testing.

@michbeck100 Thnx! I might give it a shot.

@woodhouse said in Node v8 plugin compatibility:

Would it be a lot of work to account for the api changes?

No. As @michbeck100 said please check the docs. Additionally you can have a look at the changes made for the serialport driver of pimatic.homeduino

Diff view:
https://github.com/pimatic/homeduinojs/compare/0b10da93cf2838c75f3e17878190d70eff14b8bd…master#diff-eb19dd2a13797301e6eff1e1b7fa3e74

or
Unified-Diff View:
https://github.com/pimatic/homeduinojs/compare/0b10da93cf2838c75f3e17878190d70eff14b8bd…master?diff=unified#diff-eb19dd2a13797301e6eff1e1b7fa3e74

• Click on “Files changed” Tab
• Click on the in the text “Showing 12 changed files with …”
• Click on link for “src/driver/serialport.coffee” at the bottom of the list
• Right-hand side of the diff is the current head of the branch

@mwittig

A nice challenge for me! Can anyone advise me on a good read up on coffeescript?

First things first. Right now we have to deal with a heatwave >40C here in mid western europe…

Darn! Didn’t RTFF… Updated everything, Node 10.16. Fail…
MySensors running into the same issues as RFlink. Tries to install serial port 2.0.6 just as RFlink does.

So tomorrow back to node 4 and see if I can find a way to produce a working version of MySensors on v10.16

@saxnpaule Can you add pimatic-telegram@1.1.13 and upwards please?

EDIT: Done