pimatic-telegram@1.1.14

---

@bertreb said in pimatic-telegram@1.1.14:

Homeduino was recently updated to support node v10. So that part should work (see Homeduino node10)
The older serialport 2.x is used in serveral plugins and blocks upgrades to higher node versions than v4. I introducted a new smartmeter plugin (with some extra features) just to get passed the blocking version of serialport in the older (not maintained) smartmeter plugins.

Ah ok, will do a test run on the raspad then, maybe this weekend. Gonna try a clean install of raspbian, node and pimatic to see how it runs. (because installing pimatic with node 10.x gave me errors on my running system)

@bertreb said in pimatic-telegram@1.1.14:

1. the updater knows witch node version Pimatic is running. It checks plugins for node v4 compatibility and doesn’t offer to update plugins that do not support v4.

I have changed Pimatic core to check for node version required by latest released plugin against installed node version. Intended behaviour of the fixture would be:

• incompatible updates would not be pushed to the list of “to be updated” plugins.

Big IF: Plugin devs need to ensure the minimum node version is listed in package.json

  "engines": {
    "node": ">=8.0.0",
    ...
  }

@mwittig will need to review my PR and approve. I have only done a dummy test on my dev by mocking a lower node version installed.

In general:

The discussion is starting to branch off from the pimatic-telegram release, and is becoming more about node compatibility.
Let’s open a different topic / discuss in the appropriate topics re node > v4 and plugin compatibility

Very nice!

I tested your PR. Some results:
On my node 4.6.2 pimatic the new plugin manager solves show incompatible plugin updates. So my installed pimatic-telegram@1.1.11 is not showing up anymore as a possible upgrade.
On my node 10.16.3 test system I changed a plugin package, to get a minimum required node version 20. In the same package I lowered the installed version number.
On the update page the plugin is shown as a possible update, that shouldn’t be because I don’t have node 20 installed (yet).
Is it the way I test or something else?

@bertreb this could not happen in a production environment, unless the user hacks a package as you did.
The change in pluginManager pulls package info such as version and required engine.node version from the NPM repository, and then compares requested (NPM package.json) node.engine.version against environment node version.

In your case it sees an upgradeable package:
(HACKED local package.json version < NPM package.json.version) => upgradeable)
(HACKED local package.json engine.node version is higher BUT not evaluated)

Unless I do not understand correctly.

@Dan your description is correct.
But shouldn’t the package.json engines.node version also be checked?

@bertreb Should not be necessary as we are only interested in the required node version listed in the upgrade package on the remote site. Then again, my logic is not necessarily logical .

@bertreb said in pimatic-telegram@1.1.14:

Thanks, I will downgrade to 1.1.11.

Hi. I’m quite newby with node js… Could you please tell me how to downgrade to 1.1.11. I already have the ZIP on my pimatic/node-modules and have replaced the main files. Althouh I get get “1.1.11” when i see the plugin list it does not work. I have already reboot pimatic, and verufy the token and ChatID, but I still get the “Could not find an provider…” error when creating a rule because the predicate “send” does not appear.

Than you very much!!

@villariezo

sudo systemctl stop pimatic

cd ~/pimatic-app/node_modules
sudo rm -rf pimatic-telegram
npm install pimatic-telegram@1.1.11

sudo systemctl start pimatic

@dan WORKING!!!

Thank you very much!!

@villariezo said in pimatic-telegram@1.1.14:

@dan WORKING!!!

Thank you very much!!

Great to hear! Enjoy!

hi, i installed pimatic from scratch and activated telegram plugin. i just cant set a telegram receiver device…the class is not available. manually adding in config also doesnt work

@joamann said in pimatic-telegram@1.1.14:

hi, i installed pimatic from scratch and activated telegram plugin. i just cant set a telegram receiver device…the class is not available. manually adding in config also doesnt work

Can you provide more information? The above does not really tell much…Also, did you follow the install guide?

• Output of node version node -v
• Pimatic startup log
• Telegram plugin and Telegram receiver device config from config.json

