You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get this when running or starting the container:
19:31:07.936 INFO - Info enabled
19:31:07.940 INFO - Connecting MQTT client
19:31:08.510 INFO - MQTT client connected
Exception in thread "OkHttp Dispatcher" java.lang.NullPointerException
at de.rnd7.mqtttelegram.telegram.BotService.handleUpdate(BotService.java:59)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at de.rnd7.mqtttelegram.telegram.BotService.lambda$start$1(BotService.java:50)
at com.pengrad.telegrambot.impl.UpdatesHandler$1.onResponse(UpdatesHandler.java:73)
at com.pengrad.telegrambot.impl.UpdatesHandler$1.onResponse(UpdatesHandler.java:49)
at com.pengrad.telegrambot.impl.TelegramBotClient$1.onResponse(TelegramBotClient.java:52)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Wireshark trace shows that connection to Telegram API is established. I only see one packet application data from the container to Telegram and afterwards one from Telegram to the container. I used the config.json and filled in my own data.
Using latest build of mqtt-to-telegram with Docker on Ubuntu 22.04 LTS.
The text was updated successfully, but these errors were encountered:
I get this when running or starting the container:
Wireshark trace shows that connection to Telegram API is established. I only see one packet application data from the container to Telegram and afterwards one from Telegram to the container. I used the config.json and filled in my own data.
Using latest build of mqtt-to-telegram with Docker on Ubuntu 22.04 LTS.
The text was updated successfully, but these errors were encountered: