@Andi-Tudor, @Sven and others,
As far as I have been able to test the issue seems to have been resolved by downgrading the js spec for one of the dependencies. Currently release 1.1.1 is available, which works as expected.
People who have not upgraded to 1.1.0 can simply upgrade. If you have upgraded and ended up with a non-working version of Pimatic-Telegram you can upgrade, or alternatively clean your installation first:
- stop Pimatic if daemonized (execute “sudo service pimatic stop”)
- in your <pimatic-app>/node_modules folder execute “rm -rf pimatic-telegram”
- start Pimatic in console mode: “<pimatic-app>/node_modules/pimatic/pimatic.js” (this will automatically re-install pimatic-telegram, provided you have not removed the plugin from your config.json file)
- If the plugin was not installed automatically, you can do so by installing it through the plugins webpage
-if all is well (absence of the error “Unexpected token {” after loading plugin Pimatic-Telegram) you can stop the console mode, and start the pimatic daemon again: sudo service pimatic start
Of course, the known issue re upgrading old rules to the new syntax remains. Please read the documentation and familiarize yourself with the functionality changes.
My sincere apologies for any caused inconvenience.
"Screw the captain. It's the engineer running the ship!"
pimatic-telegram, pimatic-tts, pimatic-woox, pimatic-lg-smart-tv, pimatic-spotify, pimatic-wakeuplight and some not-announced plugins