adapter stopped working

daniel-lo commented 3 weeks ago

Hi all, I just noticed that my telegram adapter has stopped working. I have a bot that was used successfully for quite a long time but not anymore. I am not aware of any change that might have caused this. Could anyone point me into a direction how to trouble-shoot this?

BR

mcm1957 commented 3 weeks ago

Please ask at out Forum (https://forum.iobroker.net). You might get a solution faster there.

If there is some bug please add missing information:

A detailed info what going wrong. Any error Messages? Adapter green / red ? ...

Versions of

adapter
js-controller
node
o/s

And attach a log with level DEBUG

daniel-lo commented 3 weeks ago

Admin 7.1.5 Nodejs: v20.18.0 js-controller: 6.0.11 Telegram Adapter: 3.9.0 Instance-Status: green (all green)

used "response"-object to send a message ... no log (debug) and .. of course .. no message

This is all I get when I restart the instance:

daniel-lo commented 3 weeks ago

@mcm1957 I'd classify this as bug .. but not sure .. information added above.

mcm1957 commented 3 weeks ago

I still recommend to discuss this issue at the forum - you will get responses from more users there. The above log is most likely no DEBUG log. There is no indication that you wrote anything to any state logged. Please set instance to debug level and reproduce the problem.

How do you write data to responce state? Is ack set to false?

daniel-lo commented 3 weeks ago

Yes, ack is unchecked .. but I tried it checked too .. no change. I will try to make a more extensive log and I also started a forum thread. Maybe I should uninstall and reinstall the adapter?!

daniel-lo commented 3 weeks ago

You were correct "debug" didn't stick .. but typing something via "response" still doesn't trigger anything. I already tried renewing all the objects.

telegram.0 | 2024-11-05 07:23:33.820 | debug | getMe: {"id":765455045,"is_bot":true,"first_name":"ringbot","username":"ring53bot","can_join_groups":true,"can_read_all_group_messages":false,"supports_inline_queries":false,"can_connect_to_business":false,"has_main_web_app":false} -- | -- | -- | -- telegram.0 | 2024-11-05 07:23:33.596 | debug | Start polling with: 300(number) ms interval telegram.0 | 2024-11-05 07:23:33.390 | info | starting. Version 3.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.18.0, js-controller: 6.0.11 telegram.0 | 2024-11-05 07:23:32.963 | debug | Plugin sentry Initialize Plugin (enabled=true) telegram.0 | 2024-11-05 07:23:32.928 | debug | States connected to redis: 127.0.0.1:9000 telegram.0 | 2024-11-05 07:23:32.869 | debug | States create User PubSub Client telegram.0 | 2024-11-05 07:23:32.868 | debug | States create System PubSub Client telegram.0 | 2024-11-05 07:23:32.857 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 telegram.0 | 2024-11-05 07:23:32.833 | debug | Objects connected to redis: 127.0.0.1:9001 telegram.0 | 2024-11-05 07:23:32.826 | debug | Objects client initialize lua scripts telegram.0 | 2024-11-05 07:23:32.788 | debug | Objects create User PubSub Client telegram.0 | 2024-11-05 07:23:32.787 | debug | Objects create System PubSub Client telegram.0 | 2024-11-05 07:23:32.785 | debug | Objects client ready ... initialize now telegram.0 | 2024-11-05 07:23:32.755 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001 telegram.0 | 2024-11-05 07:23:27.076 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason telegram.0 | 2024-11-05 07:23:27.074 | info | terminating telegram.0 | 2024-11-05 07:23:26.572 | info | Got terminate signal TERMINATE_YOURSELF

daniel-lo commented 3 weeks ago

As I mentioned .. I didn't change anything .. these settings worked. And I know the bot works because my n8n instance provides me with messages.

grafik grafik