Error Block-scoped declaration… with Homegear WS PlugIn
Hello,
I am using pimatic quite a while and I am still excided. My next step is the control of Homematic switches with it.
I just loaded the Homegear-WS Plugin and got the following error message after reboot:
22:42:44.280 [pimatic] info: Loading plugin: “pimatic-homegear-ws” (0.1.8)
22:42:53.978 [pimatic] error: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
npm -v 2.15.5
node -v v4.4.5
Any idea what went wrong?
Thanks for your help
@smally did you also update pimatic? If not, it is probably related to the plugin.
And i think the plugin isnt updated to this version of pimatic.
@Gleno0h Thanks for your quick response!
I’m using Pimatic Version 0.9.42. Updating to higher Pimatic version freezes the whole application.
I use the last version of the plugin, can this one be outdated?
How can I solve this to use Homematic with Pimatic?
@smally can you use the plugin homegear instead of homegear-ws? Im not sure what you want to do, maybe that one does what you need?
@Gleno0h I want to use it to control the Homematic switches but the plugin Homegear only controls MAX! and Homematic thermostats.
@smally ah yes, hmm i dont know then.
Does anyone else have any idea how to solve this?
Had a similar problem with an other plugin which was using some library which was using an other library without specifying a version. Because no version was specified it updated to the latest version of this library which was no longer compatible with node 4.
Most likely the same is happening here.
If you have some more of the error output you should be able to figure out which library causes the problem. Then you go backwards to check who depends on it in the package.json. Most likely there then no version is specified. Add the version of the library which still is node 4 compatible. Delete the library folder from the node_modules folder and run npm install in the directory of the module using the library which then should install the latest node 4 compatible version.
@thex Thanks - I’ll try that
