iobroker-community-adapters / iobroker.telegram Goto Github PK
View Code? Open in Web Editor NEWUse Telegram service to communicate with ioBroker
License: MIT License
Use Telegram service to communicate with ioBroker
License: MIT License
In telegram api its possible to sent messages "silently" without notification at smartphones.
parameter: disable_notification: true
In moment I use it with an own sendtotelegram function in blockly.
It would be very interesting for all blockly-users too, to get an option to silence low-level messages I guess.
As the adapter restarts after each iobroker restart (initiated by backitup or manually) or on every day (adapter cron) the push message "Bot wird neu gestartet" gets more and more annoying. I suggest an option in the adapter settings to activate silent mode (like in backitup).
2019-01-08 20:14:21.303 - error: Caught by controller[0]: Tue, 08 Jan 2019 19:14:07 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
2019-01-08 20:14:21.304 - error: Caught by controller[0]: In the future, you will have to enable it yourself.
2019-01-08 20:14:21.304 - error: Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:653:30
2019-01-08 20:14:21.304 - info: host.iobroker instance system.adapter.telegram.1 terminated with code 0 (OK)
Hey, is it possible to implement the feature to change the "I don't undestand" message?
thank you very much
Solution: delete break;
in line 88 of main.js.
I don't know why it is there, but it renders the loop useless.
Caught | 2018-06-06 22:49:29.815 | error | by controller[3]: at TCP.onread (net.js:547:20)
Caught | 2018-06-06 22:49:29.814 | error | by controller[3]: at readableAddChunk (_stream_readable.js:176:18)
Caught | 2018-06-06 22:49:29.813 | error | by controller[3]: at Socket.emit (events.js:188:7)
Caught | 2018-06-06 22:49:29.813 | error | by controller[3]: at emitOne (events.js:96:13)
Caught | 2018-06-06 22:49:29.812 | error | by controller[3]: at Socket.Parser.__onData (C:\ioBroker\node_modules\iobroker.telegram\node_modules\socksv5\lib\client.parser.js:33:10)
Caught | 2018-06-06 22:49:29.810 | error | by controller[3]: at Parser._onData (C:\ioBroker\node_modules\iobroker.telegram\node_modules\socksv5\lib\client.parser.js:122:21)
Caught | 2018-06-06 22:49:29.809 | error | by controller[3]: 2018-06-06 22:49:29.240 - telegram.0 Error: ttl expired
Caught | 2018-06-06 22:49:29.808 | error | by controller[2]: 2018-06-06 22:49:29.238 - telegram.0 uncaught exception: ttl expired
Caught | 2018-06-06 22:49:29.807 | error | by controller[1]: at TCP.onread (net.js:547:20) code: 'ETTLEXPIRED' }
Caught | 2018-06-06 22:49:29.806 | error | by controller[1]: at readableAddChunk (_stream_readable.js:176:18)
Caught | 2018-06-06 22:49:29.805 | error | by controller[1]: at Socket.emit (events.js:188:7)
Caught | 2018-06-06 22:49:29.804 | error | by controller[1]: at emitOne (events.js:96:13)
Caught | 2018-06-06 22:49:29.803 | error | by controller[1]: at Socket.Parser.__onData (C:\ioBroker\node_modules\iobroker.telegram\node_modules\socksv5\lib\client.parser.js:33:10)
Caught | 2018-06-06 22:49:29.801 | error | by controller[1]: at Parser._onData (C:\ioBroker\node_modules\iobroker.telegram\node_modules\socksv5\lib\client.parser.js:122:21)
Caught | 2018-06-06 22:49:29.799 | error | by controller[1]: { Error: ttl expired
I am sending me a message, but all I get:
on({id: "telegram.0.communicate.requestUserId"/*Last received request*/, change: "any"}, function(value) {
console.log(JSON.stringify(value));
// "telegram.0.communicate.requestUserId"/*User ID of last received request*/
})
[info] | javascript.0 script.js.common.telegram: {"id":"telegram.0.communicate.requestUserId","newState":{"val":"","ts":1544480669826,"ack":false,"lc":1544305043073,"from":"system.adapter.telegram.0"},"oldState":{"val":"","ts":1544480648684,"ack":false,"lc":1544305043073,"from":"system.adapter.telegram.0"},"state":{"val":"","ts":1544480669826,"ack":false,"lc":1544305043073,"from":"system.adapter.telegram.0"}}
-- | --
the "request" also does not contain userid
We have 10 registered users, but only want to send a message to user 1, 3 and 4..
sendTo telegram.0 user: 'User1,User3,User4' ...
The current polling interval is 1 second.
User may want to change to a longer polling interval.
It would be desired to make polling user configurable.
it would be nice, if the state command could be disabled in the config tabs.
not every registered user should be able to read or change all states.
thanks for your work!
When i try to include "send To" telegram into my Script, it always close after clicking on it.
I see the Script Adapter Icon, but when i click on it, it always close again.
More people with the same Problem here:
https://forum.iobroker.net/viewtopic.php?t=11377
last two entries.
Bekommt seit der aktuellen Version folgenden Error:
Caught | 2018-12-03 16:45:48.158 | error | by controller[0]: See yagop/node-telegram-bot-api#319. at module.js:577:32 |
---|---|---|---|
Caught | 2018-12-03 16:45:48.158 | error | by controller[0]: In the future, you will have to enable it yourself. |
Caught | 2018-12-03 16:45:48.158 | error | by controller[0]: Mon, 03 Dec 2018 15:45:38 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. |
Caught | 2018-06-06 22:50:01.241 | error | by controller[0]: See yagop/node-telegram-bot-api#319. at module.js:570:32
Caught | 2018-06-06 22:50:01.240 | error | by controller[0]: In the future, you will have to enable it yourself.
Caught | 2018-06-06 22:50:01.238 | error | by controller[0]: Wed, 06 Jun 2018 15:49:35 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
I have filed an iobroker issue, before I found out about this Git!
So for the sake of "redundancy makes for persuasion" here it is again...
This is the English request following up to this German forum post: https://forum.iobroker.net/viewtopic.php?f=22&t=3890&p=166023#p166023 .
O.K., so in the Blockly "SendTo" block for a Telegram messsage, there is a "receiver" (Empfänger) field where you can enter the Telegram user id for a specific receiver. The Javascript that's being generated, uses the "user" parameter to the "sendTo" object. The generated code looks like this:
sendTo("telegram.0", "send", {
text: 'Woof!',
user: '123456789'
});
The "user" parameter does not support sending to group chat id's, but the "chatId" parameter does!.
On the other hand, the "chatId" parameter also supports sending to single users!!
So by exchanging the "user" parameter for the - better - "chatId" parameter in Blockly, you could make admins and users much happier without losing existing functionality.
The better code would then look like this:
sendTo("telegram.0", "send", {
text: 'Meeow!',
chatId: '-987654321'
});
Thanks for considering this change.
Oliver.
adapter.config.rememberUsers
is allways false when loading the adapter, regardless of the checkbox in the config-dialog.
Ironically this checkbox is always checked, when reopening the config-dialog.
Anyone got an idea?
If I got the time tomorrow, I will attempt to debug this.
The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466
Hello! Are you planning to support MTProto?
Hi
Can i disable the start/stop/restart message from the adapter ?
As I was having another issue regarding the blocky script with user name field, I realised that the adapter detects me with my first name as username and not my actual username.
Since first names are not unique this could lead to some issues down the road.
I tried to delete everything and reinstall the Adapter and bot but still it shows my first name as user and not my actual one.
Not sure if this is just me, or it is how it is.
I receive the following error during the night for around 10 times in the row - anything i can do?
2018-07-04 03:17:02.725 - error: telegram.0 polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway
Hallo,
könnte bitte einer der Entwickler die Möglichkeit einbauen ein Photo auch wie in der API möglich als Buffer (Binary) zu senden. Dadurch muss man das Bild einer Kamera z.B. nicht erst auf der Festplatte zwischenspeichern und kann es direkt senden. Beispiel:
`var TelegramBot = require('node-telegram-bot-api');
var bot = new TelegramBot(token);
var requestSettings = {
url: 'http://httpbin.org/image',
encoding: null
};
request(requestSettings, function (error, response, buffer) {
if (!error && response.statusCode == 200) {
bot.sendPhoto(chatId, buffer)
}
});`
Leider habe ich im Moment keiner Zeit einen Fork zu machen und dies selber einzubauen.
Danke und Gruß AlGu
Add possibility to remove User from Adapter.
Idee eines einfach zu konfigurierendem Telegram Bots.
Kein Javascript mehr für jede Funktion sondern ein GUI ähnlich Blockly
Man wählt ein Objekt aus definiert was der Bot damit tun soll und gibt die Ausgabe an den User an.
Man kann sich mit Telegram einen kleinen Bot basteln der bei einem Keyword oder Command entweder die passende Ausgabe ausgibt oder eine Auswahl anbietet.
https://core.telegram.org/bots/2-0-intro
Ich habe mit ein JS gebaut das bei dem Triggerwort Temperatur eine Auswahl der verfügbaren Temperaturmesser zeigt die man dann per Button anklicken kann. Dann bekomme ich die Temperatur.
Es geht alles über Blockly oder JS ist aber für mich zumindest kompliziert wenn es komplexer wird.
Übernommen von ioBroker/AdapterRequests#19
Hello!
Possibly I found an bug.
When I try to insert something in response field from Node-red ioBroker node, nothing sends to Telegram.
But when I update this field manually message sends successfully.
Possible this happens because node-red sends messages "From: node-red.0" user and via interface I send it "From: admin.0".
Also I can successfully send messages via text2command plugin...
Seit 3 Tagen startet der Telegram Adapter um 05:04 Uhr jeweils neu. In der Log steht "Scheduled Restart" bzw. Fehler Code 156.
The adapter is configured in "server" mode. If I send a message to the bot, the adapter reloads with an error. Messages from the adapter come to me without any problems.
time | debug | message |
---|---|---|
2018-11-30 19:41:44.140 | - error: | telegram.0 uncaught exception: msg is not defined |
2018-11-30 19:41:44.141 | - error: | telegram.0 ReferenceError: msg is not defined |
--- | --- | at IncomingMessage.req.on.e (/opt/iobroker/node_modules/iobroker.telegram/main.js:216:31) |
--- | --- | at emitNone (events.js:86:13) |
--- | --- | at IncomingMessage.emit (events.js:185:7) |
--- | --- | at endReadableNT (_stream_readable.js:978:12) |
--- | --- | at _combinedTickCallback (internal/process/next_tick.js:80:11) |
--- | --- | at process._tickCallback (internal/process/next_tick.js:104:9) |
2018-11-30 19:41:44.646 | - info: | telegram.0 terminating |
2018-11-30 19:41:44.663 | - error: | Caught by controller[1]: ReferenceError: msg is not defined |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at IncomingMessage.req.on.e (/opt/iobroker/node_modules/iobroker.telegram/main.js:216:31) |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at emitNone (events.js:86:13) |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at IncomingMessage.emit (events.js:185:7) |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at endReadableNT (_stream_readable.js:978:12) |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:80:11) |
2018-11-30 19:41:44.665 | - error: | Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:104:9) |
2018-11-30 19:41:44.665 | - error: | host.iobroker instance system.adapter.telegram.0 terminated with code 0 (OK) |
2018-11-30 19:41:44.666 | - info: | host.iobroker Restart adapter system.adapter.telegram.0 because enabled |
2018-11-30 19:41:45.705 | - info: | host.iobroker instance system.adapter.telegram.0 started with pid 17078 |
2018-11-30 19:41:46.788 | - info: | telegram.0 starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.telegram, node: v6.14.4 |
2018-11-30 19:41:48.440 | - info: | telegram.0 https server listening on port 8443 |
I have to iobroker servers set up. On each of those servers I am receiving the following error message
`
host.raspberrypi | 2018-07-26 05:04:00.611 | info | Restart adapter system.adapter.telegram.0 because enabled
host.raspberrypi | 2018-07-26 05:04:00.610 | error | instance system.adapter.telegram.0 terminated with code 156 ()
telegram.0 | 2018-07-26 04:36:04.092 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway
telegram.0 | 2018-07-26 04:36:00.840 | error | polling_error:ETELEGRAM, ETELEGRAM: 500 Internal server error: restart
telegram.0 | 2018-07-26 04:21:44.415 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway
`
This occuring on both machine every day at the same time.
Nach Update auf telegram Version 1.2.4 bekomme ich folgenden Fehler/Hinweis im Log mit verweis auf yagop/node-telegram-bot-api#319
Caught | 2018-06-03 22:05:05.724 | error | by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at module.js:577:32
Caught | 2018-06-03 22:05:05.724 | error | by controller[0]: In the future, you will have to enable it yourself.
Caught | 2018-06-03 22:05:05.724 | error | by controller[0]: Sun, 03 Jun 2018 20:04:53 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
Es wäre praktisch wenn die parse_mode Option um Text per Markdown oder HTML zu formatieren auch per Blockly Block möglich wäre.
z. B. als Option im telegram Block oder als optionaler Schalter in der Adapterkonfiguration im Nachrichten Feld, also wenn z. B. die Option HTML gesetzt ist wird immer der parse_mode: 'HTML' per telegram Blockly Block im Code mit eingefügt.
For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268
Ist es wichtig jede Stunden diesen Eintrag als Info zu bekommen?
telegram.0 | 2019-01-23 20:04:06.582 | info | getMe (reconnect):id":1124567890"is_bot":true,"first_name":.....
The Datapoint "telegram.0.communicate.requestChatId" and "telegram.0.communicate.requestMessageId" has currently the chatID and the messageId of the last recived message.
In some cases I need the chatID and the messageID of the last send message. (in case If I wan't to update or delete the last message by the Bot.)
To Thus the BotAPI return a Message object, of a message was send On success. As part of this returned object is the message_id and the chat identifier.
Would it be possible to have two additional objects in the Telegram adapter which containes the message and the chat ID of the last send message?
As workaround I currently stores my own message ID, where I use the value of "telegram.0.communicate.requestMessageId" and add a 1 on every send message anbd reset this to the value of "telegram.0.communicate.requestMessageId" on reciving a new message. But that solution is not so good.
I am not sure if this is intended or if user has a function at all, but shouldn't "username" be the chatId so we can ad a text field to Username in blocky in order to text a specific person?
So far this only works when we use chatId: 'XXX' instead of user in JS.
Thanks in advance!
Ist versuche über telegram ein PhotoAlbum zu verschicken.
Laut API Spezifikation ist die Funktion sendMediaGroup dafür gedacht (https://core.telegram.org/bots/api/#).
Meine Idee war wie folgt:
var mediastring = "{type: 'photo', media: '/tmp/camera.jpg' }, {type: 'photo', media: '/tmp/camera.jpg' }, {type: 'photo', media: '/tmp/camera.jpg'}";
// JSON serialize
var meineBilder = JSON.stringify(mediastring);
var obj = JSON.parse(meineBilder);
sendTo("telegram.0", {
text: 'mediagroup',
chatId: 398694033,
media: obj,
});
Ich bekomme in telegram App nur den Text "mein Text" angezeigt, aber nicht die Bilder.
Laut der Spezifikation (siehe den Link oben) soll man auch nur die chatid und media angeben. Wenn ich "text" weg lasse, erhalte ich aber folgende Fehlermeldung im iobroker log:
telegram.0 2018-01-26 14:45:01.278 error Cannot send message [user - undefined]: Error: ETELEGRAM: 400 Bad Request: message text is empty
Muss man die den Adapter eventuell abändern, dass er auch ohne den Parameter "text" funktioniert?
Beim täglichen Neustart des Adapters wird eine Meldung vom Typ error in die Logdatei geschrieben.
Da dieser Neustart des Adapters jedoch fest einprogrammiert ist und es sich dabei um ein normales Ereignis handelt, wäre es sehr wünschenswert, wenn die Meldung lediglich eine info-Meldung wäre.
bei aktivierung des adapters (1.3.0) auf Raspi-Image (ioBroker_Image_RPi_2-3_20180401_stretch.img)
kommt immer die Meldung:
polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
debug:
2018-09-24 20:40:33.332 - debug: telegram.0 objectDB connected
2018-09-24 20:40:33.411 - debug: telegram.0 statesDB connected
2018-09-24 20:40:33.425 - info: telegram.0 States connected to redis: 127.0.0.1:6379
2018-09-24 20:40:33.686 - info: telegram.0 starting. Version 1.2.7 in /opt/iobroker/node_modules/iobroker.telegram, node: v8.11.1
2018-09-24 20:40:33.992 - debug: telegram.0 Schedule restart: 4 5 * * *
2018-09-24 20:40:34.073 - debug: telegram.0 Start polling with: 300(number) ms interval
2018-09-24 20:40:34.196 - debug: telegram.0 redis pmessage io.telegram.0.communicate.request io.telegram.0.communicate.request {"val":"","ack":true,"ts":1537814434178,"q":0,"from":"system.adapter.telegram.0","lc":1537813620368}
2018-09-24 20:40:34.201 - debug: telegram.0 redis pmessage io.telegram.0.communicate.response io.telegram.0.communicate.response {"val":"","ack":true,"ts":1537814434181,"q":0,"from":"system.adapter.telegram.0","lc":1537813620369}
2018-09-24 20:40:34.597 - info: telegram.0 getMe: {"id":164045638,"is_bot":true,"first_name":"Cluxxxx","username":"Cluxxxx_bot"}
2018-09-24 20:40:41.104 - error: telegram.0 polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2018-09-24 20:40:47.976 - error: telegram.0 polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2018-09-24 20:40:54.859 - error: telegram.0 polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
2018-09-24 20:41:03.501 - error: telegram.0 polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
mfg
Farmer
telegram.0 | 2017-10-05 21:44:34.342 | error | polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhook
-- | -- | -- | --
Every second a line like above!
Hi, after updating to latest iobroker 3, i'm getting a log of errors logged from telegram adapter:
I've a watchdog running, restarting iobroker when a load of 6 is reached on my raspi3.
This is now happening every day!
I'm runnign telegram adapter version 1.1.4, because with v1.2.0 i was not able to connect to the bot at all!
should I try to update again?
Or make a remove/reinstall of the adapter?
`
host.ioBroker | 2018-09-13 20:36:06.678 | error | instance system.adapter.telegram.0 terminated with code 0 (OK) |
---|---|---|---|
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at WritableState.onwrite (_stream_writable.js:90:5) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at onwrite (_stream_writable.js:378:7) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at afterWrite (_stream_writable.js:387:3) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/PerMessageDeflate.js:249:5 |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:368:7 |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/Receiver.js:536:18 |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at Receiver.ontext (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:841:10) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at WebSocket.emit (events.js:191:7) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at emitTwo (events.js:106:13) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at WebSocket.onMessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/ws/lib/WebSocket.js:442:14) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transports/websocket.js:146:10) |
Caught | 2018-09-13 20:36:06.678 | error | by controller[8]: at WS.Transport.onData (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:137:8) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at WS.Transport.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/transport.js:145:8) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at WS.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at WS. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:268:10) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket.onPacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/engine.io-client/lib/socket.js:451:14) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9) |
Caught | 2018-09-13 20:36:06.677 | error | by controller[8]: at Socket.that.getForeignObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:724:21) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at /opt/iobroker/node_modules/iobroker.telegram/main.js:65:32 |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at Object.createServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:55:26) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at Object.Greenlock.create (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/index.js:258:13) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at promisifyAllSelf (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/index.js:15:20) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at Array.forEach (native) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/index.js:17:33 |
Caught | 2018-09-13 20:36:06.676 | error | by controller[8]: TypeError: util.promisify is not a function |
Caught | 2018-09-13 20:36:06.676 | error | by controller[7]: Detected Let's Encrypt v02 URL. Changing version to draft-12. |
Caught | 2018-09-13 20:36:06.676 | error | by controller[5]: This will be required in versions v2.3+ |
Caught | 2018-09-13 20:36:06.676 | error | by controller[5]: (also 'npm install --save le-acme-core' as this legacy dependency will soon be removed) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[4]: 'v01' for Let's Encrypt v1 (deprecated) |
Caught | 2018-09-13 20:36:06.676 | error | by controller[3]: or |
Caught | 2018-09-13 20:36:06.675 | error | by controller[3]: ('v02' is an alias of 'draft-12' |
Caught | 2018-09-13 20:36:06.675 | error | by controller[2]: 'draft-12' for Let's Encrypt v2 and ACME draft 12 |
Caught | 2018-09-13 20:36:06.675 | error | by controller[2]: Please specify 'version' option: |
Caught | 2018-09-13 20:36:06.674 | error | by controller[2]: ========================================================== |
Caught | 2018-09-13 20:36:06.674 | error | by controller[2]: == greenlock.js (v2.2.0+) == |
Caught | 2018-09-13 20:36:06.674 | error | by controller[2]: ========================================================== |
Caught | 2018-09-13 20:36:06.674 | error | by controller[0]: See yagop/node-telegram-bot-api#319. at module.js:577:32 |
Caught | 2018-09-13 20:36:06.674 | error | by controller[0]: In the future, you will have to enable it yourself. |
Caught | 2018-09-13 20:36:06.674 | error | by controller[0]: Thu, 13 Sep 2018 18:36:05 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. |
`
Hello,
how could i make a new line in a message response?
Hi,
the folowing error ocurred again and again (mostly at night):
telegram.0 | 2018-02-01 03:06:42.618 | error |
-- | -- | -- | --
telegram.0 | 2018-02-01 03:06:42.618 | error |
telegram.0 | 2018-02-01 03:06:42.618 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:42.618 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:42.618 | error |
telegram.0 | 2018-02-01 03:06:42.618 | error |
telegram.0 | 2018-02-01 03:06:42.618 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:42.285 | error |
telegram.0 | 2018-02-01 03:06:42.285 | error |
telegram.0 | 2018-02-01 03:06:42.285 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:42.285 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:42.285 | error |
telegram.0 | 2018-02-01 03:06:42.285 | error |
telegram.0 | 2018-02-01 03:06:42.285 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:41.949 | error |
telegram.0 | 2018-02-01 03:06:41.949 | error |
telegram.0 | 2018-02-01 03:06:41.949 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:41.949 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:41.949 | error |
telegram.0 | 2018-02-01 03:06:41.949 | error |
telegram.0 | 2018-02-01 03:06:41.949 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:41.617 | error |
telegram.0 | 2018-02-01 03:06:41.617 | error |
telegram.0 | 2018-02-01 03:06:41.617 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:41.617 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:41.617 | error |
telegram.0 | 2018-02-01 03:06:41.617 | error |
telegram.0 | 2018-02-01 03:06:41.617 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:41.285 | error |
telegram.0 | 2018-02-01 03:06:41.285 | error |
telegram.0 | 2018-02-01 03:06:41.285 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:41.285 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:41.285 | error |
telegram.0 | 2018-02-01 03:06:41.285 | error |
telegram.0 | 2018-02-01 03:06:41.285 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:40.941 | error |
telegram.0 | 2018-02-01 03:06:40.941 | error |
telegram.0 | 2018-02-01 03:06:40.941 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:40.941 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:40.941 | error |
telegram.0 | 2018-02-01 03:06:40.941 | error |
telegram.0 | 2018-02-01 03:06:40.941 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:40.607 | error |
telegram.0 | 2018-02-01 03:06:40.607 | error |
telegram.0 | 2018-02-01 03:06:40.607 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:40.607 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:40.607 | error |
telegram.0 | 2018-02-01 03:06:40.607 | error |
telegram.0 | 2018-02-01 03:06:40.607 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:40.267 | error |
telegram.0 | 2018-02-01 03:06:40.267 | error |
telegram.0 | 2018-02-01 03:06:40.267 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:40.267 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:40.267 | error |
telegram.0 | 2018-02-01 03:06:40.267 | error |
telegram.0 | 2018-02-01 03:06:40.267 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:39.936 | error |
telegram.0 | 2018-02-01 03:06:39.936 | error |
telegram.0 | 2018-02-01 03:06:39.936 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:39.936 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:39.936 | error |
telegram.0 | 2018-02-01 03:06:39.936 | error |
telegram.0 | 2018-02-01 03:06:39.936 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:37.487 | error |
telegram.0 | 2018-02-01 03:06:37.487 | error |
telegram.0 | 2018-02-01 03:06:37.487 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:37.487 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:37.487 | error |
telegram.0 | 2018-02-01 03:06:37.487 | error |
telegram.0 | 2018-02-01 03:06:37.487 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:37.157 | error |
telegram.0 | 2018-02-01 03:06:37.157 | error |
telegram.0 | 2018-02-01 03:06:37.157 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:37.157 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:37.157 | error |
telegram.0 | 2018-02-01 03:06:37.157 | error |
telegram.0 | 2018-02-01 03:06:37.157 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:36.825 | error |
telegram.0 | 2018-02-01 03:06:36.825 | error |
telegram.0 | 2018-02-01 03:06:36.825 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:36.825 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:36.825 | error |
telegram.0 | 2018-02-01 03:06:36.825 | error |
telegram.0 | 2018-02-01 03:06:36.825 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:36.496 | error |
telegram.0 | 2018-02-01 03:06:36.496 | error |
telegram.0 | 2018-02-01 03:06:36.496 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:36.496 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:36.496 | error |
telegram.0 | 2018-02-01 03:06:36.496 | error |
telegram.0 | 2018-02-01 03:06:36.496 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:36.162 | error |
telegram.0 | 2018-02-01 03:06:36.162 | error |
telegram.0 | 2018-02-01 03:06:36.162 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:36.162 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:36.162 | error |
telegram.0 | 2018-02-01 03:06:36.162 | error |
telegram.0 | 2018-02-01 03:06:36.162 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:35.831 | error |
telegram.0 | 2018-02-01 03:06:35.831 | error |
telegram.0 | 2018-02-01 03:06:35.831 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:35.831 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:35.831 | error |
telegram.0 | 2018-02-01 03:06:35.831 | error |
telegram.0 | 2018-02-01 03:06:35.831 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:35.482 | error |
telegram.0 | 2018-02-01 03:06:35.482 | error |
telegram.0 | 2018-02-01 03:06:35.482 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:35.482 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:35.482 | error |
telegram.0 | 2018-02-01 03:06:35.482 | error |
telegram.0 | 2018-02-01 03:06:35.482 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:35.151 | error |
telegram.0 | 2018-02-01 03:06:35.151 | error |
telegram.0 | 2018-02-01 03:06:35.151 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:35.151 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:35.151 | error |
telegram.0 | 2018-02-01 03:06:35.151 | error |
telegram.0 | 2018-02-01 03:06:35.151 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:34.814 | error |
telegram.0 | 2018-02-01 03:06:34.814 | error |
telegram.0 | 2018-02-01 03:06:34.814 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:34.814 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:34.814 | error |
telegram.0 | 2018-02-01 03:06:34.814 | error |
telegram.0 | 2018-02-01 03:06:34.814 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:34.487 | error |
telegram.0 | 2018-02-01 03:06:34.487 | error |
telegram.0 | 2018-02-01 03:06:34.487 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:34.487 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:34.487 | error |
telegram.0 | 2018-02-01 03:06:34.487 | error |
telegram.0 | 2018-02-01 03:06:34.487 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:34.148 | error |
telegram.0 | 2018-02-01 03:06:34.148 | error |
telegram.0 | 2018-02-01 03:06:34.148 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:34.148 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:34.148 | error |
telegram.0 | 2018-02-01 03:06:34.148 | error |
telegram.0 | 2018-02-01 03:06:34.148 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:33.809 | error |
telegram.0 | 2018-02-01 03:06:33.809 | error |
telegram.0 | 2018-02-01 03:06:33.809 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:33.809 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:33.809 | error |
telegram.0 | 2018-02-01 03:06:33.809 | error |
telegram.0 | 2018-02-01 03:06:33.809 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:33.476 | error |
telegram.0 | 2018-02-01 03:06:33.476 | error |
telegram.0 | 2018-02-01 03:06:33.476 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:33.476 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:33.476 | error |
telegram.0 | 2018-02-01 03:06:33.476 | error |
telegram.0 | 2018-02-01 03:06:33.476 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:33.140 | error |
telegram.0 | 2018-02-01 03:06:33.140 | error |
telegram.0 | 2018-02-01 03:06:33.140 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:33.140 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:33.140 | error |
telegram.0 | 2018-02-01 03:06:33.140 | error |
telegram.0 | 2018-02-01 03:06:33.140 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:32.814 | error |
telegram.0 | 2018-02-01 03:06:32.814 | error |
telegram.0 | 2018-02-01 03:06:32.814 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:32.814 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:32.814 | error |
telegram.0 | 2018-02-01 03:06:32.814 | error |
telegram.0 | 2018-02-01 03:06:32.814 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:32.488 | error |
telegram.0 | 2018-02-01 03:06:32.488 | error |
telegram.0 | 2018-02-01 03:06:32.488 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:32.488 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:32.488 | error |
telegram.0 | 2018-02-01 03:06:32.488 | error |
telegram.0 | 2018-02-01 03:06:32.488 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:32.133 | error |
telegram.0 | 2018-02-01 03:06:32.133 | error |
telegram.0 | 2018-02-01 03:06:32.133 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:32.133 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:32.133 | error |
telegram.0 | 2018-02-01 03:06:32.133 | error |
telegram.0 | 2018-02-01 03:06:32.133 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:31.808 | error |
telegram.0 | 2018-02-01 03:06:31.808 | error |
telegram.0 | 2018-02-01 03:06:31.808 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:31.808 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:31.808 | error |
telegram.0 | 2018-02-01 03:06:31.808 | error |
telegram.0 | 2018-02-01 03:06:31.808 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:31.477 | error |
telegram.0 | 2018-02-01 03:06:31.477 | error |
telegram.0 | 2018-02-01 03:06:31.477 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:31.477 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:31.477 | error |
telegram.0 | 2018-02-01 03:06:31.477 | error |
telegram.0 | 2018-02-01 03:06:31.477 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:31.152 | error |
telegram.0 | 2018-02-01 03:06:31.152 | error |
telegram.0 | 2018-02-01 03:06:31.152 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:31.152 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:31.152 | error |
telegram.0 | 2018-02-01 03:06:31.152 | error |
telegram.0 | 2018-02-01 03:06:31.152 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:30.813 | error |
telegram.0 | 2018-02-01 03:06:30.813 | error |
telegram.0 | 2018-02-01 03:06:30.813 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:30.813 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:30.813 | error |
telegram.0 | 2018-02-01 03:06:30.813 | error |
telegram.0 | 2018-02-01 03:06:30.813 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:30.486 | error |
telegram.0 | 2018-02-01 03:06:30.486 | error |
telegram.0 | 2018-02-01 03:06:30.486 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:30.486 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:30.486 | error |
telegram.0 | 2018-02-01 03:06:30.486 | error |
telegram.0 | 2018-02-01 03:06:30.486 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:30.158 | error |
telegram.0 | 2018-02-01 03:06:30.158 | error |
telegram.0 | 2018-02-01 03:06:30.158 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:30.158 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:30.158 | error |
telegram.0 | 2018-02-01 03:06:30.158 | error |
telegram.0 | 2018-02-01 03:06:30.158 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:29.831 | error |
telegram.0 | 2018-02-01 03:06:29.831 | error |
telegram.0 | 2018-02-01 03:06:29.831 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:29.831 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:29.831 | error |
telegram.0 | 2018-02-01 03:06:29.831 | error |
telegram.0 | 2018-02-01 03:06:29.831 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
telegram.0 | 2018-02-01 03:06:29.434 | error |
telegram.0 | 2018-02-01 03:06:29.434 | error |
telegram.0 | 2018-02-01 03:06:29.434 | error | nginx/1.12.2
telegram.0 | 2018-02-01 03:06:29.434 | error | 502 Bad Gateway
telegram.0 | 2018-02-01 03:06:29.434 | error |
telegram.0 | 2018-02-01 03:06:29.434 | error |
telegram.0 | 2018-02-01 03:06:29.434 | error | polling_error:EPARSE, Error: EPARSE: Error parsing Telegram response:
Can you adjust the polling somewhere or see how it is set?
Thanks
AlGu
Allow the search for states using partial ids, ids with wildcards and names.
How to make sure not to return hunderts of ids? :-)
Maybe also allow to use SMartnames to search/Access states?
seit den letzten zwei updates bekomme ich immer Fehlermeldungen:
telegram.0 | 2018-07-26 03:14:23.329 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
---|---|---|---|
telegram.0 | 2018-07-26 03:14:23.006 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:22.684 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:22.360 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:22.037 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:21.715 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:21.391 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:21.067 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:20.743 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:20.419 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:14:20.093 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway |
telegram.0 | 2018-07-26 03:04:02.336 | info | getMe (reconnect): {"id":3782233634,"is_bot":true,"first_name":"IoBroker","username":"ww_bot"} |
The cron-based restart will go back to default 4 5 * * * every time an update installs. User changes should be persistant
Add please tcp socks5 proxy support.
In Russia Telegram was blocked :(
It is very strongly necessary.
If the password for the Bot is changed in the instance settings the previously authenticated users should be deleted for safety reasons. (Or maybe at least give the user the possibility to choose if the users must reauthenticate or not (checkbox?)) Otherwise the users which were authenticated before the change of the password can just continue to use the bot without entering the new password.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.