Telegram bot issues

Tags: #<Tag:0x00007efec5a9d0b0> #<Tag:0x00007efec5a9cfe8>

I’m having the following issues at the minute with the telegram action. My log looks like this:

2016-03-28 12:45:51 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Doorbell_bot loaded from config file
2016-03-28 12:45:51 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Alarm_bot loaded from config file
2016-03-28 13:27:15 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Doorbell_bot loaded from config file
2016-03-28 13:27:15 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Alarm_bot loaded from config file
2016-03-28 22:51:45 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Doorbell_bot loaded from config file
2016-03-28 22:51:45 INFO o.o.a.t.i.TelegramActionService[:67]- Bot Alarm_bot loaded from config file
2016-03-28 22:52:08 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-28 22:52:37 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-28 22:52:52 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-29 05:49:06 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-29 05:49:31 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-29 05:49:36 ERROR o.o.a.t.internal.Telegram[:74]- Bot ‘Alarm_bot’ not defined, action skipped
2016-03-29 08:19:37 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 08:19:37 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file
2016-03-29 08:32:51 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 08:32:51 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file
2016-03-29 09:58:33 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 09:58:33 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file
2016-03-29 10:03:48 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 10:04:32 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 10:05:57 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 10:13:37 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 10:14:24 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 11:17:26 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 11:25:20 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 13:52:35 ERROR o.o.a.t.internal.Telegram[:175]- Method failed: HTTP/1.1 401 Unauthorized
2016-03-29 14:30:22 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 14:30:22 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file
2016-03-29 14:34:01 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 14:34:01 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file
2016-03-29 15:24:21 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Doorbell_bot loaded from config file
2016-03-29 15:24:21 INFO o.o.a.t.i.TelegramActionService[:69]- Bot Alarm_bot loaded from config file

I’m using the 1.8.2 binding, I orinially had both that and the 1.9.0 snapshot version, but I’ve renamed it to “org.openhab.action.telegram-1.9.0-SNAPSHOT.bkup” which I’m guessing will disable it.