Wow, that would be great!! Thank you very much for this super service!!
Please let us know when you’re ready…
-
New plugin for Telegram
-
1.1.11 is now available, with support for HTML formatted text as described earlier.
As it is relatively complicated to safely parse long messages (needed to preserve HTML markup per chunk) and the maximum message size is now 4096 characters, I have decided to disable the chunking of messages to allow unlimited length for now: Meaning the maximum length for text messages is now 4096 chars.Enjoy!
"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 -
Thanks a lot Dan!! I’m going to test tomorrow…
-
Thx for the update @Dan. I immediately change some rules where I was wishing the code-block format, but didn’t dare to ask about it…
-
@ortin said in New plugin for Telegram:
Thx for the update @Dan. I immediately change some rules where I was wishing the code-block format, but didn’t dare to ask about it…
ok ok, I’ve been told I can come across intimidating in real life, but I thought I was really friendly on the forum
Just kidding @OrTiN, dude you were one of the early adopters…you can always ask"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 -
-
it would be awesome to handle different Bots on one pimatic device. or is it somehow possible to let a specific message popup on my phone with a specific sound? for some events i need an alarm sound, for others the usual “ping” sound is enough (possible through botfather ai?)
-
@vincent-würzinger Hello Vincent, I have not seen options in the API allowing for custom notification sounds based on a message pattern. Implementing the ability to operate multiple bots requires associating the API token per-device, and then implementing a feature in the action provider so a user can define over which device (=specific bot) to send a message. On a mobile device you could then associate sounds per-bot. I’ll put this on the feature list, but currently I cannot give an estimate when this will be implemented.
"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 -
Hey Dan,
I haven’t use the TelegramReceiverDevice function for a long time. In the past, maybe you remember I had problems to get a response from the bot. Now I observed the same behavior in the last days as before. After pimatic restart or recreating the device it works for a while (approx. one day) after this it stops to response.I really have no idea, but from my knowledge the problem occurs the first time after the last functional update, where you’ve implemented the request of Zomer.
Can you please have a look to it. My config didn’t change since month regarding this function.
-
I still have the same problem. After a while (some days), Telegram stops responding. Is there a way to restart the Telegram service by rule or something?
-
@flop2006 said in New plugin for Telegram:
I still have the same problem. After a while (some days), Telegram stops responding. Is there a way to restart the Telegram service by rule or something?
Same here.
-
I found out that a “recreation” helps here. Means open the “TelegramReceiverDevice” and save it. The Telegram listener will be stopped and that started again. Now it will work for a while.
Maybe this restart of the listener can be achieved by an api command as well? -
since today I have a problem starting pimatic with the telegram bot. Seems to be sth with the connection to telegram - or? Internet etc. is working fine… Some ideas here?
[bot.error.webhook] { [Error: socket hang up] code: 'ECONNRESET', __trace: 'Error: From connect\n at TLSSocket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)\n at Object.TLSSocket._init.ssl.onclienthello.ssl.oncertcb.exports.connect (_tls_wrap.js:1048:11)\n at Agent.createConnection (https.js:79:22)\n at Agent.createSocket (_http_agent.js:188:16)\n at Agent.addRequest (_http_agent.js:157:23)\n at new ClientRequest (_http_client.js:142:16)\n at Object.exports.request (http.js:31:10)\n at Object.socket.once.exports.request (https.js:189:15)\n at Request.start (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:747:32)\n at Request.end (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:1506:10)\n at end (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:560:14)\n at Immediate._onImmediate (/home/pi/pimatic-app/node_modules/pimatic-telegram/node_modules/telebot/node_modules/request/request.js:574:7)\n at processImmediate [as _immediateCallback] (timers.js:396:17)' }
-
Very strange but it works as expected, today. So by now it is fine
-
I try to send messages to my bot. I get every time the issue that i must enter my passcode… I receive messages via my bot and admin in plugin settings are set… I don’t set a rule at the moment. But help didn’t work either…
-
Hi guys,
During startup of Pimatic I can see an error logged in the logfile:
12:22:42.226 [pimatic-telegram] debug: Listener enabled ruleset command: ' test ' 12:22:42.229 [pimatic-telegram] debug: TelegramReceiverDevice::constructor => Mapping Telegram predicate command: test to TelegramActionHandler for rule.id: telegram-test 12:22:42.365 [pimatic-telegram] debug: Listener enabled ruleset command: ' Iemand ' 12:22:42.366 [pimatic-telegram] debug: TelegramReceiverDevice::constructor => Mapping Telegram predicate command: Iemand to TelegramActionHandler for rule.id: telegram-karin-thuis (node) warning: possible EventEmitter memory leak detected. 201 variableValueChanged listeners added. Use emitter.setMaxListeners() to increase limit. Trace at VariableManager.addListener (events.js:239:17) at VariableManager.notifyOnChange (/home/pi/pimatic-app/node_modules/pimatic/lib/variables.coffee:748:8) at /home/pi/pimatic-app/node_modules/pimatic-chronotherm/chronotherm.coffee:221:29 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:693:18) at Promise._fulfill (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:638:18) at null._onTimeout (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/timers.js:26:46) at Timer.listOnTimeout (timers.js:92:15)
It looks like this can be solved by:
Use emitter.setMaxListeners() to increase limit.
How do I do this?
-
I’m getting the following errors when sending messages:
19:35:43 error [pimatic-telegram]: [BotClient] Error: Message was NOT sent to all recipients 19:35:43 error [pimatic-telegram]: [Message] Sending Telegram "Supermarkt-Tankstelle 1.159" to Hans: failed; reason: Not Found 19:35:43 info [pimatic-telegram]: { ok: false, error_code: 404, description: 'Not Found' }
with this rule:
when $prices.dieselMin gets updated send text telegram to Hans "$prices.dieselLocation $prices.dieselMin"
-
@hanss said in New plugin for Telegram:
I’m getting the following errors when sending messages:
19:35:43 error [pimatic-telegram]: [BotClient] Error: Message was NOT sent to all recipients 19:35:43 error [pimatic-telegram]: [Message] Sending Telegram "Supermarkt-Tankstelle 1.159" to Hans: failed; reason: Not Found 19:35:43 info [pimatic-telegram]: { ok: false, error_code: 404, description: 'Not Found' }
with this rule:
when $prices.dieselMin gets updated send text telegram to Hans "$prices.dieselLocation $prices.dieselMin"
Experience same problems with sending pictures.
-
Prob is solved for the moment. Had a typo in the chatID.
-
i used pimatic the last time 1-2 years ago. everything working well etc.
today i tried to setup a new rpi and i just cant get telegram plugin to work. its not loading, status is only “activated”, i put in in all data in the config but its not “loaded” which makes me not able to create a telegramreceiverdevice. any suggestions?