Solved Migrate from MMM-TelegramBot to EXT-TelegramBot
-
Hi, this error is related to
EXT-UpdateNotification
Please verify for defaultCommand:
it must be:defaultCommand: "git reset --hard && git pull && npm install",
I think, you have configure this:
defaultCommand: "git --reset hard && git pull && npm install",
-
Yes the command is like the second one you have reported (with the “–” before “reset”), but I didn’t change anything… and until now it automatically upgrade other modules, even this morning just before the error with telegrambot.
-
So… ?
what can I do for you, If you don’t want to change the
defaultCommand
ofEXT-UpdateNoyification
?MMM and EXT have not the same command to update
that why
defaultCommand
exist- correct the feature for MMM modules
- update
- I will never install a module/plugin or modify a config without interact confirmation of users
-
Ok thank you.
Should I update and keep MMM or migrate to EXT?How to migrate from MMM to EXT?
-
Now I got this error:
[08.03.2023 21:35.56.805] [LOG] [UN] [8/11] Scan: MMM-TelegramBot
[08.03.2023 21:35.56.809] [LOG] [UN] Scan Infos: {
module: ‘MMM-TelegramBot’,
behind: 7,
current: ‘master’,
tracking: ‘origin/master’
}
[08.03.2023 21:35.56.819] [LOG] [NPM] Found: 0/10 @bugsounet library [EXT-Alert]
[08.03.2023 21:35.56.827] [LOG] [NPM] Found: 1/10 @bugsounet library [Gateway]
[08.03.2023 21:35.56.855] [LOG] [NPM] Found: 3/10 @bugsounet library [MMM-GoogleAssistant]
[08.03.2023 21:35.56.877] [LOG] [NPM] Found: 3/10 @bugsounet library [EXT-Detector]
[08.03.2023 21:35.56.893] [LOG] [NPM] Found: 0/10 @bugsounet library [EXT-Pir]
[08.03.2023 21:35.56.897] [LOG] [NPM] Found: 0/10 @bugsounet library [EXT-Screen]
[08.03.2023 21:35.56.903] [LOG] [NPM] Found: 0/10 @bugsounet library [EXT-UpdateNotification]
[08.03.2023 21:35.56.908] [LOG] [NPM] Found: 0/10 @bugsounet library [MMM-TelegramBot]
[08.03.2023 21:35.56.914] [LOG] [NPM] Found: 0/10 @bugsounet library [EXT-Governor]
[08.03.2023 21:35.56.924] [LOG] [NPM] Found: 0/10 @bugsounet library [MMM-Tools]
[08.03.2023 21:35.58.416] [ERROR] [UN] exec error: Error: Command failed: git reset --hard && git pull && npm install
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Committer identity unknown*** Please tell me who you are.
Run
git config --global user.email “you@example.com”
git config --global user.name “Your Name”to set your account’s default identity.
Omit --global to set the identity only in this repository.fatal: unable to auto-detect email address (got ‘pi@magicmirror.(none)’)
-
you have this error just because some module are in EOL. so your git program don’t know what can do
-
I noticed (on my setup) that EXT-TelegramBot is not listed in the plugin section on the gateway (V2.2.5). Install via Terminal is required.
-
@bugsounet said in Migrate from MMM-TelegramBot to EXT-TelegramBot:
you have this error just because some module are in EOL. so your git program don’t know what can do
Ok, MMM-TelegramBot I believe is in EOL. So my first question comes back: How should I migrate to EXT? Should I install EXT, maybe copy configuration and remove MMM?
-
Can you read this part of wiki ?
I think it’s really not difficult to understand …
- just uninstall, disable or delete
MMM-TelegramBot
- install `EXT-TelegramBot and compare each configuration (old and new configuration) and replace all needed values on the new plugin
- create new config from wiki (
EXT-TeklegramBot
) - delete, disable or delete old config (
MMM-TelegramBot
)
I really don’t understand why you take your head over very simple things
- just uninstall, disable or delete
-
Thank you for clarifying all the steps.
Followed those and migrated successfully! -