CalendarEXT2 and Calendar (default)

sdetweil

@ankonaskiff17 I don’t edit in the ssh window. I use a file system connection over ssh to edit the file with the local system editor. Best of both worlds.

sdetweil

@ankonaskiff17 and if u edit the module source files, you get what u deserve when updates come…

BKeyport

@ankonaskiff17 and I can’t hate either SSH or VNC. They both have their uses. I use a vertical mirror, so SSH is far more useful to me than VNC, but they both are useful.

I’m the kind of person that sets up SAMBA and shares the entire Pi drive over to Windows so I can edit directly, then use MMM-Remote-Control to restart my mirror when needed. 🤣

ankonaskiff17

Do updates load to my machine without me knowing? If they do, you’re right, that will be a problem.
If they are announced and I choose then I just copy the whole existing MM complex to sd card.
That way if update is bad I can revert. I imagine most end users are like me. They build a display, configure with a little tweaking and then rarely update,
I have two Pi’s running ADSB receivers and the underlying Raspian OS are several years since I’ve done apt update on either SSH’ed in to one just now. 2017

sdetweil

@ankonaskiff17 mm gets an update once every 3 months. Next jan 1.

I’ve spent most of the last quarter fixing the calendar module. Things u might want to update

ankonaskiff17

I’m going to move everything over to config.js but it would be nice if the sample config file that people copy paste contained all the configurable items.
If there is a big list in the module code like this sample, can I just copy it in one big block, paste appropriately in config.js, change default to config and bracket appropriately and plug in my values and they’ll override the defaults lines in xyz.js even if they have values plugged in already.
So that this sample config directly below becomes more like the second block?

 modules: [
        {
            "module": "MMM-WeatherChart",
            "position": "top_right",
            **"config":** {
                "apiKey": "xxxx",
                "dataNum": 12,
                "dataType": "hourly",
                "height": "500px",
                "width": "800px",
                "lat": 35.571337,
                "lon": 139.633989,
                "units": "metric",
            }
        },

 defaults: {
        updateInterval: 10 * 60 * 1000,
        retryDelay: 5000,
        apiBase: "https://api.openweathermap.org/data/",
        apiVersion: "2.5",
        apiEndpoint: "onecall",
        apiKey: "",
        lat: "",
        lon: "",
        units: "standard",
        lang: "en",
        chartjsVersion: "2.9.3",
        chartjsDatalablesVersion: "0.7.0",
        height: "300px",
        width: "500px",
        fontSize: 16,
        dataNum: 24,
        timeOffsetHours: 0,
        title: "Weather Forecast",
        iconURLBase: "https://openweathermap.org/img/wn/",
        dataType: "hourly",
        nightBorderDash: [5, 1],
        showIcon: false,
        showRain: false,
        color: 'rgba(255, 255, 255, 1)',
        backgroundColor: 'rgba(0, 0, 0, 0)',
        fillColor: 'rgba(255, 255, 255, 0.1)',
        dailyLabel: 'date',
        hourFormat: "24h"
    },

Alvinger

@ankonaskiff17 In most cases the default values are set so that you do not need to change more than a few values to adjust to your needs. It makes no sense copying the entire config just to set the values to the default ones. That said, yes, you can copy the default block and change it to “config”, just remember to set the other module options appropriately.

@sdetweil has put significant effort into the calendar module and done a great job of fixing all the quirks so expect the default calendar module to be really great in the next MM version! Just be sure to move all your config stuff to config.js so you can upgrade without issues.