@dan said in pimatic-telegram@1.1.14:

node -v

v4.6.2

i manually added telegramreceiver device in config but only had errors and on the UI fields were grey-out so i removed it again. in the past i used telegram plugin without problem but this time it doesnt work somehow

log:
21:23:37.499 2019-12-13 Friday
21:24:14.999 [pimatic] info: Starting pimatic version 0.9.54
21:24:15.040 [pimatic] info: Node.js version 4.6.2
21:24:15.049 [pimatic] info: OpenSSL version 1.0.2j
21:24:24.279 [pimatic, ppm] info: 2.15.12
21:24:24.480 [pimatic] info: Loading plugin: “pimatic-cron” (0.8.8)
21:24:26.751 [pimatic] info: Loading plugin: “pimatic-mobile-frontend” (0.9.16)
21:24:30.076 [pimatic] info: Loading plugin: “pimatic-aqara” (0.4.5)
21:24:30.373 [pimatic] info: Loading plugin: “pimatic-telegram” (1.1.14)
21:24:30.647 [pimatic] error: Unexpected token {
21:24:31.609 [pimatic] info: Loading plugin: “pimatic-ping” (0.9.5)
21:24:31.863 [pimatic] info: Loading plugin: “pimatic-tplink-smartplug” (0.0.8)
21:24:34.057 [pimatic-cron] info: the time is: Fri Dec 13 2019 21:24:34 GMT+0000 (GMT)
21:24:37.329 [pimatic-tplink-smartplug] info: Starting pimatic-tplink-smartplug plugin
21:24:38.321 [pimatic] info: New device “Mi9T”…
21:24:38.498 [pimatic] info: New device “Temp”…
21:24:38.647 [pimatic] info: New device “Küche”…
21:24:38.763 [pimatic-tplink-smartplug] warn: {“state”:{“description”:“Current State”,“type”:“boolean”,“labels”:[“on”,“off”]},“watt”:{“description”:"The measured w$
21:24:39.149 [pimatic] info: New device “MUC”…
21:24:39.512 [pimatic-aqara] info: Gateway discovered
21:24:40.483 [pimatic-mobile-frontend] info: packing static assets
21:24:41.829 [pimatic-mobile-frontend] info: packing static assets finished
21:24:41.859 [pimatic-mobile-frontend] info: rendering html
21:24:49.718 [pimatic-aqara] info: Gateway is ready
21:25:23.567 [pimatic-mobile-frontend] info: rendering html finished
21:25:23.694 [pimatic] info: Listening for HTTP-request on port 80…
TCP Timeout
TCP Timeout
TCP Timeout
TCP Timeout
[undefined] device.send() Error: TCP Timeout
[undefined] device.send() Error: TCP Timeout
[undefined] device.send() Error: TCP Timeout
[undefined] device.send() Error: TCP Timeout
21:25:24.126 [pimatic-tplink-smartplug] error: Unable to get consumption of device: Error: TCP Timeout
21:25:24.144 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
21:25:24.152 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
21:25:24.192 [pimatic-tplink-smartplug, TPlinkHS110] error: Error getting attribute value MUC-AC-84-C6-29-06-27.state: undefined
21:25:24.476 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
21:25:24.496 [pimatic] warn: Could not update variable MUC-AC-84-C6-29-06-27.state: undefined

@joamann latest telegram plugin is not working on node 4.x.

Try this to get it to work again:

sudo systemctl stop pimatic

cd ~/pimatic-app/node_modules
sudo rm -rf pimatic-telegram
npm install pimatic-telegram@1.1.11

sudo systemctl start pimatic

@djmvt its working now. thx!

@djmvt correct, It says so in the main post of this thread

@dan true! It’s too bad actually because the latest telegram plugin prevents me now from doing other pimatic updates within the GUI. I’m working on migrating to hass.io so for the time being it’s fine by me.

@djmvt Understood. To be fair I am not even using telegram myself anymore. Just providing maintenance and support as a courtesy to others for now.