Sounds like the refresh token lifetime got reduced.
Probably the module should only take credentials and get the token itself. Unfortunately, I currently don’t have the time to look into it.

@sil3ntstorm you get the token now directly from the developer portal, see https://github.com/CFenner/MMM-Netatmo?tab=readme-ov-file#connection-to-netatmo-service-api

@Laz great that it works again. Sorry that is took so long. What about the RU translations, everything good?
Will try to find some time for the transformation.

@cgillinger I merged a PR from @ottolote to replace the sync-fetch. Please try if that fixes the issue for you. It work for me now, but also did before that change using mm v2.26.

@tommys great that you solved the issue! Would you mind contributing that back into the repository?

@timogden I’ve created a module to extract the config so you don’t need to maintain your own whole MM fork: https://forum.magicmirror.builders/topic/16224/mmm-personalconfig-persist-personal-config-to-github/1

A way to achieve what you want could be to create your own copy of personal config with your mirror config. Then make a clone of if for your friend where you do the specific changes. Changes to your repo then can be pulled to the other one via Pull requests.
In combination with MMM-UpdateNotification with can pull updates automatically, your friend won’t need to do anything.

@bugsounet thanks, i have no issues anymore.

@fab the waf dropped to low that I teared down the mirror for 3 years ;)
Now I reinstalled it and it’s running for a week now.

@sdetweil thanks, didn’t check that! Will do so.

Could you add your module to the modules list: https://github.com/MichMich/MagicMirror/wiki/3rd-Party-Modules

Description:

This module is meant to host your personal mirror configuration and persist it to GitHub to easily restore your config if it’s lost and to have a change history (config-as-code).

The linked repository is a template repository that you can use to create your own copy. Clone your personal copy to your mirror.

The module as of now just provides the ability to link your config files (config.js, custom.css) to the right locations. Thanks to updateNotification module, changes to the config repository are highlighted on the mirror.

Future features:

• update config via telegram command (chat-ops)
• auto update config & restart on changes (git-ops)

Screenshots:

This module provides no visualization.

Configuration:

{
  module: "MMM-PersonalConfig",
  position: "top_left",
},

Download:

[card:https://github.com/CFenner/MMM-PersonalConfig-Template]

@bugsounet said in Automatic Updates:

@cliff365 I have done a. Module for this ;)

Would be nice to have repository specific auto update functionality in the default module.

@fab I have (or had in the past) the issue that my wifi device hangs up after some amount for uptime (maybe a week). Never found the reason for that though.

@bugsounet Just to clarify, I think we don’t need multiple bot instances, just reuse one bot instance from multiple UI instances.

I files a PR for prevent re-initialization if there is already a bot.

Maybe the node_helper should only be initialized for the first time:

https://github.com/bugsounet/MMM-TelegramBot/blob/d569c7ee9d22c7ff7618b67101cf68ad7b93106e/node_helper.js#L424

I’m new to the Telegram module. I installed it and it works so far. But whens I’m developing on my modules, I typically run the Mirror UI on my laptop. This gives me than the following error:

1|mm  | [TELBOT] Error 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running

Also the Telegram chat says that I must not run multiple bot instance.

How can I overcome this? Shouldn’t the bot be running on the mirror and not in my browser?

I’m on Safari / Mac

The styles in the forum are broken for me. I already resetter cache & cookies. Anything I’m missing?

Seems do be the magic mirror config :( I need to specify the ip in the config (“address”) to be accessible.

originally Hamburg, now Heidelberg, Germany

@blebbens, please make sure that the “:” are not part of parameters!

I just added a description how to do this with curl, this is a bit easier.