Tado is no longer displayed after update 2.28

[sdetweil]

@JoeFranz let’s look this way

pm2 stop all
cd ~/MagicMirror
npm start

[JoeFranz]

@sdetweil The same, Tado is not displayed :-(

[sdetweil]

@JoeFranz but what are the messages from npm start

[JoeFranz]

@sdetweil

pi@raspberrypi:~/MagicMirror $ npm start

> magicmirror@2.28.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

[2024-07-01 12:56:47.307] [LOG]   Starting MagicMirror: v2.28.0 
[2024-07-01 12:56:47.381] [LOG]   Loading config ... 
[2024-07-01 12:56:47.387] [LOG]   config template file not exists, no envsubst 
[2024-07-01 12:56:51.040] [LOG]   ====================== Starting node_helper for module [MMM-OpenWeatherMapForecast] 
[2024-07-01 12:56:51.056] [LOG]   [Tools] MMM-Tools Version: 2.1.7 
[2024-07-01 12:56:51.066] [LOG]   Starting node_helper for module: MMM-PhilipsHue 
[2602:0701/125724.577098:ERROR:atom_cache.cc(229)] Add WM_CHANGE_STATE to kAtomsToCache

[sdetweil]

@JoeFranz well that’s incredibly short

[JoeFranz]

@sdetweil But everything else works, except Tado

[JoeFranz]

@sdetweil I have now reinstalled Tado and am getting these messages

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.0: Glob versions prior to v9 are no longer supported

added 100 packages, and audited 101 packages in 33s

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

2 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

[sdetweil]

@JoeFranz noise, ignore
does it work now?

[JoeFranz]

@sdetweil No, it is not displayed

[JoeFranz]

@sdetweil
There was probably an error in the config regarding the position of the modules. Two modules had “top_right” and Tado had “right”. With “bottom_right” for Tado it is now displayed again. Strange that it worked like this before the update…