I just tested this module and have found it working, if you use the following:

Test your Miele@Home acount:
https://www.miele.com/developer/swagger-ui/index.html

Get your client_ID and client_Secret here:
https://www.miele.com/f/com/en/register_api.aspx

Your UserName and password are the same you use to login to Miele@Home app

vg: ‘da-DK’, // default = ‘de-DE’, Choose the app Country
language: ‘en’, // default = ‘de’, Miele only support ‘de’ or ‘en’
showAlwaysAllDevices: true, // default = false , True show component even if it’s off

Language supported:
de - Deutsch
en - English

VG supported:
‘en-AU’ - Miele Australia
‘nl-BE’ - Miele België
‘en-CA’ - Miele Canada
‘es-CL’ - Miele Chile
‘hr-HR’ - Miele Croatia
‘cs-CZ’ - Miele Czechia
‘da-DK’ - Miele Danmark
‘de-DE’ - Miele Deutschland
‘et-EE’ - Miele Eesti
‘es-ES’ - Miele España
‘fr-FR’ - Miele France
‘ko-KR’ - Miele Hanguk
‘en-HK’ - Miele Hong Kong, China
‘en-IE’ - Miele Ireland
‘en-IL’ - Miele Israel
‘it-IT’ - Miele Italia
‘el-CY’ - Miele Kypros
‘lv-LV’ - Miele Latvija
‘lt-LT’ - Miele Lietuva
‘de-LU’ - Miele Luxemburg
‘hu-HU’ - Miele Magyarország
‘en-MY’ - Miele Malaysia
‘es-MX’ - Miele México
‘nl-NL’ - Miele Nederland
‘en-NZ’ - Miele New Zealand
‘ja-JP’ - Miele Nihon
‘no-NO’ - Miele Norge
‘pl-PL’ - Miele Polska
‘pt-PT’ - Miele Portugual
‘ro-RO’ - Miele România
‘de-CH’ - Miele Schweiz
‘en-SG’ - Miele Singapore
‘sl-SI’ - Miele Slovenia
‘sk-SK’ - Miele Slovensko
‘en-ZA’ - Miele South Africa
‘fi-FI’ - Miele Suomi
‘sv-SE’ - Miele Sverige
‘en-TH’ - Miele Thailand
‘tr-TR’ - Miele Türkiye
‘en-GB’ - Miele UK
‘en-US’ - Miele USA
‘en-AE’ - Miele United Arab Emirates
‘zh-CN’ - Miele Zhōngguó, dàlù
‘de-AT’ - Miele Österreich
‘el-GR’ - Miele Ελλάδα
‘ru-BY’ - Miele Беларуси
‘bg-BG’ - Miele България
‘ru-KZ’ - Miele Казахстан
‘ru-RU’ - Miele Россия
‘sr-RS’ - Miele Србија
‘uk-UA’ - Miele Україна

Working config:

		{
            disabled: false,
            module: "MMM-MieleAtHome",
            position: "top_right",
            classes: 'medium bright',
            config: {
                userName: "??@??.??", // Your email to Miele@Home app
                password: "??????", // Your password to Miele@Home app
                client_ID: "????", // Your client_ID you get from the link above
                client_Secret: "????", // Your client_Secret you get from the link above
                vg: 'da-DK', // Your country code from the list above
                language: 'en', // Language supported from list above
                showAlwaysAllDevices: true //always display component
			}
            },

@sdetweil Yes default calendar is ok,so it has to be CalendarEXT2 that has a problem, and it could be the ical.js from above that could help?

@mlcampbe said in Calendar timezone problems:

I’ve solved this problem by replacing the node-ical script that the default calendar modules uses with a fork of it.

I did some research and found that the default calendar module uses the node-ical modules to parse calendar data. I notice that it is based off of https://github.com/peterbraden/ical.js. I also found https://github.com/jens-maus/node-ical that is based off of the original peterbraden/ical.js. but seems to have been updated to use the npm package moment-timezone.

