Telegram instance loses token about iobroker.telegram HOT 13 CLOSED

3.6.0 is available at latest repository.
Github install is N̈OT recommended - besides thst github version is 3.6.0++.

Please Test with version 3.6.0 available at latest repository.

from iobroker.telegram.

3.6.0 is available at LATEST repository.

• Switch to latest / beta repository
• press search for updates
• update to current lates version (which is 3.6.0)
• switch back to stable repository

from iobroker.telegram.

Current telegram release is 3.6.0.
Please check whether this problem still exists with current version of adapter.

In addtion please add missing version information

adapter: 3.3.2 -> to be testets with 3.6.0
js-controller:
admin:
node: 18.19.0

from iobroker.telegram.

Stable version of the telegram adapter in github is still 3.3.2. therefore i think it is the reason 3.6.0 is not available in iobroker yet.
Make it pls. to stable first.
Your question "In addtion please add missing version Information", You mean version of what?

from iobroker.telegram.

Sorry i see it now first:
js-controller: 5.0.19
admin: 6.13.16

from iobroker.telegram.

3.6.0 is not available in iobroker yet:

How can I test with 3.6.0?

from iobroker.telegram.

3.6.0 loses Token also, no changes

from iobroker.telegram.

Please check the ioBroker log for any issues like DB not able to write files or such. because this should never happen and means that your configuration gets not stored.
Is this only happening when restarting adapter? Or is whole js.controller restarted?

Please enable expert mode in admin, then go Objects -> system.adapter.telegram.0 and use the pencil icon on right to see the instance config. When you see the error copy the json. check for "common.token".
Then enter the token in admin panel and save, adapter should restart.
check the json again- token now in?
restart telegram? working? if not check object again
restart js-controller - check json again

from iobroker.telegram.

Under system.adapter.telegram.0 is token available (encrypted), but not "commn.token"(?):

"native": { "server": "false", "port": "8443",. ... "answerTimeoutSec": 60, "token": "$/aes-192-cbc:fe3f6ae85b46735e8c158e4a5a183580:1b9ee6dab9d4b6c5506a880462d10a6b11aa58071d0dbb2ea4cababbecfc06b39e4d079037dfdf5a0bad81d95b1eee10" },

The token is in the instance settings on the morning after router-restart in the night empty again (iob will be not restartet).
Log:

• 2024-06-26 05:59:40.935 - �[32minfo�[39m: host.iobroker instance system.adapter.telegram.0 started with pid 26444
  2024-06-26 05:59:42.506 - �[32minfo�[39m: hm-rpc.0 (26405) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.19.0, js-controller: 5.0.19
  2024-06-26 05:59:43.050 - �[32minfo�[39m: hm-rpc.0 (26405) xmlrpc server is trying to listen on 192.168.178.30:2001
  2024-06-26 05:59:43.056 - �[32minfo�[39m: hm-rpc.0 (26405) xmlrpc client is trying to connect to 192.168.178.208:2001/ with ["http://192.168.178.30:2001","iobroker:hm-rpc.0:f450d720733ca0e751df7aaee8207549"]
  2024-06-26 05:59:43.186 - �[32minfo�[39m: hm-rpc.0 (26405) xmlrpc <- system.listMethods ["iobroker:hm-rpc.0:f450d720733ca0e751df7aaee8207549"]
  2024-06-26 05:59:43.204 - �[32minfo�[39m: hm-rpc.0 (26405) xmlrpc <- listDevices ["iobroker:hm-rpc.0:f450d720733ca0e751df7aaee8207549"]
  2024-06-26 05:59:43.327 - �[32minfo�[39m: hm-rpc.0 (26405) xmlrpc -> 52 devices
  2024-06-26 05:59:43.359 - �[32minfo�[39m: hm-rpc.0 (26405) Connected
  2024-06-26 05:59:47.245 - �[32minfo�[39m: alexa2.0 (26429) starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.19.0, js-controller: 5.0.19
  2024-06-26 05:59:47.326 - �[32minfo�[39m: alexa2.0 (26429) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
  2024-06-26 05:59:48.398 - �[32minfo�[39m: telegram.0 (26444) starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.19.0, js-controller: 5.0.19
  2024-06-26 05:59:48.565 - �[31merror�[39m: telegram.0 (26444) Token is not set!

But restarting the instance manually causes no errors.

For me is not clear where I can see the error copy the json - in log is nothing about.

By the way: iobroker ist a docker container (see my first post above) - but other adapter keeps their settings.

from iobroker.telegram.

Ok. instance parameters are store at local. So this is OK.
Does this entry exist when the problem occures too or is it removed / changed?

And if I read this correctly:

• restarting the telegram instance works and there is no message about an unset token
• the complete ioBroker instance is not restarted

So what restart do you refer to when you wite: '"telegram" status is every day/by restart warning' ?
Guess you refer to a restart of your router. Please confirm.
Is the token entry at the instance object empty or unchanged after the router restart?

from iobroker.telegram.

I referred to a restart of my router. The token entry at the instance object empty at the morning after router and telegram restart.
I've checked without telegram restart in the night is everything ok - so was last night.
I'll check the logs of few next days and reopen the issue if wrong again.

from iobroker.telegram.

@marian-t-web-de The token is a protected attribute.

Do you start/stop/restart the instance automatically by using setObject?

from iobroker.telegram.

Yes, I've forgotten to replace it with extendObject() at one place.
This issue can therefore be closed, thanks for Your help.

from iobroker.telegram.