Potential conflict between MMM-TelegramBOT and MMM-UpdateNotification
-
I have successfully installed the MMM-TelegramBOT, entered the admin chat and confirmed it reacts to the commands. After that I installed the MMM-UpdateNotification. Then I run /update command and the only module MMM-NewPIR was updated. But in the Telegram I got several warning messages, please see below. What it could mean? How to make sure everything is working without issues?
-
just because you have 2 MMM-TelegramBot instence launched.
how can happen ?
- MMM-RemoteControl can be the cause
- launch another instence of MagicMirror (don’t use your browser you see what happen in the mirror app), use VNC embed
in all case MMM-UpdateNotification is not the cause
Note: Maybe you have not speciced the installation type
in
update: {}
you can see this partjust adjust with you actual config (usePM2,PM2Name, etc, etc)
-
Hi, I don’t have MMM-RemoteControl.
I also checked the update: {} part, and changed it to PM2 (because I use it) and disabled logToConsole.
After applying those changes I restarted the MagicMirror process, but after a while got the same warning in Telegram that this instance would be stopped.Than I restarted the whole Raspberry Pi and after that got a welcome message in Telegram and no errors so far.
Right after that I got also a message in Telegram that MMM-UpdateNotification v1.2.2 is now initialized! and I noticed that no update information was showing up in chat (what was the case before changing to PM2 in the configuration)
So I think that solved the issue with running two instances. Thank you!
-
@bugsounet my telegram bot not getting internet
[07.06.2021 18:49.45.203] [LOG] [TELBOT] Error EFATAL No internet ?
[07.06.2021 18:49.45.204] [LOG] [TELBOT] stopPolling and waiting 1 min before retry… -
@arora1mayank : stop whining everywhere … it becomes painful to read the same thing everywhere
-
Moved from by
bugsounet