I did a drop in replacement and it seems to work:

cd modules/default/calendar/vendor
mv ical.js ical.js.orig
git clone https://github.com/jens-maus/node-ical
mv node-ical/ ical.js
cd ical.js
npm install

Restarted MM and now my timezones are showing up properly. So I made my own modules out of this so it won’t get overwritten by updates.

I have a problem with the google ical calendar format, its 1 hour off when its used in MMM-CalendarEXT2, but I think it has something to do with winter/summer time.
Can the quote fix this problem?

I can see in the folder " ~/MagicMirror/modules/MMM-CalendarExt2/node_modules " that there is a file called ical.js, but how to i update the file to the one in the qoute, so i can test if thats is the problem?

My pi has timezone to Europe / Copenhagen, and the calender entry is ok when i look at my phones calender and also ok on the google calender.

In 2021 I war running MagicMirror 2.16 with MMM-MyWastePickup and everything was working just fine.

Here i 2022 I updated MagicMirror to 2.18 and updated MMM-MyWastePickup.

I then updated the schedule_custom.csv with 2022 dates, and now it dosent work, it just says Loading. If i change dates in schedule_custom.csv to 2021 or 2023, then i says “no schdule”

Have anybody a clue what to do?
Is it something with MM 2.18?

Working, says “No Schdule”

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,01/02/21,0,1,0,0,0
Custom,01/07/21,0,1,0,0,0
Custom,01/12/21,1,0,1,0,1

Not Working, Says “Loading”

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,01/02/22,0,1,0,0,0
Custom,01/07/22,0,1,0,0,0
Custom,01/12/22,1,0,1,0,1

@florjanklancar

Take a look at MMM-CalendarWeek

It can dispaly events from google.

@tippon
I use MMM-FreeboxTV ( https://github.com/bugsounet/MMM-FreeboxTV )
It works with RTSP, so your camera has to support this.

@earlman
Tryed the new main.css

Stock i working, it should be “top_bar”.
Calender should be position: “bottom_bar”, under travle time, but bottom_bar is over bottom_left, bottom_center and bottom_right

@earlman

As you can see, the top_bar and bottom_bar dosent work.

The calender should be in the bottom_bar and the stock should be in the top_bar

@bravooscar @jalibu

pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ git fetch
pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ git checkout feat/useYahoo
Branch 'feat/useYahoo' set up to track remote branch 'feat/useYahoo' from 'origin'.
Switched to a new branch 'feat/useYahoo'
pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ npm i
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
added 262 packages from 267 contributors and audited 263 packages in 33.609s

35 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

I removed MMM-Jast folder, and did a clean install of MMM-Jast.
Then I did this

git fetch
git checkout feat/useYahoo
npm i

Everythink works now, and also one of my stocks that was not available before.

Good work!
Think is should be made as master, maby make a config option, so its possible to cange from Yahoo to the other one.

@jalibu

pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ git fetch
From https://github.com/jalibu/MMM-Jast
   1cd91dc..c18758f  master        -> origin/master
 * [new branch]      feat/useYahoo -> origin/feat/useYahoo
 * [new tag]         v1.1.0        -> v1.1.0
 * [new tag]         v1.2.0        -> v1.2.0
pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ git checkout feat/useYahoo
error: Your local changes to the following files would be overwritten by checkout:
	MMM-Jast.css
	MMM-Jast.js
Please commit your changes or stash them before you switch branches.
Aborting
pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ npm i

> magicmirror@2.14.0 install /home/pi/MagicMirror
> echo "Installing vendor files ...
" && cd vendor && npm install --loglevel=error

Installing vendor files ...

audited 24 packages in 1.694s

It looks like there is a error when using “git checkout feat/useYahoo”.

Now the alert message on MM says there is a update for MMM-Jast

@jalibu

I will test it later today, but I need to know of this is this a upgrade or is it a new install.

I use the originale MMM-JaST, should this be removed before a new install?