@kair I’ve checked this, and you are right! You can even run the 0.9.43 version with node 8. I didn’t test everything, but at least the default config seems to be running fine. Nevertheless the node_v8 branch also uses a newer CoffeeScript which in turn compiles to ES6 syntax (which is btw the reason for all the errors).
I think we should still go for this change, as it ensures more future compatibility.
-
Node v8 plugin compatibility
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@kair said in Node v8 plugin compatibility:
22:33:50.748 [pimatic, ppm] info: 2.15.12
There is one constraint, though: Because of the package.json from 0.9.43 you are using ppm (aka npm) in version 2.15.12 whereas the npm version that comes with node 8 is 4.x. This might have some implications that we don’t know yet.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@saxnpaule
Plugins installed, activated and working:
alarm 0.2.0
cron 0.8.8
filebrowser 0.9.0
iframe 0.3.1
links 0.8.6
log-reader 0.9.2
metar-weather 0.9.2
mobile-frontend 0.9.13 (already in your list)
openweather 0.9.4
ping 0.9.5
samsung-tv 0.9.0
shell-execute 0.9.11
sunrise 0.9.3
sysinfo 0.9.4Unfortunately could not install:
homeduino 0.9.11
rflink 0.7.2 -
Node 8.15 :
echo 0.5.3
homeduino 0.9.15Works too.
-
Easter holidays and with my spare raspberry start testing.
mobile-frontend 0.9.13
openweather 0.9.4
pimatic-charts 0.0.4
samsung-tv 0.9.0
shell-execute 0.9.11
sunrise 0.9.3
sysinfo 0.9.4
mail 0.8.6First tried node 8.15 and then with node 10.15.3
With both versions the above works and pimatic installation was without problems. I will stay with node 10.15.3 to try pimatic-owjs, pimatic-climasens.
Plugin: unipi-evok only not working:
error [pimatic-unipi-evok]: [UniPiUpdateManager] Web Socket Closed 00:44:49error [pimatic-unipi-evok]: [UniPiUpdateManager] Web Socket Error: Error: getaddrinfo ENOTFOUND 82ws 82ws:80 00:44:30error [pimatic-unipi-evok]: Error at Object.stack (/home/pi/pimatic-app/node_modules/pimatic-unipi-evok/node_modules/pimatic-plugin-commons/lib/index.js:251:100) at Object.rejectWithErrorString (/home/pi/pimatic-app/node_modules/pimatic-unipi-evok/node_modules/pimatic-plugin-commons/lib/index.js:155:21) at /home/pi/pimatic-app/node_modules/pimatic-unipi-evok/unipi-update-manager.coffee:166:18 at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:690:18) at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12) at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:705:18) at tryOnImmediate (timers.js:676:5) at processImmediate (timers.js:658:5) at process.topLevelDomainCallback (domain.js:120:23) 00:44:30error [pimatic-unipi-evok]: [UniPiUpdateManager] Error: unable to get status for all devices, exception caught: Error: getaddrinfo ENOTFOUND 82rest 82rest:80
And pimatic-zwave-usb gives an error and installation stops.
-
Thank you. I extended the first post. Also with not working plugins.
-
@bill-blacksoll said in Node v8 plugin compatibility:
getaddrinfo ENOTFOUND 82ws 82ws:80
Can you please provide the plugin configuration you have setup?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
After your answer i found out that i was my fault.
The local ip in plugin configuration was missing the htt://
So yes the Plugin: unipi-evok is working with node 10.15.3.
@SaxnPaule
Please update the first post to working -
@bill-blacksoll said in Node v8 plugin compatibility:
unipi-evok
I have also re-tested this on with node v10 and can confirm unipi-evok is working as expected
EDIT: Updated first post - move unipi to list of working plugins, added rflink to “NOT Working”
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
pimatic-owjs also working with node v8 and v10.15.3
EDIT mwittig: Updated first post
-
I updated node to 8.16.0. After reinstalling pimatic the system works.
I am using the telegram plugin which isn’t listed yet above.
Keep in mind telegram is a little bit tricky. When you use your old database, then no problem will occur during the first start. If you want to use a fresh db you need to disable the plugin before the first start in the config.json. After the system is up you can activate it. From now on the system will normally start with the running plugin. Unfortunately the plugin dev @Dan is not mor active here to fix this effect.
@SaxnPaule: Can you update the list above regarding telegram please.
-
pimatic-maxcul is now compatible too.
-
tested pimatic-jointspace with node 10.16.0 successfully
-
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
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@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.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
-
- Create a fork of the plugin from Github and checkout into
pimatic-app/node_modules
. - set the version of serialport to 6.2.2 in the
package.json
of pimatic-rflink. - run
npm install
in the plugin directory - Run pimatic and try if the plugin works
- I you have problems check the documentation of serialport@6.2.2 and restart at 4.
- 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.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten - Create a fork of the plugin from Github and checkout into
-
@michbeck100 Thnx! I might give it a shot.